Skip to main content

Overview

Navigate to Compute → Instances in the sidebar to manage compute instances.

Launch an Instance

Click Create Instance to open the 4-step wizard.
For the complete field-by-field reference, see Launch an Instance.

Instance Actions — Every Option Explained

The Instances list exposes one direct row action (Console), a More dropdown with five action submenus, and a batch-action toolbar at the top of the table that operates on multi-selected rows.

Direct row action

More → Instance Status

Power and lifecycle actions. Each is a separately gated permission. Attach or detach things to a running instance.

More → Backups and Snapshots

More → Clone and Template

More → Configuration Update

Other row actions (ungrouped)

Batch actions (multi-select toolbar)

Select multiple rows with the checkboxes at the left of the table; the batch toolbar appears above the table.

Admin-view extras

When viewing instances through the admin view (visible to users with the admin role), additional actions appear:

Auto-Discovery of Instances Launched Outside the Dashboard

The Polystack compute layer keeps a single source of truth for every running virtual machine. Whether an instance was launched through the Dashboard, CLI, infrastructure-as-code, orchestration, or a custom SDK workflow, the instance appears in Compute → Instances automatically. How it works — every compute host added to the cluster through the deployment console runs the Polystack compute agent, which reports every VM running on the hypervisor back to the platform’s central state. The Dashboard reads from that central state, so it always reflects what is actually running on the cluster — there is no separate “import” or “register VM” step needed for instances launched outside the Dashboard. Two prerequisites for auto-discovery:

The compute host is added to the cluster

The hypervisor running the VM must have been added to the cluster through the deployment console → Hosts. Hosts not registered with the cluster cannot report their VMs, and any VMs running on them remain invisible until the host is added.

Project visibility applies

The signed-in user must have access to the project that owns the instance. Cross-project visibility requires the admin view, which exposes every instance on the cluster.
This behavior is independent of how the instance was provisioned, what toolchain manages it, or which user created it. Even an instance booted from a Heat stack months ago by a teammate who has since left appears in Compute → Instances as long as the host is in the cluster and you have project access.

Instance Detail Page

Click any instance name in the list to open the detail page. The detail page exposes eight tabs: Detail-page row actions are the same set as the list row actions — Console as the direct action, plus the More menu with all submenus described above.

Detailed Guides

Launch an Instance

Complete 4-step wizard reference

Resize

Change flavor with confirm and revert

Live Resize

Adjust vCPU and RAM without reboot

Console Access

Browser-based VNC console

Snapshots

Capture and manage instance snapshots

Clone and Template

Duplicate an instance or save it as a reusable template

Live Migration

Move a running instance to another host with zero downtime

Server Groups

Affinity and anti-affinity placement policies

Instance Tagging

Tag instances for organization, billing, and automation