Cloud Provider Account Support for Rackspace (OpenStack)

Document created by Chris Sommerstad Employee on Jul 20, 2017Last modified by Jijius Jabez on Aug 11, 2017
Version 2Show Document
  • View in full screen mode

Setup Rackspace or Rackspace (OpenStack) 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.

Use the following steps to enter your valid Rackspace credentials as a CloudTest Pro/Enterprise 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. 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 “Rackspace Cloud (OpenStack)”. The dialog box changes to reflect the available Rackspace data centers (e.g. a tab for DFW1 or another location appears).
  1. Check the box for the first Rackspace cloud site this account uses and then enter the Rackspace Account Name and API key, and then enter the API key a second time in the Confirm API key field. Repeat this step if other Rackspace data centers will be used with this account.
  2. To find your API key, :
    1. Log in to the Rackspace Cloud management portal.
    2. Click the Your Account sidebar link, and then API Access in the sub-menu that appears.
    3. Click the "Show Key" button (or "Generate New Key" if you don't already have one).
    4. Note your username, and copy your API Key
  3. 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 Rackspace. 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 Rackspace data center will be automatically created, if it does not already exist. For more information about Locations, refer to Using Locations.

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