Cloud Configuration

 

See the following pages for additional information:

Add Cloud(s) for Tenants

The parent administrator can enable any parent cloud for its tenants. Tenants can only use clouds added for them by their parent or create private clouds (tenant-specific CCO).

To add cloud(s) for tenants, follow this procedure:

  1. Login as the administrator for the parent tenant and access the Sub-Tenants tab to view the list of sub-tenants.
  2. Click the Actions dropdown and select Add Clouds. The Add Clouds for User page displays.
  3. Select the check box(es) for the required clouds and click Save. This tenant administrator now has permission to Clouds for this tenant.

Windows Password Settings

The Windows-generated password is a random string of characters that includes special characters that can cause programmatic issues. Excluding the programmatically-challenging characters (single and double quotes, back slashes, and so forth) can ease the cloud configuration process.

CloudCenter 4.8.0.1 includes an enhancement where you can specify the characters to be dropped when a Windows image is configured. To use this feature, follow this procedure.

  1. Access the CCM UI > Admin > Clouds > Add Cloud as described in Configure Cloud(s).
  2. 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.

  3. Assign a cloud account Name and other details as detailed in Configure Cloud(s).

  4. In the Exclude these special characters for Windows password field.

  5. Click Save.
    You have now edited the cloud settings to exclude programmatically-challenging characters.

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.






  • No labels