Flavor explanation: Difference between revisions

From MediaWiki
Jump to navigation Jump to search
No edit summary
 
(21 intermediate revisions by the same user not shown)
Line 3: Line 3:


= Naming convention =
= Naming convention =
== Naming convention - Specifications ==
The flavor name contains three vital pieces of information:
The flavor name contains three vital pieces of information:
  - The host aggregate
  - The host aggregate
  - The number of CPUs
  - The number of CPUs
  - The amount of Memory (in GiB)
  - The amount of Memory (in GiB)
== Naming convention - CPU & Memory ==
* The number of CPUs is prefixed with the character <code>c</code> 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 <code>m</code> and padded with 0s to a total of 3 decimal digits.
Here is an example for a flavor with one CPU and 2 GiB of RAM in the "Standard Düdingen North" host aggregate:
  Standard Düdingen North c002m0004
[[Image:Flavor_explanation_1.png|752px × 117px]]
  1. CPU: 1 virtual processor
  2. Memory: 2 GiB


== Naming convention - Host aggregates ==
== Naming convention - Host aggregates ==
These host aggregates exist:
These host aggregates exist:
- Standard Düdingen
  - Developer Düdingen
  - Developer Düdingen
  - Standard Düdingen
  - Enterprise Düdingen
  - Standard Windows Düdingen
  - Standard Windows Düdingen
  - Standard Düdingen South
  - Standard Düdingen South
  - Standard Düdingen North
  - Standard Düdingen North
- Enterprise Düdingen


The number of CPUs is prefixed with the character <code>c</code> 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 <code>m</code> and padded with 0s to a total of 3 decimal digits.
* The attributes North and South refer to the location of ..
 
== Naming convention - Sceduling properties ==


Here is an example for a flavor with two CPUs and 4 GiB of RAM in the "Standard Düdingen" host aggregate:
We have defined a custom scheduling property called <code>vm_quality_class</code>. It represents the quality classes we offer: "standard"(1), "developer"(2) and "enterprise"(3). This property is added to host aggregates and flavors. When scheduling VMs, the <code>AggregateInstanceExtraSpecsFilter</code> will match VMs to VM Nodes accordingly.
Standard Düdingen c002m0004


== Naming convention - Sceduling properties ==


We have defined a custom scheduling property called <code>vm_quality_class</code>. It represents the quality classes we offer: "developer", "standard" and "enterprise". This property is added to host aggregates and flavors. When scheduling VMs, the <code>AggregateInstanceExtraSpecsFilter</code> [[OpenStack_-_Nova_scheduler_filters|schedule filter]] will match VMs to VM Nodes accordingly.
[[Image:Flavor_explanation_3.png|752px × 437px]]


[[Category: Instances]]
[[Category: Instances]]

Latest revision as of 17:01, 5 July 2024

Overview

This page explains the flavor naming convention stepping stone AG uses.

Naming convention

The flavor name contains three vital pieces of information:

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

Naming convention - CPU & Memory

  • 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 one CPU and 2 GiB of RAM in the "Standard Düdingen North" host aggregate:

  Standard Düdingen North c002m0004


752px × 117px

  1. CPU: 1 virtual processor
  2. Memory: 2 GiB

Naming convention - Host aggregates

These host aggregates exist:

- Standard Düdingen
- Developer Düdingen
- Enterprise Düdingen
- Standard Windows Düdingen
- Standard Düdingen South
- Standard Düdingen North
  • The attributes North and South refer to the location of ..

Naming convention - Sceduling properties

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


752px × 437px