In keeping up with my extracurricular doc-building activities, I am happy to release the latest iteration of my vCAC implementation guide for the deployment and configuration of vCAC 6.0. This unofficial Proof of Concept and Detailed Implementation guide is provided, with no guarantees (or support), to assist with the end-to-end implementation of vCloud Automation Center 6.0 in a pre-configured vSphere 5.x environment.

The guide walks through – in plenty of detail – vCAC 6.0’s deployment, concepts, technologies, and features as they would be used in a real-world implementation. This document can also double as an unofficial hands-on training guide which covers:

– New Features in vCAC 6.0
– Deployment Architecture
– Implementation on VMware platforms (vSphere)
– IaaS and XaaS Configuration
– Usage and Navigation
– Advanced Concepts and Use Cases

vCAC 6.0 Implementation Workflow

Click to Download

 

Update (06/20/14): this is v1.1 of the guide, which includes some minor updates and fixes.  Be sure to be on the lookout for updates here or on my twitter feed.

DISCLAIMER: This guide is intended for use in a test/dev or sandbox environment and NOT for a production build and comes with no guarantees, support, etc.

Happy Installing!

++++
@virtualjad

 

19 Comments
  1. Anonymous

    good times! Thanks for throwing this together!!! will read again A+++++

  2. awesome awesome awesome!

  3. Anonymous

    brilliant work! really appreciated..

  4. Jad, 2 things to note regarding your PoC guide:

    1. You create the AD endpoint in the Orchestrator GUI, while I think you're supposed to created it in the Advanced Services Administration section of the vCAC UI

    2. When configuring the AD endpoint you configure it without SSL; this will result into a read-only AD connection; in order to actually execute a workflow that changes anything (e.g. change a user's password), you'll need to configure SSL; make sure you have an SSL certificate installed on your Domain Controller (happens automatically when you configure an Enterprise CA), then specify SSL when configuring the endpoint with port LDAP 636 or GC 3269

  5. Anonymous

    excellent work!! this should be made VMware official guide -:)

  6. Kurt Milne

    Nice summary Jad. Nice to see service catalog and catalog items as a step.

    Did you get a chance to look at API and integration to automate through vSphere? I'm curious about your take on the robustness of API set etc.

    Kurt

  7. Anonymous

    Excellent work!

  8. Anonymous

    Awesome it make poc eazy

  9. Very clear, educational and 100% hands-on vCAC filed consultants and technicians new to the product. BIG THANKS!

  10. Jad – your PoC guide is excellent and very useful out in the real world – yours and Kenny's guides saved a lot of time in upskilling from 5.x to 6.x

    as an FYI.. There is a bug that your users need to be aware of that people using this guide will run into 90 days after following this guide, there is an expiring password in the vCAC SSO/ID appliance that will mean tenants won't be able to login after 90 days.

    I blogged about it here with the workaround…

    http://vinf.net/2014/05/20/cannot-logon-to-vcac-portal-and-you-get-internal-error-when-logging-on-as-the-root-tenant/

    longer-term fix hopefully coming from VMware soon!

  11. Anonymous

    can you please share the url for downloading ur document vCloud Automation Center 6.0 POC and Detailed Implementation Guide

  12. Anonymous

    http://bit.ly/1h3dhii link is not having any document … can you please update the / link/ share the document

  13. Deploying the identity and vcac appliances sets the IP and FQDN.
    That becomes the public fqdn for users to acccess the vcac
    But my VM to VM communication is on a different internal only network.
    So after I setup the vcac appliances and install iaas components, I try add the Windows AD identity store when I add tenants.

    Problem is that vcac cannot find the AD domain because AD is on the internal only network and vcac is on the public network.

    Seems to me the vcac appliances need to have two NICs; one to for public FQDN and second for inter-VM communications in order to resolve AD domain.

    Can I manually add a second NIC to the identity and vcac appliances in order for them to find the windows AD domain?

    If not does this mean vcac only operates on one network for public and VM to VM communication?

  14. p.s. The Windows IaaS VM is joined to the Windows Domain but still when adding an AD identity store, it cannot find the AD domain…

  15. ravi

    Excellent Article !!! Thank you for publishing it.

Leave a Reply