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

Deployment Environment Defaults

Overview

Deployment Environment Defaults is a new feature to address the following functionalities:

  • To create security around cloud defaults and at the same time, retaining the functionality of configured defaults deployment settings for each deployment environment.

  • To lock a deployment environment defaults so to ensure that defaults are not changed by end users during the deployment process.

  • To allow the flexibility to define deployment environment default configurations, but not lock them, so end users can select the default value at the time of deployment but also have the option to select any other value allowed in the list.

  • To allow the flexibility to select the allowed options at the time of deployment even if deployment environment default configurations are not defined.

  • To enable users to use network defaults provided as part of the Extensions process.

UI Behavior

See UI Behavior for additional context.

Default Options

When launching a job, the configured default settings are populated based on the deployment environment and the cloud account. If any of defaults are missing, then the user is allowed to provide the values when launching the job. You can set defaults for any of the following resources:

  • Instance types – you must manually select your default instance.

  • Cloud accounts.

    Default regions are not displayed if a user is not permitted access to those regions.

  • Network settings (VPC, subnets, availability zone, and so forth)

  • SSH keys

Restrictions

If you configure the Set Defaults details for any of these clouds, then during an Application Deployment, when configuring your cloudParams, you only need to provide the cloud region name and the instance type for each cloud.

The Deployment Environment Defaults functionality is NOT supported for SaaS/Interactive applications.

Configure Default Settings

To define default settings for your cloud, follow this procedure.

  1. Access the CCM UI and navigate to the Environments tab. The page refreshes to display the configured environments and you can edit an existing environment or add a new environment as required.

  2. Click Add Environment. The New Deployment Environment page displays.

  3. In the General Settings section:

    1.  Provide the deployment environment Name

    2. Optionally, provide a Description.

    3. Identify if approval is required to deploy to this environment by switching On the button. 

      1. On: To require the approval an authorized user for the deployment of any application to this deployment environment. 

      2. Off: Approval is not required 

  4. In the Cloud Selection section:

    1. Select the checkbox for the required Cloud Region or Container Cloud. This cloud region must be the same as the CCO cloud region (used to manage your new APIC controller extension in the above section). You can select any combination of clouds from the available clouds list.

    2. Select the Cloud Account from the dropdown list, if multiple clouds are available for this account.

  5. Click Define Default Cloud Settings. The Deployment Environment Defaults page displays for the selected cloud region and defaults to the Instance Type section. 

  6. In the Instance Type section, select the instance type(s) that you would like to make available to your end-users. 

    If you do not see the required instance type listed in this section, be sure to add the instance type first. See Manage Instance Types for additional context.

    To select the instance types for your VMware cloud region and account, follow this procedure.

    1. Select the required instance type(s) using one of three methods, each method is contained in a tab:

      • All Instance Types: This tab automatically selects all configured instance types.

      • Multiple (Range of) Instance Types: This tab allows you to filter instances types using a range selection based on Price, Virtual CPU, MilliCPUs (for Container clouds effective CloudCenter 4.9.0), Memory (GB), and Storage (MB). Effective CloudCenter 4.9.0, this field is renamed to Multiple Instance Types.

        1. Use the sliders to increase or decrease your range for each filter.  

        2. After you determine the required range, the instance types that meet that range are displayed in the Available Instance Types section. 

        3. Select one or more of the Instance Types displayed in the Available Instance Types section. To select multiple instance types, hold down the Shift button on your keyboard and click each instance type.

          • Blue = Selected instance type 

          • Grey = Available, but not selected instance type

      • Single Instance TypeThis tab allows you to filter a single instances type based on Price, Virtual CPU, Memory (GB), and Storage (MB).

        1. Use the sliders to increase or decrease your requirement for each filter.  

        2. After you determine the required filter, the instance type that meet that requirement is displayed in the Available Instance Types section. 

    2. Identify if the Hardware Information should be Visible (Default) to your end users by toggling the control switch.

    3. Identify if the Pricing Information should be Visible (Default) to your end users by toggling the control switch.

    You have now configured the instance type for your cloud region and account.

  7. Configure the Cloud Settings section and the Network Settings section for your cloud.

    If you do not see the required instance type listed in this section, be sure to add the instance type first. See Manage Instance Types for additional context.

    Once you configure the cloud settings, you have two control options to identify if the Cloud Settings should be:

    • Visible (Default) to your end users by toggling the control switch.

    • Configurable (Default) by your end users by toggling the control switch.

    Toggle the required settings as required for your deployment environment defaults.

      

    •  VMware - Cloud and Network Settings

      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:


    •  vCD - Cloud and Network Settings

      vCD Cloud Settings

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

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

      FieldDescription
      vCloud Org VDC
      Required. The name of the Virtual Data Center (VDC) in vCloud Director.
      vCloud Storage ProfilesRequired. The storage profiles to deploy the VMs.
      vCD Network Settings
      1. Select the Network in the NIC section. If you select vCD, select the OrgVdcNetwork in the NIC section. See IP Allocation Mode for additional context on NIC configuration
      2. Add additional NICs, if required.
      SSH Options

      See SSH Options for additional context.

      Back to:


    •  OpenStack - Cloud and Network Settings
      OpenStack Cloud Settings

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

      FieldDescription
      Cloud Tenant

      Multiple OpenStack tenants share cloud accounts in the CloudCenter platform. At deployment time, the CloudCenter platform allows you to select the required OpenStack tenant. You can create access key pairs in the OpenStack console so these key pairs are visible when submitting jobs using the CloudCenter platform.

      In this case, the concept of Tenant Name and Tenant ID is specific to the OpenStack cloud, not the CloudCenter platform. See OpenStack Configurations for additional context.

      Auto Select Zone

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

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

      • DisabledDefault. Can select a zone during deployment because the CloudCenter platform determines the zone for the deployment. The Availability Zone(s) settings is available and can be configured.
      • Enabled – Cannot select a zone during deployment because the CloudCenter platform determines the zone for the deployment. The Availability Zone(s) setting is NOT available and cannot be configured.
      Availability Zone(s)The default and/or additional Availability Zone(s) for this region. See Availability Sets and Zones for additional context.
      OpenStack 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 associate the public IP with the NIC.

        • ON: End users are allowed to associate the public IP with the NIC.

      2. Select the required Network in the NIC section.

      3. Select the Private IP Allocation mode in the NIC section. See IP Allocation Mode for additional context on NIC configuration.

        1. DHCP: (Default) This strategy allows the IP to be allocated by the DHCP server to the instance on server boot up. This IP address is not known prior to server boot up.

        2. Preallocate IP: This strategy allows the cloud infrastructure IP allocation to be dynamically provided before the server boots up.

      4. Add additional NICs, if required.

      Back to:


    •  IBM BlueMix (SoftLayer) - Cloud and Network Settings

      IBM BlueMix (SoftLayer) Cloud Settings

      Effective CloudCenter 4.9.0 and later, configure the fields described in the table below for IBM Bluemix cloud regions. These fields are configurable for the following features:

      FieldDescription
      Root DiskEffective CloudCenter 4.9.0, the Root Disk setting is available in the Tier Settings > Volumes section.
      Additional Volume

      This field only displays if it is configured in the application (see Application Tier Properties > General Setting > Number of Volumes and Default Volume Size for additional context).

      If configured, you will see this field populated with the relevant information. You can configure the GB size for this deployment.

      The only available type for this field is SAN disks.

      IBM BlueMix (SoftLayer) Pack Network Settings

      Effective CloudCenter 4.9.0, the Default Private VLAN & Default Public VLAN fields are not available as region-level settings when you Configure a SoftLayer Cloud. Instead, you can configure the following settings.

      Effective CloudCenter 4.9.0 and later, you have the option to configure these details:

      1. Select the required Private VLAN  and Subnet fields in the Cloud Settings section. These fields specify the default private cloud network to which this CloudCenter instance must be launched.

      2. Toggle the Visibility  switch to determine if you want to allow your end users to configure the Public IP settings.  

        1. OFF: (Default) End users are not allowed to assign the public IP.

        2. ON: End users are allowed to assign the public IP.

      3. Select the required Public VLAN and Subnet fields. These fields specify the default public cloud network to which this CloudCenter instance must be launched.

      Back to:



    •  Google - Cloud and Network Settings

      Google Cloud Settings

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

      FieldDescription
      ZoneThe default and/or additional zone(s) to be launched for this region. See Availability Sets and Zones for additional context.
      Project

      The list of projects from which you can choose network.

      If using an Shared VPC network, you have the following options:

      • Select the host project associated with your Shared VPC.
      • Select the service or the host project associated with your Shared VPC.

      The list of projects is shown for narrowing down the list of networks. The application instances will be deployed in the project associated with the cloud account.

      Network Mapping

      The name of the network that you created in the CloudCenter platform when you assigned the Google Network Settings (see the next section).

      Enable Resource ValidationToggle the switch to YES to Enable Resource Validation.
      Google Network Settings

      The NIC configuration and Simplified Networks configuration is available for both networks and sub-networks. The CloudCenter platform only supports a single NIC configuration.

      1. Select one of the configured networks retrieved from Google cloud:

        • Non-legacy Networks – Select the required network and then select the sub-network-based Google project (or the CloudCenter-specific Shared VPC host project) contained within that network.

        • Legacy Networks – Select the legacy network and the sub-network selection is no longer available.

      2. Select the checkbox to indicate if a public IP in the NIC section. See IP Allocation Mode > Cloud-Specific Nuances > Google for additional context.

      Back to:



    •  Dimension Data Cloud and Network Settings

      Dimension Data Cloud Settings

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

      AWS Network Settings
      1. Select the required option from the dropdown list for the Network Domain field. 

      2. 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 associate the public IP with the NIC.

        • ON: End users are allowed to associate the public IP with the NIC.

      3. Select the required VLAN and Public IP in the NIC section.

      4. Add additional NICs, if required (effective CloudCenter 4.9.1). 

        Each NIC must be assigned to a VLAN and only one NIC is allowed per VLAN. Firewall rules and security policies are applied to all NICs.

      Back to:

    •  Container Cloud - Kubernetes Cloud Settings

      Kubernetes Cloud Settings

      Select the Kubernetes Settings from the Namespace dropdown list, if applicable. This is a new field effective CloudCenter 4.9.0. The list is automatically populated and only requires a selection to be made. Go back to the following pages for related details.

      Kubernetes Network Settings

      Kubernetes container configurations do not require additional network settings.


    •  Azure Stack - Cloud and Network Settings

      Azure Stack Cloud Settings

      Configure the fields described in the table below for Azure Stack cloud regions (effective CloudCenter 4.9.0). These fields are configurable for the following features:

      FieldDescription
      Resource GroupThe same region as your CCO. 
      Storage Account

      The reason to create two storage accounts is that, some instance types (for example, Standard_DS1, Standard_GS1) can use the premium storage account to enhance performance and use standard storage account. The other instance type can use the standard storage account only.

      Enable Availability Set

      All VMs within a cluster are placed in the same subnet. So all VMs inside the same Availability Set are placed in the same subnet. If you do not enable the Availability Set, an availability set is NOT created. To ensure high availability, the VM(s) placement in fault/update domains are not guaranteed to be in different domains. See Availability Sets and Zones for additional context.

      Virtual NetworkBased on the Resource Group and the CCO location.
      Enable Resource ValidationToggle the switch to YES to Enable Resource Validation.
      Azure Stack 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 associate the public IP with the NIC.

        • ON: End users are allowed to associate the public IP with the NIC.

      2. Select the required Subnet in the NIC section.

      Back to:


    •  AzureRM - Cloud and Network Settings

      AzureRM Cloud Settings

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

      FieldDescription
      Resource GroupThe same region as your CCO. 
      Storage Account

      The reason to create two storage accounts is that, some instance types (for example, Standard_DS1, Standard_GS1) can use the premium storage account to enhance performance and use standard storage account. The other instance type can use the standard storage account only.

      Diagnostics

      CloudCenter users can view diagnostics provided by Azure Resource Manager from multiple places in the Azure console. The metrics and logs are stored in the related storage account.

      Microsoft has multiple settings to determine how metrics are collected (time interval) and to specify the metrics to be collected. CloudCenter uses the default Microsoft settings.

      Enable Availability Set

      All VMs within a cluster are placed in the same subnet. So all VMs inside the same Availability Set are placed in the same subnet. If you do not enable the Availability Set, an availability set is NOT created. To ensure high availability, the VM(s) placement in fault/update domains are not guaranteed to be in different domains. See Availability Sets and Zones for additional context.

      Virtual NetworkBased on the Resource Group and the CCO location.


      AzureRM 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 associate the public IP with the NIC.

        • ON: End users are allowed to associate the public IP with the NIC.

      2. Select the required Subnet in the NIC section.

      3. Add additional NICs, if required.

      Back to:

    •  Azure Pack - Cloud and Network Settings

      Azure Pack Cloud Settings

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

      Azure Pack 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 associate the public IP with the NIC.

        • ON: End users are allowed to associate the public IP with the NIC.

      2. Select the required Subnet in the NIC section.

      3. Add additional NICs, if required (effective CloudCenter 4.9.0).

      Back to:


    •  AWS - Cloud and Network Settings

      AWS Subnet and Deployment Nuances

      Pinning Behavior in AWS Network Settings

      When configuring the Deployment Environments defaults for AWS, be aware of the following nuances:

      • You have the option to select multiple subnets for the first NIC (NIC1) and among those subnets you can pin one subnet. The pinned subnet becomes the default network for this VM
      • Subsequent NICs (NIC2, NIC3, ...) only list subnets that belong to the availability zone of the pinned subnet of the first NIC. Example, in NIC1 the pinned subnet belongs to the availability zone us-west-1b, then subsequent NICs only list subnets belonging to the first NIC's us-west-1b zone.

        Multiple NICs do not span across different zones.

      AWS Availability Sets Behavior

      During a job deployment - If you launch

      • A clustered VM setup, the subnet set is passed as the job payload.
      • A single VM setup, the VM is launched as the pinned subnet.

      AWS Cloud Settings

      The Instance Profile field is optional – provide the Amazon Resource Name (ARN) used for the Instance Profile configured in your AWS Cloud account. If you specify the Instance Profile name, the CloudCenter platform launches VMs within the IAM role that is associated with the corresponding instance profile.

      The instance type disk size is for ephemeral (temporary scratch) disk, the root disk size is what specified in the VM image. Some instance types may have multiple ephemeral disks. You can change the root disk size at deployment time, if required, to a size that is higher than what is in a VM image.


      Configure the fields described in this section for AWS cloud regions. These fields are configurable for the following features:

      AWS Network Settings
      1. Select the required option from the dropdown list for the VPC field. See AWS Configurations for additional context.

      2. 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 associate the public IP with the NIC.

        • ON: End users are allowed to associate the public IP with the NIC.

      3. Select the required Network in the NIC section.

      4. The Private IP Allocation mode in the NIC section defaults to DHCP. The DHCP strategy allows the IP to be allocated by the DHCP server to the instance on server boot up. This IP address is not known prior to server boot up. See IP Allocation Mode for additional context on NIC configuration.

      5. Add additional NICs, if required.

      Back to:

    •  Alibaba - Cloud and Network Settings

      Alibaba Cloud Settings

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

      As SSH key access is not allowed into Alibaba cloud environments, you must provide the instance password as follows:

      • Linux: Provide the root password.

      • Windows: Provide the administrative password.

      Alibaba Network Settings
      1. Configure the Instance Password

      2. Select the required Subnet in the NIC section.

      Back to:

  8. In the SSH Options section, configure the following fields (see SSH Options  for additional context). 
    1. Select the Assign SSH Key checkbox to identify if the user must provide the public or private keys as part of the authorized keys for this deployment environment. 

    2. Select the Persist the Private Key checkbox to identify if the user is allowed to SSH between instances for this deployment environment .
  9. Click Done to save your Deployment Environment Defaults settings. 
© 2017-2019 Cisco Systems, Inc. All rights reserved