Hello John, Can we also mention about what is the recommended way for customers or users to set this option ? I see that is missing in the above comment. Thanks kasturi
sorry if i was not clear the way i asked the question. I was expecting us to add a line in the document saying "though there are two ways of enabling this feautre at 3.11.2, recommended way of doing would be via storage class options" . I was looking for the above statement as well in the doc inputs you provided. Hope i am clear now.
(In reply to RamaKasturi from comment #7) > sorry if i was not clear the way i asked the question. > > I was expecting us to add a line in the document saying "though there are > two ways of enabling this feautre at 3.11.2, recommended way of doing would > be via storage class options" . I was looking for the above statement as > well in the doc inputs you provided. > > Hope i am clear now. Sure. That sounds OK to me. I'm still not 100% on documenting the latter but I'm not dead set against it.
Hi John, The changes suggested by Rachael involve adding the glusterfs_zone variable in the examples shown for the glusterfs and glusterfs_registry section in the inventory file (Chapters 4 and 5 of the Deployment Guide). I have made this change as per Rachael's inputs in the bug. She has also requested to add a separate note/section on how to use the heketi zone checking feature and any pre-requisites required for the same. As per my understanding, you have suggested not to document all the ways to configure the storageclass. Kasturi suggested adding a line "There are two ways of enabling this feature at 3.11.2, recommended way of doing would be via storage class options" and you have disagreed with the latter part of her suggestion. Therefore, could you please let me know your thoughts. It would be helpful if you can provide your inputs at the earliest as I need to address this bug by today as we are nearing the GA. Thanks, Chandrakanth
(In reply to Chandrakanth Pai from comment #11) > Hi John, > > The changes suggested by Rachael involve adding the glusterfs_zone variable > in the examples shown for the glusterfs and glusterfs_registry section in > the inventory file (Chapters 4 and 5 of the Deployment Guide). I have made > this change as per Rachael's inputs in the bug. Sounds good. > > She has also requested to add a separate note/section on how to use the > heketi zone checking feature and any pre-requisites required for the same. > As per my understanding, you have suggested not to document all the ways to > configure the storageclass. Kasturi suggested adding a line "There are two > ways of enabling this feature at 3.11.2, recommended way of doing would be > via storage class options" and you have disagreed with the latter part of > her suggestion. > > Therefore, could you please let me know your thoughts. > It would be helpful if you can provide your inputs at the earliest as I need > to address this bug by today as we are nearing the GA. > Sorry if I was unclear. I _do_ want to document the method of enabling strict zone checking using the storage class. I _do not_ want to document enabling strict zone checking using the ZONE_CHECKING environment variable at this time. Please let me know if this response is sufficient to answer your questions or you need more details.
Created attachment 1546307 [details] PDF version of the OCS 3.11 Deployment Guide
Created attachment 1546761 [details] PDF version of the OCS 3.11 Deployment Guide
Created attachment 1546826 [details] PDF version of the OCS 3.11 Deployment Guide
Created attachment 1547176 [details] PDF version of the OCS 3.11 Deployment Guide
Created attachment 1547532 [details] PDF version of the OCS 3.11 Deployment Guide