Load generators can be hosted on either local computers or in a cloud account. This topic discusses load generators on the cloud. To host a load generator on the cloud, you must have access to a cloud account that will host the load generator. You use the LoadRunner Controller to maintain the list of cloud accounts that are available to host load generators.
You must already have access to a cloud account before you can use LoadRunner to use a cloud account for hosting load generators. All costs incurred by the provisioning of cloud machines through LoadRunner, are external to LoadRunner. They are the sole responsibility of the user, and are subject to the cloud vendor's pricing schedule.
When you add a cloud-based load generator to a scenario, you specify which of the available accounts will host the load generator. For details on how to add a cloud account, see
LoadRunner supports cloud accounts on specified cloud providers only. For a list of the supported cloud providers, see the
On your cloud machines, you use the Controller to create load generators for the cloud account. The process of creating a load generator is known as provisioning. When you use the Controller to provision a load generator, the Controller deploys an selected image upon the machine with the load generator software. When a load generator is first provisioned, it has the status of "In Progress". When it reaches the "Down" status. it is ready to run Vuser scripts as part of a scenario.
You can configure the Controller to remove a load generator from the cloud after the scenario is completed. Load generators are removed in order to reduce cloud usage and the associated costs. For details on how to specify whether or not to remove load generators at the end of a scenario, see
If you specify to terminate load generators at the end of a scenario run, its termination differs slightly depending on whether the scenario is completed successfully or fails.
If the scenario fails, then you can specify to terminate the load generator after a specified amount of time after a scenario fails. This delay may be useful because it enables you to access information on the load generator that may indicate why the scenario failed. After the load generator is removed, this information is no longer available.
The Controller will terminate a load generator only if the load generator has been configured to be removed at the end of a scenario run. For details on this setting, see