openstack-capacitylisted

# OpenStack Capacity Planning -- Resource Management Operations Capacity planning is proactive operations -- the discipline of preventing outages before they happen by ensuring the cloud has sufficient resources to serve its users. A reactive operator discovers capacity problems when `openstack server create` returns "No valid host found." A proactive operator sees the trend weeks before and plans accordingly. The three capacity domains are **compute** (vCPU, RAM, local disk), **storage** (volume GB, snapshots, images, objects), and **network** (floating IPs, ports, subnets, bandwidth). Each domain has its own exhaustion symptoms, its own metrics, and its own expansion procedures. Allocation ratios create overcommit flexibility -- a host with 16 physical cores and a 4:1 CPU allocation ratio offers 64 vCPUs. This works because most workloads are idle most of the time. The art of capacity planning is setting ratios high enough to maximize density but low enough that contention does not degrade performance. This skill maps to NASA SE Phase E sustainment and resource management. In NASA terms, capacity planning is the operational activity that ensures the system continues to meet its Measures of Performance (MOPs) throughout its operational life. ## Deploy ### Capacity Management Tooling **Placement service** -- the authoritative source for resource inventory: ```bash # List all resource providers (one per compute node) openstack resource provider list # Show resource in