Ashmita, in the link pasted above i do see mention of glusterblock-storage-provisioner pod. Is this what you are expecting to be there or is the ask something else ? Can you please confirm.

Hi Chandrakanth, 

There is no requirement to add "openshift_storage_glusterfs_block_deploy=true" inventory file parameter to section 4.6

If you see in comment 2, I've added the #oc get pods result. 

You need to just add the gluster-block-provisioner pod to the existing #oc get pods result in section 4.6 verify your deployment. 

As of now, in the guide, it is like this:

# switch to the app-storage namespace
oc project app-storage
# get the list of pods here (3 gluster pods +1 heketi pod)
oc get pods
NAME                    READY          STATUS          RESTARTS          AGE
glusterfs-storage-pm8sf 1/1            Running         0                 1h
glusterfs-storage-rsb2v 1/1            Running         0                 1h
glusterfs-storage-zmkfk 1/1            Running         0                 1h
heketi-storage-1-v5skm  1/1            Running         0                 1h

The above has to be changed to:

# switch to the app-storage namespace
oc project app-storage
# get the list of pods here (3 gluster pods +1 heketi pod + 1 gluster block provisioner pod)
oc get pods
NAME                                          READY     STATUS    RESTARTS   AGE
glusterblock-storage-provisioner-dc-1-mphfp   1/1       Running   0          1h
glusterfs-storage-6tlzx                       1/1       Running   0          1h
glusterfs-storage-lksps                       1/1       Running   0          1h
glusterfs-storage-nf7qk                       1/1       Running   0          1h
glusterfs-storage-tcnd8                       1/1       Running   0          1h
heketi-storage-1-5m6cl                        1/1       Running   0          1h

Created attachment 1545474 [details]
PDF version of the OCS 3.10 Deployment Guide

Created attachment 1545475 [details]
PDF version of the OCS 3.11 Deployment Guide