Virtual machine flavors

From Alliance Doc
Jump to navigation Jump to search
Other languages:

Parent page: Cloud

Virtual hardware templates are called "flavors" in OpenStack, defining sizes for RAM, disk, number of cores, and so on. ... Flavors define a number of parameters, resulting in the user having a choice of what type of virtual machine to run—just like they would have if they were purchasing a physical server. - NetApp OpenStack Deployment and Operations Guide

Researchers are able to view all the flavors they have been allocated for their project. These can be seen in the Horizon Dashboard and via the OpenStack command line client with the following command:

[name@server ~]$ openstack flavor list --sort-column RAM

If you have a project and need a flavour not currently allocated, please email

Virtual machine flavors have names like:


By convention the prefix "c" designates "compute", "p" designates "persistent", and "g" designates "vGPU". The prefix is followed by the number of virtual vCPUs/vGPUs, then the amount of RAM after the dash. If a second dash is present it is followed by the size of secondary ephemeral disk in gigabytes. In the case of vGPUs, the compute flavour is included after the vGPU information.

Openstack flavors
Openstack flavors

A virtual machine of "c" flavor is intended for jobs of finite lifetime and for development and testing tasks. It starts from a qcow2-format image. Its disks reside on the local hardware running the VM and have no redundancy (raid0). The root disk is typically 20GB in size. "c" flavor VMs also have an secondary ephemeral data disk. These storage devices are created and destroyed with the instance. The Arbutus cloud treats “c” flavors differently as they have no over-commit on CPU so are targeted towards CPU intensive tasks.

A virtual machine of "p" flavor is intended to run for an indeterminate length of time. There is no predefined root disk. The intended use of "p" flavors is that they should be booted from a volume, in which case the instance will be backed by the Ceph storage system and have greater redundancy and resistance to failure than a "c" instance. We recommend using a volume size of at least 20GB for the persistent VM root disk. The Arbutus cloud treats “p” flavors differently as they will be on compute nodes with a higher level of redundancy (disk and network) and do over-commit the CPU so are geared towards web servers, data base servers and instances that have a lower CPU or bursty CPU usage profile in general.