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

Table 1. Flavor Extra Specs in VMware Integrated OpenStack

Extra Spec

Description

Configurable by Image Metadata

vmware:hw_version

Specify the hardware version used to create images. In an environment with different host versions, you can use this key to place instances on the correct hosts.

No

vmware:latency_sensitivity_level

Specify the latency sensitivity level for virtual machines. Setting this key will adjust certain settings on virtual machines.

Yes

vmware:storage_policy

Specify the storage policy used for new instances.

If Storage Policy-Based Management (SPBM) is not enabled, this parameter is ignored.

Yes

vmware:tenant_vdc

Specify the UUID of the tenant virtual data center in which to place instances.

Yes

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.

Yes

hw:vifs_multi_thread

Specify true to provide each virtual interface with its own transmit thread.

No

quota:cpu_limit

Specify the maximum CPU allocation in MHz. The value 0 indicates that CPU usage is not limited.

Yes

quota:cpu_reservation

Specifies the guaranteed CPU allocation in MHz.

Yes

quota:cpu_reservation_percent

Specifies the guaranteed CPU allocation as a percentage of the actual CPU speed of the instance.

This parameter takes precedence over the cpu_reservation parameter.

Yes

quota:cpu_shares_level

Specifies the level of CPU shares allocated. You can enter custom and add the cpu_shares_share parameter to provide a custom value.

Yes

quota:cpu_shares_share

Specifies the number of CPU shares allocated.

If the cpu_shares_level parameter is not set to custom, this value is ignored.

Yes

quota:memory_limit

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

Yes

quota:memory_reservation

Specify the guaranteed memory allocation in MB.

Yes

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.

Yes

quota:memory_shares_level

Specifies the level of memory shares allocated. You can enter custom and add the memory_shares_share parameter to provide a custom value.

Yes

quota:memory_shares_share

Specifies the number of memory shares allocated.

If the memory_shares_level parameter is not set to custom, this value is ignored.

Yes

quota:disk_io_limit

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

Yes

quota:disk_io_reservation

Specify the guaranteed disk transaction allocation in IOPS.

Yes

quota:disk_io_shares_level

Specifies the level of disk transaction shares allocated. You can enter custom and add the disk_io_shares_share parameter to provide a custom value.

Yes

quota:disk_io_shares_share

Specifies the number of disk transaction shares allocated.

If the disk_io_shares_level parameter is not set to custom, this value is ignored.

Yes

quota:vif_limit

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

Yes

quota:vif_reservation

Specify the guaranteed virtual interface bandwidth allocation in Mbps.

Yes

quota:vif_shares_level

Specifies the level of virtual interface bandwidth shares allocated. You can enter custom and add the vif_shares_share parameter to provide a custom value.

Yes

quota:vif_shares_share

Specifies the number of virtual interface bandwidth shares allocated.

If the disk_io_shares_level parameter is not set to custom, this value is ignored.

Yes