CloudCenter 4.8 has reached End of Life (EOL) as of November 14, 2018. See End of Support Notices for additional context.
VMware Cloud Settings

The following fields are available for VMware cloud regions.

Select the required option from the dropdown lists for each field identified in the following table:

DatacenterRequired. The name of the datacenter object in vSphere.

Required.The name of the server group in this datacenter's virtual environment in vSphere where you want to deploy VMs.


The list of DataStores (DS) from vSphere. Effective CloudCenter 4.8.0, you can select both the datastore cluster and the the DS if DRS is disabled. When you select a Datastore cluster, if DRS is:

  • Disabled – Select a Datastore deployment from a dropdown menu or leave the DS un-selected so the CloudCenter platform can make a random selection.
  • Enabled – The Datastore dropdown is disabled and neither you nor the CloudCenter platform can make any selection.
Resource PoolThe default computing resources used to manage resource allocations between VMs. Use the default source pool name from vSphere where you need to deploy instances.
Target Deployment Folder

The default folders used to group objects of the same type for  management and VM deployment.

Enable Full Clone

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 use VM Template when configuring images for VMware cloud environments, be aware of the following settings.

Full Clone
  • Use if deploying to a different VMware cluster from the worker image.

  • Use if you select an image that is mapped to a VM Template.
  • The full clone operation is performed on the source VM or VM template, the cloned VM can be on either datastore or datastore cluster that you specify.
  • You can use the Full clone option for both Snapshots and VM Templates.
Linked Clone
  • Use if the image is mapped to a snapshot.
  • Add a folder in vSphere (to store your CloudCenter snapshots), name it CliqrTemplates, and add this snapshot to the CliqrTemplates folder.

When you use a Snapshot, both the Linked Clone and Full Clone options are possible settings. See Configure Image IDs for additional context.

To configure these settings, you should have already configured the following entities in VMware:

  • A VMware cluster
  • A datastore cluster

To configure the clone settings in the CloudCenter platform, select the Enable Full Clone (linked clone) checkbox

Full Clone SettingDescription

CloudCenter creates a full disk clone of the VM.

If the root size reflects the same size as the template, be sure to resize the partition once the instance is up and running.

Not Selected (default)CloudCenter creates a thin clone which is faster but relies on the original VM disk being available in its original location.

Root Disk Resizable

You can only select the Root Disk Resizable if the Cloning Mode is set to Full Clone (Enable Full Clone = Selected).

This feature is only available for VMware VMs.

The CloudCenter platform provides the capability to resize the root disk for VMware VMs by a configurable setting to specify the root disk size based on the OS type. This configuration setting is similar to the data store cluster setting.

When you initially provision the VM, you can define the base OS disk size in the instance type configuration for each VM. A default VM includes a base (root) OS disk and an ephemeral disk. Some enterprises may have a requirement in place to only use one disk instead of both disks.

You can only increase (not reduce) the VM root disk size – The new root disk size should not be smaller than the default root disk size.

For example, if the root disk size is 250 GB, then you can only resize the instance type to be greater than 250 GB. The instance size in this case cannot be less than 250 GB.

  • Enabled: When you specify the Instance Type Storage for a deployment and if this setting is greater than the configured root disk size in the template or snapshot, then the root size of the deployed VM will be set to the size specified in the instance type.

    The additional space is not formatted or partitioned by CloudCenter. Use the Node initialization script to perform these tasks.

  • Disabled: When this option is disabled, an additional disk with the specified size is created in the instance type.

VMware Network Settings
  1. Toggle the Visibility  switch to determine if you want to allow your end users to use pre-configured settings.  

    • OFF: (Default) End users are not allowed to use preconfigured ACI extensions.

      1. Select the Network in the NIC section. See IP Allocation Mode for additional context on NIC configuration.

      2. Add additional NICs, if required.

    • ON: End users are allowed to use preconfigured ACI extensions.

      1. Select the required extension, the corresponding options are displayed in the dropdown list for the remaining fields (see Extensions for additional details):

      2. Select the APIC Extension from the dropdown list (see ACI Extensions for additional details).

      3. Select the APIC Virtual Machine Manager (VMM) associated with this APIC Extension from the filtered dropdown list .

      4. Select the APIC Tenant associated with this APIC Extension from the filtered dropdown list.

  2. Select the Network in the NIC section.

    • If you select VMware, select the Network in the NIC section. See IP Allocation Mode for additional context on NIC configuration.

    • If you select Cisco ACI, select the type in the End Point Group (EPG) Type field.

      1. Existing EPG: If you select this type, you must further select a pre-existing EPG (that is already connected to one of the Bridge Domains) from the Existing EPG dropdown, which appears if you select this type.

      2. New EPG: If you select this type, you must further select a pre-existing Bridge Domain (to which this EPG must connect) from the Bridge Domain dropdown list.

      3. Bridge Domain Template: See Extensions for additional context.

  3. Add additional NICs, if required.

SSH Options

See SSH Options for additional context.

© 2017-2019 Cisco Systems, Inc. All rights reserved