VMware vCloud Director: An Introduction

Cloud computing is growing at a spectacular pace. Most organizations are either using cloud technology or developing products that support it. VMware’s cloud management tool is called vCloud Director (vCD), which works on Infrastructure-as-a-Service (IaaS) architecture. Some key points related to vCloud Director have been mentioned below:

  • VMware vCloud Director uses existing VMware vSphere deployments
  • Provides flexible storage, networking, and compute interfaces for multiple clusters using features like Distributed Resource Scheduler (DRS) and High Availability (HA)
  • Provides logical pooling infrastructure capacity using policy-based virtual datacenters resulting in efficient use of resources
  • Resource provisioning without the need for repeated configuration or significant maintenance as virtual datacenters are used

Terminologies used in VCloud Director:

  • Virtual Data Center (vDC)
  • Provider Virtual Data Center (PvDC)
  • Organization Virtual Data Center (Org vDC)
  • Allocation Models
  • vCloud Director Networking
  • Network Pools
  • Organizations
  • Users and Groups
  • Catalogs

vDC stands for Virtual Data Center. There are two types of vDCs, 1) Provider vDC and 2) Organization vDC

Provider Virtual Datacenter (PvDC):

A provider virtual datacenter (PvDC) is used for compute and memory resources of a single vCenter server resource pool.

Multiple Provider vDCs can be created as per requirements. They can also be defined for various geographic locations.

Here are some details regarding PvDCs:

  1. It is good to have a PvDC mapped to a Cluster (also known as the Root Resource Pool). The main reason for this is to keep resource contention to a minimum, as per different allocation models.
  2. Apart from being a resource pool, PvDC also provides the ability to manage storage. Please note that compute (CPU and Memory) is managed at the vSphere layer, but storage (data store where VM resides) is managed by vCloud Director.
  3. For PvDC, it is mandatory to have same storage types since vCloud Director is not capable of managing different types of storage. If data stores are backed by a mix of SATA and SSD, then you have no control over VM placement on these data stores.
  4. Users can specify reservations and limits at the resource pool level in the vSphere layer; however these are maintained by allocation models from within vCloud Director.

Organization Virtual Datacenter (Org vDC):

An organization virtual datacenter (vDC) gives resources to an organization and can be created by partitioning a Provider vDC.Users can create virtual systems through Organization vDC.

Resources created in Provider vDC (PvDC) can be used in Organization vDCs. Hence, organization virtual datacenters consume CPU, memory and storage types from the Provider vDC. A resource pool is created within vSphere under the PvDC resource pool when an Org vDC is created in vCloud Director.

Please refer to the diagram below for reference:

vcloud director 1

Allocation Models:

As mentioned earlier, allocation models are used to define how resources can be allocated to organizations. It is essentially the creation of a child resource pool for Provider vDC in the vSphere layer. Some key points regarding allocation models are:

  • Allocation models are defined on a per Organization vDC basis
  • It defines how resources come out of the Provider vDC backing the Organization vDC.
  • All reservation settings are taken from the available pool

We can divide allocation models into three parts:

  1. Pay-as-you-Go
  2. Allocation Pool
  3. Reservation Pool

Please take a look at the diagram below for an explanation of the three allocation models.

vcloud director 2

vCloud Director Networking:

vCloud Director supports three types of networks which have been mentioned below:

  1. External networks
  2. Organization networks
  3. vApp networks

Please refer to the diagram below for vCD networking:

vcloud director 3

  1. External Networks:
    • Network which is external to VMware vCloud Director.
    • External networks are created in the vSphere layer.
    • Provides external connectivity to organizations which are present on vCD.
    • At the VMware vSphere layer, it actually maps to a port.
    • Port group is attached to vCloud Director as an “external network”.
    • External Networks allow vCloud Director to connect to the outside world.
  2. Organization Networks:
    1. An organization network is contained within a vCloud Director organization and is available to all vApps in the organization.
    2. It allows vApps within an organization to communicate with each other
    3. Users can connect an organization network to an external network in order to provide external connectivity.
    4. Users can also create an isolated organization network which is internal to the organization. Some types of organization networks are backed by network pools.
    5. System administrators have the access to create organization networks.
  3. vApp Networks:
    1. Inside a single vApp, users can create multiple virtual machines and vApp Network allows those virtual machines to communicate with each other.
    2. For communication with other vApps within the same organization or outside of the organization, users can connect a vApp network with the organization network.
    3. Network pools are required for vApp networks if the organization network is connected to an external network.
    4. Users with access to vApp can manage/create their own vApp networks.

Network Pools:

  • A group of undifferentiated networks available under organization vDC.
  • Using VLANs or port groups, a network pool is backed by vSphere network resources.
  • Network pools are used by vCloud Director and they create vApp networks and internal organization networks.
  • For one organization vDC, users can only create a network pool in vCloud Director.
  • Multiple organization vDCs can share the same network pool.
  • Network pool for an organization vDC gives the network quota for an organization vDC.
  • Creation and management of network pools is done by system administrators.

Organizations:

Multi-tenancy is a nice feature and vCloud Director supports it through the use of organizations. An organization is a unit of administration for a collection of users, groups, and computing resources. Authentication is provided at the organization level. After providing credentials, users can be imported or created by an organization administrator. Creation and provision of organizations is handled by system administrators and catalog, users/groups are handled by organization administrators.

Users and Groups:

An organization contains several users and groups. Users can be created by the organization administrator or can be imported from a directory service such as LDAP. Groups are always imported from the directory service. Permissions are controlled using an assignment of rights and roles to users and groups.

Catalogs:

Catalogs are used for storing vApp templates and media files. Organizations created in vCloud Director can use catalogs. All members of an organization which have access to a catalog can use the catalog’s vApp templates and can create their own vApps.

Reference: https://www.vmware.com/pdf/vcd_15_admin_guide.pdf

Virendra Kumawat

Virendra Kumawat

Senior Principal QA Engineer at Calsoft Inc.
Having 8 Years of experience in NAS and Automation. Worked on Shell/Perl and Python scripting. Currently working in Calsoft.
Virendra Kumawat

Leave a Reply

Your email address will not be published. Required fields are marked *