Yesterday I pretty much spent a whole day attempting to install the IaaS component of vCAC 6. I’d referred to Jad El-Zien’s guide and Kendrick Coles post on the topic. I must have tried 20 times before I got it right so here are my tips to getting installed without errors on a Windows 2008 R2 Server:
- Install the vCAC VA and Identity VA as per Jad or Kendricks instructions found HERE and HERE
- Make sure when installing the above appliances that you have static IPs and DNS is solid
- Install a VM with Windows 2008 R2 SP1
- Don’t use IP6 and make sure you use a static IP address and the hostname can be resolved
- Update the VM with windows updates BUT DO NOT INSTALL .NET FRAMEWORK 4.5.1
- Reboot and restart windows update again and keep doing this until there are no updates left expect .Net Framework 4.5.1
- Browse to https://FQDN of vCAC VA:5480/Installer and download and install .Net framework 4.5
- Download the powershell script to prepare the IaaS server to speed up a lot of the steps mentioned in Jad’s guide found HERE
- Browse to https://FQDN of vCAC VA:5480/Installer and download and install setup for vCAC IaaS server as per Jad’s instructions
- And you should be good to go
On 21st (this week) I’m running my popular session on developing vSphere/vCloud .Net Apps for novice programmers. My pals over at LiquidwareLabs have offered to give me 50 USB keys with instructions to get a FREE single host copy of Flex-IO. I had the pleasure of testing the beta and in a nutshell Flex-IO allows you to create a vSphere datastore that is backed up by 16GB memory from the host. The results is >25,000 IOPs for VMs running on that datastore….
So to grab a free copy better get to my session.
So this week I finally got around to gluing my vCAC deployment with my vCloud in my home lab. I create a blueprint which is based on a VCD template for deploying a DC and an Exchange 2003 vApp. I have been on the vCAC 5.2 training course but I found it easier to follow the install guide from Jad El-Zein at http://www.virtualjad.com/ … Just to follow on from the install guide to glue vCAC and vCD I had to define the AD LDAP settings in the vCD organisation for where users who have access to the provision the blueprint. OK for sure that is obvious but makes for a nice blog post. When I say glue vCAC to vCD I’m actually referring to enable the provisioning of vCloud vApps through a vCAC blueprint.
So without configuring the LDAP setting in the respective organisations you will get the following error found in the vCAC Log View when you try to deploy your Blueprint:
To configure this you first have to login into vCloud Director as either admin at the provider level and then open the relevant origination construct or an admin of the organisation. Next Click on Administration then the LDAP menu item under Settings. In the LDAP dialog window select the Custom LDAP service then click on the Custom LDAP tab.
For me I only had to define the server address, the base distinguished name, user and password as per the above picture.
Click on Synchronise LDAP and after a few minutes click on the Test LDAP Settings
In this dialog window search of a user that has rights to your vCAC blueprint and click TEST
You should see that AD data about this user if your LDAP settings are correct.
Next we have to add a user account into the vCD org that has permissions to deploy the vCAC blueprint.
Back in the vCD organisation Administration click on Users menu item under Members and click the import users icon
In the Import Users dialog search for the user that has access to the vCAC blueprint, select the user and click the Add button.
Now when you try to deploy your vCAC blueprint it should work just fine.