Hosting

Entry: /hosting. Hosting owns compute platforms, Hosts, clusters, pools, Service Environments, workloads and recorded placement. Start with the correct Group, CPU/memory capacity and responsible Team. You need the relevant management permission; optional Asset or other peer references require authorized, compatible owner records.

Register a platform and Host

1. Open Infrastructure → Platforms and choose Register Platform. Record the platform's name, vendor and version.
2. Open Hosts and choose Register Host. Select the platform, enter the Host name and optional management endpoint, and record CPU capacity and memory in MiB.
3. Review the saved Host and its lifecycle. Use its Settings to apply a supported state change when appropriate.
4. If you need clusters or pools, create them under Clusters & pools, add eligible Hosts and set the pool's CPU and memory limits.

Place or move a workload

1. Open Workloads → Service environments and create the environment with its name, environment class and responsible Team.
2. Open Workloads and choose Create Workload. Select its Service Environment and the intended eligible Host, cluster or pool, and enter vCPU, memory MiB and any applicable storage GiB.
3. Review available headroom and submit. Verify the saved placement and capacity figures.
4. To move an existing record, use its Settings → Move Workload, review the destination and current version, then verify the resulting placement.

Link context and check observations

1. Use the permitted Host or Workload reference action to select an existing compatible Asset or other supported resource. Do not create a second identity for the same equipment merely to fill a selector.
2. Review the authorized links in Related resources and capacity evidence in Capacity & reviews.
3. Where inventory ping is configured, use the Host's Settings → Monitoring to choose Managed or Unmanaged and inspect its observation time separately from lifecycle.

Blockers and limits: insufficient capacity, incompatible platform/pool membership, retired subjects, stale versions or inaccessible references can prevent placement. The interface's selected state/retirement operations accept up to 100 records and execute individual commands with per-record outcomes; retry only failed items after review. A Hosting record change does not promise that a hypervisor deployed or migrated a real virtual machine. Workloads do not acquire an inferred physical location or ping address, and an old observation is not proof of current availability.