...

Gen	CPU architecture	AES-acecleration	AVX	AVX2	AVX512 1.generation	AVX512 2.generation
1	Westmere
2	Sandy-Bridge
3	Haswell
4	Sky-Lake
5	Cascade-Lake

AMD EPYC based flavors:

Storage locations

The storage-location can optionally be described with a letter. The letter have the following meanings:

• no letter: The default storage-location is on a centralized SAN.
• h: The default storage-location is HDD's localized on the compute-node
• s: The default storage-location is SSD's localized on the compute-node.

Extended specifications

Some flavors equips the VM with additional resources like locally mounted storage or GPUs. Such flavors have extension appended to the flavor name to signal what resources are available.

GPUs

The GPUs are defined with the extension "<GPU-Type>-<GPU-RAM>". This will for example result in the following flavor name:

• dx5.12c96r.v100-8g: A flavor defining a VM with 12 dedicated Cascade-Lake CPU cores, 96GB RAM and a Nvidia Tesla v100 GPU with 8GB of memor

Local Storage

Some VM's would for performance reasons need storage which are locally attached to the compute-server, as that results in lower disk-latency than the regular case where storage is mounted over networks. Flavors providing local storage have the following extension in its name:

e<disk-size><size-suffix>

A flavor with local attached ssd's might be named like so:

• gx3s.8c32r.e500g: A flavor Intel Haswell cores (gx3), default storage at a local SSD (s), 8CPU+32GB RAM (8c32r), and an extra disk of 500GB backed by the default storage configuration (e500g).

Custom flavors

Some of our tenants have requirements not fitting the "general purpose" use-cases, and is investing in dedicated compute-nodes equipped with accellerators, local storage and similar. These tenants usually gets custom flavors (Identified by the keyword 'custom' in its name) providing access to these resources. The meaning behind each of the custom flavors is given to the personell needing access.

...