You can add a vCenter cloud account for the account regions to which you want to deploy vRealize Automation cloud templates.
For network and security purposes, you can associate a vCenter cloud account with an NSX-T or NSX-V cloud account. An NSX-T cloud account can be associated to one or more vCenter cloud accounts. However, an NSX-V cloud account can only be associated to one vCenter cloud account.
- Verify that you have the required administrator credentials and have enabled HTTPS access on port 443. See Credentials required for working with cloud accounts in vRealize Automation.
- Verify that you have the cloud administrator user role. See What are the vRealize Automation user roles.
- If you are creating the cloud account for use with a remote vSphere agent (which is possible by using the Forward all traffic through proxy option), verify that you have deployed and configured a vRealize Automation extensibility (vREx) proxy on the target remote vCenter server. See How can I configure and use a vRealize Automation Extensibility proxy with a vCenter cloud account for improved vRealize Automation performance across data centers.
- Verify that you have properly configured your ports and protocols to support the cloud account. See the Ports and Protocols for vRealize Automation topic in Installing vRealize Automation with vRealize Easy Installer and the Port Requirements topic in vRealize Automation Reference Architecture Guide in the vRealize Automation product documentation.
- Select Add Cloud Account. and click
- Select the vCenter account type and enter the vCenter server host IP address.
- If you want to use a remote vSphere agent, select the Forward all traffic through proxy option and select the vRealize Automation extensibility (vREx) proxy from the drop-down menu.
After you select a vREx proxy, you must revalidate and save your user name and password credentials.
- Enter your vCenter server administrator credentials and click Validate.
All data centers that are associated with the vCenter account are data-collected.The following elements are data-collected, as are all vSphere tags for the following elements:
- Clusters and hosts
- Port groups
- Data stores
Remote vSphere agents (proxies) are also collected if they have been configured on the vCenter, see How can I configure and use a vRealize Automation Extensibility proxy with a vCenter cloud account for improved vRealize Automation performance across data centers.
You might consider using the vRealize Automation extensibility proxy option to gain a more reliable connection to a distant server, to get better processing throughput, or for network isolation reasons. To use a remote vSphere agent, where you have already met the required prerequisites for deploying and configuring a vRealize Automation extensibility (vREx) proxy, select the Forward all traffic through proxy checkbox and select the configuredvRealize Automation extensibility (vREx) proxy from the drop-down menu of available vRealize Automation extensibility (vREx) proxies. After you select a vREx proxy, you must revalidate and save your user name and password credentials.
- Select at least one of the available data centers on the specified vCenter server to allow provisioning for this cloud account.
- For efficiency, create a cloud zone for provisioning to the selected data centers.
You can also create cloud zones as a separate step according to your organization's cloud strategy.
For information about cloud zones, see Learn more about Cloud Assembly cloud zones.
- Select an existing NSX cloud account.
You can select the NSX account now, or later when you edit the cloud account.
For information about NSX-V cloud accounts, see Create an NSX-V cloud account in vRealize Automation.
For information about NSX-T cloud accounts, see Create an NSX-T cloud account in vRealize Automation.
For information about making network association changes after you have deployed a cloud template, see What happens if I remove an NSX cloud account association in vRealize Automation.
- If you want to add tags to support a tagging strategy, enter capability tags.
You can add tags now, or later when you edit the cloud account. For information about tagging, see How do I use tags to manage Cloud Assembly resources and deployments.
For more information about how capability tags and constraint tags help control deployment placements, see the Constraint Tags and Placement video tutorial.
- Click Save.
The cloud account is added and the selected data centers are available for the specified cloud zone. Collected data such as machines, networks, storage, and volumes is listed in the Resources section of the Infrastructure tab.
What to do next
Configure remaining infrastructure resources for this cloud account. See Building your Cloud Assembly resource infrastructure.
For information about converting an existing cloud account, see Convert a traditional vCenter cloud account to one based on a vRealize Automation extensibility (vREx) proxy.