Windows Azure (IaaS) Support - deprecated

Document created by Chris Sommerstad Employee on Jul 20, 2017Last modified by Dave Murphy on Aug 14, 2017
Version 3Show Document
  • View in full screen mode

Setup Windows Azure as a Cloud Provider

In CloudTest Pro/Enterprise, an additional Cloud Provider Accounts node appears at Central > Cloud. Users with Cloud Provider Accounts can use this node to configure those accounts for use in testing for use with CloudTest Pro. CloudTest currently supports Amazon EC2, GoGrid, and Windows Azure accounts.

When Central > Cloud > Cloud Provider Accounts is selected, the Cloud Provider Accounts list shows all currently configured cloud provider accounts.

To use Windows Azure from CloudTest Pro, you will need the following:

  • The Windows Azure subscription ID. This is available in the Windows Azure Management Portal.
  • A Windows Azure management certificate for API access. This is not the same thing as a service certificate, which is used to enable HTTPS access to a Windows Azure hosted service. To learn more about creating a management certificate, see http://technet.microsoft.com/en-us/magazine/gg607453.aspx.
  • A dedicated hosted service and a storage account in each Region that you wish to use. These must be created in advance, using the Windows Azure Management Portal. You will need the Storage Name and Key to configure IaaS regions.

Use the following steps to create a Windows Azure Cloud Provider Account.

  1. Select Central > Cloud Provider Accounts and then click New to launch the Cloud Provider Account dialog box.
  2. Enter a name for the account. This name will be populated to the Cloud Provider Account field in the Grid Manager (as well as the automatically created Location(s) that correspond to this Windows Azure account).
  3. Change the “Type” drop-down to “Windows Azure (IaaS)”.

  1. Enter the Windows Azure (IaaS) subscription ID.
  2. Browse to locate the API Certificate file for upload.
  3. If the API certificate is protected by a password, then enter the Certificate Password and then enter it a second time in the Confirm Password field.
  4. For each Region that you wish to use:
    1. Check the box in the list on the left.
    2. On the right, enter the URL Prefix (a.k.a. “DNS Prefix”) of the dedicated hosted service to use for this Region, the dedicated storage account name, and the storage access key.
  5. You can optionally configure an access control list to restrict which CloudTest users are able to launch Azure servers with this account. This step is not required if you are the only CloudTest user that will be launching servers.
 
  1. To configure an access control list:
    1. Select the CloudTest user you want to grant access to in the drop-down at the bottom of the dialog.
    2. Click the Add button.
    3. A new row will appear in the list above the drop-down.
    4. To allow the user to view the Cloud Provider Account object (but not necessarily use it), check the Read box. Note that even with this box checked, the user will notbe able to view secure information (such as storage access keys).
    5. To allow the user to modify, delete, or re-name the Cloud Provider Account, check the Write box.
    6. To allow the user to launch new servers using this Cloud Provider Account, check the Use box.
    7. Repeat steps a-f for each CloudTest user that you want to grant access to.

  1. Click OK to complete configuration of the Cloud Provider Account. The account information will be validated by issuing a call to Azure. If the credentials are invalid, a warning will be shown. You can choose to go back and correct the credentials, or continue.
  2. After the Cloud Provider Account is saved, a new Location for each Azure data center will be automatically created, if it does not already exist. Refer to Using Locations.

Setup Windows Azure (IaaS) as a Cloud Provider

In CloudTest Pro/Enterprise, an additional Cloud Provider Accounts node appears at Central > Cloud. Users with Cloud Provider Accounts can use this node to configure those accounts for use in testing for use with CloudTest Pro.

When Central > Cloud > Cloud Provider Accounts is selected, the Cloud Provider Accounts list shows all currently configured cloud provider accounts.

To use Windows Azure (IaaS) from CloudTest Pro, you will need the following:

  • The Windows Azure subscription ID. This is available in the Windows Azure Management Portal.
  • A Windows Azure management certificate for API access. This is not the same thing as a service certificate, which is used to enable HTTPS access to a Windows Azure hosted service. To learn more about creating a management certificate, see http://technet.microsoft.com/en-us/magazine/gg607453.aspx.
  • A dedicated hosted service and a storage account in each Region that you wish to use. These must be created in advance, using the Windows Azure Management Portal. You will need the Storage Name/Key pair for each region you wish to configure.

Use the following steps to create a Windows Azure Cloud Provider Account.

  1. Select Central > Cloud Provider Accounts and then click New to launch the Cloud Provider Account dialog box.
  2. Enter a name for the account. This name is used in locations and also appears in the Cloud Provider Account drop-down in the Grid Manager.
  3. Change the “Type” drop-down to Windows Azure (IaaS)”. .

 

Note:  As a part of enabling Azure IaaS grid deployment for non-SOASTA Azure accounts, the process now copies CloudTest images from the SOASTA Azure account into the storage accounts specified in the CPA before deploying servers using these images. 

  1. Enter the Windows Azure (IaaS) subscription ID.
  2. Browse to locate the API Certificate file for this service.

Note: The Windows Azure (IaaS) certificate file must be in PKCS12 format, and must include both the certificate and the private key. As a part of supporting Azure IaaS grid deployment for non-SOASTA Azure accounts, the process copies CloudTest images from the SOASTA Azure(IaaS) account into the storage accounts specified in the CPA before deploying servers using these images. 

  1. Enter the corresponding Certificate Password and then enter it again in the Confirm Password field.
  2. Check each Region you wish to configure and provide the Storage Account Name and Storage Access Key to useand then provide the key a second time to confirm.
  3. You can optionally configure an access control list to restrict which CloudTest users are able to launch Windows Azure (IaaS) servers with this account. This step is not required if you are the only CloudTest user that will be launching servers.
 
  1. To configure an access control list:
    1. Select the CloudTest user you want to grant access to in the drop-down at the bottom of the dialog.
    2. Click the Add button.
    3. A new row will appear in the list above the drop-down.
    4. To allow the user to view the Cloud Provider Account object (but not necessarily use it), check the Read box. Note that even with this box checked, the user will notbe able to view secure information (such as storage access keys).
    5. To allow the user to modify, delete, or re-name the Cloud Provider Account, check the Write box.
    6. To allow the user to launch new servers using this Cloud Provider Account, check the Use box.
    7. Repeat steps a-f for each CloudTest user that you want to grant access to.
    1. Click OK to complete configuration of the Cloud Provider Account. CloudTest will issue a call to validate the Windows Azure (IaaS) account. If the credentials are invalid, a warning will be shown. You can choose to go back and correct the credentials, or continue.
    2. After the Cloud Provider Account is saved, new Location for Windows Azure (IaaS) will be automatically created and will appear in the Central > Locations list (e.g. if they do not already exist). Refer to Using Locations.
    3. One or more of these locations must be specified during Grid Manager configuration of grids:
      • Windows Azure (IaaS) Asia East
      • Windows Azure (IaaS) Asia Southeast
      • Windows Azure (IaaS) Europe North
      • Windows Azure (IaaS) Europe West
      • Windows Azure (IaaS) US East
      • Windows Azure (IaaS) US West

 

Access Control Configuration

Once the account is configured (for any cloud provider), add users and/or tenants via the Security section of the Cloud Provider Account dialog box.

    • Security

Configure permissions per User / Tenant. Each user (per tenant) can have Read, Write, and Propagate access control permissions.

    • Read

The user/tenant can view the Cloud Provider Account but not edit or execute tests.

    • Write

The user/tenant can view and edit the Cloud Provider Account.

    • Use

The user/tenant can view, edit, and use the Cloud Provider Account to launch Grids and Results Databases.

    • Add

Click Add to include users or tenants in the Security list and then configure permissions per user or tenant.

Note: Once configured, the Cloud Provider Account name is specified prior to runtime via the Grid Manager > Server Instances page.

If the wrong credentials are used here deployments in the Grid Manager that use this cloud provider account will fail.

Attachments

    Outcomes