track updated manpages

Author: juanvallejo

docs/man/man1/oadm-diagnostics.1

@@ -38,22 +38,19 @@ you will receive an error if they are not found. For example:
 .nf
 oadm diagnostics \-\-master\-config=/etc/origin/master/master\-config.yaml
 
-If master/node config files are not found and the \-\-host flag is not
-
 .fi
 .RE
+.IP 
 
-.PP
+.IP
+\(bu If master/node config files are not found and the \-\-host flag is not
 present, host diagnostics are skipped.
-    If the client has cluster\-admin access, this access enables cluster
-
-.PP
+.IP
+\(bu If the client has cluster\-admin access, this access enables cluster
 diagnostics to run which regular users cannot.
-    If a client config file is not found, client and cluster diagnostics
-
-.PP
+.IP
+\(bu If a client config file is not found, client and cluster diagnostics
 are skipped.
-
 .PP
 Diagnostics may be individually run by passing diagnostic name as arguments.
 The available diagnostic names are:

docs/man/man1/oc-adm-diagnostics.1

@@ -38,22 +38,19 @@ you will receive an error if they are not found. For example:
 .nf
 oc adm diagnostics \-\-master\-config=/etc/origin/master/master\-config.yaml
 
-If master/node config files are not found and the \-\-host flag is not
-
 .fi
 .RE
+.IP 
 
-.PP
+.IP
+\(bu If master/node config files are not found and the \-\-host flag is not
 present, host diagnostics are skipped.
-    If the client has cluster\-admin access, this access enables cluster
-
-.PP
+.IP
+\(bu If the client has cluster\-admin access, this access enables cluster
 diagnostics to run which regular users cannot.
-    If a client config file is not found, client and cluster diagnostics
-
-.PP
+.IP
+\(bu If a client config file is not found, client and cluster diagnostics
 are skipped.
-
 .PP
 Diagnostics may be individually run by passing diagnostic name as arguments.
 The available diagnostic names are:

docs/man/man1/oc-create-clusterresourcequota.1

@@ -0,0 +1,121 @@
+.TH "OC CREATE" "1" " Openshift CLI User Manuals" "Openshift" "June 2016"  ""
+
+
+.SH NAME
+.PP
+oc create clusterresourcequota \- Create cluster resource quota resource.
+
+
+.SH SYNOPSIS
+.PP
+\fBoc create clusterresourcequota\fP [OPTIONS]
+
+
+.SH DESCRIPTION
+.PP
+Create a cluster resource quota that controls certain resources.
+
+.PP
+Cluster resource quota objects defined quota restrictions that span multiple projects based on label selectors.
+
+
+.SH OPTIONS
+.PP
+\fB\-\-hard\fP=[]
+    The resource to constrain: RESOURCE=QUANTITY (pods=10)
+
+.PP
+\fB\-o\fP, \fB\-\-output\fP=""
+    Output mode. Use "\-o name" for shorter output (resource/name).
+
+.PP
+\fB\-\-project\-selector\fP=""
+    The project selector for the cluster resource quota
+
+
+.SH OPTIONS INHERITED FROM PARENT COMMANDS
+.PP
+\fB\-\-api\-version\fP=""
+    DEPRECATED: The API version to use when talking to the server
+
+.PP
+\fB\-\-as\fP=""
+    Username to impersonate for the operation.
+
+.PP
+\fB\-\-certificate\-authority\fP=""
+    Path to a cert. file for the certificate authority.
+
+.PP
+\fB\-\-client\-certificate\fP=""
+    Path to a client certificate file for TLS.
+
+.PP
+\fB\-\-client\-key\fP=""
+    Path to a client key file for TLS.
+
+.PP
+\fB\-\-cluster\fP=""
+    The name of the kubeconfig cluster to use
+
+.PP
+\fB\-\-config\fP=""
+    Path to the config file to use for CLI requests.
+
+.PP
+\fB\-\-context\fP=""
+    The name of the kubeconfig context to use
+
+.PP
+\fB\-\-google\-json\-key\fP=""
+    The Google Cloud Platform Service Account JSON Key to use for authentication.
+
+.PP
+\fB\-\-insecure\-skip\-tls\-verify\fP=false
+    If true, the server's certificate will not be checked for validity. This will make your HTTPS connections insecure.
+
+.PP
+\fB\-\-log\-flush\-frequency\fP=0
+    Maximum number of seconds between log flushes
+
+.PP
+\fB\-\-match\-server\-version\fP=false
+    Require server version to match client version
+
+.PP
+\fB\-n\fP, \fB\-\-namespace\fP=""
+    If present, the namespace scope for this CLI request.
+
+.PP
+\fB\-\-server\fP=""
+    The address and port of the Kubernetes API server
+
+.PP
+\fB\-\-token\fP=""
+    Bearer token for authentication to the API server.
+
+.PP
+\fB\-\-user\fP=""
+    The name of the kubeconfig user to use
+
+
+.SH EXAMPLE
+.PP
+.RS
+
+.nf
+  # Create an cluster resource quota limited to 10 pods
+  oc create clusterresourcequota limit\-bob \-\-project\-selector=openshift.io/requester=user\-bob \-\-hard=pods=10
+
+.fi
+.RE
+
+
+.SH SEE ALSO
+.PP
+\fBoc\-create(1)\fP,
+
+
+.SH HISTORY
+.PP
+June 2016, Ported from the Kubernetes man\-doc generator

docs/man/man1/oc-deploy.1

@@ -22,26 +22,18 @@ and scaling up new ones. Use 'oc rollback' to rollback to any previous deploymen
 
 .PP
 There are several deployment strategies defined:
+.IP 
 
-.PP
-.RS
-
-.nf
-Rolling (default) \- scales up the new deployment in stages, gradually reducing the number
-
-.fi
-.RE
-
-.PP
+.IP
+\(bu Rolling (default) \- scales up the new deployment in stages, gradually reducing the number
 of old deployments. If one of the new deployed pods never becomes "ready", the new deployment
-  will be rolled back (scaled down to zero). Use when your application can tolerate two versions
-  of code running at the same time (many web applications, scalable databases)
-    Recreate \- scales the old deployment down to zero, then scales the new deployment up to full.
-
-.PP
+will be rolled back (scaled down to zero). Use when your application can tolerate two versions
+of code running at the same time (many web applications, scalable databases)
+.IP
+\(bu Recreate \- scales the old deployment down to zero, then scales the new deployment up to full.
 Use when your application cannot tolerate two versions of code running at the same time
-    Custom \- run your own deployment process inside a Docker container using your own scripts.
-
+.IP
+\(bu Custom \- run your own deployment process inside a Docker container using your own scripts.
 .PP
 If a deployment fails, you may opt to retry it (if the error was transient). Some deployments may
 never successfully complete \- in which case you can use the '\-\-latest' flag to force a redeployment.

docs/man/man1/oc-set-probe.1

@@ -28,9 +28,12 @@ Setting both liveness and readiness probes for each container is highly recommen
 The three probe types are:
 .IP \(bu 2
 
-\item Open a TCP socket on the pod IP
-\item Perform an HTTP GET against a URL on a container that must return 200 OK
-\item Run a command in the container that must return exit code 0
+.IP
+\(bu Open a TCP socket on the pod IP
+.IP
+\(bu Perform an HTTP GET against a URL on a container that must return 200 OK
+.IP
+\(bu Run a command in the container that must return exit code 0
 .PP
 Containers that take a variable amount of time to start should set generous
 initial\-delay\-seconds values, otherwise as your application evolves you may suddenly begin

docs/man/man1/oc-set-volumes.1

@@ -29,30 +29,23 @@ you cannot change a pod's volumes once it has been created.
 
 .PP
 Volume types include:
+.IP 
 
-.PP
-.RS
-
-.nf
-emptydir (empty directory) *default*
-
+.IP
+\(bu emptydir (empty directory) \fIdefault\fP
 A directory allocated when the pod is created on a local host, is removed when
 the pod is deleted and is not copied across servers
-hostdir (host directory)
-
+.IP
+\(bu hostdir (host directory)
 A directory with specific path on any host (requires elevated privileges)
-persistentvolumeclaim or pvc (persistent volume claim)
-
+.IP
+\(bu persistentvolumeclaim or pvc (persistent volume claim)
 Link the volume directory in the container to a persistent volume claim you have
 allocated by name \- a persistent volume claim is a request to allocate storage.
 Note that if your claim hasn't been bound, your pods will not start.
-secret (mounted secret)
-
+.IP
+\(bu secret (mounted secret)
 Secret volumes mount a named secret to the provided directory.
-
-.fi
-.RE
-
 .PP
 For descriptions on other volume types, see 
 \[la]https://docs.openshift.com\[ra]