vCloud Automation Center (vCAC) is VMware’s central cloud management tool and offers a self-service catalog for requesting and managing all types of IT services across multiple clouds and platforms to provide customers with on-demand access to any service. vCAC is capable of managing virtual (vSphere, Hyper-V, KVM, XenServer), physical (Dell, Cisco, HP) and cloud (Amazon, OpenStack, VMware vCloud) based resources.
Simple installation is compound out of 3 servers deployed and installed on below order:
- First component is Identity Appliance – The Identity Appliance is a pre-configured virtual appliance that provides single sign-on capabilities. It is delivered as an open virtualization format (OVF) template.
- Second component is vCloud Automation Center Appliance – The vCloud Automation Center Appliance is a pre-configured virtual appliance that deploys the vCloud Automation Center Appliance server and web console (the user portal) delivered in OVF format.
- Third component is IaaS installed on a Windows server (or more servers depends deployment method)
Besides above 3 virtual machines other infrastructure components such as:
- Active Directory (or OpenLDAP)
- vCenter server with one or more ESXi hosts
My environment is composed as following:
- vCloud Identity appliance. NOTE: with vSphere 5.5b you can point your vCAC appliance to vCenter server SSO.
- vCloud Automation Center Appliance
- Windows 2008 R2 with installed all vCAC IIS components.
Distributed Execution Managers
- AD 2012 as authentication services. I also use the same server to host DNS and NTP services.
- vSphere 5.5 vCenter Appliance
- 2 ESXi servers (installed on 2 HP BL460c G6)
- SQL server for vCAC DB.
In the next posts I will cover all the steps required to succesfully deploy vCAC.