OSOpenStack Learning Academy
INTERVIEW PREPARATION

OpenStack Question & Answer Bank

All 50 questions from the supplied senior interview guide, grouped by module.

MODULE F · Q41–Q50

Advanced Operations & Troubleshooting

Q41. How do you assign a project/tenant to a user using the modern OpenStack CLI?
Access is normally granted by assigning a role to a user on a project. A typical command is `openstack role add --user <user> --project <project> <role>`. Verify with `openstack role assignment list --user <user> --project <project> --names`. The user, project and role must exist, and the administrator needs permission. This is more precise than saying a project is simply assigned to a user.
Q42. What is the difference between Live Migration and Cold Migration of an instance?
Live migration moves a running instance between compute hosts with very low intended interruption. It generally transfers or shares memory and execution state and requires compatible hosts, networking and storage. Cold migration moves an instance that is not running, usually requiring it to be stopped. It causes more downtime but has fewer live-state constraints. Requirements depend on hypervisor, storage, CPU compatibility and policy.
Q43. How do you generate or upload SSH key pairs to inject into an instance via CLI?
Generate a key locally with `ssh-keygen`, protect the private key and upload only the public key. Register an existing public key with `openstack keypair create --public-key <public-key-file> <keypair-name>`, or generate through the client with `openstack keypair create <keypair-name>`. Select it at server creation with `--key-name <keypair-name>`. The image must support injection, commonly through cloud-init, and network rules must permit SSH.
Q44. What is the function of the cloud-init utility inside an OpenStack instance image?
cloud-init initializes a newly launched guest. It reads metadata and user data and can create users, configure SSH keys, set hostnames, write files, install packages and run first-boot commands. OpenStack can provide metadata through the metadata service or config-drive. cloud-init runs inside the guest; Nova makes metadata available but does not perform all guest configuration itself. Behavior depends on image and datasource configuration.
Q45. If an instance is stuck in an ERROR state, what is your initial troubleshooting workflow?
Inspect `openstack server show <server>` for status, fault, task/power state, host and attached resources. Review Nova API, scheduler, conductor and compute logs. Determine whether failure occurred during scheduling, image retrieval, networking, storage attachment, hypervisor creation or guest boot. Check quotas, Placement capacity, image availability, Neutron port/security rules, Cinder volume and compute-host health. Preserve evidence before reset or deletion; recover only after identifying the failing layer.
Q46. What tool is commonly used to deploy production-ready, containerized OpenStack environments?
Kolla-Ansible is a commonly used project for deploying OpenStack services in containers using Ansible. It provides container images and automation for configuring and operating a containerized control plane. Operators define inventory and configuration, then use Ansible workflows to deploy and manage it. Other approaches include OpenStack-Ansible and vendor platforms. Selection depends on release support, architecture, requirements and team skills.
Q47. Explain the term "Overcommit Ratio" in OpenStack and why it is used.
An overcommit ratio allows a cloud to offer more virtual resources than physical capacity, assuming workloads will not all use their maximum allocation simultaneously. CPU overcommit is commonly expressed as vCPU capacity relative to physical CPU capacity; memory and disk policies may also use ratios or reserved capacity. It improves utilization but increases contention risk. Monitor workloads and tune ratios; excessive overcommit can cause poor performance or scheduling failures.
Q48. What is the role of the Placement API in modern OpenStack environments?
Placement tracks resource-provider inventories, traits, aggregates and allocations. Nova uses it to determine availability and record resources allocated to instances. Inventories include resources such as VCPU, MEMORY_MB and DISK_GB; traits describe capabilities. Placement supports accurate selection and accounting. It is distinct from nova-scheduler, which makes decisions using Placement data and configured filters/weighers.
Q49. How do you check the health status of all OpenStack services via the CLI?
No single CLI command proves every component is healthy. Start with `openstack service list` for registration and `openstack endpoint list` for endpoints. Use `openstack compute service list` for compute and `openstack network agent list` where Neutron agents are deployed. Then test APIs, inspect processes/logs and check databases, message queues and storage. In OVN deployments inspect OVN/OVS components too. Registered/enabled does not necessarily mean end-to-end operational.
Q50. What is the structural difference between an OpenStack "Public Endpoint" and an "Internal Endpoint"?
Keystone's catalog can publish different endpoint interfaces. A public endpoint is intended for client access from outside the internal service network; an internal endpoint is intended for access from the cloud's internal network. An admin endpoint may be provided for administrative use. These are catalog labels and URLs, not firewall rules. DNS, routing, TLS, proxies and access controls determine actual reachability.