Infrastructure Management
Sites, machines, MAAS, and provisioning workflows.
- Same layout your operators see in production
- Click to zoom in
- Works alongside the rest of Cloud Admin
Click the screenshot to open full size, zoom, and pan.
Core infrastructure
Infrastructure Management: sites, machines & provisioning workflows
Under Core Infrastructure → Infrastructure, operators model physical reality before Kubernetes namespaces matter: logical sites, enrolled machines, optional Ceph OSD candidate counts, and JSON-driven provisioning workflows, MAAS-ready when your metal fabric is wired in.
Product walkthrough
See it in Cloud Admin
Screens from the live product, with a short note on when you would open each view.
Metal-to-cluster discipline
Ground Kubernetes in real hardware state
Infrastructure Management prevents “cluster sprawl on imaginary machines” by forcing sites, IPs, and workflow payloads to agree before automation promotes builds into production namespaces.
Intent before kubectl
JSON workflows capture CPU/RAM envelopes and topology counts, easy to diff when finance asks why nodes doubled.
Shared vocabulary
Sites map neatly into MAAS regions so networking and facilities teams talk about the same coordinates.
Storage foresight
OSD candidate counts surface early. Operators stop guessing whether Ceph can absorb the next tenant burst.