anchor.diff:  . Create the PersistentVolume from the file:
   +
   ----
  -$ oc create -f pv.yaml
  +$ oc create -f pv1.yaml
   ----
  +
  +. Create a PersistentVolumeClaim that maps to the PersistentVolume you created in the previous step.  Create a file, `pvc1.yaml`, with the PersistentVolumeClaim object definition:
  ++
  +[source,yaml]
  +----
  +apiVersion: v1
  +kind: PersistentVolumeClaim
  +metadata:
  +  name: pvc1 <1>
  +spec:
  +  accessModes:
  +    - ReadWriteOnce
  +  resources:
  +   requests:
  +     storage: "1Gi" <3>
  +  volumeName: pv1 <4>
  +----
  +<1> A unique name that represents the PersistentVolumeClaim.
  +<2> The PersistentVolumeClaim’s access mode. With ReadWriteOnce, the volume can be mounted with read and write permissions by a single node.
  +<3> The size of the PersistentVolumeClaim.
  +<4> The name of the existing PersistentVolume.
  +
  +. Create the PersistentVolumeClaim from the file:
  ++
  +----
  +$ oc create -f pvc1.yaml
  +----
  
positive.code: $ shell vmware-vdiskmanager -c -t 0 -s <size> -a lsilogic <disk-name>.vmdk
  ----
  
  . Create a PersistentVolume that references the VMDKs. Create a file, `pv.yaml`, with the PersistentVolume object definition:
  +
  [source,yaml]
  ----
  apiVersion: v1
  kind: PersistentVolume
  metadata:
    name: pv <1>
  spec:
    capacity:
      storage: 2Gi <2>
    accessModes:
      - ReadWriteOnce
    persistentVolumeReclaimPolicy: Retain
  
negative.code:   * Create using `vmkfstools`. Access ESX through Secure Shell (SSH) and then use following command to create a VMDK volume:
  +
  ----
  $ vmkfstools -c <size> /vmfs/volumes/<datastore-name>/volumes/<disk-name>.vmdk
  ----
  
    * Create using `vmware-diskmanager`:
  