Skip to content

Servers

The Servers tab inside a project lists every virtual machine you've launched, and is where you create, modify, start, stop, and delete them. Underlying service: Virtual Machines.

Overview

Servers list The Servers tab — one row per VM, with status, flavor, IPs, region, and age.

The list view surfaces:

Column What it shows
Name VM name (your choice; not the underlying ID)
Flavor The vCPU / RAM size — e.g. large (4 CPU, 8 GB RAM), xlarge (8 CPU, 16 GB RAM)
IPs All attached private + public IPs
Status Active (running), Shutoff (stopped), Building, Error, Migrating
Created At Relative timestamp
Region BD-DHK-1 / BD-CTG-1 / BD-SYL-1

Above the list: tabs to switch between Servers and Placement Groups, plus a global + Create a Cloud Server button.

Administration

Per-project quotas and defaults live in Project Settings → Quota and Project Settings → General → Default region. As a project admin you can:

  • Raise / lower vCPU and RAM quotas (within the org-level cap; request increases via support)
  • Set the default region for new resources
  • Define placement groups for affinity / anti-affinity policies (e.g. "spread these 3 VMs across different hypervisors")
  • Define default tags that every new server must carry (see Projects → Tagging conventions)

Placement groups

A placement group is a hint to the scheduler about how to lay out servers in the group:

Policy Scheduler tries to… Use case
Anti-affinity Place each VM on a different hypervisor HA: don't lose all replicas on one host failure
Affinity Place every VM on the same hypervisor Tight inter-VM latency, shared local NVMe
Soft anti-affinity Anti-affinity if capacity allows, fall back if not HA when possible, no provisioning failures

Create from Servers → Placement Groups → + Create Placement Group, then reference the group when launching VMs.

Operation

Creating a server

Click + Create a Cloud Server. The wizard asks for:

  1. Name — must be unique within the project (≤ 64 chars)
  2. Region — defaults to the project default; override here
  3. Flavor — Standard / Memory-optimized / CPU-optimized, plus size. See VM flavors
  4. Image — stock (Ubuntu / Rocky / Windows / etc.) or one from your project's custom images
  5. Boot source — image (default), volume, snapshot
  6. Storage — boot disk size + any additional data disks; pick NVMe HCI or Provisioned IOPS per disk
  7. Network — VPC + subnet; pick a public-IP option (none / dynamic / floating)
  8. Security groups — at least one (default allows SSH from any source; you can lock this down per project)
  9. SSH key — pick a public key uploaded earlier, or paste a new one inline
  10. User-data — optional cloud-init payload for first-boot provisioning
  11. Placement group — optional
  12. Tags — required tags per project policy + any extras

Click Create. The VM enters Building for 30–60 seconds, then Active with IPs assigned.

Common day-2 actions

Click a row in the Servers list to open the server detail panel, where you can:

  • Power — Start / Stop / Reboot (graceful) / Hard reboot
  • Resize — change to a larger or smaller flavor (warm-resize where possible; reboot otherwise)
  • Snapshot — create a point-in-time image of the running VM; see Images
  • Console — open a VNC-equivalent serial / graphical console (no SSH key required; useful when the VM is unreachable on the network)
  • Attach / detach volumes — see Volumes
  • Attach / detach floating IP
  • Change security groups
  • Edit tags
  • Rescue — reboot into a minimal recovery image with the original disk mounted; useful when SSH is broken
  • Delete — terminate the VM and detach (but not delete) any attached volumes

Bulk actions

Tick multiple rows in the list view to apply an action to all of them at once: bulk start, stop, reboot, delete, or tag-edit. The console asks for one confirmation, then runs the action concurrently.

Each column header in the list has a filter funnel icon. Combine filters across columns (e.g. Status = Active AND Region = bd-dha-1 AND tag environment = prod). The global search box (top bar) is fuzzy across name, ID, and tag values.

Troubleshooting

Symptom Likely cause Fix
VM stuck in Building for > 5 min Capacity contention in the chosen region or quota exhausted Check Project Settings → Quota; try a different region or smaller flavor
VM in Error after create Bad cloud-init script or unsupported image Open the detail panel → Error reason field; fix cloud-init and retry
Cannot SSH Security group blocks port 22 / wrong key / wrong network ACL Open the Console action — confirm the VM is alive and check the SSH service. Check Networking → Security groups for an inbound tcp/22 rule from your source IP
Status Migrating won't progress Live-migration target hypervisor unavailable Open a support ticket; the platform team can force-cancel and retry
Resize button greyed out VM was launched from a snapshot pinned to its original flavor Stop the VM → Resize is allowed → Start
Public IP not attached after create Floating IP pool exhausted Networking → Floating IPs → request a new IP or release one you're not using
Console action shows blank screen VNC websocket blocked by an extension or corp proxy Try incognito; whitelist *-vnc.* paths in proxy

For platform-wide outages or per-region status, see Status.