anchor.diff:  So, to do a database backup repeatably, you will need to following
   this general pattern:
   
  - * as openshift admin user, create a unique PV (e.g. backup-pv-mydatabase)
  + * as OpenShift admin user, create a unique PV (e.g. backup-pv-mydatabase)
    * as a project user, create a unique PVC (e.g. backup-pvc-mydatabase)
    * reference the unique PVC within the backup-job template
    * execute the backup job template
    * as a project user, delete the job
    * as a project user, delete the pvc
  - * as openshift admin user, delete the unique PV
  + * as OpenShift admin user, delete the unique PV
   
   This procedure will need to be scripted and executed by the devops team when
   performing a database backup.
  
positive.code: replica-dc deployment with replicas count of 2.
  
  
  == Openshift Tips
  
  === Tip 1: Finding the Postgresql Passwords
  
  The passwords used for the PostgreSQL user accounts are generated
  by the Openshift 'process' command.  To inspect what value was
  supplied, you can inspect the master pod as follows:
  
  ....
  
negative.code: === *workshop* - workshop
  
  This example, $CCPROOT/examples/openshift/workshop, provides an
  example of using OpenShift Templates to build pods, routes, services, etc.
  
  You use the *oc new-app* command to create objects from the
  JSON templates.  This is an alternative way to create OpenShift objects
  instead of using *oc create*.
  
  This example is used within a joint Redhat-Crunchy workshop that is
  given at various conferences to demonstrate OpenShift and Crunchy Containers
  working together.  Thanks to Steven Pousty from Redhat for this
  example!
  
  