Configure a VMware Cloud
To configure the logical mapping for a VMware cloud, follow this process:
Access the CCM UI > Admin > Clouds > Add Cloud in the CCM UI main menu.
Select the VMware Private Cloud option, provide a Name and Description for this cloud, and click Save.
Locate the newly-added cloud and click Add Cloud Account button to add an account for this cloud family. The Add Cloud Account popup displays.
Assign a new cloud account Name.
Select the checkbox to Track Cloud Costs.
Provide the vCenter account details.
Cloud Account Details
The IP address to be configured for this account.
vCenter User Name/Password
The credentials to access this cloud account. See the next table for the required permissions.
If vCenter users do not have full administrator rights, verify that each user (using CloudCenter) has the following permissions at a minimum:
If the default network in a template/snapshot must be changed
For persistent disk operation
Low level file operations
For user folder creation
For datastore cluster support
Assign VM to resource pool
For resource pool selection
For VM operation
Global Role Set Custom Attributes To add custom attributes on virtual machines Manage Custom Attributes
Click Save and verify that the newly added cloud is displayed in the Cloud Configurations page.
Click the Regions tab to add a cloud region.
Click Add Cloud Regions.
Select the required regions for this cloud.
Add the Region Name and an optional Display Name for this cloud region.
(Optional) Click Edit Cloud Settings.
If you Edit Cloud Settings, you must save the changes to the CCO to ensure that these changes are also propagated to CCOs inside a firewall configuration.
If your CCO is already configured, you must re-register the CCO for these Cloud Settings to take effect.
To complete the cloud configuration, you must register the CCO with the CCM.
You must set up separate RabbitMQ for each region. You cannot share RabbitMQ across cloud regions or reuse the RabbitMQ specific to a cloud region in another cloud region.Register the CCO with the CCM
Register thewith the
Cloud Region Nuances
Once you register a CCO with the CCM, the CloudCenter platform considers this cloud region to be active and you can only delete the cloud region from the CloudCenter platform under specific conditions. See Cloud Region Configuration > Delete Cloud Region for additional details.
While the example provided references the AWS cloud, be aware that the screen captures may differ for each cloud.
To register thewith the , follow this procedure:
In the Configure Orchestrator popup, provide theIP address that is accessible by and select the cloud account that is used to host the :
If you are not already at this page, verify that you are in the Configure Regions page (Admin > Clouds > Configure Regions for the required cloud).
Click Configure Orchestrator in the Regions tab.
Orchestrator IP or DNS: Provide the IP or DNS address for the CCO server.
Remote Desktop Gateway DNS or IP: The IP address of the Guacamole server (enables browser-based access to the VMs). If the Guacamole component resides in the AMQP server, provide the IP address of the AMQP server.
Cloud Account: Select the cloud account that you want to use with this CCO.
Amazon Cloud Nuance
This setting is important if you have configured an IAM Role. Be sure to select the cloud account that contains this role.
Click Save. Theand have now established a mutual trust relationship. The CloudCenter platform now manages the cloud region with the deployed .
If in HA mode while registering, provide the IP or DNS of the CCO_LB server in the Orchestrator IP or DNS field and the AMQP_LB server IP or DNS in the Remote Desktop Gateway DNS or IP field.
You have registered theVM and completed your configuration.
You have the following options at this point:
Add other cloud regions and register a CCO for each of these clouds. See Per Cloud Region (Required) for additional context.
Map your images. See Map Images for additional context.
If you need to grant permissions to launch images for your cloud account, see Image Launch Permissions.
Model, Deploy, and Manage Applications. See Application Profile for additional context.
Return to: Configure Cloud(s)