Placement Inventory & Allocation Reconcile Prompt
Audit and reconcile the OpenStack Placement service for resource-provider inventory drift, leaked/orphaned allocations, and incorrect allocation ratios that cause phantom 'full' hypervisors or scheduling failures.
- Target user
- OpenStack operators managing Nova/Placement capacity
- Difficulty
- Advanced
- Tools
- Claude, ChatGPT
The prompt
You are a senior OpenStack operator auditing the Placement service for inventory drift and leaked allocations that make hypervisors appear full when VMs have been deleted or migrated. Work in read-only/advisory mode: `placement` allocation deletes and inventory edits are destructive, so propose them with explicit safeguards. I will provide: - Per-provider inventory and usage: `openstack resource provider list`, `openstack resource provider inventory list <rp>`, and `openstack resource provider usage show <rp>` for the suspect hosts. - The set of allocations: `openstack resource provider allocation ... ` / `openstack allocation ... ` output, plus the live instance list on that host (`openstack server list --host <h> --all-projects`). - nova-compute logs and whether `nova-manage placement heal_allocations` / `audit` has been run. - The configured allocation ratios (cpu/ram/disk) and reserved values per provider. Your tasks: 1. **Compute the truth table** — for VCPU, MEMORY_MB, DISK_GB: total = inventory*ratio - reserved; used = sum of allocations; and compare against the actual live instances on the host. 2. **Find leaked allocations** — list allocation consumers (instance UUIDs) that have no corresponding live server; these are the orphans inflating usage. 3. **Detect inventory drift** — flag where reported inventory disagrees with the real hardware (e.g. after a RAM/CPU change the compute didn't re-report). 4. **Recommend the safe repair** — prefer `nova-manage placement heal_allocations` and `nova-manage placement audit` over manual allocation deletes; only delete a specific orphaned allocation when the consumer is provably gone. 5. **Validate ratios** — confirm allocation ratios/reserved match the operator's overcommit policy. Output: (a) per-resource truth table, (b) list of orphaned consumers with evidence, (c) ordered repair commands (heal/audit first), (d) verification step re-showing usage.
Run this prompt with AI
Test it, get an AI-improved version, or compare models — live in the Prompt Workspace. No copy-paste.
Related prompts
-
OpenStack Capacity Planning Prompt
Plan OpenStack capacity — CPU/RAM/disk oversubscription, growth modeling, hypervisor sizing, Cinder backend planning, network bandwidth.
-
Nova NoValidHost Scheduler Triage Prompt
Diagnose why nova-scheduler returns NoValidHost for a boot/migrate request by walking the filter chain, Placement allocation candidates, and host aggregate metadata to find which constraint eliminated every compute host.
-
Placement Allocation-Ratio and Inventory Mismatch Debug Prompt
Resolve cases where Placement inventory, allocation ratios, or reserved values disagree with nova.conf or actual host capacity, causing wrong capacity, NoValidHost, or surprise overcommit.
-
Nova Allocation Ratio & Overcommit Tuning Prompt
Helps you safely set per-host and per-aggregate CPU/RAM/disk allocation ratios in Nova so you maximize density without triggering OOM kills or noisy-neighbor problems.
More OpenStack prompts & error guides
Browse every OpenStack prompt and troubleshooting guide in one place.
Reading prompts? Get all 500 in one free PDF
500 battle-tested, copy-paste AI prompts engineered by a senior systems engineer — every one with fill-in placeholders and safety/back-out notes. Drop your email and it's yours.
- 500 prompts: Linux · Kubernetes · Terraform · OpenStack · GitLab · Docker · Monitoring · Incident Response
- Instant PDF download — yours free, forever
- Plus one practical AI-workflow email a week (no spam)
Single opt-in · unsubscribe anytime · no spam.