Sportlogic uses an AWS load balancers to manage traffic.

A Load balancer direct traffics to targeting groups (e.g AppServer) which contains target instances (the actual application servers).

To stop an application server stop, we need to deregister the target in the load balancer first in AWS. Similarly, to start an application server, we need to ‘register’ the server as target in a target group under the load balancer.

Sportlogic_ALB1

Sportlogic_ALB1 is an general purpose application-level load balancer, managing traffic for a few target groups, including AppServer, Storage gateway, Xero gateway, HTR, Messaging Gateway, Sportlogic API and Payment gateway.

AppServer

AppServer is set as a target group with has 3 instances: peach, adelaide, raspberry.

See https://kb.sportlogic.com.au/system-app-server/

Deregister a target

1. Before stopping an Appserver (for upgrade), we need to deregister it from the AWS load balancer, so the load balancer will no longer direct traffic to it.
2. Login to AWS -> EC2 ->Load Balancing Target Groups
3. Select and click into the group for AppServer (appserver8-http-6888)
4. Select (check) instance, click deregister
5. The health status go from healthy -> draining
6. After a few minutes, the instance will disappear form the target list.

Register a target

1. After restarting an Appserver (for upgrade), we need to register it back to be managed by the AWS load balancer
2. Login to AWS -> EC2 ->Load Balancing Target Groups
3. Select and click into the group for AppServer (appserver8-http-6888)
4. Select “Register Targets”
5. select the target instance (e.g. peach)
6. click “include as pending”
7. The health status will become “pending”
8. Click “register pending targets”, the health status will change pending -> initial -> healthy