Galaxy Collections¶
HybridOps publishes four Ansible collections under the hybridops.* namespace. Each is versioned independently and designed to compose into end-to-end platform workflows via HybridOps.Core modules.
| Collection | Version | Purpose |
|---|---|---|
| hybridops.app | 0.1.3 | Jenkins, RKE2, NetBox, EVE-NG, and platform services |
| hybridops.common | 0.1.5 | Shared utilities: env guard, Docker, VyOS, observability, DNS |
| hybridops.helper | 0.1.3 | EVE-NG content lifecycle and NetBox seeding |
| hybridops.network | 0.1.0 | Linux WAN simulation (strongSwan + FRR) |
Install all¶
# collections/requirements.yml
collections:
- name: hybridops.app
version: ">=0.1.3"
- name: hybridops.common
version: ">=0.1.5"
- name: hybridops.helper
version: ">=0.1.3"
- name: hybridops.network
version: ">=0.1.0"
ansible-galaxy collection install -r collections/requirements.yml
HybridOps.Core manages collection installation via hyops setup ansible. Manual install is only needed for development or standalone role use.
Consumption model¶
Collections are building blocks, not vendored code. HybridOps.Core modules call roles via FQCN (e.g. hybridops.app.jenkins_controller), declare their inputs in spec.yml, and emit structured run records. Roles provide implementation; modules provide orchestration, guards, and evidence.