CliQr is now part of Cisco Learn More About Cisco

OpenStack Configurations

Overview

Multiple OpenStack tenants share cloud accounts in the CloudCenter platform. At deployment time, the CloudCenter platform allows you to select the required OpenStack tenant. You can create access key pairs in the OpenStack console so these key pairs are visible when submitting jobs using the CloudCenter platform.

In this case, the concept of Tenant Name and Tenant ID is specific to the OpenStack cloud, not the CloudCenter platform. 
These two fields specify the OpenStack project information (TenantName and TenantId in the APIs).

OpenStack Settings

This feature uses the following OpenStack Settings:

  • OpenStack Admin sharing multiple Projects (tenants) for deployment. In the following image, ven is the cloud account user and the ven (project) is paired up with the su (project) by the OpenStack admin. Consequently, ven can deploy applications to both projects as can su:
  • OpenStack Access & Security Key Pairs (visible in CloudCenter when submitting jobs):

CloudCenter Tenant Name or ID Deployment

When configuring cloud accounts in the CCM UI, you can provide the OpenStack project name as the Tenant Name. Alternately, you can provide the Tenant ID as well. If set, the Default Tenant ID (OpenStack setting in CloudCenter) has precedence  over Default Tenant Name (OpenStack setting in CloudCenter). Both the Default Tenant ID and Default Tenant Name fields are optional in the CCM UI. See Configure Cloud(s) > Logical mapping for an OpenStack cloud.

Key Pair Settings

CloudCenter users can select keys defined in OpenStack when launching deployments. The SSH key pairs are displayed in the CCM UI based on properties that CloudCenter retrieves from the cloud.

To view a list of keys, View Cloud Properties API.

Submitting Jobs

The OpenStack Cloud Tenant selector (visible for supported cloud families) displays the list of tenants obtained via the OpenStack identity management service (not tied to any tier).

The OpenStack CloudTenant is a universal property for the selected cloud/deployment environment (not attached to any tier).

 Availability Zones and Sets

  • UI: See the Availability Sets and Zones.
  • API
    availabilitySet
    • Description: While launching a job from the CloudCenter platform, you have the option to create an Availability Set at the tier level. All VMs within a cluster are placed in the same subnet. So all VMs inside the same Availability Set are placed in the same subnet. If you do not configure the Availability Set, an availability set is NOT created. See Availability Sets and Zones for additional context.
    • Type: Name-Value Pair
      • Name = availabilitySet
      • Value = nova,zone1
    • Example: