The Resource Pod provides the runtime environment for the network functions. The section covers the logical tenancy and networking components.


In VMware Integrated OpenStack, cloud administrators manage permissions through user, group, and project definitions. Projects in OpenStack are equal to tenants in vCloud NFV. A project is the administrative container where telco workloads are deployed and managed.

Tenant vDCs

A Tenant vDC allows creation of virtual data centers for tenants under different compute nodes that offer specific SLA levels for each telco workload. While quotas on projects set limits on the OpenStack resources, Tenant vDCs allow providing resource guarantees for tenants and avoid noisy neighbor scenarios in a multitenant environment.


One or more VMs that are deployed in the tenancy to provide specific network functions or telco services.

Container Network Functions

Container Network Functions (CNFs) are containerized telco workloads similar to VNFs, with the difference that the VNF components (VNFCs) are deployed as microservices in a containerized environment.

For the vCloud NFV OpenStack Edition platform, a tenant can have an exclusive Kubernetes cluster that is deployed in the tenant's project. For high availability and to meet performance requirements, the master and worker nodes need to be spread across the ESXi hosts of the resource cluster.

At the same time, multiple tenants can share the resource cluster, because the underlying VMware Integrated OpenStack infrastructure ensures efficient resource pooling, partitioning, and allocation to the Kubernetes worker nodes of the tenants in the Resource Pod in a multi-tenant way.

As part of CNF onboarding, the CNF vendor also has to provide the specifications for the CNF infrastructure such as the number of master and worker nodes and any specific performance needs of the worker nodes. In terms of tenant provisioning, the project sizing can be done as though the Kubernetes cluster is just another set of tenant workload VMs.