vCloud director 9.7 appliance deployment step by step guide
With the new vCloud director releasing and making it full appliance with embedded vpostgres, I though I will put up a post with the complete installation guide. There have been some challenges in the getting the deployment successful.
- Reverse DNS proxy must be configured for the eth0 ipaddress. This is to get the correct hostname for the appliance.
- The NFS share is setup for the VCD transfer directory.
- It is recommended to have the eth0 and eth1 in different subnets. eth0 is for the vcd cell and eth1 is for the vPostgres .The reason for the having 2 subnets is to avoid duplicate entries in the route table.
Installing vCloud director step by step guide :
- I should ideally be using different submets as per the VMware documentation but since I do not have a different portgroup setup, I am going with the same subnet.
- As mentioned in the prereq section, the reason for the having 2 subnets is to avoid duplicate entries in the route table
- Here we come to the main section. The NTP server in my case is the DNS server.
- Set the initial root password. You will have to remember this as this is going to be the password for the VCD certificate keystore.
- Deselect the Expire root password if you would like to retain the same root password entered above
- Enter the NFS share directory. In my case, I have enabled the NFS service in the SQL server and sharing a folder from there (Don't get confused with the hostname sql.wecloud.lab)
- Below is how I have got the NFS configured
- The Network routes are only required if the eth0 or eth1 has to talk to external servers like NFS share and requires a different route. In my case, all the servers are on the same subnet.
- The Domain name here is not the hostname of the VCD cell. It is just the Domain search path. I understand there is another section for the domain search path and that is for more narrowed search.
- For example, Domain name can be like wecloud.lab and Domain search Path is cloud.wecloud.lab
- Enter the network inteface IPs and its gateway and subnet.
- Once the deployment is complete, go ahead and Power On the VM
- If the firsboot script runs without any issues, the service would start automatically and your Cloud portal should be available to access.
As you can see , the hostname is also updated.
- ovfenv is a command that you can use to view the entries passed during the deployment of the appliance.
Some of the log files that you can check in case of the deployment failures are:
Some screenshots below on how the successful deployment would like :
Cheers : )
Hope it helps !!!