Deploy Dockerized load generators on Windows

This section describes how to run a Dockerized load generator on a Windows platform.

Docker is a platform that allows you to develop, ship, and run applications using a container. Refer to the product documentation for more details.

In this topic:

Prerequisites

Below is a list of prerequisites that are required to run a Dockerized load generator on a Windows platform.

Back to top

Run a Dockerized load generator using the predefined image

Use the ready-to-use image to run a load generator (OneLG) on Docker for Windows. If you need customization for your container, for example, for Java or to run under a specific user, see Run a Dockerized load generator using a custom image.

To run a Dockerized load generator:

Run the load generator container using the following command:

docker run -id -p <host_port>:54345 -e "ENABLE_GATLING=1" -e "ENABLE_JMETER=1" performancetesting/opentext_onelg_windows:<tag version number>

Back to top

Run a Dockerized load generator using a custom image

If your environment requires customized settings for running the container, you can create a Dockerfile to build a custom image for Docker on Windows.

Examples for custom images:

• To use a specific user account for the processes under which the Vusers are running, to provide support for accessing network resources like script parameter files. After running, the container should be able to verify the user.

• To run Java, Gatling, or JMeter protocols on Windows load generator containers.

• To define environment variables for proxy server host and port.

To run a custom Dockerized load generator:

1. Create a new folder, and within it create a file named dockerfile. Paste the following FROM line into the file, using the appropriate OpenText Enterprise Performance Engineering version for the <tag version number>, and add the relevant customization lines:

   Copy code

   FROM performancetesting/opentext_onelg_windows:<tag version number><Customization lines>

   For customization examples, see Examples of customized content for Dockerfiles  

   Tip: Refer to the Docker documentation for commands that can be used in Docker files.

2. Save the Dockerfile.

3. Open a command line at the dockerfile folder path and run the following command, using the name you want for your custom image:

   Copy code

   docker build -t <custom dockerfile name> .

4. Create a container for each load generator you want to use, by running the following command (or use any Docker orchestrator tool for running containers):

   Copy code

   docker run -id -p <host_port>:54345 <custom image name>

   If the custom image in step 3 was built with a tag then include it in the command:

   Copy code

   docker run -id -p <host_port>:54345 <custom image name>:<tag version number>

   Note: Check that the <host_port> on the machine is available and allows incoming requests. You specify this port on the Controller side when connecting to this load generator. This is not relevant when using elastic load generators, because this is managed by the orchestrator.

Back to top

Examples of customized content for Dockerfiles

The following gives an example of dockerfile content for running the Vusers under a specified user account with network access to shared locations. Replace the values between <> with credentials for a valid user account in your environment, with network access to the shared resources.

Example for Vusers under a specified user account:

#escape=`
FROM performancetesting/opentext_onelg_windows:24.3
RUN c:\LG\launch_service\bin\magentservice.exe -remove
RUN c:\LG\launch_service\bin\magentservice -install <domain>\<user name> <password>

Example of dockerfile content for running Java protocols:

#escape=`
FROM performancetesting/opentext_onelg_windows:24.3
COPY .\<folder contains JDK> <target path in the container>

The path to the target JDK directory defined in the COPY line for the <target path in the container> must also be added to the Java VM runtime settings page:

Back to top

After running the load generator containers

Add the load generators containers to your tests.

• For elastic hosts, see Set up Dockerized hosts.

• For manually configure Dockerized load generators, see Deploy hosts using Docker.

Back to top

Tips and guidelines

• Dockerized load generators, run from the predefined image, are not supported when running over a firewall.

• Use docker ps to list the containers that are running.

• To stop the load generator service:

  • Use docker stop <load generator container name or ID> if you want to reuse the same load generator.

  • Use docker rm -f <load generator container name or ID> to remove the load generator container.

• To access the host network directly, use --net=host in place of -p <host_port>:54345. We recommend you use this flag if the AUT generates a lot of network activity.

Back to top