-VMware Vshield Manager.
*Deploys and manages VMware Shield Edge, devices as requested by Vcloud Director.
-Connects to Vcenter via VIM API for Vshield Edge deployment.
-Manages configuration via VIX API.
*Linux based virtual application
*Runs management interface
*Aggresgates usage data for Vcenter Chargeback
*ONce per attached Vcenter Server.
*Firewall and router device that provides network and security services.
*Deployed automatically by Vcloud Director via Vshield Manager
*Deployed to Vsphere hosts as virtual appliances.
*Enforce multitenancy services-NAT, DHCP, Firewall, Port Forwarding and IP Masquerading services.
Reference: Vcloud Architecture
1.Vsphere Client for Vsphere configuration and preparation:
-Vcenter Server and Vcenter objects:
*Datastore, host clusters, resource pools, Vnetwork distributed switches.
-ESXI host configuration:
*Virtual switches and networks.
2. Vsphere resources, once attached, and managed by Vcloud and Director.
Vcloud Infrastructures rely on VMware Vsphere resources to provide CPU and memory to reun virtual machines. Vcloud Director uses VNetwork Distributed Switches and Vsphere port groups to support virtual machine networking. Vsphere datastores provide storage for virtual machine files and other files necessary for virtual machine operations.
Vcloud Director requires all workloads to be virtualized. Clusters enabled by VMware Vsphere distributed resources scheduler(DRS) should be set to automatically balance the Vcloud Director deployed workloads across the physical compute resources of the DRS cluster.
Multiple cells should be used to address availability and scalability. The is achieved by a load balancer or content switching front end layer. Load Balancer present a consistence address for the services regardless of the underlying node responding . They can be spread session load across cells and have monitoring cell health by add/remove cell from the active service pool.
Vcloud Director installation includes multiple cloud cells running behind a load balancer or NAT or if the cloud doe not have publicly routing IP address. It can be set to a public console proxy address.
Load Balancer that supports SSL, session persistence and has network connectivity to the public facing internet or internal service network can perform load balancing of Vcloud Director Cells as be consisted for security and manageability requirements.
Vcloud Directory support multiple Vcenter instances. These instance should all be in same site to avoid latency.
*Make sure put provisioning operational limits in the Vcenter Server and Vsphere resource.
Vcloud Director Cell are stateless front-end processors for the Vcloud. Each cell has a variety of purposes an self manages various functions among cells. While connecting to a central database.
Scaling Vcloud Director to a large environment is supported by install multiple Vcloud Director cells. Cell activities are coordinated through shared database.
One cell is designed as the coordinator cell; all other cells are designed salve cells.
The coordinator cell designates which services run on the salve cell this all done automatically by Vcloud Director.
A Vcloud Director server group consists of one or more Vcloud Director Server. The share a common database and link to an arbitrary number of vCenter server and ESXI host resources.
Web based portal consists of two or more major components:
-Vcloud Administration Portal-
*Providing allocation and separate resources into organizations.
*Time leases to control how long resource can run be stored.
-Vcloud Customer Portal- allow self service means to create and manage their own virtual machine.
*Role based model permissions.
*HTTP load balance in front of the cells.
*Vcloud Director cell scale horizontally.
*NFS Server for Vsphere vApp file transfer service.
-All cells in a single site.
-All cells share Vcloud Director database.
vcloud director multicell environment.
Vcloud Director Cell
*Runs on RHEL
*Run cloud web service portal for Vcloud Director Web Console
-Split between consumers (organization portals) and administrator (systems).
*Access to Vsphere infrastructure can be on a private network segment for security reasons.
-Run on physical or virtual (preferred) machine.
-Connects to LDAP server for user management
-Connects to SMTP server for notifications
-Connects to NFS server for Vapp file transfer services(multicellular environment).
_Connection to Vcloud Director Database.
vcloud all Architecture
VMware vCloud Director Architecture
VCloud Director requires all workloads to be virtualized. Clusters enabled by VMware Vsphere. Distributed Resource Scheduler (DRS) set to aromatically balance the VCloud Directory deployed workloads across the physical compute resources of the DRS clusters. *Vcloud Director Requires Enterprise, Enterprise Plus licensing for Vnetwork Distributed Switches.
Use Vsphere Clients for Vsphere configuration and preparation”
*Vcenter Server and Vcenter Objects:
-Datacenters, host clusters, resource pools, vNetwork distributed switches
*ESX/ESXI Host configuration:
-Virtual switches and networks
*Vsphere resources, once attached, are managed by Vcloud Director
Vcloud infrastructures rely on VMware Vsphere resources to provide CPU and memory to run virtual machine. Vcloud Director also uses vNetwork Distributed Switches and vsphere port group to support virtual machine network, Vsphere datasotres provide storage for virtual machine files and other files necessary for virtual machine operations. You use these underlying Vsphere resources to create clound resources.