anchor.diff:      readOnly: false
     persistentVolumeReclaimPolicy: Retain <7>
   ----
  -<1> The name of the PV which is referenced in pod definitions or displayed in
  +<1> The name of the PV, which is referenced in pod definitions or displayed in
   various `oc` volume commands.
   <2> The amount of storage allocated to this volume.
  -<3> `accessModes` are used as labels to match a PV and a PVC. They currently
  -do not define any form of access control. 
  -<4> This defines the volume type being used, in this case the *glusterfs* plug-in.
  +<3> `*accessModes*` are used as labels to match a PV and a PVC. They currently
  +do not define any form of access control.
  +<4> This defines the volume type being used. In this case, the *glusterfs*
  +plug-in is defined.
   <5> This references the endpoints named above.
  -<6> This is the gluster volume name, preceded by "/"
  -<7> A volume reclaim policy of "retain" indicates to preserve the volume after the pods
  -accessing it terminate.
  +<6> This is the Gluster volume name, preceded by `/`.
  +<7> A volume reclaim policy of *retain* indicates that the volume will be
  +preserved after the pods accessing it terminate.
   ====
   
   Save the PV definition to a file, for example *_gluster-pv.yaml_*,
  
positive.code:                   <2>
                                       <2>
  ----
  <1> the owner has id 592.
  <2> the group has id 590.
  ====
  
  In order to access the "_HadoopVol_" volume, the container must match the SELinux label, and
  either run with a UID of 592, or with 590 in its supplemental groups. It is recommended to gain
  access to the volume by matching the gluster mount's groups, which will be defined in the pod
  definition below.
  
  By default, SELinux does not allow writing from a pod to a remote Gluster server. To enable
  writing to GlusterFS volumes with SELinux enforcing on each node, run:
  
  ----
  # setsebool -P virt_sandbox_use_fusefs on
  ----
  
  [NOTE]
  ====
  The `virt_sandbox_use_fusefs` boolean is defined by the *docker-selinux* package.
  If you get an error saying it is not defined, please ensure that this package is installed.
  ====
  
  == Creating the Pod
  A pod definition file or a template file can be used to define a pod. Below is a pod spec that
  creates a single container and mounts the gluster volume for read-write access:
  
  .Pod Object Definition
  ====
  
negative.code:     Environment Variables:
  Conditions:
    Type		Status
    Ready 	True
  Volumes:
    gluster-vol1:
      Type:	PersistentVolumeClaim (a reference to a PersistentVolumeClaim in the same namespace)
  