After receiving an email asking about automating the deployment of VCF Operations 9.0 using the OVA image, I remembered that I had previously written a blog post on this topic back in 2014. Revisiting that article, it was clear the content needed to be refreshed, especially the OVF properties used within the script.
Since I have a written (not using AI) numerous deployment scripts over the years, I was able to quickly adapt the VCF Operations 9.0 changes and also enhance it a bit further.
Here is both PowerShell (using PowerCLI) and Bash Script (using OVFTool) to automate the deployment of VCF Operations 9.0 OVA
- PowerShell - deploy_vcf_operations.ps1
- Bash - deploy_vcf_operations.sh
In addition to deploying the VCF Operations OVA, it will power on the appliance and wait for the /admin URL endpoint to be ready before completing.
Note: Since the bash script uses OVFTool, there is a hidden OVF property that allows you to enable SSH if you need. This option is not available with the PowerShell script.
For additional VCF Operations configurations post-deployment, you can refer to the VCF Operations API.
Hi Will!
Do you know if this is going to change much for VCF-9.1?
For example, are our own scripted installs going to be possible with VCF Operations 9.1, or are we really going to have to deploy VCF Installer? We only do rigid VVF deployments, and ideally only want VCSA and ESX on our systems, but cognisant that we may have to have VCF-Ops and VCF-Licensing appliances there to keep licenses alive.