update docs to reflect openshift container platform 3.5

Author: Jeff McCormick

Makefile

@@ -7,7 +7,9 @@ run:
 pgo:
 	cd client && go build -o $(GOBIN)/pgo pgo.go
 clean:
-	rm $(GOBIN)/pgo $(GOBIN)/postgres-operator
+	rm -rf $(GOPATH)/pkg/* $(GOBIN)/*
+	go get -u github.com/FiloSottile/gvt
+	gvt restore
 operatorimage:
 	cd operator && go install postgres-operator.go
 	cp $(GOBIN)/postgres-operator bin/postgres-operator

README.asciidoc

@@ -21,6 +21,7 @@ Once the objects are detected, the PostgreSQL Operator enables users to perform
 * Upgrade Cluster
 * View PVC
 * Test Connections
+* Clone a Cluster
 
 What actually gets created on the Kube cluster for a 
 *pgcluster* resource is defined as a *deployment strategy*.  Strategies
@@ -29,6 +30,7 @@ are documented in detail here link:docs/strategies.asciidoc[Deployment Strategie
 == Requirements
 
 * Kubernetes 1.5.3+
+* Openshift Origin 1.5.1+ or Openshift Container Platform 3.5
 * link:https://hub.docker.com/r/crunchydata/crunchy-postgres/[PostgreSQL 9.5+ Container]
 * link:https://hub.docker.com/r/crunchydata/crunchy-backup/[PostgreSQL Backup Container]
 * link:https://hub.docker.com/r/crunchydata/crunchy-upgrade/[PostgreSQL Upgrade Container]
@@ -100,6 +102,12 @@ pgo show pvc mypvc
 pgo test mycluster
 ----
 
+.Clone Cluster
+[source,bash]
+----
+pgo clone mycluster --name=myclone
+----
+
 Details on the *pgo* commands are found in the 
 link:docs/user-guide.asciidoc[User Guide] 
 

docs/build.asciidoc

@@ -13,7 +13,7 @@ from source, you can download them from the following:
 == Requirements
 
 * Kubernetes 1.5.3+
-* Openshif Origin 1.5.1+
+* Openshift Origin 1.5.1+ and Openshift Container Platform 3.5
 * link:https://hub.docker.com/r/crunchydata/crunchy-postgres/[PostgreSQL 9.5+ Container]
 * link:https://hub.docker.com/r/crunchydata/crunchy-backup/[PostgreSQL Backup Container]
 

docs/user-guide.asciidoc

@@ -236,6 +236,25 @@ cluster.  The cluster credentials are accessed and used to test
 the database connections.  The equivalent *psql* command is printed
 out as connections are tried, along with the connection status.
 
+== Clone Cluster
+
+To create a cluster clone from an existing cluster, use the following:
+....
+pgo clone mycluster --name=myclone
+....
+
+When you execute the *clone*, it will orchestrate the following
+actions:
+
+ * create a PgClone TPR to start the cloning workflow
+ * create a replica on *mycluster* that will become the clone master
+ * watch for cloned replicas to complete their replication
+ * copy the original cluster's secrets for the clone to use
+ * create a PgCluster TPR for the new clone cluster
+ * create the Postgres trigger file on the clone to cause it to recover
+   and become a valid read-write master
+ * remove the PgClone TPR
+
 == bash Completion
 
 There is a bash completion file that is included for users to try, this