Flavor extra specs are used for the advanced configuration of compute instances. VMware Integrated OpenStack exposes additional capabilities through flavor extra specs.
Configuring virtual interface quotas is not supported in NSX-T Data Center. The following extra specs cannot be used with NSX-T Data Center deployments:
- quota:vif_limit
- quota:vif_reservation
- quota:vif_shares_level
- quota:vif_shares_share
However, vSphere 7.0, when used with the new VDS and NSX-T Data Center, certainly supports the additional capabilities of the preceding extra specs.
To configure QoS for NSX-T Data Center, create a Network I/O Control (NIOC) profile and apply it to the N-VDS for the transport nodes in your deployment. See Configuring Network I/O Control Profiles.
If an image metadata and flavor extra spec conflict, the image metadata takes precedence over the flavor extra spec.
| Extra Spec | Description |
|---|---|
| hw:vifs_multi_thread |
Specify true to provide each virtual interface with its own transmit thread. |
| quota:cpu_limit |
Specify the maximum CPU allocation in MHz. The value |
| quota:cpu_reservation |
Specify the guaranteed CPU allocation in MHz. |
| quota:cpu_reservation_percent |
Specify the guaranteed CPU allocation as a percentage of the actual CPU speed of the instance. This parameter takes precedence over the cpu_reservation parameter. |
| quota:cpu_shares_level |
Specify the level of CPU shares allocated. You can enter custom and add the cpu_shares_share parameter to provide a custom value. |
| quota:cpu_shares_share |
Specify the number of CPU shares allocated. If the cpu_shares_level parameter is not set to |
| quota:disk_io_limit |
Specify the maximum disk transaction allocation in IOPS. The value |
| quota:disk_io_reservation |
Specify the guaranteed disk transaction allocation in IOPS. |
| quota:disk_io_shares_level |
Specify the level of disk transaction shares allocated. You can enter custom and add the disk_io_shares_share parameter to provide a custom value. |
| quota:disk_io_shares_share |
Specify the number of disk transaction shares allocated. If the disk_io_shares_level parameter is not set to |
| quota:memory_limit |
Specify the maximum memory allocation in MB. The value |
| quota:memory_reservation |
Specify the guaranteed memory allocation in MB. |
| quota:memory_reservation_percent |
Specify the guaranteed memory allocation as a percentage of the actual memory of the instance. The value This parameter takes precedence over the memory_reservation parameter. |
| quota:memory_shares_level |
Specify the level of memory shares allocated. You can enter custom and add the memory_shares_share parameter to provide a custom value. |
| quota:memory_shares_share |
Specify the number of memory shares allocated. If the memory_shares_level parameter is not set to |
| quota:vif_limit |
Specify the maximum virtual interface bandwidth allocation in Mbps. The value |
| quota:vif_reservation |
Specify the guaranteed virtual interface bandwidth allocation in Mbps. |
| quota:vif_shares_level |
Specify the level of virtual interface bandwidth shares allocated. You can enter custom and add the vif_shares_share parameter to provide a custom value. |
| quota:vif_shares_share |
Specify the number of virtual interface bandwidth shares allocated. If the vif_shares_level parameter is not set to |
| vmware:boot_efi_secure_boot |
Specify true to perform signature checks on any EFI images loaded during startup. |
| vmware:boot_enter_bios |
Specify true to make virtual machines enter the BIOS configuration on next startup. Virtual machines automatically reset this parameter after the next startup. |
| vmware:boot_retry |
Specify the delay in milliseconds before the boot sequence is started. |
| vmware:boot_retry_delay |
Specify the delay in milliseconds before the boot sequence is retried. If the boot_retry_enabled parameter is set to |
| vmware:boot_retry_enabled |
Specify true to retry the boot sequence if a boot failure occurs. |
| vmware:cpu_affinity |
Specify a list of CPUs that instances can use. vmware:cpu_affinity can be set like '[0,"2-3","50-60",71,74,"81-82"]' 0 means cpu0, "2-3" means cpu2 and cpu3 "50-60" means cpu50, cpu51,cpu52...cpu59,cpu60 |
| vmware:extra_config |
Specify custom configurations in the JSON format. For example, |
| vmware:hw_version |
Specify the hardware version used to create images. In an environment with different host versions, you can use this parameter to place instances on the correct hosts. |
| vmware:latency_sensitivity_level |
Specify the latency sensitivity level for virtual machines. |
| vmware:latency_sensitivity_per_cpu_high | Specify the high latency sensitivity level for selected virtual CPUs within a virtual machine. Use the OpenStack CLI to specify this option. For example, |
| vmware:resource_pool |
Specify the resource pool on which to place new instances. If the name of the project containing the instance matches the name of a resource pool in your environment, the instance is placed in that resource pool by default. Setting this parameter overrides the default behavior and forces the instance to be placed in the specified resource pool. |
| vmware:set_bios_uuid |
Specify true to use the Nova UUID of instances as the device UUID. |
| vmware:storage_policy |
Specify the storage policy used for new instances. If Storage Policy-Based Management (SPBM) is not enabled, this parameter is ignored. |
| vmware:tenant_vdc |
Specify the UUID of the tenant virtual data center in which to place instances. |
| vmware:vgpu |
Specify the number of shared vGPUs to attach to the instance. |
| vmware:vm_group |
Specify the DRS VM group in which virtual machines will be placed. If the specified VM group does not exist, instances fail to power on. |
