Deployment Model
Fleet Manager is deployed as a hub plus one or more satellites.- The hub provides the API and the global control-plane view
- Each satellite is scoped to a site and runs workflow workers, agents, and site-local configuration
What A New Site Needs
A new site deployment typically requires:- an agreed deployment identifier such as
glo1orsta1 - Kubernetes clusters for the target environments
- devices and config context in NetBox
- 1Password vaults and service-account tokens
- OpenStack application credentials and IPA image configuration
- DHCP server access and restart controls
- SLURM connectivity for burn-in and validation workflows
Use These Pages
- Site Dependencies & External Systems for the prerequisite systems and ownership boundaries
- OpenStack Application Credentials for the required Ironic, Placement, and Nova access rules
- Deploy Fleet Manager at a New Site for the rollout sequence
- Site Validation for post-deployment checks
- PKI & Certificate Trust for hub/satellite trust setup