VMware Cloud Settings

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

Workload Manager 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.

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

FieldDescription
Root Disk

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)

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 Configure a vCenter Cloud for additional context.

DatacenterRequired. The name of the datacenter object in vSphere.

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. 

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).





Back to:

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