Set up a fully containerized environment

This section describes how to deploy LoadRunner Enterprise as a fully containerized Docker environment. The environment contains four elements: LoadRunner Enterprise server, LoadRunner Enterprise host, a load generator, and a database server (this must be provided by your database administrator).

Requirements

  • Docker host machine (minimum requirements): 4 CPU cores ,16 GB RAM ,150 GB of storage. For installation details, see https://docs.docker.com/install/.

  • The setup was verified on Windows Server version 1809 build 17763.1282 running Docker version 19.3.0.5.

  • If you have McAfee Antivirus, disable Adaptive Threat Protection. Consider disabling other antivirus software since it might also impact functionality within containers.

  • Create the files listed below on a local machine, edit them to suit your needs*, and then copy them to the Docker host machine.

    You can create each file by copying the file's content from the dropdown below to a text file, and then renaming the file accordingly.

    Consists of container images and their parameters.

    Runs the LoadRunner Enterprise Configuration Wizard silently.

    Pulls the images and runs the run_configuratator.bat file.

    *For example, in docker-compose.yml you can add your DNS, change images if you tag them differently or have your own repository (similarly in bring_env_up_W2019.ps1), and add your enterprise proxy server).

  • Pull the images. You can pull the images to the Docker node by running bring_env_up_W2019.ps1, or directly from the performance testing page in the Docker hub (see Deploy LoadRunner Enterprise as a fully containerized environment for the pull commands).

Back to top

Set up the containerized environment

  1. Install Docker on the node:

    1. Open PowerShell with elevated mode.

    2. Run the following command to install the Docker module:

      Install-Module-Name DockerMsftProvider -Repository PSGallery -Force

    3. Run the following command to install Docker:

      Install-Package-Name docker-ProviderName DockerMsftProvider

    4. Run the following command to reboot your machine:

      Restart-Computer-Force

    5. Download “docker-compose” from Git.

    6. Rename docker-compose-Windows-x86_64.exe to docker-compose.exe and copy it to the C:\ProgramFiles\Docker\ folder.

    7. If you are working behind a proxy, add the proxy details as follows:

      [Environment]::SetEnvironmentVariable("HTTPS_PROXY", "<your-proxy>" [EnvironmentVariableTarget]::Machine)

    8. Run the following command to restart Docker service:

      Restart-Service -Name docker

  2. Verify that you can pull images from Docker hub.

    1. From PowerShell, run:

      docker login

    2. Type your Docker hub username and then your password.

  3. From the unzipped folder, open PowerShell in elevated mode and run the following:

    .\bring_env_up_W2019.ps1

    You should see output similar to the following:

    PS C:\Users\kenanom\Desktop\DockerEnv2019> .\bring_env_up_W2019.ps1
    2019: Pulling from performancetesting/custom_mssql
    65014b3c3121: Already exists
    b5405b758079: Pull complete
    3ff63bb3ff9a: Pull complete
    8668147df005: Pull complete
    f95c19a4e4f3: Pull complete
    d80a36b06e59: Pull complete
    92afe54f2e10: Pull complete
    1bfdb9eff817: Pull complete
    010169b2d320: Pull complete
    af98f149fa7d: Pull complete
    57ab89a1cb0b: Pull complete
    c 91905387c6: Pull complete
    86303b4b67a1: Pull complete
    238d10482797: Pull complete
    6a94026c0319: Pull complete

    Digest: sha256:302b44eac54c9bccecb935f0c8ca995406e4b8804a9567be10ce315910d0b172

    Status:
    Downloaded newer image for performancetesting/custom_mssql:2019
    docker.io/performancetesting/custom_mssql:2019
    Creating mssql ... done
    Creating lgsa ... done
    Creating lrhost ... done
    Creating lre ... done
    Attempting stop...
    Internet services successfully stopped
    Attempting start...
    Internet services successfully restarted
    Running Configuration Wizard, wait another five minutes before connecting to LRE !!!

Back to top

Configure LoadRunner Enterprise to use a containerized environment

Wait about five minutes after setting up the environment before logging onto LoadRunner Enterprise Administration.

  1. Log onto LoadRunner Enterprise Administration.

    For details, see Log onto LoadRunner Enterprise Administration.

  2. Create a project.

    For details, see Create domains and projects.

  3. Add LoadRunner Enterprise hosts.

    Add a Controller host and standalone load generator from LoadRunner Enterprise as defined in the docker-compose.yml file. For details, see Add a host.

    In the docker-compose.yml file, we use "lrhost" for the Controller host and "lgsa" for the standalone load generator.

  4. Perform other site and lab administration tasks, and set the license keys.

    For details, see Key tasks and Manage licenses.

  5. Design and run your test.

    After you finish configuring LoadRunner Enterprise to use a containerized environment (in LoadRunner Enterprise Administration), you can design and run your performance test.

    For details, see Design a test and Run performance tests.

Back to top

Troubleshoot container issues

To troubleshoot container issues, perform the following:

  1. Run the following from an elevated PowerShell:

    docker exec -it <container name or id> powershell

  2. Verify that the LoadRunner Enterprise services are running. From PowerShell run:

    Get-Service -Name "LoadRunner*"

    You should see the following results:

    Status   Name               DisplayName
    ------ ---- -----------
    Running LoadRunner Aler... LoadRunner Alerts Service
    Running LoadRunner Back... LoadRunner Backend Service
    Running LoadRunner Data... LoadRunner Data Collection Agent
    Running LoadRunner Remo... LoadRunner Remote Management Agent ...
  3. In the LoadRunner Enterprise container, verify in the Configuration Wizard log that schemas were created and services were installed.

    Open an interactive session to the LoadRunner Enterprise container and run:

    type C:\PC_Server\orchidtmp\Configuration\configurationWizardLog_pcs.txt

  4. Check the LREcore log from the LoadRunner Enterprise container. From PowerShell run:

    more C:\PC_Server\orchidtmp\LTLogger\LRECore.API\log.txt

  5. Check the w3wp log from the LoadRunner Enterprise container. From PowerShell run:

    more C:\PC_Server\orchidtmp\LTLogger\w3wp\log.tx

  6. Check the services are running on the host container. From PowerShell run:

    Get-Service -Name "LoadRunner*"

    You should see the following results:

    Status   Name               DisplayName
    ------ ---- -----------
    Running LoadRunner **bleep**... LoadRunner Analytics Service Running LoadRunner Data... LoadRunner Data Collection Agent Running LoadRunner Data... LoadRunner Data Service Running LoadRunner Load... LoadRunner Load Testing Service Running LoadRunner Remo... LoadRunner Remote Management Agent ... Running LoadRunnerAgent LoadRunner Agent Service
  7. If you have issues adding a host, check the logs on the host. From PowerShell run:

    more C:\PC_Host\orchidtmp\LTLogger\LTOPSvc\log.txt

  8. Verify that the Load Generator services are running. From PowerShell run:

    Get-Service -Name "LoadRunner*"

    You should see the following results:

    Status   Name               DisplayName
    ------ ---- -----------
    Running LoadRunner Remo... LoadRunner Remote Management Agent ... Running LoadRunnerAgent LoadRunner Agent Service

Back to top

See also: