anchor.diff:  node2     Ready     22h
   NAME                               READY     STATUS              RESTARTS   AGE           1/1       Running             0          1d
   glusterfs-node0-2509304327-vpce1   1/1       Running   0          1d        192.168.10.100   node0
  -glusterfs-node1-3290690057-hhq92   1/1       Running   0          1d        192.168.10.101   node1 <1> 
  -glusterfs-node2-4072075787-okzjv   1/1       Running   0          1d        192.168.10.102   node2 
  +glusterfs-node1-3290690057-hhq92   1/1       Running   0          1d        192.168.10.101   node1 <1>
  +glusterfs-node2-4072075787-okzjv   1/1       Running   0          1d        192.168.10.102   node2
   heketi-3017632314-yyngh            1/1       Running   0          1d        10.42.0.0        node0 <2>
   ----
  -<1> Example of GlusterFS storage pods running (notice there are three for this example).
  -<2> Heketi Server pod.
  -
  -
  -If not already set in the environment, export the HEKETI_CLI_SERVER
  +<1> Example of GlusterFS storage pods running. There are three in this example.
  +<2> Heketi server pod.
  +
  +
  +. If not already set in the environment, export the `HEKETI_CLI_SERVER`:
  ++
   ----
   $ export HEKETI_CLI_SERVER=$(oc describe svc/heketi | grep "Endpoints:" | awk '{print "http://"$2}')
   ----
   
  -Identify the Heketi REST URL and Server IP Address:
  +. Identify the Heketi REST URL and server IP address:
  ++
   ----
   $ echo $HEKETI_CLI_SERVER
   http://10.42.0.0:8080
   ----
   
  -
  -Identify the Gluster EndPoints that are needed to pass in as a parameter into the StorageClass which will be used in a later step (heketi-storage-endpoints).
  -----
  -oc get endpoints
  +. Identify the Gluster endpoints that are needed to pass in as a parameter into
  +the storage class, which is used in a later step (`heketi-storage-endpoints`).
  ++
  +----
  +$ oc get endpoints
   NAME                       ENDPOINTS                                            AGE
   heketi                     10.42.0.0:8080                                       22h
   heketi-storage-endpoints   192.168.10.100:1,192.168.10.101:1,192.168.10.102:1   22h <1>
   kubernetes                 192.168.10.90:6443                                   23h
   ----
  -<1> The defined GlusterFS EndPoints, in this example, they are called `heketi-storage-endpoints`.
  -
  -
  -[NOTE]
  -By default, user_authorization is disabled, but if it were enabled, you might also need to find the rest user 
  -and rest user secret key (not applicable for this example as any values will work).
  -
  -====
  -
  -
  -
  -
  -== Create a StorageClass for our GlusterFS Dynamic Provisioner
  -
  -xref:../../install_config/persistent_storage/dynamically_provisioning_pvs.adoc#install-config-persistent-storage-dynamically-provisioning-pvs[Storage Classes]
  - are used to manage and enable Persistent Storage in {product-title}.  Below is an example of a _Storage Class_ that will request
  -5GB of on-demand storage to be used with our _HelloWorld_ application.
  -
  +<1> The defined GlusterFS endpoints. In this example, they are called `heketi-storage-endpoints`.
  +
  +[NOTE]
  +====
  +By default, `user_authorization` is disabled. If enabled, you may need to find
  +the rest user  and rest user secret key. (This is not applicable for this
  +example, as any values will work).
  +====
  +
  +[[create-a-storage-class-for-your-glusterfs-dynamic-provisioner]]
  +== Create a Storage Class for Your GlusterFS Dynamic Provisioner
  +
  +xref:../../install_config/persistent_storage/dynamically_provisioning_pvs.adoc#install-config-persistent-storage-dynamically-provisioning-pvs[Storage
  +classes] manage and enable persistent storage in {product-title}.
  +Below is an example of a _Storage class_ requesting 5GB of on-demand
  +storage to be used with your _HelloWorld_ application.
   
   ====
   ----
  
positive.code:     persistentVolumeClaim:
        claimName: gluster1 <1>
  ----
  <1> The name of the PVC created in previous step.
  
  
  Create the Pod YAML file.  Save it.  Then submit it to {product-title}.
  ----
  oc create -f nginx-pod.yaml
  pod "gluster-pod1" created
  ----
  
  View the Pod (Give it a few minutes, it might need to download the image if it doesn't already exist).
  ----
  oc get pods -o wide
  NAME                               READY     STATUS    RESTARTS   AGE       IP               NODE
  nginx-pod                          1/1       Running   0          9m        10.38.0.0        node1 
  glusterfs-node0-2509304327-vpce1   1/1       Running   0          1d        192.168.10.100   node0
  glusterfs-node1-3290690057-hhq92   1/1       Running   0          1d        192.168.10.101   node1
  glusterfs-node2-4072075787-okzjv   1/1       Running   0          1d        192.168.10.102   node2
  heketi-3017632314-yyngh            1/1       Running   0          1d        10.42.0.0        node0
  ----
  
  Now we will exec into the container and create an index.html file in the mountPath definition of the Pod.
  ----
  oc exec -ti nginx-pod /bin/sh
  $ cd /usr/share/nginx/html
  $ echo 'Hello World from GlusterFS!!!' > index.html
  $ ls
  
negative.code: $ exit
  ----
  
  . Using the `curl` command from the master node, `curl` the URL of the pod:
  +
  ----
  $ curl http://10.38.0.0
  Hello World from GlusterFS!!!
  ----
  
  . Check your Gluster pod to ensure that the *_index.html_* file was written.
  Choose any of the Gluster pods:
  +
  ----
  $ oc exec -ti glusterfs-node1-3290690057-hhq92 /bin/sh
  $ mount | grep heketi
  /dev/mapper/VolGroup00-LogVol00 on /var/lib/heketi type xfs (rw,relatime,seclabel,attr2,inode64,noquota)
  /dev/mapper/vg_f92e09091f6b20ab12b02a2513e4ed90-brick_1e730a5462c352835055018e1874e578 on /var/lib/heketi/mounts/vg_f92e09091f6b20ab12b02a2513e4ed90/brick_1e730a5462c352835055018e1874e578 type xfs (rw,noatime,seclabel,nouuid,attr2,inode64,logbsize=256k,sunit=512,swidth=512,noquota)
  