Flavor extra specs are used for advanced configuration of compute instances. VMware Integrated OpenStack exposes additional capabilities through flavor extra specs.

Note: 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

If an image metadata and flavor extra spec conflict, the image metadata takes precedence over the flavor extra spec.

Table 1. Flavor Extra Specs in VMware Integrated OpenStack
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 0 indicates that CPU usage is not limited.

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 custom, this value is ignored.

quota:disk_io_limit

Specify the maximum disk transaction allocation in IOPS. The value 0 indicates that disk transactions are not limited.

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 custom, this value is ignored.

quota:memory_limit

Specify the maximum memory allocation in MB. The value 0 indicates that memory usage is not limited.

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 100 indicates that guest memory is also fully reserved.

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 custom, this value is ignored.

quota:vif_limit

Specify the maximum virtual interface bandwidth allocation in Mbps. The value 0 indicates that virtual interface bandwidth is not limited.

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 custom, this value is ignored.

vmware:extra_config

Specify custom configurations in JSON format. For example, '{“acpi.smbiosVersion2.7”:“FALSE”}' .

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: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: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:vm_group

Specify the DRS VM group in which virtual machines will be placed. If the specified VM group does not exist, instances will fail to power on.