Compute Overview & Presets
Virtual Machine preset specifications, vCPU/RAM allocation profiles, and VM lifecycle state transitions.
Compute Hardware Presets
In microsrv, compute capacity is allocated via balanced hardware presets offering dedicated vCPU cores and guaranteed RAM allocations.
Available Instance Specifications
| Flavor | vCPU | RAM | Root disk | Target Workload Profile |
|---|---|---|---|---|
| std.1c2g | 1 | 2 GiB | 8 GiB | Light scripts, proxies, notification bots |
| std.2c4g | 2 | 4 GiB | 16 GiB | Web applications, REST APIs, microservices |
| std.4c8g | 4 | 8 GiB | 32 GiB | Databases, CI/CD runners, heavier services |
Root disk size is part of the flavor. Extra data volumes are sold in 8 GiB increments (8, 16, 24 or 32 GiB).
Virtual Machine State Lifecycle
A virtual machine transitions through the following lifecycle states in the console and API:
1. ALLOCATION & CLOUD-INIT
[INIT] Provisioning NVMe disk (30 GB) • vNIC allocated • Cloud-Init running...
- Creating: Provisioning block storage, setting up virtual NICs, and executing Cloud-Init.
- Running: The instance is fully active, receiving network connections and executing workloads.
- Migrating: Automatic background transfer of memory pages to a standby physical host without guest OS downtime.
- Stopped: User-initiated shutdown. Compute cores and RAM are released, while attached NVMe block volumes are retained.
- Terminated: Instance and associated transient volumes are permanently destroyed.