Cloud Provider Account Support for Qingcloud

Document created by Chris Sommerstad Employee on Jul 20, 2017
Version 1Show Document
  • View in full screen mode

Users can now create Cloud Provider Accounts, and launch Grids and RSDBs for the QingCloud vendor. QingCloud provides data centers in the U.S., Africa, Asia Pacific, and Europe.

Setup QingCloud as a Cloud Provider

Use the following steps to enter your valid QingCloud 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 new cloud provider 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 QingCloud”.

  1. Enter the QingCloud Access Key ID
  2. Enter the Secret Access Key and then enter it in the Confirm Secret Access Key field a second time.

  1. Optionally, configure an access control list in the Cloud Provider Account box in CloudTest. Refer to Cloud Provider Accounts for additional Access Control List steps.

  1. Click OK to complete configuration of this Cloud Provider Account

The completed item appears in the Cloud Provider Accounts list in Central

When the Cloud Provider Account is saved, a new set of locations for QingCloud will be automatically created, if they do not already exist.

These locations must be specified during Grid Manager configuration of grids (as described below)

TFor more information about Locations, refer to Using Locations

Additionally, CloudTest creates all of the Server Classes supported by the QingCloud vendor.

QingCloud Server Instance Types

The following SOASTA server instance types map to the following QingCloud configurations


SOASTA Instance Type

QingCloud Configuration


8 GB total RAM and 2 CPU cores


16 GB total RAM and 4 CPU cores


16 GB of RAM and 2 CPU cores


32 GB of RAM and 4 CPU cores


64 GB of RAM and 8 CPU cores


8 GB of RAM and 8 CPU cores


16 GB of RAM and 8 CPU cores

These Server Instance Types can be used in either Results Server or Test Server instances

Launching Test Servers using QingCloud

Once a QingCloud Provider Account has been created for use with CloudTest, you are ready to create a grid that will provision servers via that cloud vendor

Creating a Grid using QingCloud

  1. Select Central > Grids and then click New. The Grid Manager appears with Step 1 General displayed.

  1. Select the SOASTA product to which the grid pertains, which in this case is CloudTest.

    1. Enter a Grid Name, and optionally, enter a description and a repository location for the new grid, and then click the right arrow

The Step 2 Server Instances page appears.

Note:  Every QingCloud server is given a bandwidth limit by the user. Total bandwidth across the given QingCloud account is capped by QingCloud. The Default cap is 1 Gbps (e.g. 8,000 Mbps). Bandwidth is specified in the CloudTest Grid Manager, Server Instances page, Provisioned Bandwidth setting.

  1. Change the Location” drop-down to one of defined QingCloud locations. For example, QingCloud Asia-Pacific 1 (Hong Kong) (shown in the first location above) or QingCloud China Beijing 1 (shown in the second location above)
  2. Optionally, specify additional locations such as the QingCloud China Quangdong 1 location (or a second Beijing location that uses a different combination of results and test servers.

  1. Specify the number of Test Server instances, and then optionally, define Results Server Instances. For most cases, the default One for every 50 Test Serverinstancesis acceptable for result servers
  2. If you wish to combine the QingCloud servers from one location with servers from another location (or even with other cloud providers), click the Add a Location box and make the appropriate selection(s). Otherwise, click the right arrow icon to proceed

The Step 3 Summary and Deploy Tear Down page appears. Click the Deploy Instances button to begin launching servers.

Note: CloudTest Pro users may see an additional Grid Monitor Database field for those configurations where more than one Results Database is available. For more about using and launching grids, refer to Managing Grids.