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

Versions Compared

Key

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

...

  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. 

    Tip

    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 

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

    Tip

    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.

      

    • Expand
      titleVMware - Cloud and Network Settings

      Include Page
      VMware Network Settings
      VMware Network Settings

    • Expand
      titlevCD - Cloud and Network Settings

      Include Page
      vCD Network Settings
      vCD Network Settings

    • Expand
      titleOpenStack - Cloud and Network Settings
      Include Page
      OpenStack Network Settings
      OpenStack Network Settings
    • Expand
      titleIBM BlueMix (SoftLayer) - Cloud and Network Settings

      Include Page
      IBM Cloud Network Settings
      IBM Cloud Network Settings

    • Expand
      titleGoogle - Cloud and Network Settings

      Include Page
      Google Network Settings
      Google Network Settings

    • Expand
      titleDimension Data Cloud and Network Settings

      Include Page
      Dimension Data Network Settings
      Dimension Data Network Settings

    • Expand
      titleContainer Cloud - Kubernetes Cloud Settings

      Include Page
      Kubernetes Cloud Settings
      Kubernetes Cloud Settings

    • Expand
      titleAzure Stack - Cloud and Network Settings

      Include Page
      Azure Stack Network Settings
      Azure Stack Network Settings

    • Expand
      titleAzureRM - Cloud and Network Settings

      Include Page
      AzureRM Network Settings
      AzureRM Network Settings

    • Expand
      titleAzure Pack - Cloud and Network Settings

      Include Page
      Azure Pack Network Settings
      Azure Pack Network Settings

    • Expand
      titleAWS - Cloud and Network Settings
      Note
      titleAWS 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.

        Note

        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.

      Include Page
      AWS Network Settings
      AWS Network Settings

    • Expand
      titleAlibaba - Cloud and Network Settings

      Include Page
      Alibaba Network Settings
      Alibaba Network Settings

  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