VMware Cloud Director Logical Constructs
by Amine Badaoui, Senior Technical Product Manager, Rackspace Technology
At Rackspace, we’ve enjoyed the many benefits VMware Cloud Director brings as it has allowed us to engineer a VMware-based cloud solution that delivers some amazing customer benefits once thought not possible on VMware. In this series over the next few weeks, I’ll provide an overview of some of the key features of VMware Cloud Director and our learnings. The series will cover the following topics so be sure to check back for new posts.
- VCD Overview
- VCD Autoscaling
- VCD Terraform interaction
- VCD Tanzu integration
- VCD 3.0 New Features
- VCD Storage Policies
- VCD VCF Integration
Introduction
To facilitate multi-tenancy consumption of resources, VMware Cloud Director introduces various logical constructs that are critical to understand. In this article we will go through these constructs and how they all fit together.
Provider Virtual Data Center
A Provider Virtual Data Center is a partition of the vSphere capacity and services that are made available to tenants. A PVDC provides compute, memory, storage and network connectivity for the VMs and vAPPs running within a VCD organization.
Resources are configured and allocated via various mechanisms such as storage policies for storage, resource pools for memory and CPU. These resources are allocated to tenant organizations from the Provider Virtual Data Center.
Organization
An Organization is a unit of administration and a security boundary that represents a collection of users, groups, and resources. Each Organization has a dedicated portal called the tenant portal. Example below:
Organization Virtual Data Center
An Organization Virtual Data Center (OVDC) is a subset of the resources that are provided by the Provider Virtual Data Center. These resources are securely shared through predefined allocation models. We will go through the available allocation models in an upcoming article.
Putting it all together, we end up with the below
- PVCDs are created from vSphere resources.
- Organizations are security boundaries to which resources are provided.
- Organization VDCs consume their resources from PVDCs.
Conclusion
I hope this was helpful. In the next article, we will look at allocation models which determine how and when resources are committed.
Recent Posts
Padrões de rede híbrida do Google Cloud - Parte 2
Outubro 16th, 2024
Padrões de rede híbrida do Google Cloud - Parte 2
Outubro 15th, 2024
How Rackspace Leverages AWS Systems Manager
Outubro 9th, 2024
O Windows Server impede a sincronização da hora com o Rackspace NTP
Outubro 3rd, 2024