Hide Forgot
Additional info: This bug tracks documentation for the following use cases outlined in CNS 3.4 Content Plan: https://docs.google.com/document/d/1SrbUxavmmdbLn7FT2nhOAlX0Q3VTsqPCZyx6wV3gjn0/edit# Use Case #1 As an administrator, I need to understand concepts related to provisioning storage for a CNS 3.4 deployment. Documentation: Provide descriptive content and workload information related to the following concepts: - dynamic provisioning - storage class - claims - glusterFS Use Case #2 As an administrator, I need to create a storage class that points to a CNS 3.4 deployment. Documentation: Provide detailed instructions regarding how to create a storage class. Provide an applicable example that reflects a CNS 3.4 context. Use Case #3 As an administrator, I need to create a claim that uses a specific storage class to provision CNS 3.4 volumes. Documentation: Provide detailed instructions regarding how to create a claim. Provide an applicable example with a storage class that reflects a CNS 3.4 context. Use Case #4 As an administrator, I need to understand the ramifications/impact that deleting a claim has on both my CNS 3.4 persistent volume and the actual volume. Documentation: Provide comprehensive information that explains the impact and consequences (if any) that occurs when a claim is deleted.
Worked with Humble and reworked on the TOC and the workflow. Currently going through the video created by Humble to try out and document the commands. Updated TOC: https://docs.google.com/document/d/16VFLcm2DUtEg__3-FbikKI0lmlkyf9e1BkxmUKz--zM/edit#heading=h.ekhdtd8n5rrn Video: https://asciinema.org/a/90986
The updated steps are added in the following google doc: https://docs.google.com/document/d/16VFLcm2DUtEg__3-FbikKI0lmlkyf9e1BkxmUKz--zM/edit#heading=h.ekhdtd8n5rrn Need to add oc specific commands and sync up with Humble for a review.
Hi Humble, I have updated the following google doc based on our discussion: https://docs.google.com/a/redhat.com/document/d/16VFLcm2DUtEg__3-FbikKI0lmlkyf9e1BkxmUKz--zM/edit?usp=sharing Please note that I am in the process of bringing up a container setup and add oc specific outputs for each of the command. The o/ps currently are kubernetes specific which will be changed. Let me know if there are anymore changes that are required to be made for the same. Thanks
(In reply to Bhavana from comment #7) LGTM.
The details are now added to the following link. Some of the changes are yet to reflect to this site. http://ccs-jenkins.gsslab.brq.redhat.com:8080/job/doc-Red_Hat_Gluster_Storage-3.4-Container_Native_Storage_with_OpenShift_Platform-branch-dynamic_provisioning_volume_security/lastSuccessfulBuild/artifact/tmp/en-US/html-single/index.html#chap-Documentation-Red_Hat_Gluster_Storage_Container_Native_with_OpenShift_Platform-OpenShift_Creating_Persistent_Volumes Minor tasks pending.
http://ccs-jenkins.gsslab.brq.redhat.com:8080/job/doc-Red_Hat_Gluster_Storage-3.4-Container_Native_Storage_with_OpenShift_Platform-branch-dynamic_provisioning_volume_security/lastSuccessfulBuild/artifact/tmp/en-US/html-single/index.html#idm140175946598960 Moving the bug on_qa
1) section 5.2.1, After creating a Storage Class, a secret for heketi authentication must be creating before proceeding with the creation of persistent volume claim. should be, After creating a Storage Class, a secret for heketi authentication must be created before proceeding with the creation of persistent volume claim. 2) secretNamespace + secretName: Identification of Secret instance that containes should be, secretNamespace + secretName: Identification of Secret instance that contains 3) Under, 5.2.1.2. Creating Secret for Heketi Authentication Create a secret file by executing the following command: should be, Create a secret file, sample secret file is provided below 4) Similar to the above comment, "Create a Persistent Volume Claim file by executing the following command: " has to be changed 5) To verify that the persistent volume is mounted inside the container, execute the following command: # oc rsh busybox The command provided only logs into the shell of the application pod. To check if the mountpoint exists, 'df' command has to be executed in the shell
Also, can you please confirm if this bug has only introduced section "5.2 Dynamic Provisioning of Volumes". I don't see what changes has been introduced as part of this bug.
Hi Karthik, The entire section 5.2, that you reviewed is the new section that was added for dynamic provisioning. This bug includs those updates. The other comments are incorporated: http://ccs-jenkins.gsslab.brq.redhat.com:8080/job/doc-Red_Hat_Gluster_Storage-3.4-Container_Native_Storage_with_OpenShift_Platform-branch-master/lastSuccessfulBuild/artifact/tmp/en-US/html-single/index.html#chap-Documentation-Red_Hat_Gluster_Storage_Container_Native_with_OpenShift_Platform-OpenShift_Creating_Persistent_Volumes-Dynamic_Prov
Looks good, moving the bug to verified.