Deploy a Docker container for Linux

Deploy and configure a Docker container to load test your secure applications.

Note: The Docker client (engine) must be installed on each host machine where you want to install the LoadRunner Cloud Docker container.

Notes and limitations

Limitation/Note Solution
Date and time

Ensure that the date and time on the load generator machine are correct.

Tip: Synchronize your computer clock with an Internet time server.

Connection between LGs and LoadRunner Cloud

The load generator machine needs to be able to access the LoadRunner Cloud servers in SaaS and the cloud machines. (Only outbound HTTPS connection on port 443 needs to be enabled.)

If there is no connection between LoadRunner Cloud servers and the Load Generator (on-premises load generator Status=Not Connected), an error message is reported when you try to run your test.

If you receive a system error -1030, check the network connectivity between your on-premises load generator and the cloud (AWS). Also ensure that outbound communication over port 443 is enabled.

If your company's security or firewall requires static allocated IP addresses, open a support ticket to request them.

One test per load generator

The load generator can run only one test at a time. If the required load generator is already in use by another test, an error message is reported when you try to run your test.

Vusers

Vusers in your on-premises load test cannot exceed the maximum number of Vusers in your license.

Back to top

LoadRunner Cloud on-premises Docker versions on Docker Hub

Beginning with version 2020.10, a new Docker image contains the on-premises load generator, OneLG, for all of the LoadRunner family products. This container can be used instead of the Docker images provided for releases prior to 2020.10.

Note: In future releases, the former Docker image will be deprecated, and only the OneLG image will be available.

Version Description
Full version

The full version supports the following script protocols:

  • Gatling
  • JMeter HTTP
  • Mobile HTTP
  • MQTT
  • Oracle NCA
  • Oracle Web
  • SAP Web
  • TruAPI
  • DevWeb
  • Web HTTP/HTML
Lite version

The lite version supports the following script protocols:

  • Gatling
  • JMeter HTTP

  • TruAPI

For details of supported protocol versions, see Version compatibility.

For additional help, consult the Docker help.

Back to top

Deploy and configure the Docker container from Docker Hub

For LoadRunner Cloud version 2020.10, a new repository, microfocus_onelg_linux_ubuntu, was introduced with the OneLG image. The exiting repository, loadrunnercloud_load_generator, is still supported, but will be deprecated in an upcoming release.

Back to top

Manually deploy and configure a Docker container

You can manually deploy the Docker container.

Action How to
Define your LoadRunner Cloud load generator in LoadRunner Cloud and note the key:
  1. In LoadRunner Cloud, select Assets > Load Generators.
  2. Click Create. Give the load generator a meaningful name and description.

  3. Select Linux as the OS.
  4. Note the load generator's key.

Create the container

For the new microfocus_onelg_linux_ubuntu image, run:

docker run -t -i \
      -e "STORM_DISABLE_AUTO_REGISTER=1" \
      --net=host performancetesting/microfocus_onelg_linux_ubuntu

For the former loadrunnercloud_load_generator image, run:

docker run -t -i \
-e "STORM_DISABLE_AUTO_REGISTER=1" \
--net=host performancetesting/loadrunnercloud_load_generator

The current working folder is: /opt/testexec.server/stormagent

Edit the sample_conf.json

Add your load generator key and your credentials to the sample_conf.json file:

{
    "key": "<YOUR KEY>",
    "interval": 20000,
    "logLevel": "info",
    "server": {
        "protocol": "https:",
        "addr": "stormrunner-load.saas.microfocus.com",
        "user": "<YOUR USERNAME>",
        "password": "<YOUR PASSWORD>",
        "tenant": "<YOUR TENANTID>"
    },
    "injector": {
        "rootPath": "../injector_mdrv"
    }
}
Launch the container

Type the following command:

node bin/stormagent.js --config ./sample_conf.json

Back to top

Run a test using my Docker container

Action How to
Create a test

From LoadRunner Cloud > Load Tests, select a load test or create a new test.

Select On-premise as the location of the load generators

From the Scripts tab, select a script and then select On-Premise from the Location drop-down list.

Add a load generator

From the Distribution tab, click On Premise and then click Add from Assets to select the on-premises LoadRunner Cloud Load Generators to use for your test.

Back to top

Create and view logs

You can create and view test run logs.

Create a log

To use the Docker container to create logs, launch the container with the -r or --reserveTestLog flag. For example:

Example: docker run -d -e STORM_AGENT_EXTRA_CONFIG='--reserveTestLog'

Logs are saved in the inj_o_*** folders under /storm.

View logs

You can view logs from within a running Docker container, or copy the logs to your local file system.

  • View logs from within a running Docker container

    1. Run the command: docker exec -t -i <container ID> /bin/bash
    2. Enter the /storm folder and check the required log.
  • Copy logs to your local file system

    Run the command: docker cp <container ID>:/storm /tmp/

    In this instance, the logs are copied to the tmp folder in your local file system.

  • Back to top