Bug 1013166

Description of problem:
Currently, haproxy, when scaled to 3 or more gears, will shutdown the application cartridge (i.e. ruby, python, php, etc) in the gear that also houses haproxy so that haproxy has access to the entire gear's resources. It is requested that the number of gears required to shutdown the application cartridge be adjustable.

The goal of this is to allow the application creator to have one haproxy gear and just one application gear or , if load permits, have 3 total gears and still have the application cartridge running on the haproxy gear.

Additional info:

Current upstream/1.2/2.0 code:

cartridges/openshift-origin-cartridge-haproxy/hooks/set-gear-endpoints

122 # Disable the local endpoint if one of the remote gears is available and it
123 # isn't already disabled
124 if [ $(grep -E "server\s*gear" $HAPROXY_CONFIG | wc -l) -ge 2 ]; then
125     if grep "local-gear" $HAPROXY_CONFIG | grep "weight 0" &>/dev/null; then
126         echo "Local gear already disabled in config. "
127     else
128         echo "Disabling local gear in the config. "
129         nohup $OPENSHIFT_HAPROXY_DIR/usr/bin/fix_local.sh &
130     fi
131 fi

If we change "2" to an adjustable environment variable in line 124, this should achieve the goal. I am unsure if this is the method development would like to take.