Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Configure a vCenter Region

A vCenter cloud has one region that you configure from the vCenter cloud Details tab. Follow this procedure:

  1. Navigate to Clouds page: Admin > Clouds. Find the your newly created vCenter cloud from the cloud list on the left half of the screen and click its Configure Cloud link. This displays the Details tab for this cloud as shown in the figure below.

  2. Click Edit Cloud Settings to open the Configure Cloud Settings dialog box.

    The Cloud Settings section contains fields that are unique to the vCenter cloud family and settings that are common to all cloud families. Adjust these field values per the instructions in the following tables:

    vCenter Specific Cloud Settings:

    FieldUsage
    vCenter API EndpointThis field is set to the value you set for the API endpoint when you created this vCenter cloud. You can edit it here but should only do so if the API endpoint address of your vCenter cloud has changed since you added it to CloudCenter Suite.
    VM Create Workflow

    This field has two options that can be selected from a dropdown menu:

    • "Clone, Reconfig and Customize together" (default value) and
    • "Clone, Reconfig and Customize separately".

    Choose the second option only if the default value is resulting in failures to deploy VMs.

    Concurrent Nodes LaunchesThis is the maximum number of VMs that can be launched simultaneously per application deployment. If left blank, the default value of 30 is applied. A value of 0 or 1 both mean only one VM will be launched at a time.
    Linux Max SocketsWhen the number of vCPUs assigned to a Linux VM is a prime number, Workload Manager will direct vCenter to configure the VM with that many cores on one socket. If the number of vCPUs assigned to a Linux VM is a not a prime number, Workload Manager will direct vCenter to configure the VM with X sockets of Y cores each, where X is the largest factor of the number of vCPUs which is no greater than Linux Max Sockets, and Y is vCPUs / X.

    The platform attempts to use the maximum number of sockets during deployment as well as when resizing instance types. During an application deployment:  

    • If set, the Workload Manager ensures that the number of sockets set for the VM does not exceed the number specified in the setting. 
    • If not set, the current behavior of setting the VMs vCPU as the number of sockets will continue.
    • Even if set, the Workload Manager does not use the Max Sockets setting when resizing the instance type.
    Windows Max Sockets
    Allowed Root Disk Sizes (GB)Entering a comma separated string of integers will result in corresponding options for root disk size being displayed in the deploy form.
    Allowed Additional Volume Sizes (GB)Entering a comma separated string of integers will result in corresponding options for secondary disk size being displayed in the deploy form.


    Include Page
    Cloud Agnostic Cloud Settings
    Cloud Agnostic Cloud Settings

    When you are done editing the settings in the dialog box, click Save.

  3. Include Page
    Region Connectivity - CR not required VM-based
    Region Connectivity - CR not required VM-based
  4. If any of the connectivity toggles in the Region Connectivity dialog box are set to No, then you must install and configure Cloud Remote for this region

    Expand
    titleSteps to configure Cloud Remote in a vCenter Cloud

    Include Page
    Cloud Remote for vCenter
    Cloud Remote for vCenter

  5. VM Naming and IPAM Strategy (conditional): Configure any VM naming or IPAM strategies in the Strategy section as explained in VM Naming and IPAM Strategies. If you leave the settings at the defaults, no IPAM strategy is applied and the default VM naming strategy is applied.
  6. External Lifecycle Actions (conditional): Specify any external lifecycle actions to be performed on all VMs launched by Workload Manager in this region as explained in External Lifecycle Actions Settings
  7. Instance Types (conditional): A vCenter cloud region includes one "default" instance type with 1 vCPU, 1 vNIC, 1024 MB RAM, and no additional disk storage. CloudCenter Suite will also automatically create instance types based on the parameters of VMs you deploy from within vCenter. You would manually add more instance types to your vCenter region if you want Workload Manager to deploy jobs to this region with different sized instance types. See Instance Types Settings for more details.
  8. Storage Types (conditional): For private VM-based clouds like vCenter, CloudCenter Suite uses storage types for cost tracking purposes. CloudCenter Suite creates a default storage type with zero cost. You would manually edit this storage type to enter your own cost factor. You can optionally add more storage types to your vCenter region. See Storage Types Settings for more details.
  9. Image Mappings: Image mappings allow services based on CloudCenter Suite logical images to be deployed using the appropriate physical image stored on the target cloud region. You must manually import these physical images into your vCenter region and then map the appropriate CloudCenter Suite logical images to these physical images. See Map Images for details.
Terms & Conditions Privacy Statement Cookies Trademarks