Knowledge Base

Cloud Provider Accounts (CloudTest Pro)

by Community Manager on 07-07-2011 10:01 AM - last edited on 07-12-2011 08:24 AM by Community Manager

In CloudTest Pro, an additional Cloud Provider Accountsnode appears in Central > Settings. 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 > Settings > Cloud Provider Accounts is selected, the Cloud Provider Accounts list shows all currently configured cloud provider accounts.

Create a Cloud Provider Account for Amazon EC2

The following instructions presume a valid cloud provider account. Refer to the instructions provided by the cloud vendor to obtain such an account. Once valid credentials exist create a corresponding cloud provider account in Central using the instructions below.

  1. To create a new Cloud Provider Account, click New while Cloud Provider Accounts is selected in Central.
  2. The New Cloud Provider Account dialog box appears.

  1. Provide a Cloud Provider Account Name (this will appear in the Cloud Provider Accounts list in Central), as well as the necessary account configuration fields for the given cloud provider (shown in the following sections).

Specify the type and then specify the account configuration details. For EC2, the following details must be provided.
Key / I.D. – Enter a valid cloud provider key or I.D.
Secret Key – Enter the secret key for the account
Confirm Secret Key – Re-enter the secret key for the account

Configuring Access Control

Once the account is configured, add users and/or tenants via the Security section of the New 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.

Setup GoGrid as a Cloud Provider

Use the following steps to enter your valid GoGrid credentials as a CloudTest Pro 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.
Change the “Type” drop-down to “GoGrid”.

  1. Enter the GoGrid API key.
  2. To find your API key, log onto the GoGrid Management Portal (my.gogrid.com), click the “My Account” link in the upper-right corner, and then choose the “API Keys” tab. If the list is empty, click the “Add an api key” link on the left.

See the GoGrid Customer Portal < API Keys Tab topic for more information.

  1. Enter the Shared Secret.
  2. You can optionally configure an access control list to restrict which CloudTest users are able to launch GoGrid servers with this account. This step is not required if you are the only CloudTest user that will be launching servers. 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 not be able to view secure information (such as the GoGrid shared secret).
    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 GoGrid. 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 GoGrid will be automatically created, if it does not already exist. This location must be specified during Grid Manager configuration of grids (as described below). For more information about Locations, refer to Using Locations.
  

Setup Windows Azure as a Cloud Provider

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.

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

  1. Enter the Windows Azure 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 not be 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 calls to Windows Azure for each Region. 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 will be created for each Windows Azure region that you configured. This location must be specified during Grid Manager configuration of grids (as described below). For more information about Locations, refer to Using Locations.
  

0