Skip to main content

Configure for an enterprise OpenLab Server topology

Configure the load balancer in front of an enterprise OpenLab Server cluster so that Test Services routes correctly and survives a node failure. This page is for the administrator who manages the cluster and its load balancer. In an enterprise deployment, clients reach Test Services through the load balancer, which monitors each server node and routes traffic only to healthy nodes.

Prerequisites

  • You must have administrator access to the load balancer in front of the OpenLab Server cluster.
  • Test Services must be installed on each server node in the cluster. (See Install Test Services.)
  • The cluster nodes must share the same Central Management database. (See How Test Services works.)

Configure the load-balanced URIs​

The load balancer must forward three Test Services URIs. Two carry the web client and need sticky sessions; the third carries the central backend services and does not.

  1. Add a rule for /testservices, used by clients to reach the Test Services website.

    Enable sticky sessions for this URI.

  2. Add a rule for /openlab/testservices, also used by clients to reach the website.

    Enable sticky sessions for this URI.

  3. Add a rule for /openlab/testservicesserver, which provides the central backend services to client systems.

    Sticky sessions are not required for this URI.

Set up the health checks​

The load balancer must detect an unhealthy node, remove it silently, and add it back when it recovers. Use the Test Services health endpoints for the checks.

  1. Configure a website health check that sends a request to /openlab/testservices/api/v1/Environment/getwindowslanguage on each node.

    A return code of 200 indicates the website is healthy on that node.

  2. Configure a backend health check that sends a request to /openlab/testservicesserver/v1/Health on each node.

    A return code of 200 indicates the backend services are healthy on that node.

  3. Set the load balancer to remove a node from the cluster when a check fails, and to restore it when the checks pass again.

note

To run tests against a specific server node and collect that node's reports, run Test Services locally on that node at https://localhost/testservices rather than through the load balancer.

See also​