I finally got some time to update my Automated VMware Cloud Foundation Lab (VCF) Deployment script to support the latest VCF 5.1 release as this has been requested by a number of folks both internally and externally.
In addition to updating some of the new resource requirements such as increasing the Nested ESXi vSAN capacity drive from 60GB to 100GB, I was also thinking about some of the feedback that I had received internally from one of our engineers and that gave me some ideas on how to further stream the deployment using automation. I also came up with a few new ideas that I have added to the script, some of which I will cover in a future blog post 😁
The script is doing more than just deploying the required Nested ESXi VM, but it will actually generate the VCF commission host file (JSON) that can then be used make SDDC Manager aware of the new ESXi hosts, which can then be used to deploy a Workload Domain.
While the previous version of the script already generated the required VCF Management Domain bringup file (JSON) based on your input, the VCF Bringup was performed manually by logging into the Cloud Builder UI and uploading the generated JSON file to begin the deployment. I have now enhanced the script to automatically wait for the Cloud Builder VM to be ready and then automatically initiate the VCF Bringup using the generated JSON, so there are no additional manual steps required other than opening a browser to the Cloud Builder URL to monitor the progress of your VCF deployment!
In my environment, the deployment of the 8 x Nested ESXi VM, Cloud Builder VM and initiating the bringup process took ~19minutes and then it took another ~1.5hrs for the complete VCF Management Domain to be fully deployed and configured. YMMV based on your available resources
Hopefully folks apperciate the additional simplicity of using this script and if you have any feedback, feel free to drop a comment here or better yet, leave a comment directly in the repo or even submit a PR. For the complete list of changes in the script, be sure to check out the change log section of the README in the repo. Enjoy!