Overview
Configure regions, zones, resource pools, and deployment targets, and map them to your real infrastructure. Topology is where you organize your physical infrastructure into regions and zones and monitor your nodes from a single console, keeping an up-to-date view of your hosts and their capacity, so your workloads always run where they should.
At its centre is a single, provider-agnostic idea of a location that every other service
references the same way, so the whole platform agrees on where a resource lives. Topology keeps
that picture current by discovering your qibdo clusters automatically: a cluster registers
the regions it provides and records itself on each one, administrators carve those regions into
zones and approve what discovery proposes, and the deployment targets are projected from your
fleet. Only an approved, active location can host a workload, which is what keeps placement
landing somewhere real and usable.
Core concepts
Section titled “Core concepts”- Location: the universal reference to a place. Every location has a kind, one of global, region, multi-region, or zone, and a status that says whether it can take new placements. A single read tells you both.
- Global: a single, always-available location that means “no particular place.” A resource that does not care where it lives defaults to global.
- Region: a geographic area that maps to a backing physical cluster. Regions are discovered automatically from the fleet rather than created by hand.
- Multi-region: an administrator-defined grouping of regions, for resources that should span more than one.
- Zone: a failure domain within a region, the concrete place a workload actually lands. Zones in the same region are expected to fail independently.
- Resource pool: a grouping of deployment targets within a zone, used for scheduling. Membership follows the hosts’ labels rather than a hand-kept list.
- Deployment target: an individual physical host within a zone, described by its CPU, memory, GPU, disks, network, and operating system.
- Lifecycle: every location other than global moves through pending approval, active, and disabled. Only an active location accepts new placements; placing onto a non-active one is refused.
Naming a location is the same everywhere: a service includes a location reference in its create request, omitting it to default to global, and the choice is fixed for the life of the resource. Topology’s own changes return an operation record that comes back already completed.