Configure an OpenStack Cloud
To configure the logical mapping for an OpenStack cloud, follow this procedure.
Access the CCM UI > Admin > Clouds > Add Cloud in the CCM UI main menu.
Select OpenStack, provide a Name and Description for this cloud, and click Save.
Locate the newly-added cloud and click Add Cloud Account to add an account for this cloud family.
Click Add Cloud Account to add an account for this cloud family. The Add Cloud Account popup displays.
If OpenStack users do not have full administrator rights, verify that each user (using CloudCenter) has access credentials at a minimum.
Cloud Account Details Description OpenStack User Name/Password The credentials to access this cloud account. Default Domain Name (V3) Optional. When you add an OpenStack cloud account, you can choose V2 or V3 OpenStack endpoints:
Not required if you use V2
If you use V3, provide either the default Domain ID or Default Domain Name.
The cloud region setting validates the region.
Default Domain ID (V3)
Default Tenant Name (V3 Project Name)
Optional. The OpenStack project name.
Default Domain ID (V3 Project ID) Optional. If set, the Default Tenant ID (OpenStack setting in CloudCenter) has precedence over the Default Tenant Name.
Assign a new cloud account Name.
Select the check box to Track Cloud Costs.
Provide the OpenStack user credentials.
Optional. You can add the Domain ID and Domain Name to configure an OpenStack domain that uses their V3 APIs. If you select a V3 API domain, provide the Domain ID or the Domain Name.
Click Save and verify that the newly added cloud account (see Cloud for additional context on terminology) is displayed in the Clouds page.
Click the Configure Cloud link. The Accounts tab in the Cloud Accounts page displays all configured cloud accounts.
- 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.
Click the Edit Cloud Settings link to update the settings for each cloud region.
Region (the region must be a valid OpenStack region)
- OpenStack Keystone API Version (the dropdown list includes both v2 and v3 options – select one of these options)
OpenStack Keystone Authentication Endpoint (this setting is not available in the Cloud Account popup, it is only available in the Cloud Region popup)
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 update the Use Config Drive and Nodes Per Batch fields, see Cloud Configuration.
Effective CloudCenter 184.108.40.206, you can also configure the Bootable Volume Mapping Required field.
This field has the following choices:
Default: Use this option if your native OpenStack configuration supports the Create Servers OpenStack API.
No Blocked Device Mapping Required for Launch: Only use this option if OpenStack is configured along with a third-party infrastructure that is not visible to the CloudCenter platform – if your native OpenStack configuration does not support the Create Servers OpenStack API (with bootable volume mapping).
To complete the cloud configuration, you must register the CCO with the CCM.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)