Cloud schedule overview
Schedule provides a way to apply huge user load on the
application under test. To apply that amount of load, you need good
infrastructure support ranging from physical desktop computers with
enough RAM, Processors, and different operating systems. You need
labs to host the computers. There is good amount of investment required.
You can cut down on that investment by running the schedule in a cloud
location.
Video: Learn about this functionality with the help of this video.
IBM® Rational® Performance Tester supports running the schedule on the public cloud by using the SoftLayer infrastructure or on the private cloud of VMware.
- About Promotional code and Subscription ID
To run a cloud schedule, you require a promotional code (trial) or a subscription ID. With the trial promotional code, you are not charged for the run. When you purchase the cloud load generation service, the cost of running a cloud schedule is based on the number of virtual tester hours that the schedule runs. So, you pay only when you run the cloud schedule. - Creating location templates for SoftLayer
A location template defines virtual machine attributes such as operating system image type, data center location, and host type for the agent virtual machines to be hosted in the cloud. After creating location templates, when creating a cloud schedule, you associate the location templates with the schedule and specify the number of agent virtual machines to use to run the schedule. - Creating location templates for VMware
A location template contains virtual machine attributes such as data center location, resource pool, and datastore for the agent virtual machines to be hosted in the cloud. After creating location templates, when creating a cloud schedule, you associate the location templates with the schedule and specify the number of agent virtual machines to use to run the schedule. - Connecting to the cloud manager for SoftLayer
To run a cloud schedule, first, you must establish a connection to the cloud manager. By connecting to the cloud manager, you specify properties for the workbench and agent machines on cloud such as location of data center, type of operation system, and type of host manager. - Connecting to cloud manager through proxy
To run a schedule on the cloud, the workbench must connect to Rational Performance Tester Cloud Manager. If the workbench is installed behind a firewall, use a proxy computer that is connected to the workbench computer as well as has access to the Internet. - Connecting to the VMware server
To initiating a cloud run, first, you must establish the connection to the vCenter server. On connecting to the server, you specify the properties of the workbench template such as data center, resource pool, and domain that hosts the virtual machine. If you connect to the vCenter server through the location template, you must also establish the connection through the Preferences window by following the instructions in this topic. - Creating a cloud schedule
If you must scale up the user load for a performance test and cannot invest in physical computers, you can create a schedule that runs on the cloud. - Running a cloud schedule
IBM Rational Performance Tester can be used to run schedules in the cloud. The benefits of running a schedule in the cloud include access to load generating agents in the cloud, access to System Under Test from geographically diverse locations with data centers located worldwide, and paying for load generation services only when needed. - Auditing measurement accuracy
In a virtualized environment, the load generating capacity can be degraded significantly for throughput, CPU utilization, and measurement accuracy. For instance, in a cloud environment, measuring the response time can vary, depending on factors such as the location of data center, type of host, and life-span of agent virtual machines. It is difficult to get an accurate response time every time because not all factors can be controlled by IBM Rational Performance Tester. But, you can do a statistical comparison of the reported measurements against a trusted control.
Related concepts:
Feedback