Overview
The Instances panel under Project → Compute → Instances is the primary interface for managing the full lifecycle of compute instances — from initial launch through day-to-day operations, scaling, and eventual termination.Prerequisites
memberrole or higher in the active project- At least one image available in the project (see Images)
- A network in the project to attach the instance to
Instance List View
The instance table displays all instances in the active project:| Column | Description |
|---|---|
| Name | Instance display name (click to open detail view) |
| Image Name | Source image or snapshot used at launch |
| IP Address | Private IP(s) — hover to see all addresses |
| Size | Flavor name (vCPU/RAM/disk) |
| Key Pair | SSH key pair name injected at launch |
| Status | Active, Shutoff, Error, Paused, Suspended, Resize, etc. |
| Availability Zone | AZ the instance was scheduled into |
| Task | In-progress operation (e.g., Rebooting, Migrating) |
| Age | Time since instance was created |
| Actions | Per-row action dropdown |
Launch an Instance
Open the launch dialog
Navigate to Project → Compute → Instances and click Launch Instance in the top-right corner.
Details tab
| Field | Description |
|---|---|
| Instance Name | Display name for the instance |
| Description | Optional description |
| Availability Zone | Select or leave on nova (auto-schedule) |
| Count | Number of instances to launch (bulk launch) |
Source tab
Select the boot source:
Enable Create New Volume to automatically create a persistent root volume (recommended for production). Set volume size ≥ minimum disk requirement of the image.
| Source | Description |
|---|---|
| Image | Launch from a platform image |
| Instance Snapshot | Restore from a previous snapshot |
| Volume | Boot from an existing block storage volume |
| Volume Snapshot | Boot from a volume snapshot |
Flavor tab
Select the instance flavor that defines vCPU, RAM, and disk allocation. Flavors with a root disk smaller than the image’s minimum disk requirement are shown but unavailable.For workloads that need elastic scaling, choose a flavor with hot-add extra specs — see Live vCPU/RAM Scaling.
Networks tab
Allocate at least one network to the instance. Drag networks from Available to Allocated. The order determines the interface assignment (
eth0, eth1, etc.).Security Groups tab
Select which security groups to apply. The
default security group allows all egress and permits traffic between instances in the same group. Add additional groups as needed (e.g., web-http, ssh-access).Key Pair tab
Select an existing key pair or create a new one. The public key is injected into the instance via cloud-init — you’ll need the corresponding private key to SSH in.
Instance Actions
Each instance row has an Actions dropdown with the following operations:Create Snapshot
Create Snapshot
Captures the current state of the instance root disk as a platform image. The instance is briefly quiesced during snapshot creation.Snapshots appear under Project → Compute → Images with type
Snapshot. Use them as restore points or as a base for new instances.Resize Instance
Resize Instance
Changes the flavor — adjusting vCPU, RAM, and/or disk. Requires a reboot and a confirmation step (accept or revert within 24 hours).See Resize an Instance for the full workflow.
Live vCPU/RAM
Live vCPU/RAM
Adjusts vCPU count and/or RAM on a running instance with no downtime. Available only on instances running a flavor with hot-add extra specs configured.See Live vCPU/RAM Scaling for prerequisites and usage.
Reboot Instance
Reboot Instance
Soft Reboot: Sends ACPI shutdown signal to the guest OS — graceful shutdown and restart.Hard Reboot: Forces an immediate power cycle — equivalent to pulling the power cord. Use when soft reboot is unresponsive.
Shut Off / Start
Shut Off / Start
Shut Off: Sends a power-off signal to the guest. The instance moves to
Shutoff status and releases vCPU/RAM on the hypervisor (storage persists and is billed).Start: Powers on a Shutoff instance. The instance boots from where it was shut off.Suspend / Resume
Suspend / Resume
Suspend: Saves the full memory state to disk (like hibernation). vCPU/RAM are released but disk state is preserved. Transition to
Suspended status.Resume: Restores the memory state and continues execution. Faster than a cold boot.Pause / Unpause
Pause / Unpause
Pause: Freezes the instance in memory — all vCPUs halt but memory is retained. No disk write. Transition to
Paused status.Unpause: Resumes execution from the frozen state instantly.Pausing keeps the instance consuming vCPU and RAM on the host. Use Suspend for longer idle periods to free host resources.
Rescue Instance
Rescue Instance
Boots the instance from a rescue image (small Linux ISO) with the original root disk attached as a secondary disk. Use to recover from boot failures or lost root access.See Rescue an Instance for the full workflow.
Delete Instance
Delete Instance
Permanently terminates the instance. If the root volume was created with Delete Volume on Instance Delete enabled, the volume is also deleted.
Instance deletion is irreversible. Ensure all data is backed up or the root volume is set to persist before deleting.
Instance Metadata & Tags
and tags let you annotate instances for inventory management, cost attribution, automation, and search. Both are stored in the compute service and returned in API responses.Metadata (Key-Value Pairs)
- Dashboard
- CLI
Edit metadata
In the Overview tab, scroll to the Metadata section. Click Edit (pencil icon). Add key-value pairs — click + after each entry.
| Example Key | Example Value | Use Case |
|---|---|---|
environment | production | Environment classification |
team | platform-eng | Team/cost-center ownership |
project_code | PROJ-042 | Billing/chargeback code |
backup_policy | daily | Backup automation trigger |
patch_group | group-A | Patch management segmentation |
role | web-server | Instance role in the stack |
Tags
Tags are simple string labels — no key, just a value. They enable fast instance filtering across projects.Add tags to an instance
List instances by tag
Remove a tag
Metadata vs Tags
| Feature | Metadata (Properties) | Tags |
|---|---|---|
| Format | Key-value pairs | Simple strings |
| Filtering | --property key=value | --tags tag1,tag2 |
| Hypervisor access | Not available inside guest | Not available inside guest |
| Config drive | Available via /openstack/latest/meta_data.json | Not included |
| Use for | Structured data, automation keys | Quick labels, grouping |
Instance Detail View
Click an instance name to open its detail page with tabs:| Tab | Contents |
|---|---|
| Overview | Flavor, image, IP addresses, security groups, key pair, metadata |
| Log | Console output from the last boot (cloud-init, kernel messages) |
| Console | Live browser-based VNC console — no SSH required |
| Action Log | History of all operations performed on this instance |
Next Steps
Attach a Volume
Add persistent storage to running instances
Configure Networking
Assign floating IPs and manage security groups
Live vCPU/RAM Scaling
Scale compute resources without rebooting
Resize Instance
Change instance flavor with a controlled reboot