Keywords: General - Virtual Machines - How to - Other
After finding a number of your appliances through the VRealize Automation Marketplace, I began talking to our analytics team and they are interested in using them for testing. Because this would be various virtual machines being created and destroyed after they served their purpose, vRealize Automation is the perfect method for deployment.
I have run into a snag during deployment that stops me from being able to release this for their use. Also please note, we will be using these machines on-premise only, no cloud deployments are allowed due to the nature of our business.
When an appliance (the ova) is selected for deployment, it gives no option for giving it an internal IP address. If the OVA is deployed anyway, it only has an IPv6 address available. Our vRA is configured to automatically give an IP address to a deployed virtual machine but this doesn’t work for any of the bitnami appliances.
We are currently using vRA 8.4 and have NSX-T 3.1.1 and are running VMware 7.0.1
If its something I am overlooking in vRA, I’m happy to go back and look, I just can’t figure out how to automatically give this OVA an internal IP that is not bridged for VMware Workstation or is designed for the cloud.