Rainbow - [WW] Maintenance on load balancer haproxy-externals – Maintenance details

Step1: 9:00 pm (France time), Rainbow team will add 2 new load balancers in France, please ensure they are trusted in customer's firewall:
- 178.32.126.211, 178.32.126.97 (*.openrainbow.com)
- 178.32.126.251, 178.32.127.14 (agent.openrainbow.com)
- 178.32.126.70, 178.32.127.143 (rdd.openrainbow.com)

> Note: you may also use Rainbow Pilot: https://pilot.openrainbow.com/networkRequirements to obtain the Network requirements.

Step2: 9:30 pm (France time), following load balancers will be drained:
haproxy-external-gra3-prod-2 (178.32.125.107, 178.32.125.135, 178.32.125.149 will be removed from DNS answer)
haproxy-external-rbx8-prod-2 (178.32.125.161, 178.32.125.168, 178.32.125.241 will be removed from DNS answer)

Step3: 10:00 pm (France time), a gentle reconnection (based on PBX country) of OXE cloud-agent during non-working hours will be performed
At this stage, if connections are established on above load balancer, a reconnection will happen (3xx answer returned by load balancer) and PBXs connected upon to load balancer will initiate a new connection which establish on available load balancers.

Step4: Rainbow team will monitor the remaining connections on haproxy-external-gra3-prod-2 and haproxy-external-rbx8-prod-2. Once all connections are closed to null, Rainbow team will proceed for OS migration. A dedicated maintenance will be published in Rainbow status page.

Key points:
- Ensure all load balancers' IP addresses are trusted in customer's firewall
- Ensure customers use FQDN instead of IP Addresses
- Reconnection timers must be defined properly to ensure seamless connection