Skip to content

Reference

Flavours and images

How flavour names work, the facts that hold for every flavour and image, and how to read the current catalogue.

Flavours and images are the same in ca-central and ca-east. The catalogue changes as flavours and images are added, so read the current list from your project rather than from a page.

Flavour names

A flavour sets an instance's vCPUs, memory and GPUs. Its name says which, after the v1. that every current flavour starts with:

Part Meaning In v1.c4r8 In v1.c12r24g1
c vCPUs 4 12
r Memory (RAM), in GB 8 24
g GPUs, only on GPU flavours none 1

Facts about flavours

Fact What it means for you
Flavours have no local disk openstack flavor list shows a disk of 0 for every flavour
Every instance boots from a volume You set the root volume's size when you launch, and all of an instance's storage is volumes
A flavour can be changed later Resizing moves an instance to another flavour; its volumes stay as they are

Facts about images

Fact What it means for you
An image sets a minimum root volume size The launch fails if the root volume is smaller. Windows Server images need at least 80 GB
Windows Server images are visible to every project They're priced to include the Windows licence: there's nothing to request or bring
Images you upload belong to your project Other projects don't see them

Read the current catalogue

In the Breqwatr Cloud Portal (Strata), the launch form's Browse... pickers list the flavours and images your project can use, with their sizes.

With the OpenStack CLI:

openstack --os-cloud <cloud-name> flavor list
openstack --os-cloud <cloud-name> flavor show v1.c2r8
openstack --os-cloud <cloud-name> image list
openstack --os-cloud <cloud-name> image show "<image-name>" -c name -c min_disk -c visibility

flavor list shows each flavour's memory in MB, its disk (0) and its vCPUs. image list shows the images every project can use and your project's own; add --public for only the ones every project can use. min_disk is the smallest root volume, in GB, an image will boot from. Add --os-region-name ca-east to read the other region; the lists are the same.