Skip to main content

Overview

Flavors define the virtual hardware profile for compute instances — vCPU count, memory, root disk size, ephemeral disk, and swap. As an administrator, you control the flavor catalog available to all projects and can create private flavors restricted to specific projects for specialized workloads.
Prerequisites
  • admin role
  • Navigate to Admin → Compute → Flavors

Default Flavors

FlavorvCPUsRAMRoot DiskUse Case
m1.tiny1512 MB1 GBLightweight agents, test workloads
m1.small12 GB20 GBDevelopment, CI runners
m1.medium24 GB40 GBGeneral-purpose applications
m1.large48 GB80 GBWeb servers, mid-tier services
m1.xlarge816 GB160 GBDatabases, compute-intensive workloads

Create a Flavor

Open the Create Flavor dialog

Navigate to Admin → Compute → Flavors and click Create Flavor.

Flavor Information tab

FieldDescription
NameUnique flavor identifier (e.g., c4.2xlarge, gpu.v100)
vCPUsVirtual CPU count
RAM (MB)Memory in megabytes
Root Disk (GB)Root disk size — 0 for ephemeral root from Ceph
Ephemeral Disk (GB)Optional local scratch disk (lost on delete)
Swap (MB)Optional swap partition size
RX/TX FactorNetwork bandwidth multiplier (1.0 = standard)
PublicAvailable to all projects (toggle off for private flavors)
Flavor IDLeave auto unless you need a specific ID

Flavor Access tab

If Public is toggled off, add projects that can access this private flavor in the Flavor Access tab.

Create

Click Create Flavor. The new flavor appears in the list and is immediately available for instance launches.
Verify the flavor is visible to a project member by checking the flavor list in the Launch Instance wizard.

Add Extra Specs

Extra specs pass hardware-level hints to the scheduler and hypervisor. They control CPU pinning, huge pages, NUMA topology, TPM, and hot-add (live scaling) configuration.

Open the Extra Specs editor

Click the flavor name to open its detail view. Navigate to the Extra Specs tab. Click Create.

Add key-value pairs

Enter the key and value, then click the + button to add. Repeat for each spec.

Common Extra Specs

KeyExample ValueDescription
hw:cpu_policydedicatedPin vCPUs to exclusive physical threads
hw:cpu_thread_policyisolateAvoid hyperthreading siblings
hw:mem_page_size1GBRequest 1 GB huge pages
hw:numa_nodes2Expose 2 NUMA nodes inside the VM
hw:tpm_version2.0Enable virtual TPM 2.0
os:secure_bootrequiredRequire UEFI Secure Boot
pci_passthrough:aliasv100:1Request 1 NVIDIA V100 GPU
hw:cpu_max_sockets16Max vCPU ceiling for live scaling
hw:mem_max_mb65536Max RAM (MB) ceiling for live scaling
hw:mem_page_sizeanyAllow memory balloon for live scaling
For live vCPU/RAM scaling, set hw:cpu_max_sockets, hw:cpu_max_cores, hw:cpu_max_threads, and hw:mem_max_mb. See Live vCPU/RAM Scaling for full configuration.

Flavor Metadata (Quota Specs)

Flavor metadata (distinct from extra specs) can be used to set display hints or custom properties visible to users. Navigate to Actions → Update Metadata on any flavor to add display-layer metadata.

Delete a Flavor

In the flavor row, open Actions → Delete Flavor and confirm.
Deleting a flavor does not affect running instances already using it — they retain their hardware profile. However, the flavor name will no longer appear in their detail page. New instances cannot be launched with a deleted flavor.

Next Steps

Flavor Management (CLI)

Full CLI-based flavor management with extra specs reference

Live vCPU/RAM Scaling

Configure hot-add flavors for live scaling

Advanced Features

CPU pinning, huge pages, and GPU passthrough configuration

Quotas

Manage per-project compute quotas