HybridOps¶
HybridOps is a contract-driven automation platform for hybrid infrastructure. These docs cover the runtime, reference scenarios, design decisions, and supported runbooks.
Start Here¶
| If you want to... | Start here | What you get |
|---|---|---|
| Run the platform | Quickstart | Install the CLI, connect credentials, and execute a first module. |
| Understand what the platform does | Reference Scenarios | Outcome-led scenarios with architecture, operations, and supporting implementation detail. |
| Run a procedure | Runbooks | Reproducible operating paths with verification and rollback guidance. |
Execution Model¶
Four abstractions keep the runtime consistent across environments and providers:
- Module: Declares intent, inputs, constraints, probes, outputs, and credential requirements.
- Driver: Executes tools in isolated workdirs, captures redacted run records, and normalises outputs.
- Profile: Applies environment policy such as backend strategy, naming, timeouts, and tool versions.
- Pack: Supplies the implementation bundle a driver executes, without changing the contract seen by the caller.
Platform Scope¶
- On-prem: Proxmox networking, storage, compute, and VM lifecycle.
- Cloud: Azure and GCP landing zones, managed services, and recovery targets.
- Edge: Hetzner control surfaces, ingress lanes, and burst targets.
- Delivery: Terraform, Terragrunt, Ansible, Packer, GitHub Actions, Jenkins, and Argo CD.
- Observability: Prometheus, Grafana, and decision services for burst and recovery control.
- Data and recovery: PostgreSQL HA, backups, failover, failback, and managed standby patterns.
Repositories¶
HybridOps is published as a set of focused repositories:
| Repository | Role |
|---|---|
| HybridOps.Core | Open-source runtime: hyops CLI, modules, drivers, probes, and execution utilities. |
| HybridOps.Workloads | GitOps workload definitions reconciled by Argo CD across environments. |
License¶
Code: MIT-0 · Documentation and diagrams: CC BY 4.0