===== Haproxy configuration change =====

  - Add and support 10.166.152.16
<code>
frontend http-ingress
  bind 10.166.152.16:80
  ...
frontend chat-ingress
  bind 10.166.152.16:80
  …
backend leanrexa
  source 10.166.152.240
</code>

  - Remove 10.166.152.14 (Remove commented code)
<code>
frontend http-ingress
  #bind 10.166.152.14:80
frontend chat-ingress
  #bind 10.166.152.14:80
</code>

  - Add redundant block
<code>
backend learnexa_bkp
        balance roundrobin
        cookie SERVERID insert indirect
        server prodapp01 10.166.152.11:80 cookie app1 maxconn 64  inter 8000
        server prodapp02 10.166.152.19:80 cookie app2 maxconn 64  inter 8000 
        option httpclose
frontend http-ingress
  acl prm_is_dead nbsrv(learnexa) lt 1
  ...
  use_backend learnexa_bkp if prm_is_dead
#similar for chat
</code>





====old code====
Challenge 1: Reconfigure health checks without relying on Opsource firewall.
Challenge 2: Reconfigure health checks without any deploy scenario changes.

*Needs to be tested* \\
#2: \\
Deploy script blocks 10.166.152.240 through .250.  \\ 
If we set a source IP for haproxy probe in this range, we should be able to retain the test before site goes live functionality (last step of deployment) via
the machine IP (assigned by Opsource during instance creation). \\
<code>
source <IPAddress>
</code>

#1: