To get started, select Central list > GridsThen, click New. When you do so, the Grid Manager, General page appears.
Enter a Grid Name, an optional Description, and a Save Location (this is the folder where the grid settings will be stored).
Click the Next button to go to Step 2.When you do so, the Grid Manager, Server Instances page appears. Using this page, define both Test Server and Result Server instances. Test Server instances will be used to generate load, and Results Service instances will be used to analyze and report on the test data in real-time.
Enter the number of Test Server instances to be created per Location, or select a Composition(s) to automatically determine the number for you.
Define Result Server instances per Location as a ratio to Test Server instances or as a Fixed Amount.
Optionally, you can propagate grid-related settings such as Locations from your test composition. Click Select Composition(s)and specify the composition(s) to use in this grid.
Optionally, in the Server Instances page, check Show Advanced Settings to perform any of the following tasks:Note: See Grid Advanced Settings for more about each field in the Location's Advanced Settings.
To specify a Pending Timeout for this location (e.g. different timeouts for Amazon EC2 and GoGrid).
Specify the time in seconds until the allocation request will timeout and be added to the retry queue.For example, after an instance is requested, it stays in the "Pending" state until it's ready, and then changes to "Running". The time it takes to reach "Running" can be anywhere from 30 seconds to 10 minutes. Use this setting to specify a cut-off in seconds. By default, any servers that don't reach "Running" after 5 minutes are thrown away, and are re-tried.
To specify server classes for Test Server or Results Service instances
Configured Server Classes can be selected from the Server Class drop-down. See Server Classes. TIP: If you are using Amazon Web Services Security Group(s), you can specify them in the Security Group field (shown above). Refer to Support for AWS Security GroupsDepending on the cloud vendor, allocations settings may vary.
For Amazon EC2, the grids will by default automatically choose the EC2 availability zone for new instances via the Let the cloud provider pick the zone for me option. This can reduce the time needed to allocate large numbers of instances. To override this behavior, and specify a zone, click the "Show advanced settings" box in Step 2 of the wizard and then select a different Zone Distribution option instead.
To specify a zone in which servers will be launched
With Zone Distribution > All in the Same Zone radio button checked, select a zone from the available zones in the drop-down. Optionally, check the Failover to different zone(s) if initial allocation fails box if you want CloudTest to use different zones on retry.
To switch from the default server allocation algorithm (which tries to allocate servers all in one zone) to another algorithm that will get servers in groups of 25 by doing round robin on all of the zones
Check the Distribute evenly across all zones box to use the alternate round-robin algorithm for server instances.
Click the Next button to go to Step 3. The Summary and Deploy/Tear Down page appears.Use the Summary and Deploy/Tear Down page to review your settings before using Deploy Instances. Click the Back button to return to the prior screen(s) to change settings.
In the Summary and Deploy/Tear Down page, click the Advanced Settings tab.
Optionally, check Advanced Settings and change any of the following defaults as necessary