Gabarits d'instances (machines virtuelles)

Other languages:

English
français

Page enfant de Service infonuagique de Calcul Canada

Les gabarits (flavors) OpenStack pour le matériel virtuel définissent plusieurs paramètres dont le nombre de cœurs et la capacité de mémoire vive et sur disque, permettant à l'utilisateur de sélectionner le type de machine virtuelle qui convient, tout comme il choisirait un serveur physique. Voir NetApp OpenStack Deployment and Operations Guide

Les gabarits de machines virtuelles dans les environnements infonuagiques de Calcul Canada ont des noms semblables à

c2-7.5gb-92
p1-0.75gb

Par convention, le préfixe c désigne « calcul » (compute) et le préfixe p désigne « persistant » (persistent). Le préfixe est suivi du nombre de CPUs virtuels, d'un tiret, puis de la quantité de mémoire vive. Si le nom du gabarit comprend un deuxième tiret, il est suivi de la taille du disque éphémère secondaire.

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. It's 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 (West) 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 (West) 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.