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

Configure an Azure Pack Cloud

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

Prerequisites

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

  • A valid Windows Azure Pack account with access to:

    • Azure Pack Console – Azure Pack Service Management Portal

    • SCVMM – System Center Virtual Machine Manager Console

  • An Azure Pack cloud account, network and image. If you do not have these requirements configured, do so now by connecting via RDP to the SCVMM Administrator:

    • Azure Pack Clouds (cloud account):

    • Azure Pack VM Networks (network):

    • One Azure Pack Cloud Libraries VHDX image for each OS (image) – The CloudCenter Custom Image Installation must include these custom images.

  • An Azure Pack Login ID and Subscription ID: Have these IDs ready. If you do not have these IDs ready, find them now by accessing the Azure Pack Service Management Portal:
    • Azure Pack Login ID: The ID that you use to access the Azure Pack Service Management Portal.
    • Azure Pack Subscription ID: The Subscription ID from this page.

    • Management Certificate: Upload the azure-certificate.cer file (generated by Cisco) to Azure Console > Settings > Manage Certificates.

      • SSH keys and management certificate for this account.

        Be aware that OpenSSL that is not from MacPorts, specifically OpenSSL 1.0.1f 6 Jan 2014 does not seem to create a valid SSH key-pair. Another option is FWIW.

      • Generate SSH keys using OpenSSL:

        # You may want to use another dir than /tmp
        cd /tmp
        openssl req -x509 -nodes -days 365 -newkey rsa:2048 -keyout azure-
        private.key -out azure-certificate.pem
        chmod 600 azure-private.key azure-certificate.pem
        openssl x509 -outform der -in azure-certificate.pem -out azure-
        certificate.cer
      • Generate a keystore which will be used by the plugin to authenticate with a certificate for all Azure API calls:

        # Generate a keystore (azurekeystore.pkcs12)
        # Transform private key to PEM format
        openssl pkcs8 -topk8 -nocrypt -in azure-private.key -inform PEM -out azure-pk.pem -outform PEM
        # Transform certificate to PEM format
        openssl x509 -inform der -in azure-certificate.cer -out azure-cert.pem
        cat azure-cert.pem azure-pk.pem > azure.pem.txt
        # You MUST enter a password!
        openssl pkcs12 -export -in azure.pem.txt -out azurekeystore.pkcs12 -name
        azure -noiter -nomaciter

         Fill out the Upload Management Certificate dialog information and press the done Checkmark.

        When you create the Azure Pack Region in the CCM UI, you will need to upload these files to Azure so you can run the commands from your local device or a device from which you can easily copy files.

Configuration Process

To configure the logical mapping for an Azure Pack cloud, follow this procedure.

  1. Access the CCM UI > Admin > Clouds > Add Cloud in the CCM UI main menu.

  2. Select the Windows Azure Pack 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 account name.

      Tip

      The name should not contain any space, dash, or special characters.

    2. Add the following Cloud Credentials associated with your Azure Pack account.

      1. Azure Pack Login ID: The email address used to login to your Azure Pack cloud account

      2. Azure Pack Subscription ID: To retrieve the Subscription ID

      3. Tenant ID: The UUID identified in the VIEW ENDPOINTS bullet in the Prerequisites section above.

      4. Private Key in PEM Format: Copy and paste the key information from the Azure Pack Service Management Portal identified in the Prerequisites section at the beginning of this procedure.

      5. Certificate in PEM Format: Copy and paste the certificate information from the Azure Pack Service Management Portal identified in the Prerequisites section at the beginning of this procedure.

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

  5. Click the Edit Cloud Settings link to configure the required settings for each cloud region.

    Use the default values and avoid making changes unless advised by a CloudCenter expert.

    • Azure Pack Network: The SCVMM console's Azure Pack VM Networks (network) listing identified in the Prerequisites section above. Copy the name exactly as displayed in the SCVMM console and paste it into this field. This field is deprecated in CloudCenter 4.9.0.

    • Azure Pack Data Disk: The SCVMM console's Azure Pack Cloud Libraries VHDX (image) data disk listing identified in the Prerequisites section above.

      This Data Disk configuration is only required if you are configuring additional volumes.

      Image Mapping

       These instructions are for a blank disk

      For Azure Pack, you cannot specify Multiple Volumes in the Application Tier Properties (General Settings) Default Volume Size field. Instead, you must use a Blank Disk (you cannot change the size) as follows:

      1. Access the SCVMM console's Azure Pack Cloud Library

      2. Click Library Servers.

      3. Click the VHDX folder

      4. Identify the required Blank Disk.

      5. Right-click this Blank Disk and select Properties. The Properties popup for this Blank Disk displays.

      6. The name is automatically displayed.

      7. In the Family field, you must assign a name of your choice – If you do not provide this format the configuration does not complete successfully.

      8. In the Release field, you must provide 4 numbers separated by three periods (for example: 1.2.3.4). This precise format is required as the identifier for this disk – If you do not provide this format the configuration does not complete successfully.

      9. In the Operating system field, you must select CentOS6.

        This precise format is required when you Map Images – You must provide the exact OS specified in this field. If you do not provide this format the image mapping configuration does not complete successfully.

      10. Click OK to save your changes.

      11. The SCVMM console's Equivalency Information section is updated with this new information.

      12. In the CCM UI's Azure Pack Data Disk field, you need to add these two details in the following format:

        BlankDisk:0.0.0.0

        If you do not provide this format the configuration does not complete successfully.

       These instructions are for a normal disk

      To map images for a normal disk, follow this procedure.


      1. Access the SCVMM console's Azure Pack Cloud Library

      2. Click Library Servers.

      3. Click the VHDX folder

      4. Identify the required Disk.

      5. Right-click this Disk and select Properties. The Properties popup for this Disk displays.

      6. The name is automatically displayed.

      7. In the Family field, you must assign a name of your choice – If you do not provide this format the configuration does not complete successfully.

      8. In the Release field, you must provide 4 numbers separated by three periods (for example: 1.2.3.4). This precise format is required as the identifier for this disk – If you do not provide this format the configuration does not complete successfully.

      9. In the Operating system field, you must select CentOS6.

        This precise format is required when you Map Images – You must provide the exact OS specified in this field. If you do not provide this format the image mapping configuration does not complete successfully.

      10. Click OK to save your changes.
      11. The SCVMM console's Equivalency Information section is updated with this new information.
      12. In the CCM UI's Azure Pack Data Disk field, you need to add these two details in the following format:
        Exact_Family_Name:Release
        If you do not provide this format the configuration does not complete successfully.
      13. Add the Exact_Family_Name:Release details as the Cloud Image ID in the CCM UI.
    • Endpoint: The exact DNS name and the port used for the SCVMM console.
      For example: wap1.dcv.svpod:30006

    • Metadata Server: You can use the default metadata server provided by Cisco (mds.cliqrtech.com) or build and use your own metadata server.

    • Domain: The domain in which the Azure Pack server resides. Check with your Azure Pack domain admin for the exact name for this domain.

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

    Registration Process

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

    1. In the Configure Orchestrator popup, provide the CCO 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 Configure Regions page (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.

      If in HA mode while registering, provide the IP or DNS of the CCO_LB server in the Orchestrator IP or DNS field and the AMQP_LB server IP or DNS in the Remote Desktop Gateway DNS or IP field.

    You have registered the CCO VM and completed your configuration.

    Next Steps

    You have the following options at this point:


Return to: Configure Cloud(s)

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