Share this page

# Manage Dockerized hosts

This section describes how to set up and manage elastic Dockerized load generator hosts.

In this topic:

## Configuration methods

You can use one of the following methods for configuring and assigning Dockerized hosts to a performance test either from:

Method | Description
--- | ---
Automatic provisioning | You can automatically provision and de-provision load generators from Docker containers. For details, see Automatic provisioning of Docker hosts.
Manual provisioning | REST API. You can assign Dockerized load generators and Controllers to tests from the LoadRunner Enterprise REST API. For details, see Add Dockerized hosts to tests from the REST API. User Interface. You can assign Dockerized load generators and Controllers to tests from the LoadRunner Enterprise user interface. For details, see Manually configure and assign Dockerized hosts to tests.

For details on deploying Dockerized LoadRunner Enterprise images and updating the default image, see Manage Dockerized images.

Back to top

## Notes and limitations

The following notes and limitations apply to elastic Dockerized hosts:

Migrated Docker tests | When migrating a project that contains tests using Dockerized hosts, only the Orchestration configurations are migrated; the path to your updated Docker images must be redefined. Resolution: To run a migrated test using Docker hosts, you need to add the Docker images (if different from the default ones), associate the orchestrator configuration with the valid images, and then assign the images to the test in the Performance Test Designer. For details, see Distribute load generators among Vuser groups.
Dockerized load generators | After migrating a project from Performance Center to LoadRunner Enterprise, you need to enter new values for Token (Kubernetes). This is because this value is hidden and replaced by asterisks, and asterisks cannot be retrieved to the LoadRunner Enterprise Administration user interface. Windows containers on Swarm orchestrators are created without CPU limit by design. NV is not supported when using elastic Dockerized hosts. Running over a firewall is not supported. Elastic hosts using a TLS (SSL) configuration are not supported. Do not use the `[Test]ElasticCont{ID}` host in a test. For issues when running tests without collating results, or if collation fails, see Retain run results after a test ends. A performance test fails to initialize if all node resources for load generator containers have been assigned. Workaround: Do not set the Resource Limits in Configuration > Orchestration with the maximum machine resources; leave some resources spare for the node itself. If Security-Enhanced Linux (SELinux) is enabled on your Linux operating system, it can prevent Docker containers from loading the required load generator libraries. Workaround: Contact your IT department to configure SELinux so that it is still effective while letting the load generators load the required libraries for them to operate. Any errors encountered by Dockerized hosts are written to the Event log under the docker node host name and port. IP spoofing should be disabled for Dockerized load generators.

Back to top

https://admhelp.microfocus.com LoadRunner Enterprise 8942
Tips to improve your search results... LoadRunner Enterprise Help Center LoadRunner Enterprise Help LR Enterprise Help 2023-2023 R1 All View Local Help Center View Online Help Center back Go back in browser history forward Go forward in browser history Remove search highlights next topic Go to next topic previous topic Go to previous topic Print the current topic Version: