- vCloud Automation Center – vCAC 6.0 – Overview and distributed architecture
- vCloud Automation Center – vCAC 6.0 – Generate Certificates
- My vCAC Journey: Deploy & Configure PostgreSQL
- My vCAC Journey: Deploy & Configure Identity Appliance
- My vCAC Journey: Deploy & Configure 1st vCloud Automation Center Appliance
- My vCAC Journey: Deploy & Configure 2nd vCloud Automation Center Appliance
The next step in the installation is to deploy the first vCAC appliance.
The vCloud Automation Center Appliance is a pre-configured virtual appliance that deploys the vCloud Automation Center server. The vCloud Automation Center Appliance is delivered as an open virtualization format (OVF) template. The system administrator deploys the virtual appliance into the existing virtualized infrastructure.
The server includes the vCloud Automation Center Appliance console, which provides a single portal for self-service provisioning and management of cloud services, as well as authoring, administration, and governance.
To deploy this vApp once its purchased navigate to File >Deploy OVF Template within the vSphere client. Provide a path to the ova file for the vApp and click on Next.
Click on Next
Read and accept the EULA then click on Next.
Enter a name for the vApp and choose a folder to store the VM.
Select the cluster / Resource pool that you wish to deploy this vApp into.
Select the datastore / datastore cluster that you wish to place the VM into.
Select the disk format of your choice.
Select the network to provision the vApp into.
Enter a default password for the vApp and the networking information that the vApp will use. Be sure to set the FQDN for the hostname property. Be sure to set the FQDN for the hostname property.
Verify the vApp details and click on Finish to deploy the vApp.
Before you power the appliance on
Check that “Synchronize guest time with host” is enabled in VM Properties
Right… Now turn power on the 1st vCAC vApp that you wish to configure ONLY. Do not power on any of the other vCAC vApps until you have configured this one.
Logon to this vCAC vApp over SSH using the user root and the password created during install and run the following commands;
chmod 666 /etc/vcac/setenv-core
echo ‘VCAC_OPTS=”$VCAC_OPTS -Dspring.profiles.active=default,cluster”‘ >> /etc/vcac/setenv-core
echo ‘# VCAC_OPTS=”$VCAC_OPTS -Dcluster.cache.invalidation.poll.enabled=true”‘ >> /etc/vcac/setenv-core
chmod 400 /etc/vcac/setenv-core
sed -i ‘s/acceptCount=”100″ address=”localhost”/acceptCount=”100″ address=”*”/g’ /etc/vcac/server.xml
test -s /etc/vcac/encryption.key || dd if=/dev/random of=/etc/vcac/encryption.key bs=48 count=1
Open the web management console https://vcac-va-hostname.domain.name:5480/ and login using the user root along with the password that was set during the vApp deployment.
Set the Timezone (Should be the same as all other systems in your vCAC environment).
(If necessary) set the proxy configuration to allow this VM to reach the internet for updates.
Set the vApp to check for updates on a schedule of your choice.
Connect to the postgreSQL database that was deployed & configured earlier. The message Error restarting VCAC server appears. This warning is safe to ignore, as the vCloud Automation Center server has not been started yet.
Log back onto the vCAC vApp over SSH using the user root and the password created during install and run the following commands to disable the now unneeded services;
service vpostgres stop
chkconfig vpostgres off
service vco-server stop
chkconfig vco-server off
Go back to the web management console and login using the same credentials as earlier. Click on vCAC Settings > Host Settings and click on resolve host name. The FQDN for this server should be displayed in the CAFE Host Name field. Click on Save Settings.
Click on SSL and choose to Import a PEM encoded Certificate – use the certificate info generated earlier by the powershell script, then click on replace certificate.
Identity Appliance. Enter the fully qualified domain name of the Identity Appliance with the port (:7444) at the end of the string. Do not prefix the SSO hostname with https://.
For the SSO Admin User enter [email protected], then enter the password set while configuring the Identity Appliance earlier. Click on Save Settings.
When prompted to trust the SSO certificate click on Yes.
The process of joining the vsphere.local SSO domain will take some time. In a few minutes the status should change to Connected. If this does not happen, try closing your browser and returning to the SSO configuration page to see whether it has completed successfully.
Click on Licensing, enter your vCAC license code and click on Submit Key.
Trackback from your site.