// removed jquery ui css and js

Region-Level Cloud Settings

Instance Naming Strategy

If you make changes to the callouts or attributes for a Cloud Region, you must restart the CCO for the changes to take effect.

If you make changes to the macro replacements for a Cloud Region, you must re-register the CCO with the CCM for the changes to take effect.

You can configure the Instance Naming Strategy to identify callouts using a standard strategy for some clouds using one of the following options:

OptionsDescriptionSupported Clouds
DefaultThe default value provided by Cisco. A predefined token prefixed with cqjw-
CliQr Macro Replacement

Marcos specified in the Node Name Config field are set as the instance name. If you choose this strategy, you must also configure the Node Name Config field to rename a VM (node) using this macro. Your must first define the macros before specifying them.

You must restart the CCO for the Node Name Config macro to take effect.

Predefined Macros Requirements for the Node Name Config Field

Hostname CalloutHostname Callout support is available for specific clouds. Callouts are defined on the CCO so you can use the same script for these supported clouds. See Callout Scripts for additional details.

Node Name Config

The VM name should meet the following requirements for a job submission to succeed

  • Only contain the following characters:
    • a to z (lowercase only)  
    • 0 to 9
    •  The - (hyphen)
  • Start with an alpha character
  • Cannot end with - (hyphen)

The predefined macros that you can use for Macro Replacement are listed in the following table:

NameValue
%os1%First character of OS type string in lower case
%os2%First two character of os type string in lower case
%OS1%First character of os type string in upper case
%OS2%First two character of os type string in upper case
%RND<number>%

Fixed length random string, e.g., %RND10%, 10 character long random string

This is a mandatory field, only values in the range : %RND6% to %RND11% or just %RND% which defaults to %RND6%"

%UID%User ID
%VID%Vendor ID
%VM_PREFIX%

VM name prefix must be added as a global parameter in the app profile

Only macro whose value can be user customized

Instance IPAM Strategy

If you make changes to the callouts or attributes for a Cloud Region, you must restart the CCO for the changes to take effect.

Administrators can configure IPAM callouts at the cloud region level for VMware, AWS, OpenStack, Google Cloud, and vCD using one of two options:

OptionsDescription
No IPAMThis instance does not use IPAM callouts.
IPAM CalloutIf you select this option,
  • You must ensure that the IPAM callout is configured on the CCO (see Callout Scripts or InfoBlox for additional context).
  • The VMs will launch with IPs as configured by the IPAM callout.


Concurrent Node Launches

Caution

If you Edit Cloud Settings, you must save the changes to the CCO. If your CCO is already configured, you must re-register the CCO for these Cloud Settings to take effect.

CloudCenter 4.8.0.2 allows you to launch multiple VMs concurrently on a VMware cloud by configuring the number of nodes for a concurrent launch.

MAX_CONCURRENT_NODES refers to the maximum number of concurrent nodes that the CCO can handle on this cloud. You can configure the MAX_CONCURRENT_NODES in the CCO (gateway.properties file). This setting generally depends on your cloud capacity – for example, in an environment with 10 hosts, you would typically set this number to 30. Due to a vCenter session limit, exceeding this number may result in unpredictable consequences.

The valid range for the number of VMs that you can specify in the Concurrent Nodes Launches field is 1 to the number specified in the MAX_CONCURRENT_NODES setting. While the default is 30, no value is displayed in this field. The number that you specify in this field allows you to launch that many VMs at any given time. If you configure a number within this range, for example 45, you can launch 45 or less than 45 VMs concurrently. 

As the Concurrent Nodes Launches setting is applied on a per-job basis, you can concurrently launch the VM number configured in the MAX_CONCURRENT_NODES setting on each CCO server.

In a CCO HA setup, you have 3 CCO servers and each server can concurrenlty launch the MAX_CONCURRENT_NODES number of VMs.

Batch Node Launch

Caution

If you Edit Cloud Settings, you must save the changes to the CCO. If your CCO is already configured, you must re-register the CCO for these Cloud Settings to take effect.

On an OpenStack cloud, you can launch VMs in a loop or as a batch launch.

CloudCenter 4.8.0.2 supports both launch types. You can configure the batch launch parameter when you configure cloud settings for OpenStack cloud regions.

While you can specify any number of VMs in the Nodes Per Batch field, be aware that this number is completely dependent on your cloud capacity. The suggested number of VMs in this field should be limited to 50 VMs per batch as long as your cloud capacity can handle this many VMs.

While the default is 0 (loop launch), be aware that entering 1 in this field also launches the VM using the loop method. To launch using the batch method, be sure to enter a number greater than 1 in this field.

Configuration (Config) Drive

Caution

If you Edit Cloud Settings, you must save the changes to the CCO. If your CCO is already configured, you must re-register the CCO for these Cloud Settings to take effect.

CloudCenter 4.8.0.2 allows you to check a box to use the configuration (config) drive feature that is specific to OpenStack. 

This option is unchecked by default when configuring the OpenStack cloud from the CloudCenter platform. You can optionally enable the Use Config Drive checkbox if you decide to use this OpenStack-specific feature.


© 2017 Cisco Systems