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

Configure the fields described in the table below for VMware cloud regions. These fields are configurable for the following features:

The CloudCenter platform does not explicitly request the disk provisioning type for root disk or additional volumes on the virtual machines that it deploys on vCenter, to be thin provisioning, thick provisioning eager zeroes or thick provisioning lazy zeroed. The root disk provisioning type is the vCenter default which is the same format as the source template or snapshot on the VM. For additional volumes it will either be the vCenter default or the datastore default depending on the type of datastore.

CloudCenter 4.9.1 introduces the Allowed Additional Volume that was configured as specified in the Region-Level Cloud Settings > Allowed Additional Volume Sizes field

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

FieldDescription
Root Disk

Effective CloudCenter 4.9.0, the Root Disk setting is available in the Tier Settings > Volumes section on the Deployments page (not the Deployment Environment Defaults page).

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

Specify the Root disk size to be greater than the size specified in your template/snapshot.

Additional Volume (if configured)

Effective CloudCenter 4.9.1 the Regions tab for VMware vCenter environments displays two new fields:

  • Allowed Root Disk Sizes 

  • Allowed Additional Volume Sizes (allows users to delete or use the specified GB for this setting)

See Region-Level Cloud Settings for additional context.

DatacenterRequired. The name of the datacenter object in vSphere.

Either this setting is required

This field is ONLY available if the Capacity Management feature is enabled.

Auto Select Cluster

The CloudCenter platform makes this determination when you deploy from the the Deployment Environment Defaults form or from the Deployment (Job) Details (Job Submission) page.

  • DisabledDefault. Can select a cluster during deployment because the CloudCenter platform determines the cluster for the deployment. The Cluster, Datastore, and Resource Pool settings are available and can be configured.
  • Enabled – Cannot select a cluster during deployment because the CloudCenter platform determines the cluster for the deployment. The Cluster, Datastore, and Resource Pool settings are NOT available and cannot be configured. 

Or

This group of settings are required

Cluster

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

Datastore

The list of DataStores (DS) from vSphere. 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 assign the logic for the datastore 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 use VM Template when configuring images for VMware cloud environments, be aware of the following settings.


SettingDescription
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 Template. Add this Template to the CliqrTemplates folder
  • 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 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.
  • At the time of deployment, deploy to the datastore where the snapshot is present.

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
Selected

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.

The format is the same as the source template/snapshot disk format (the default when you create a VM from the vCenter UI).


Root Disk Resizable

This field is deprecated in CloudCenter 4.9.0 and later releases.

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.

Back to:


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