INTERVIEW PREPARATION
OpenStack Question & Answer Bank
All 50 questions from the supplied senior interview guide, grouped by module.
MODULE B · Q11–Q18
Compute (Nova) & Virtualization
Q11. What is Nova and what is its primary function?
Nova is OpenStack's Compute service. It manages instance lifecycle: scheduling, building, starting, stopping, rebooting, resizing, migrating and deleting. Nova coordinates with Placement for allocation, Glance for images, Neutron for networking, Cinder for volumes and Keystone for identity. The VM runs on a hypervisor, commonly KVM/QEMU. Nova orchestrates; it is not the hypervisor.
Q12. What is a Hypervisor and which ones does OpenStack natively support?
A hypervisor creates and runs VMs while sharing physical CPU, memory, storage and networking. KVM/QEMU is a common production choice with Nova. Other drivers and integrations have included VMware vSphere, Xen-based technologies and Hyper-V, depending on release and driver support. Nova manages lifecycle and scheduling; the hypervisor runs the guest. Verify support for the exact release rather than assuming every historical driver remains supported.
Q13. Explain the concept and architectural purpose of "Cells" in OpenStack Nova.
Cells v2 divide a large Nova deployment into logical groups of compute hosts and associated services/databases. This supports horizontal scaling, distribution of database and service load, and isolation. A typical design has an API-level layer and one or more compute cells. The API layer routes requests and tracks instance mappings; cell services manage instances in their cell. Cells are not availability zones, host aggregates or projects.
Q14. What is the operational difference between pausing and suspending a VM instance?
Pausing freezes a running instance while its memory state remains resident on the compute host, so host memory remains consumed. It suits a short interruption. Suspending saves instance state to disk and stops active execution, allowing host memory to be reclaimed; resuming restores it. Exact behavior varies by backend. Neither is the same as a clean guest OS shutdown.
Q15. What are the CLI commands used to pause and unpause an instance?
Use `openstack server pause <server>` and `openstack server unpause <server>`. Inspect with `openstack server show <server>`. For suspension, use `openstack server suspend <server>` and `openstack server resume <server>`. Commands require suitable scope and permissions; verify resulting task and power state.
Q16. What is a "Flavor" in OpenStack?
A flavor is a predefined compute resource profile used when creating or resizing an instance. It typically specifies vCPU, RAM, root disk and ephemeral disk, with optional swap, metadata and extra specs. Extra specs can influence scheduling by requiring host capabilities or traits. A flavor describes requested resources; it does not guarantee capacity. Nova and Placement determine whether a suitable host is available.
Q17. What is the architectural role of nova-conductor?
Nova-conductor coordinates operations between Nova services and compute nodes and intermediates database access that nova-compute should not perform directly. This helps protect the database and centralize coordination. It participates in instance-management workflows. It does not run VMs and is not a hypervisor. Its precise responsibilities have evolved across releases.
Q18. What is the function of the nova-scheduler and how does it make placement decisions?
Nova-scheduler selects a suitable compute host. It evaluates resource requirements and constraints against capacity and host characteristics. Modern Nova uses Placement inventories, traits and allocations; the scheduler filters and weighs candidate hosts. Requirements can include vCPU, RAM, disk, availability zone, aggregate metadata and traits. Scheduling can fail if capacity is unavailable, constraints conflict or resource data is stale.