Skip to main content

Enterprise Topology Load Balancer

In an Enterprise OpenLab Server deployment, the load balancer in front of the cluster of server nodes must be configured to monitor Test Services health on each node. When a server node is detected as "unhealthy", the load balancer must silently remove it from the cluster. When a node returns to "healthy", the load balancer must silently add it back.

URIs to load balance​

Three URIs must be load balanced for Test Services:

  1. /testservices — used when accessing the Test Services website from a client. Sticky sessions required.

  2. /openlab/testservices — also used when accessing the Test Services website from a client. Sticky sessions required.

    A return code of 200 from /openlab/testservices/api/v1/Environment/getwindowslanguage indicates the website is functioning properly on a server node.

  3. /openlab/testservicesserver — provides central backend services to Test Services client systems. Sticky sessions are not required.

    A return code of 200 from /openlab/testservicesserver/v1/Health indicates the backend services are functioning properly on a server node.

note

For testing and getting reports for a specific server node, Test Services must be run locally on that node using https://localhost/testservices.