Resource pools represent a unit of CPU, memory, and storage that are portioned from the shared infrastructure pool. By default, when a Tenant vDC is created, a resource pool is also created with resource allocations already set. The resource pool is allocated to the Tenant vDC and can be scaled to meet the future demand.
By using the Tenant vDC, virtual data centers for tenants can be created under different compute nodes (host aggregates) that provide specific SLAs for each telco workload.
Quotas on projects set limits on the OpenStack resources across multiple compute nodes or availability zones, but they do not guarantee resource reservation. Resource reservation is guaranteed by using a Tenant vDC to allocate CPU and memory for an OpenStack project or tenant on a compute node. In a multitenant environment, noisy neighbor scenarios can also be avoided in this way.
In vCloud NFV OpenStack Edition, workloads are mapped to Flavors with a predefined memory, CPU, and storage capacity. In VMware Integrated OpenStack, a Flavor is a resource template that is configured to a workload when an instance is created.
By modifying the metadata of the Flavor that is used to create the instance, QoS resource allocations such as limits, reservations, and shares, for CPU, memory, disk IOPS, and Virtual Network Interface (VIF) can be controlled. All instances that are created by using the Flavor inherit its metadata settings.
See the Multi-Tenancy with QoS section for more information about QoS shaping and control.
