Moving right along (and behind schedule), Part 3 of this series will walk through the configuration of all the prerequisite requirements for the Windows-based IaaS component.
The IaaS engine is a .NET-based component that resembles (an uncanny resemblance) previous versions of vCAC 5.x. For vCAC 6.0, IaaS is consumed through vCAC’s primary framework (deployed via the vCAC Virtual Appliance) once it is installed and registered. The prerequisites for IaaS are identical to previous vCAC versions, which I’ve covered in detail in the vCAC 5.2 Detailed Installation Guide.
Review: VMware’s vCloud Automation Center 6.0 solution is made up of 3 core components:
- vCAC VA – Delivered as a Virtual Appliance (.OVA), vCAC’s primary interface for administration and user self-service. Also includes an imbedded vCO server.
- vCAC ID – Delivered as a Virtual Appliance (.OVA), vCAC’s stand-alone Single Sign-On engine, which provides multi-tenant LDAP and Active Directory authentication services for vCAC tenants.
- vCAC IaaS – Windows Installable (.exe), vCAC’s IaaS engine for heterogeneous infrastructure as a service — setup is covered in Part 3 and 4 in the series
NOTE: this video guide was created using vCAC BETA builds and some of the steps will differ from the generally-available builds. I will try to update all the videos pre-GA.…Details