Below are illustration Vcloud Director Definition Reference:
VMware vcloud combines as Vcloud Director server group with the VMware vSphere platform.
Creating a Vcloud Director server group by:
*Installing Vcloud Director software on one or more servers.
*Connecting the Vcloud Director software to a shared database.
*Connecting the Vcloud Director software to one or more Vmware Vshield Manager Servers.
*Integrating the Vcloud Director server group with VMware Vsphere Distributed Resource Scheduler(DRS)./VMware Vsphere High Availability Clusters.
*Connecting the vCloud Director server group to optional components such as VMware vCenter chargeback server, LDAP, Server, SMTP server, and NFS server.
All Vcloud VMware Integrated Components are known as:
*Each individual Vcloud Director server is a cell in VMware Cloud.
*All of the Vcloud Director cells must connect to a common Vcloud Director database.
Installing vCloud Director 5.1.x best practices:
*Separate management from raw cloud resources.
*Underlying VSphere clusters should be split into two logical groups:
-A single management cluster running all core component and services needed to run the cloud.
-Remaining available Vcenter cluster should be aggregated into a resource pool called “Cloud consumer resource”.
The question is why should vsphere resource be separated and divided single organization units?
*Ensuring management cluster resources are for manageability.
*Reducing overhead for cloud consumer resources and allocation for client usage and consumption requirements.
* Dedicate resource for private/public separation cloud requirements.
VMware vCloud Director 5.1 Performance and Best Practices:
VMware Data Recovery is a vStorage API Data Protection – VMware based solution.
There are other vStorage AP Data Protection based backup technologies are available from third-party backup vendors:
Currently due to the UUID versus object ID issue, VMware Data Recovery cannot be used with Vcloud Directory. The following list backup and restore challenges:
*vApp naming data required for recovery.
*vApp meta data required for recovery.
*Multi-object vApp backup(protection groups for multi-tiered vApps).
*Manual recovery steps in the cloud.
*Support for backup for vApp on isolated networks or with no network connectivity.
*Enumeration of vApps by organization for use by the organization administrator
*Enumeration of vApps by organization and provider for user by the organization provider.
*User initiated backup/recovery.
*Support of provider(the provider administrator) and consumer(organization administrator and user).
Infrastructure Virtual Machine:
*Vcenter server virtual machine.
*Vcloud Director cell virtual machine
*Vcloud Chargeback server virtual machine
*Vcenter database Virtual machine
*Vcloud Director Database Virtual Machine
Optional Management Functions:
*Load balancer virtual machines for Vcloud Director cells.
*Vcloud Connector virtual machine.
*VMware Management Assistance (VMA) virtual machine.
*VMware Data Recovery Virtual Machine.
*NO user Workload
*High Availability HA
*Distributed Resource Scheduler(DRS) created to manage Vcloud Architecture.
*Management Cluster contains standard ESXI host and Vcenter Server.
*Management Cluster has it own share storage.
Cloud Consumer Resources Cluster.
*Vsphere resource managed by VMware Director Cloud
*Each resource collection represents one or more provider VDCs.
*Exclusively for cloud user workloads- no management virtual machine(except vShield Edge virtual appliances deployed automatically.
Both Management and Consumer Resource Cluster reside at the same physical location due own latency issue might arise if workloads need to be move from side to another.
Based on VMware recommendation that management components to deployed in the management cluster, but choice deploy consumer resource cluster. For example, Vcenter server system and Vshield Manager Instances.
Vcloud Connector (VCC) is a server, which is a virtual appliance that installs in Vsphere and handles all the business logic of dealing with other clouds. The VCC user interface displayed in vSphere client plug in.
Vcloud Conector Appliance Considerations:
*The Virtual Appliance must be deployed to a Vcenter server and available Vcenter Server clients. User access is via Vsphere client -via Vclould Connector must have right log into Vcenter server.
*Workload copy operation user the Vcloud connector appliance as middleware so network latency and bandwidth between clouds need to be put in an account. Most cases it may be preferred to run on multiple instance of Vcloud Connector across multiple Vcenter Server instances to avoid network latency or consuming excessive bandwidth.
Vcloud Connector (VCC) is an optional component to facilitate transfer of a powered off Vapp in open Virtualization Format (OVF) from a local Vcloud or Vsphere to a remote Vcloud.
VCC solves a need to Cloud consumers to migrate workflow in a federated cloud. VCC allows perform migration from all of your public and private clouds and obtain a consistence view of them from a single interface.
*VCC needs to be installed by Vcloud Administrator and only used by Vcloud Administrator. End users can only view and manage workloads.
*Vcloud Connector Vcc Appliciance:
-Tomcat server and embedded Postpres database to bridge between Vcloud and Vsphere environment.
-Temporary storage to facilitate file transfer to Vcloud.
*Vcloud Connector plug-in for Vsphere Client.
-Single pane of glass view across vsphere and private and public Vcloud instances.
-Visualized Workloads and Templates.
-Migrate Workloads and Templates.
-Perform basic power and deployment operations
-Access VMware Remote Console(VMRC)
-Directly launch Vcloud Director or Vcloud Datacenter Server Web UI.