Live Migration in OpenStack Nova: Planning Zero‑Downtime VM Moves
Learn how OpenStack Nova live migration works, what prerequisites you need, and a step‑by‑step example to move a running VM with minimal downtime.
Loading…
ReadMeFeed / Community knowledge
#nova
Real questions. Useful conversations. Find the people who know your stack.
openstackDiagnosing OpenStack Nova Instance Launch Failures: Spawning/Error States
Step‑by‑step diagnostic guide for OpenStack Nova instances that stall in spawning or error state, with checks, fixes, and escalation rules.
Choosing Between PCI Passthrough Aliases and Placement-Based Scheduling for GPUs and FPGAs in OpenStack Nova
Decision guide comparing legacy PCI passthrough aliases vs. Placement-based scheduling with custom resource classes and traits for GPUs, FPGAs, and SmartNICs in OpenStack Nova. Includes concrete implementation steps, validation commands, and operational trade-offs.
OpenStack Live Migration: Choosing the Right Strategy for Zero-Downtime Maintenance
Live migration enables zero-downtime OpenStack maintenance, but only if you pick the right mode, storage layout, and CPU baseline. Here's how to decide and verify.
Live Migrating OpenStack Nova Instances Between Compute Hosts Using Shared Storage
Step-by-step guide for live migrating running OpenStack Nova instances between compute hosts using shared storage (Ceph, NFS, iSCSI). Covers prerequisites, migration commands, monitoring, verification, and recovery from common failures.
OpenStack Nova Live Migration: Minimal Architecture Note
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.
Live Migrating OpenStack VMs Without Downtime: A Practical Guide
Learn how to configure, execute, and verify OpenStack live migration of VM instances, including requirements, a step‑by‑step example, and key limitations.
Diagnosing OpenStack Nova CPU Pinning Launch Failures
A guide to diagnosing and fixing OpenStack Nova CPU pinning failures, including configuration checks for topology mismatches and cgroup errors.
Does a client-side timeout cancel in-flight work in OpenStack's Nova, Neutron, and Cinder?
OpenStack has no request-wide cancellation token or deadline propagation standard shared across its services. When a client times out or disconnects, work already accepted by Nova, Neutron, or Cinder generally continues server-side unless it is explicitly aborted through a service-specific action such as Nova's delete or force-delete. The open question is ho