anchor.diff:  === Openshift Example 12 - Automated Failover
   
   This example shows how a form of automated failover can be
  -configured for a master and slave deployment.
  -
  -First, create a master and 2 slaves:
  -
  -....
  -oc process -f master-slave.json
  -oc scale rc pg-slave-rc-dc-1 --replicas=2
  +configured for a master and replica deployment.
  +
  +First, create a master and 2 replicas:
  +
  +....
  +oc process -f master-replica.json
  +oc scale rc pg-replica-rc-dc-1 --replicas=2
   ....
   
   Next, create an Openshift service account which is used by the crunchy-watch
  
positive.code: This example shows how you can use the crunchy-pgbouncer container 
  when running under Openshift.
  
  The example assumes you have run the master/slave example
  found here:
  ....
  examples/openshift/master-slave-dc
  ....
  
  Then you would start up the pgbouncer container using the following
  
negative.code: 
   * log into openshift using the service account
   * set its current project
   * find the first replica pod
   * delete the master service saving off the master service definition
   * create the trigger file on the first replica pod
   * wait 20 seconds for the failover to complete on the replica pod
   * edit the replica pod's lable to match that of the master
   * recreate the master service using the stored service definition
   * loop through the other remaining replica and delete its pod
  
  At this point, clients when access the master's service will actually
  be accessing the new master.  Also, Openshift will recreate the number
  of replicas to its original configuration which each replica pointed to the
  new master.  Replication from the master to the new replicas will be
  started as each new replica is started by Openshift.
  
  === Openshift Example 13 - Metrics Collection
  
  