Configure a Cloud and Cloud Account

  •  Configure an Alibaba Cloud

    Configure an Alibaba Cloud

    Be aware that these screen captures may change based on the Alibaba Cloud Platform changes. They are provided in this section as a point of reference.

    Prerequisites

    Before mapping an Alibaba cloud on the CloudCenter platform, verify the following Alibaba requirements:

    • A valid Alibaba Cloud Platform account.

    • Access to the following services (highlighted in orange rectangles in the image above, you must enable these services in the Alibaba cloud console):
      • Elastic Compute Service
      • Virtual Private Cloud
      • Elastic IP Address
    • Access to ID and Access Keys: Alibaba Cloud Console's AccessKeys screen:

      • Access ID: The Alibaba Cloud access key ID is the identification proof of your access to Alibaba Cloud APIs.
      • Access Keys: The 28 character, Alibaba cloud access key secret to identify this account's access parameters.
    • Account ID: Alibaba Cloud Console's Security Settings screen: This setting is required to link accounts and to download images.

    Restrictions

    Be aware of the following restrictions/limitations when configuring the Alibaba cloud:

    • The instances supported for each region differs from region to region. The Alibaba SDK and the Alibaba Web Interface differs in the instances listed for each zone. You can add new instances using the CCM UI – see Manage Instance Types for additional context.
    • Alibaba Cloud does not currently allow querying/setting user data on custom images.

      • The CloudCenter platform relies on a hosted metadata service from Cisco (mds.cliqrtech.com) to fetch user data for each instance. This requires a public IP address.

      • If the admin uses Alibaba Public Images, then the CloudCenter platform uses Alibaba’s metadata service to fetch these images.

    • The CloudCenter platform currently supports the Ultra Cloud Disks for the OS (system disks) – the Cloud Efficiency Disk configuration (this is the default setting for the Alibaba cloud). The SSD Cloud Disks option is currently not supported by the CloudCenter platform for system disks.

      However, when deploying storage types for data disks, the CloudCenter platform supports both options:

    • The CloudCenter platform supports public IP only using Elastic IP addresses. This allows users to select 0 Mbps bandwidth. When creating the Elastic IP Pool, the admin can assign maximum bandwidth for the account according to the application requirements. In the Alibaba console, select the required zone and configure this setting as required for your environment.
    • Alibaba Cloud in any region may run out of resources and is then marked sold-out (or in the case of APIs, the resource has run out) CloudCenter users must check their Alibaba’s Console and retry the operation once resource are available.
    • All instances are priced using the Pay-As-You-Go model. The CloudCenter platform does not support Alibaba’s Subscription-based Pricing Model.

      The Instance Charge Type is always Post-Paid based on the Pay-As-You-Go model.
    • The CloudCenter platform assumes that all instances are I/O optimized (default in most configurations and cannot be configured).
       
    • The CloudCenter platform does not support the Alibaba Classic Network Type – and only supports the VPC Network Type.
    • The CloudCenter platform only supports image names suffixed as follows:
      • Linux cloudinit images: Must be suffixed with 20160728, 20161115, or later.
      • Windows win images: Must be suffixed with 20160622 or later.

    Configuration Process

    To configure the logical mapping for a Alibaba cloud, follow this procedure.

    1. Access the CCM UI > Admin > Clouds > Add Cloud in the CCM UI main menu.
       
    2. Select the Alibaba Cloud Platform option, provide a Name and Description for this cloud, and click Save.
    3. Locate the newly-added cloud and click the Add Cloud Account link. The Add Cloud Account pop-up displays:

      1. Assign a new cloud name.

      2. Add the following Cloud Credentials associated with your Alibaba account and click Save.

        1. Account Email: The email address that you used to log into the Alibaba Cloud Platform account.

        2. Account Id: The Alibaba account ID for the Alibaba account as identified in Prerequisites section above.

        3. Access Id: The 16-character Alibaba Access Key ID for the Alibaba account as identified in Prerequisites section above.  
        4. Access Key: The 28-character API Access Secret for the Alibaba account as identified in the Prerequisites section above.
    4. Click the Regions tab.

    5. Click the Regions tab to add a cloud region.

      1. Click Add Cloud Regions.
      2. Select the required regions for this cloud.
      1. Add the Region Name and an optional Display Name for this cloud region.
      2. Click Save.

        The Instance Types, the Storage Types, and the Image Maps sections are automatically populated with as soon as you add the region.

    6. (Optional) Click Edit Cloud Settings to update the Alibaba cloud settings for each region.

      • Region Endpoint: Auto-populated with the selected region name.

      • Instance Naming Strategy and Instance IPAM Strategy: See the VM Name Config section for more details on configuring these values.

        Caution

        If you Edit Cloud Settings, you must save the changes to the CCO to ensure that these changes are also propagated to CCOs inside a firewall configuration.

        If your CCO is already configured, you must re-register the CCO for these Cloud Settings to take effect.

    7. To complete the cloud configuration, you must register the CCO with the CCM.

       Register the CCO with the CCM

      Register the CCO with the CCM


      Cloud Region Nuances

      Once you register a CCO with the CCM, the CCO only works for the registered cloud region.

      CloudCenter

      Once you register a CCO with the CCM, the CloudCenter platform considers this cloud region to be active and you can only delete the cloud region from the CloudCenter platform under specific conditions. See Cloud Region Configuration > Delete Cloud Region for additional details.

      While the example provided references the AWS cloud, be aware that the screen captures may differ for each cloud.

      Non-HA Mode

      To register the CCO with the CCM, follow this procedure:

      1. In the Configure Orchestrator popup, provide the CCO's IP address that is accessible by CCM and select the cloud account that is used to host the CCO:
      2. If you are not already at this page, verify that you are in the Admin > Clouds > Configure Regions for the required cloud)
        1. Click Configure Orchestrator in the Regions tab.
        2. Orchestrator IP or DNS: Provide the IP or DNS address for the CCO server.
        3. Remote Desktop Gateway DNS or IP: The IP address of the Guacamole server (enables browser-based access to the VMs). If the Guacamole component resides in the AMQP server, provide the IP address of the AMQP server.

        4. Cloud Account: Select the cloud account that you want to use with this CCO.

          Amazon Cloud Nuance

          This setting is important if you have configured an IAM Role. Be sure to select the cloud account that contains this role.

      3. Click Save. The CCM and CCO have now established a mutual trust relationship. The CloudCenter platform now manages the cloud region with the deployed CCO.

      4. Repeat Step 2 and Step 3 to establish a mutual trust between the CCM and other CCOs.

      You have registered the CCO VM and completed your configuration. You have two options at this point:

      HA Mode

      To register the CCO with the CCM, follow this procedure:

      1. Ensure that the Tomcat service is running on the Primary CCO.
      2. Login to the Secondary CCO and Tertiary CCO servers and stop the Tomcat service on both servers.

        /etc/init.d/tomcat stop
      3. Access the CCM UI and register the CCO using the CCO LB IP address.
        1. If you are not already at this page, verify that you are in the Admin > Clouds > Configure Regions for the required cloud)
        2. Click Configure Orchestrator in the Regions tab.
        3. Provide the CCO's IP address that is accessible by CCM and select the cloud account that is used to host the CCO:

          1. Orchestrator IP or DNS: Provide the IP or DNS address for the CCO server.
          2. Remote Desktop Gateway DNS or IP: The IP address of the Guacamole server (enables browser-based access to the VMs). If the Guacamole component resides in the AMQP server, provide the IP address of the AMQP server.

          3. Cloud Account: Select the cloud account that you want to use with this CCO. Be sure to select the cloud account that contains this role.

          4. Click Save. The CCM and CCO have now established a mutual trust relationship. The CloudCenter platform now manages the cloud region with the deployed CCO.
      4. After a successful registration, log into the Primary CCO server.
      5. Copy the gateway_config.properties file from the Primary CCO's /usr/local/osmosix/etc/ folder to the same location on both the Secondary CCO and the Tertiary CCO servers.
      6. Verify that the ownership and permissions for the copied file in all servers is as follows:
        • Owner = cliqruser
        • Group Permission = read and write
      7. Run the following commands to change settings – if required:

        chown 
        cliqruser:cliqruser /usr/local/osmosix/etc/gateway_config.properties
        chmod 644 /usr/local/osmosix/etc/gateway_config.properties
      8. Start the Tomcat on the Secondary CCO and the Tertiary CCO servers by issuing the following command on each server:

         /etc/init.d/tomcat start
      9. Repeat this procedure for other CCOs in HA mode to establish a mutual trust between the CCM and other CCOs.

      You have registered the CCO VM and completed your configuration. You have two options at this point:

    Return to: Configure Cloud(s)

Caution

If you Edit Cloud Settings on the Cloud Region page (CCM UI > Admin > Clouds > Configure Region), you must then save the changes to the CCO by clicking Configure Orchestrator and then Save to ensure that these changes are also propagated to CCOs inside a firewall configuration.