Deployment Environments

About Deployment Environments

An environment is a resource that consists of one or more associated cloud regions and cloud accounts and that has been set aside for specific deployment needs. Users deploy applications to deployment environments, and deployment environments can be shared with multiple users.

For example, a Development environment could be associated with a development cloud and a Production deployment environment could be associated with a production grade high-performance cloud. Users on a development team would have the ability to deploy only to the Development environment and users on an operations team would have the ability to deploy only to  the Production environment.

The Environments Page 

You can add, view, manage, and delete deployment environments from the Environments page. To access this page, choose the Environments tab.

The rank sort feature to set priorities of environments is available at any time.

The Deployment Environment pages list configured information and allows you perform the actions that the following table describes.

Actions Dropdown
Description
Edit

Change configurations for an existing deployment environment. Once configured, you can only perform the following changes to a deployment environment:

  • Change the name of the deployment environment.
  • Add or change a description
  • Change the Cloud Region
  • Change the Cloud Account
  • Change the Network Settings

See the Adding a Deployment Environment section (below) for additional details.

Share

Share a deployment environment. See Deployment Environment Permissions for details.

When you create a deployment environment and share it with a user without checking the Promote from option, be aware that the Migrate action will not be available when this user deploys an application that uses this deployment environment.

Delete

Delete a deployment environment.

If you choose to delete a configured deployment environment, the Delete Deployment Environment popup to confirm your intention, deletes the configured environment, and displays a status message at the top of the Environment page.

Associate Rules

Add system tag matching rules to a deployment environment.

When you use this deployment environment to deploy an application or an application profile you can select a tag that is associated with this environment. This automatically populates the cloud account configuration information.

See System Tags for additional context.

Adding an Environment

When you add an environment, you create a new deployment environment based on configuration settings that you make. To add a deployment environment, follow these steps:

You can add multiple cloud accounts for each cloud region. You can additionally select a default cloud account for each deployment environment by clicking the Pin icon, as shown in the following screenshot.

  1. Access the CCM UI and navigate to the Environments tab. The Deployments page refreshes to display the configured environments.

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

In this form, you can configure three sections:

  • The General Settings Tab

  • The Cloud Settings Tab (includes the Default Tier Cloud Settings section)

  • The Policy Settings Tab

Each section is explained in context below.

The General Settings Tab

To configure details in the General Settings tab, follow this procedure.

  1. Provide the deployment environment Name

  2. (Optional) Provide a Description.

  3. (Optional) Configure a tag association for this deployment. See System Tags for additional details.

  4. (Optional) Configure an extension for this deployment to route approval flows through the selected extension. See Extensions for additional details

  5. (Optional) Toggle the Approval required to deploy to this environment switch. 

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

      1. If you want tenant users or user groups to request approval before deploying the environment.

      2. If an environment requires approval, users and groups with this right can approve or deny deployments. If a job is submitted but pending approval, it displays Pending in the Job Status column for this deployment. The approving user or admin can Approve or Reject the deployment by clicking the corresponding action in the Action List. Either way, a confirmation popup confirms the action. The Job Status changes from Pending to Submitted.

      3. Only the creator of the deployment needs to be granted access directly to the cloud or clouds associated with the deployment environment. This allows you to restrict other users to only deploy to approve deployment groups.

    • OFF(Default) Approval is not required.

  6. In the Cloud Selection section, select the check boxes for the required Cloud Regions and Container Clouds. This cloud region must be the same as the CCO cloud region (used to manage your new APIC controller extension in the above section).

    1. You can only select the cloud that pertains to your environment and application – you can select any combination of clouds from the available clouds list.

    2. If you select a Container-based Deployment Environment, you are presented with the list of pure container clouds or hybrid clouds which also have a configured container.

      1. Add additional Metadata for this deployment, if applicable.

      2. The Tier Settings section displays the Number of Replicas as configured for the selected application. See Resource Placement and Validation for additional context.

      3. The list of applicable tags are displays in the dropdown. Select tags, if applicable. See System Tags for additional context.

      4. See Container Service for additional details on deploying a container service.

  7. Address errors, if identified by the CloudCenter platform, and then click Next to get to the Cloud Settings tab.

The Cloud Settings Tab

The Cloud Settings tab automatically displays the applicable settings based on your cloud selection in the General Settings tab. Additionally configure the following settings:

The Cloud Settings section includes the following sub-sections:

  • Simplified Networks

  • Default Tier Cloud Settings

Simplified Networks

Configure the deployment to Use Simplified Networks (toggle switch) by adding a New Network Mapping, if required.

If multiple users have access to some regions/clouds as part of the deployment environment, be aware that these users may not be able to access all cloud accounts and regions used in deployment environments. In such cases, the Network Mapping option is disabled for these users and they will not be able to delete any existing networks, if already defined as part of the deployment environment.

The information in this section differs based on the configured cloud.

  •  VMware - Network Settings

    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 - Network Settings

    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 - Network Settings
    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 Cloud - Network Settings

    IBM Cloud Network Settings

    The Default Private VLAN & Default Public VLAN fields are not available as region-level settings when you Configure an IBM Cloud. Instead, you can configure the following settings.

    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 Environment - Network Settings

    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 - Network Settings

    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. 

      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 Clouds - Kubernetes Network Settings

    Kubernetes Network Settings

    Kubernetes container configurations do not require additional network settings.

    Back to:

  •  AWS - Network Settings

    AWS Network Settings

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

    To configure network settings for AWS environments, follow this procedure.

    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:

  •  Azure Pack - 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.

    Back to:


  •  Azure Stack - Network Settings

    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 - Network Settings

    AzureRM Network Settings

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

    To configure network settings for AzureRM environments, follow this procedure.

    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:

  •  Alibaba - Network Settings

    Alibaba Network Settings

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

    To configure network settings for Alibaba environments, follow this procedure.

    1. Configure the Instance Password

    2. Select the required Subnet in the NIC section.

    Back to:

Default Tier Cloud Settings

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.

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.

You can set defaults for any of the following resources:

  • Instance Type

  • Hardware Info

  • Pricing Info

  • Resource Placement

  • Cloud Settings

  • SSH Options

Instance Type

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.

You only see the available instance type(s) for the selected Environment(s). This is particularly visible with the use of Virtual CPUs for VM-based instance types and MilliCPUs for container-based instance types as displayed in the following screenshot. 


You can select instance types settings from one of three methods, each method is contained in a tab:

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

  • Multiple Instance Types: This tab allows you to filter instances types using a range selection based on Price, Virtual CPU, MilliCPUs (for Container clouds), Memory (GB), and Storage (MB).

    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.

Hardware Info

Identify if the Hardware Information should be visible to your end users by toggling the control switch.

  • ON: Your end users can view the configured hardware information. See Hardware Requirements for related context.

  • OFF (Default): Your end users cannot view the configured hardware information.

Pricing Info

Identify if the Pricing Information should be visible to your end users by toggling the control switch.

  • ON: Your end users can view the configured pricing information. See Financial Overview for additional context.

  • OFF (Default): Your end users cannot view the configured pricing information.

Resource Placement and Validation

Identify if the Resource Placement or  Resource Validation information should be Visible to your end users by toggling the control switch.

  • ON: Your end users can view the configured resource placement information. See Resource Placement and Validation for additional context.

  • OFF (Default): Your end users cannot view the configured resource placement information.

Cloud Settings

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

  • ON: Your end users can view the configured cloud settings information.

  • OFF (Default): Your end users cannot view the configured cloud settings information.

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

The information in this section differs based on the configured cloud.

  •  VMware - Cloud 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.

    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 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 Environments Defaults tab or from the Deployment 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).

    Back to:


  •  vCD - Cloud 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.

    Back to:

  •  OpenStack - Cloud 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.

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

    Back to:

  •  Container Clouds - Kubernetes Settings
    Kubernetes Cloud Settings

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

    Back to:

  •  IBM Cloud - Cloud Settings

    IBM Cloud Settings

    You can configure the fields described in the table below for IBM Cloud region settings. These fields are configurable for the following features:

    FieldDescription
    Root DiskThe 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.

    Back to:

  •  Google Cloud Environment - Cloud 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.

    Back to:

  •  Dimension Data - Cloud Settings

    Dimension Data Cloud Settings

    Dimension Data cloud configurations do not require additional network settings.

    Back to:

  •  Container Clouds - Kubernetes Cloud Settings

    Kubernetes Cloud Settings

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

    Back to:

  •  AWS - Cloud Settings

    AWS Cloud Settings

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

    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.

    Back to:

  •  Azure Pack - Cloud 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:

    To configure cloud settings for Azure Pack environments, follow this procedure.

    1. Select the required Subnet in the NIC section.

    2. Add additional NICs, if required.

    Back to:

  •  Azure Stack - Cloud Settings

    Azure Stack Cloud Settings

    You can configure the fields described in the table below for Azure Stack cloud regions 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.

    Back to:

  •  Azure Stack - Cloud Settings

    Azure Stack Cloud Settings

    You can configure the fields described in the table below for Azure Stack cloud regions 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.

    Back to:

  •  AzureRM - Cloud 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.

    Back to:

  •  Alibaba - Cloud 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.

    Back to:

SSH Options

One of these three SSH options must be specified for each deployment.

  • No Preference

  • Assign Public Key

  • Persist Private Kay

See SSH Options for additional context.

The Policy Settings Tab

To configure details in the Policy Settings tab, follow this procedure

  1. In the Policy Settings section, identify the following options for each policy setting, which also has the info icon displaying additional details that you may need for the next step. See Policies for additional details on each policy type.

    You cannot configure policies settings in a purely container-based deployment environment – the Policy Settings tab is disabled and greyed out for deployment environments configured with only container clouds.

    However, you can access and configure the Policy Settings information for hybrid cloud deployment environments that include containers.

    New multi-select fields enables admins to restrict what policies and tags can be selected by end users at deploy time. Admins can also set default values for policies or completely hide policy fields from users.

  2. Identify if the following settings apply to the selected policy:

    1. Should this be visible to users in your tenant (toggle switch)?

    2. Will this be the default policy (pin icon)?

    3. Do you want to make this policy Mandatory (toggle switch)?

    4. Should the Terminate Protection configuration for this policy be visible in the Deploy form (toggle switch)?

    5. In the Deploy Time Preview section, select the required time-based option for the required policies. Refer to the info icon for the required policy in the previous step to select the corresponding option. The Deploy Time Preview section is a read-only preview and only displays how the policy selection would appear during the deploy flow with the currently selected options. Users cannot perform any action using this section.

  3. Click Done to save your new deployment environment.

Multi-Site, Multi-Account Limitations

Be aware that multi-site, multi-account deployments are NOT supported in the following scenarios:

  1. When you migrate or promote deployments. See Deployment and VM States for additional context.

  2. For single-tier application (for example, interactive applications).

  3. When you use the Benchmark feature.

Multi-Site (Multi-Tier) Cloud Configuration

You can configure a multi-site deployment to enable users to deploy N-Tier applications with each tier being configure in a different cloud or in the same cloud in different segmented networks while ensuring SLA guaranty and data sovereignty. This feature allows you to use different clouds for different tiers.

While the multi-site feature is supported for all supported clouds (see What Is Supported? for a complete list), the Set Defaults functionality is only supported for AWS, OpenStack, and VMware clouds.

For example, in a 2-Tier application, the load balancer and app cluster can be in AWS or any other public cloud offering and the database can be in the private datacenter like VMware with/without ACI. This example is also applicable in cases where the two different datacenters (regions) of an enterprise is maintained as two different cloud families and the user wants the different tiers in the application to be deployed to these two datacenters or clouds.

If a deployment environment has more than one cloud selected in the Deployment page, you see a new option in the Cloud dropdown list called Hybrid. When you select this option, you can choose different instance types and provide Advanced cloud/network settings specific to the selected cloud for each tier. The following screenshot shows an example.


          

Multi-Account Cloud Configuration

You can also configure each application tier to be deployed in different cloud accounts (multi-account) within the same datacenter. The Hybrid option allows you to choose the same cloud and different cloud accounts for each tier.

For example, a datacenter admin maintains a single cloud (for example, VMware) for the entire datacenter but maintains different cloud accounts for different segments that are managed by different Cisco Application Policy Infrastructure Controllers (APICs). In this case, each tier for this application can be deployed to these different segments. The database can be deployed to the pod or segment that has stricter security policies enforced by APIC1 and the AppCluster tier can go into different pod that is managed by a different APIC2.

Migrate without Suspending Deployments

Suspension is an optional setting during the migration process. This change helps when testing your migration – without suspending your deployment.  The following screenshot highlights suspending a deployment.

If you check (unchecked by default) the  check box, the application is terminated and NOT suspended.

Restful JSON for APIs

If using the Submit Job (v2) API, you have the added advantage of completing the forms associated with the New Deployment workflow and retrieving the corresponding JSON request body for use with the API(s). The following screenshot shows an example.

The Restful JSON button (or the restful.json link) becomes available when you complete the General Cloud Settings details (with the required selection for the clouds and network settings) and you are able to proceed without any errors or missing fields in this workflow. This button generates the contents of the job deploy page before a submit operation.

This button currently displays for N-tier deployments. When you click the Restful JSON button (or the restful.json link), a popup responds with the corresponding JSON request body. You can copy the entire REST payload and paste it in your RESTClient application to issue the API call. The following image shows an example.

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