Bug 1387507 - [Doc RFE] Document how to delete a claim
Summary: [Doc RFE] Document how to delete a claim
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Gluster Storage
Classification: Red Hat
Component: doc-Container_Native_Storage_with_OpenShift
Version: cns-3.4
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
: CNS 3.4
Assignee: Bhavana
QA Contact: Prasanth
URL:
Whiteboard:
Depends On:
Blocks: 1385252
TreeView+ depends on / blocked
 
Reported: 2016-10-21 06:53 UTC by Anjana Suparna Sriram
Modified: 2017-01-23 07:22 UTC (History)
9 users (show)

Fixed In Version:
Doc Type: Enhancement
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-01-23 07:22:38 UTC
Target Upstream Version:
hchiramm: needinfo-


Attachments (Terms of Use)

Description Anjana Suparna Sriram 2016-10-21 06:53:19 UTC
Additional info: This bug will track the following use cases from the content plan: https://docs.google.com/document/d/1SrbUxavmmdbLn7FT2nhOAlX0Q3VTsqPCZyx6wV3gjn0/edit#


Use Case #5 - As an end user, I need to delete a claim.
- Provide detailed instructions regarding how to delete a claim.
- Provide applicable example of a claim deletion reflects a CNS 3.4 context.

Comment 5 Bhavana 2016-11-07 10:26:32 UTC
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

Comment 6 Bhavana 2016-11-10 12:11:17 UTC
The steps for deleting a claim is added in the following bug:

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.

Comment 7 Bhavana 2016-11-14 10:45:58 UTC
Hi Humble,

Let me know if the steps for deleting a claim are correct. In case there are any more details (Note/Important), pls let me know so that include it.

Thanks

Comment 8 Humble Chirammal 2016-11-14 11:42:46 UTC
(In reply to Bhavana from comment #7)


> Let me know if the steps for deleting a claim are correct. In case there are
> any more details (Note/Important), pls let me know so that include it.
> 



Bhavana, I have given the required pointers there. Please fill the outputs from your setup.

Comment 11 Prasanth 2017-01-09 13:47:41 UTC
(In reply to Bhavana from comment #10)
> 5.2.1.6. Deleting a Persistent Volume Claim
> 
> 
> 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


My comments:

* # oc get PVC <claim-name> --> it should be small letter "pvc" and not "PVC"


* Step 2, 3, 4 and 5 under "5.2.1.6. Deleting a Persistent Volume Claim" --> Do we really need to mention these extra verifications as separate steps under this chapter?? AFAIK, this is NOT a mandatory step to be performed for "Deleting a Persistent Volume Claim", rather just a way to cross-check if deletion was successful. 

Can you confirm the same with devel and make the required changes?

Comment 12 Bhavana 2017-01-10 07:32:31 UTC
Hi Ashiq,

Can you please share your thoughts for the suggestion regarding 5.2.1.6. Deleting a Persistent Volume Claim" in comment 11 ?

Comment 13 Bhavana 2017-01-10 10:52:07 UTC
Also, just adding that the additional verification steps were added based on the review comments in:

https://docs.google.com/document/d/16VFLcm2DUtEg__3-FbikKI0lmlkyf9e1BkxmUKz--zM/edit#

I could retain the note at the end and remove the additional steps. Let me know if that is ok.

Comment 14 Mohamed Ashiq 2017-01-10 11:17:53 UTC
Hi,

I have discussed with prasanth and bhavana and change requested is provided. Clearing the needinfo.

Comment 16 Prasanth 2017-01-10 12:17:02 UTC
Verified


Note You need to log in before you can comment on or make changes to this bug.