Flavor explanation

From MediaWiki
Revision as of 15:21, 5 July 2024 by Sst-ska (talk | contribs) (Created page with " == Naming == The naming of the flavors has been decided in the Meeting on 2019-10-28. The flavor name contains three vital pieces of information: - The host aggregate - The number of CPUs - The amount of Memory (in GiB) Thes host aggregates exist: - Developer Düdingen - Standard Düdingen - Standard Windows Düdingen - Standard Düdingen South - Standard Düdingen North...")
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to navigation Jump to search

Naming

The naming of the flavors has been decided in the Meeting on 2019-10-28.

The flavor name contains three vital pieces of information:

- The host aggregate
- The number of CPUs
- The amount of Memory (in GiB)

Thes host aggregates exist:

- Developer Düdingen
- Standard Düdingen
- Standard Windows Düdingen
- Standard Düdingen South
- Standard Düdingen North
- Enterprise Düdingen

The number of CPUs is prefixed with the character c and padded with 0s to a total of 3 decimal digits. The amount of Memory is expressed in GiB. It is prefixed with the character m and padded with 0s to a total of 3 decimal digits.

Here is an example for a flavor with two CPUs and 4 GiB of RAM in the "Standard Düdingen" host aggregate:

Standard Düdingen c002m0004

Scheduling properties

We have defined a custom scheduling property called vm_quality_class. It represents the quality classes we offer: "developer", "standard" and "enterprise". This property is added to host aggregates and flavors. When scheduling VMs, the AggregateInstanceExtraSpecsFilter schedule filter will match VMs to VM Nodes accordingly.