Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.xloud.tech/llms.txt

Use this file to discover all available pages before exploring further.

Overview

Flavors define the virtual hardware profile for instances — vCPU count, memory allocation, root disk size, and optional hardware extensions like GPU and NUMA pinning. Administrators manage the flavor catalog. Users select flavors when launching instances.
Administrator Access Required — This operation requires the admin role. Contact your Xloud administrator if you do not have sufficient permissions.
Prerequisites
  • Administrator access to the Xloud Dashboard (admin view)

View Flavors

Navigate to Compute > Flavors in the admin sidebar. The list shows:
ColumnDescription
ID/NameFlavor identifier (clickable to view details)
CategoryGeneral Purpose, Compute Optimized, Memory Optimized, etc.
CPUNumber of vCPUs
MemoryRAM allocation (formatted as GiB)
Internal Network BandwidthNetwork throughput in Gbps
Ephemeral DiskTemporary scratch disk size (GiB)
Storage IOPSI/O operations per second limit
PublicWhether the flavor is available to all projects
Filter by Name, CPU, Memory, or Category.

Create a Flavor

The Dashboard provides a 2-step wizard: Params Setting and Access Type Setting.
1

Open the Create Flavor wizard

Navigate to Compute > Flavors in the admin sidebar. Click Create Flavor.
2

Step 1 — Params Setting

Configure the virtual hardware profile.Architecture (required) — Select the hardware architecture:
ArchitectureDescription
X86 ArchitectureStandard x86-64 virtual machines
Heterogeneous ComputingGPU-accelerated instances
Bare MetalPhysical server provisioning
ARM ArchitectureARM-based instances
Category (required) — Depends on the selected architecture:
  • X86: General Purpose, Compute Optimized, Memory Optimized, Big Data, Local SSD, High Clock Speed
  • Heterogeneous: GPU Compute, Visualization Compute
Basic parameters:
FieldTypeRequiredDescription
NameTextYesFlavor name
vCPUsNumberYesVirtual CPU count (min: 1)
Memory (GiB)NumberYesRAM allocation (min: 1)
Hot-Add Configuration (hidden for Bare Metal):
FieldDescription
Enable Hot-AddYes/No — enables live vCPU/RAM scaling
Minimum CPUMinimum vCPUs at boot (required if Hot-Add enabled)
Minimum Memory (GiB)Minimum RAM at boot (required if Hot-Add enabled)
Xloud-Developed — Hot-Add configuration for live vCPU and RAM scaling is developed by Xloud and ships with XAVS / XPCI.
Storage & Bandwidth (varies by architecture):
FieldVisibilityDescription
BandwidthHidden for Bare MetalInternal network bandwidth (Gbps)
Ephemeral DiskWhen applicableTemporary scratch disk (GiB)
Root DiskHidden when block storage enabledRoot disk size (GiB)
IOPSHidden for Bare MetalStorage I/O limit
NUMA Configuration (for non-compute-optimized, non-bare-metal):
FieldDescription
NUMA NodesNumber of NUMA nodes
Memory Page Sizelarge, small, any, or custom value
GPU Parameters (only for GPU categories):
FieldDescription
GPU TypeSelect from configured GPU models
GPU NumberNumber of GPUs (min: 1)
Compute Optimized Parameters (only for Compute Optimized category):
FieldDescription
NUMA NodesPer-node CPU and RAM allocation (total must match flavor vCPUs/RAM)
CPU Policydedicated or shared
CPU Thread Policyprefer, isolate, or require
Memory Page Sizelarge, small, any, or custom
3

Step 2 — Access Type Setting

Configure which projects can use this flavor.
OptionDescription
PublicAvailable to all projects on the platform
Access ControlRestricted to selected projects only
When Access Control is selected, a project table appears. Select one or more projects to grant access.
4

Create the flavor

Click Confirm to create the flavor.
Flavor appears in the list and is available for instance creation.

Flavor Detail

Click a flavor name in the list. The detail page shows:Detail tab — Flavor specifications:
  • Base Info: Network Bandwidth, Ephemeral Disk, IOPS, NUMA config
  • GPU Info (if applicable): GPU type and count
  • Compute Optimized Info (if applicable): Per-NUMA-node CPU/RAM, CPU/thread policy, page size
  • Extra Specs: Full JSON of all extra specifications
Instances tab — All instances currently using this flavor.

Delete a Flavor

Click the Delete action (first row action) on the flavor row. Confirm deletion.
Existing instances using the deleted flavor continue running but cannot be resized. Create a replacement flavor before deleting.

Next Steps

Launch an Instance

Use flavors when creating instances in the 4-step wizard

Live vCPU/RAM Scaling

Configure Hot-Add flavors for zero-downtime scaling

Quotas

Set per-project limits on vCPU, RAM, and instance counts

Compute Hosts

Monitor hypervisor resources and host availability