ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
Cloud & infrastructure · #openstack
A concise architecture note for OpenStack Nova live migration: requirements, minimal two‑node design, trust boundaries, pre‑migration checks, typical failure modes, and conditions that force a design change.
Learn how to configure, execute, and verify OpenStack live migration of VM instances, including requirements, a step‑by‑step example, and key limitations.
Learn how to shelve an instance to shared storage, free its compute host, and later unshelve it safely, with verification steps and known limitations.
Learn how to implement SAML2 federated identity in OpenStack Keystone to allow external authentication without storing local passwords, including mapping rules and failure diagnostics.
A guide to diagnosing and fixing OpenStack Nova CPU pinning failures, including configuration checks for topology mismatches and cgroup errors.
For a low‑traffic workload the operator wants to minimize monthly expenses while retaining the ability to snapshot and recover instances. The decision hinges on whether to boot instances from the local ephemeral disk (boot‑from‑image) or from a Cinder volume (boot‑from‑volume). Boot‑from‑image avoids per‑GB volume charges and network attachment overhead, but
Operators need to trace a failed VM deployment across Nova, Neutron, and Cinder logs to pinpoint where the failure occurred. Two documented mechanisms are available: the oslo.middleware.RequestID middleware that injects a request identifier into each service’s log line, and the Telemetry event pipeline that captures versioned notifications containing a reque
Goal: Determine whether latency spikes observed under concurrent Nova API requests stem from contention in the shared oslo.db connection pool used by both Nova API and Placement service, and whether adjusting the database max_pool_size relative to the total number of API workers eliminates the spike. Constraints: The effect is documented for OpenStack releas
After issuing a nova delete command, the instance remains visible in openstack server list output for a period governed by the oslo.cache expiration time. Subsequent attempts to show the instance with openstack server show return an InstanceNotFound error, creating a mismatch between the cached list view and the actual state. The goal is to determine whether