10.1.2

Edit

Configure load balancer

You may use any load balancer. Remember to specify the following parameters for it.

In the load balancer's configuration:

  1. Configure the list of servers to be balanced:

    • APP Server hostname 01 (for example, host-ct1.example.com)
    • APP Server hostname 02 (for example, host-ct2.example.com)

  2. Create the following list of ports that VIP will listen to:

    • TCP: 80
    • TCP: 443
    • TCP: 7083
    • TCP: 5553
    • TCP: 9092
    • TCP: 9093
    • TCP: 9073
    • TCP: 9075
    • TCP: 9076
    • TCP: 4083
    • TCP: 8200
    • TCP: 9200

  3. Create one VIP address.

    Alternatively, you can create a separate VIP for each port. In this case:

    • Each domain name must be mapped to a separate virtual IP address.
    • The health check parameter (step 4) must listen to the same port, the VIP is mapped to.
    • A separate servers' group must be created for each VIP.

  4. Configure health checks:

    • Ports to listen: TCP 443. If the port is unavailable, HAProxy is down.
    • Servers in the Target group to check: APP Server hostname 01, APP Server hostname 02.
    • Rules:
      • The number of failed health checks to consider the server is down. By default, 3.
      • The number of passed checks to consider the server is restored. By default, 1.
      • The interval of health checks. By default, 20 seconds.

  5. In the SSL configuration menu, add your SAN or wildcard certificate.

  6. Set Sticky sessions to the Round Robin mode.

  7. Set Client NAT.

  8. Map the components' domain names to the VIP. The domain names are specified in the hosts.yml file.

    Example domain names

    • vault.example.com
    • minio.example.com
    • nexus.example.com
    • rabbitmq.example.com
    • mesos.example.com
    • marathon.example.com
    • workspace.example.com
    • workfusion.example.com
    • bot-manager.example.com
    • kibana.example.com
    • ocr.example.com
    • bi.example.com
    • int1.example.com
    • int2.example.com
    • int3.example.com
    • host-ct1.example.com
    • host-ct2.example.com
    • ocr1.example.com
    • ocr2.example.com
    • bi1.example.com
    • bi2.example.com
    • bepmaster1.example.com
    • bepmaster2.example.com
    • bepmaster3.example.com
    • bepagent1.example.com
    • bepagent2.example.com
    • bepagent3.example.com
    • rpa1.example.com
    • rpa2.example.com
    • rpa3.example.com
← PreviousNext →