- 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
In my deployment I chose to go with a pre-packaged version of PostgreSQL from VMware called vFabric Postgres. My reasoning behind this was simple – I do not want another system to manage in an already complex environment… There are other benefits to using this vApp too which can be found on the VMware website here
vFabric Postgres comes packaged as a vApp from VMware. 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.
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.
Choose your vApp IP addr allocation policy.
Enter a default password for the vApp and if you chose to use a Fixed IP allocation policy you need to specify the IP address that the vApp will use.
Verify the vApp details and click on Finish to deploy the vApp.
Now comes the fun part – configuring the vApp! Logon to the vApp management interface for each of the PostgreSQL vApps. You can find the management interface here https://<FQDN of vApp>:5480
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.
Logon to the database management web console on your primary databases server. Login using the default settings & the password that you created during vApp deployment. This management interface can be found here https://<FQDN of vApp>:8443
Click on DB Login Users and create a new user for vCAC by clicking on the green (+)
Click on databases and create a database clicking on the green (+) that is owned by the new user created earlier.
Expand Databases and click on your vCAC database that was just created. Click on the Enter SQL button that is in the top right hand side of the screen.
Paste the following SQL into the text box that appears and click on execute.
CREATE EXTENSION “hstore”;
CREATE EXTENSION “uuid-ossp”;
Once the command completes close the command window and disconnect from the web client.
Now you have a server running Postgres that you can use as the external database server for this distributed vCAC installation. Finally, as this vApp is a single CPU system I chose to leverage Fault Tolerance to increase the uptime of this vApp should a ESXi host failure occur.
Trackback from your site.