Configure an Azure Stack 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 Stack cloud, verify the following requirements:

  • You have a valid Windows Azure Stack account.

    The CloudCenter platform supports both Azure Stack Development Kit and Azure Stack Integrated Setup models. The CloudCenter documentation reflects screen captures of both portals.

  • The Azure Stack portal is similar to https://portal.local.azurestack.external.

  • The Azure Stack endpoints differs based on your Azure Stack launch mode (online of offline). The endpoint is similar to https://management.local.azurestack.external. Be aware that you can change the endpoint after you configure the cloud settings as well.

    • Online Setup: The AD endpoint authentication request is routed via the login.windows.net endpoint.

    • Offline Setup: In this setup, the ADFS authentication is completely disconnected from the Internet.

  • The Azure Stack endpoint differs based on your Azure Stack launch mode (online of offline) – issue the following API (similar to the endpoint highlighted in the orange rectangle)  to retrieve the endpoint (highlighted in blue – the AD Resource is required for authentication). The audiences parameter contains the AD Resource ID.

  • The Region entry is highlighted in the orange rectangle in the Azure Stack Dashboard image provided below – this region information is required when you configure the Azure Stack cloud in the CloudCenter platform,

    You must use this same region name when configuring the Region Name in the Regions tab Cloud Settings as highlighted in the orange rectangle in the following image:

  • You can retrieve the Suffix from the following location in the Azure Stack portal (Virtual machines > Disks > OS Disks):

  • Use the same Default API version that is used in your current setup for the Microsoft.Resource and locate the Resource Type Name (see https://docs.microsoft.com/en-us/azure/azure-stack/user/azure-stack-vm-considerations for additional details).

  • For the VM Extension Version fields (Linux Custom Script, Windows Custom Script, and Linux Diagnostic), use only the first two numbers (just the major version number and the minor version number, not the maintenance version nor the build version numbers) in the version string – if you use earlier or later versions or additional numbers, the configuration may not succeed.

  • Register the required Azure providers from the Azure Stack portal:

Configuration Process

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

  1. Access the CCM UI > Admin > Clouds > Add Cloud in the side pane.

  2. Select the Microsoft Azure Stack 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 account.

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

      2. Azure Subscription ID: To retrieve the Subscription ID, toggle to the Azure Portal Interface as described in the Prerequisites section above and access Settings:

      3. Tenant ID: The Tenant ID is the Directory ID found in Azure Portal > Azure AD > Properties. See the Microsoft Azure documentation for details.

      4. Client ID: The Client ID is the Application ID found in Azure Portal > Azure AD > App Registrations > <your_app>, where <your_app> is the Azure Active Directory application associated with your Azure Stack instance. See the Microsoft Azure documentation for details.

      5. Client Key: The Client Key is the app authentication key found in Azure Portal > Azure AD > App Registrations > <your_app> > Settings > Keys, where <your_app> is the Azure Active Directory application associated with your Azure Stack instance. See the Microsoft Azure documentation for details.

    3. Click Save and verify that the newly added cloud account (see Cloud for additional context on terminology) is displayed in the Clouds page.

    4. Click the Configure Cloud link. The Accounts tab in the Cloud Accounts page displays all configured cloud accounts.

  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.

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

  5. (Optional) Click the Edit Cloud Settings link to update the required settings for each cloud region.

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

    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.

    1. Azure Stack Region Name: The Region entry in the Azure Stack Dashboard image. In the example provided in the Prerequisites section above, this entry displays local.

    2. Azure Stack RM Endpoint: The Azure Stack endpoints differs based on your Azure Stack launch mode (online of offline). The endpoint is similar to https://management.local.azurestack.external. You can change the endpoint after you configure the cloud settings as well.

    3. Azure Stack AD Endpoint: The AD endpoint authentication request is routed via the login.windows.net endpoint.

    4. Azure Stack AD Resource: The audiences parameter explained in the Prerequisites section above contains the AD Resource ID.

    5. Azure Stack Storage Endpoint Suffix: The Suffix from the Azure Stack portal explained in the Prerequisites section above.

    6. Default API version: The same API version that is used in your current setup as explained in the Prerequisites section above.

    7. Linux Custom Script Extension Version: Use only the first two numbers (just the major version number and the minor version number, not the maintenance version nor the build version numbers) in the version string as explained in the Prerequisites section above.

    8. Windows Custom Script Extension Version: Use only the first two numbers (just the major version number and the minor version number, not the maintenance version nor the build version numbers) in the version string as explained in the Prerequisites section above.

    9. Linux Diagnostics Extension Version: Not Supported.

    10. Windows Diagnostics Extension Version: Use only the first two numbers (just the major version number and the minor version number, not the maintenance version nor the build version numbers) in the version string as explained in the Prerequisites section above.

    11. Instance Naming Strategy and Node Name Config: The Region-Level Cloud Settings section provides more details on configuring these values. The instances are directly pulled from the Azure Stack instance. You can Manage Instance Types as required by you environment.

    12. Click Save.

  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)

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