Skip to content

Instances Console

Reference · Updated Sep 2026

Coming from another cloud?

▸AWS·EC2 Instances

EC2 Instanceshigh

  • Uses EC2 RunInstances API instead of Nova servers.create.
  • Requires predefined instance type selection.
  • Supports per-second On-Demand billing and Spot/Reserved options.
  • Includes hibernation state not standard in OpenStack.
AWS docs ↗
▸Azure·Virtual Machines

Virtual Machineshigh

  • Uses Azure Resource Manager (ARM) REST API at /providers/Microsoft.Compute/virtualMachines instead of OpenStack Nova API at /v2.1/servers.
  • Tightly integrated with Azure services like Azure Active Directory for authentication, unlike OpenStack's Keystone.
  • VM creation requires specifying size from predefined series with hardware-specific features (e.g., AMD/Intel/ARM), not custom flavor configs.
  • Billed per second with complex pricing tiers based on series/reservation options, vs OpenStack's typically hourly or usage-based.
Azure docs ↗
▸DigitalOcean·Droplets

Dropletshigh

  • API surface is DigitalOcean’s proprietary REST/CLI/Terraform tooling rather than OpenStack Nova/Neutron/Glance APIs (Droplets are managed via DigitalOcean UI/CLI/API/Terraform).
  • Billing is usage-based with per-second billing (60-second minimum and monthly cap) rather than the typical per-hour, quota-based charge model users often see in OpenStack-based clouds.
  • Droplets include a bundled outbound transfer allowance with each plan (starting at 500 GiB/month) rather than a separate bandwidth quota/metering model users often encounter in OpenStack deployments.
  • Droplets are described as Linux-based VMs on virtualized hardware with local SSD storage, whereas OpenStack deployments commonly expose distinct block storage (Cinder) and image services (Glance) and may not bundle bandwidth/monitoring/firewalls into the instance offering.
DigitalOcean docs ↗
▸Google Cloud·VM instances

VM instanceshigh

  • Uses REST API 'instances.insert' instead of Nova 'servers.create' with different auth via service accounts vs Keystone.
  • Supports bare metal instances (no hypervisor), not in standard OpenStack Nova.
  • Network interfaces tied to VPC subnets; differs from Neutron ports/floating IPs.
Google Cloud docs ↗
▸Hetzner·Cloud Servers

Cloud Servershigh

  • Servers provisioned individually via Hetzner API (hcloud), not OpenStack Nova flavors; fixed instance types like CX11 (1 vCPU, 2GB RAM, 20GB NVMe).
  • No flavor customization; choose from predefined shared/dedicated vCPU series.
  • Billing hourly with monthly cap per server (e.g., €3.29/mo cap for CX11), charged even when powered off until deleted, unlike typical OpenStack stop-to-pause billing.
  • Custom REST API at api.hetzner.cloud/v1/servers instead of OpenStack Nova /v2.1/servers (different auth, payloads, response formats).
Hetzner docs ↗

Instances console

Overview#

Instances are the building blocks for running applications and services in the cloud. They provide a flexible and scalable way to deploy workloads, with the ability to manage and scale resources as needed.

Select Compute > Instances to view the instances console. The console lists all instances in your project and lets you create and manage instances.

The Create Instance wizard uses four tabs: Base Config (name, availability zone, flavor, image, and disk), Network Config (network, subnet, security groups), System Config (login type, key pair, user data), and Confirm Config (review and launch). See How to create an instance for the full walkthrough.

The Instances console shows a list of all instances in a project.

Instances list showing the provisioned active instance with columns for name, status, image, flavor, IP addresses, key pair, and ageClick to zoom
Instances list with a provisioned instance showing status, flavor, and IP address

You can start, stop, and reboot instances using the controls at the top of the console.

List view actions#

The list view toolbar and More Actions menu provide quick operations you can run without opening the instance detail:

  • Start, Stop, Reboot: toolbar buttons
  • Soft Reboot: graceful OS restart via the More Actions menu
  • Delete: remove selected instances via the More Actions menu

For the full set of lifecycle, networking, and configuration operations, open the instance detail view.

Instance detail#

Select an instance to view the instance details, including:

  • Network information
  • Flavor information
  • Image information
  • Security group information
  • Instance architecture diagram
Instance detail panel showing instance name, status, flavor, image, key pair, security groups, network addresses, and architecture diagramClick to zoom
Instance detail view showing configuration, network, and resource information

Use the tabs along the top of the instance detail to navigate to other resources associated with the instance such as volumes, instance snapshots, interfaces, floating IP addresses, security groups, action logs, and console logs.

Select Console to launch an instance console. The console enables you to log in to the instance and control the virtual machine from the console terminal.

Detail view actions#

From the More menu in the detail view, you can take the following actions on the instance:

Under Instance Status, you can:

  • Stop the instance
  • Lock instances to prevent changes (any project user can lock or unlock instances in a project)
  • Reboot the instance
  • Soft reboot the instance
  • Suspend to write to disk and freeze its current state.
  • Pause to temporarily suspend the execution of the instance.
  • Shelve to offload the instance from hypervisor resources while preserving the instance's state and data

Under Related Resources, you can:

  • Attach / detach an interface to connect and disconnect virtual network interfaces to and from the instance
  • Attach / detach a volume to connect and disconnect block storage volumes to and from the instance
  • Associate floating IP addresses to assign an externally accessible IP address to the instance
  • Manage the security group for the instance

Under Backups and Snapshots, you can:

  • Create a snapshot to capture the current state of the instance, including its data, configuration, and disk contents.

Under Configuration Update, you can:

  • Resize your virtual hardware
  • Reset root or Administrator password for the instance (at the operating system)
  • Rebuild an instance; this action selects a new operating system for your instance

Select Edit to edit the name of the instance.

Select Delete to delete the instance.

You can add and modify instance tags.

Instances details#

Here's a table summarizing the properties and attributes that you should understand to create or manage instances in the Compute service.

Property/AttributeDescription
NameA human-readable name for the instance, used for identification purposes.
IDA unique identifier automatically assigned to the instance by OpenStack.
StatusCurrent state of the instance: active, shutoff, building, error, paused, suspended, shelved, shelved_offloaded, rescued, resized, verify_resize, reboot, hard_reboot, rebuild, migrating, deleted.
FlavorSpecifies the size of the instance, including CPU, RAM, and disk resources.
ImageThe ID or name of the image used to create the instance.
Key PairThe name of the SSH key pair associated with the instance for secure access.
Security GroupsA list of security groups applied to the instance for network access control.
Tenant IDThe ID of the project or tenant that owns the instance.
User IDThe ID of the user who created the instance.
Created AtThe timestamp indicating when the instance was created.
Updated AtThe timestamp indicating when the instance was last updated.
NetworksA list of networks and associated IP addresses assigned to the instance.
MetadataA set of key-value pairs associated with the instance for custom information.
Availability ZoneThe availability zone in which the instance is located.
HostThe name of the physical host machine where the instance is running.
Power StateThe power state of the instance (for example, running, paused, shutdown).
Volumes AttachedA list of block storage volumes attached to the instance.
Floating IPThe floating IP address associated with the instance for external access.

Understanding these properties and attributes is helpful for creating and managing instances, as they provide crucial information about the configuration, state, and resources of the instances.

Instances service#

Instances service CLI reference#

Instances service API reference#

See also#

Quick answers

Was this page helpful?