Bug 1389418

Summary: Customize Persistent volume auto cleaning
Product: OpenShift Container Platform Reporter: Miheer Salunke <misalunk>
Component: RFEAssignee: Bradley Childs <bchilds>
Status: CLOSED WONTFIX QA Contact: Xiaoli Tian <xtian>
Severity: medium Docs Contact:
Priority: medium    
Version: 3.1.0CC: aos-bugs, eparis, jokerman, mmccomas, swatt
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2017-02-09 16:15:41 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description Miheer Salunke 2016-10-27 14:31:08 UTC
1. Proposed title of this feature request
=> Customize Persistent volume auto cleaning 


3. What is the nature and description of the request?
=>  Request is to include a feature to delay the PV recycling for 1 - 7 days

4. Why does the customer need this? (List the business requirements here)

=> When a PVC is deleted, PV recycle is triggered immediately. Incase of a user mistakenly deletes the PVC, this behavior will cause a loss of data in Non Prod/PROD. Hence we need a solution to delay the auto cleaning  process  for a week or for three days. Incase of any humar error will lead to loss of critical bussiness data.

5. How would the customer like to achieve this? (List the functional requirements here)
=>  Delaying the PVC recycle will help us to control the loss of application/customer data. 

6. For each functional requirement listed, specify how Red Hat and the customer can test to confirm the requirement is successfully implemented.
=> If any workaround can be proposed for openshift 3.1/3.2, we would able to test and advise you.


7. Is there already an existing RFE upstream or in Red Hat Bugzilla?
=> Nope

8. Does the customer have any specific timeline dependencies and which release would they like to target (i.e. RHEL5, RHEL6)?
=> If this can be included in openshift 3.4, that would be helpful

9. Is the sales team involved in this request and do they have any additional input?
Nope

10. List any affected packages or components.
=> 

11. Would the customer be able to assist in testing this functionality if implemented?
=>   If any workaround can be proposed for openshift 3.1/3.2, we would able to test and advise you.

Comment 2 Steve Watt 2017-02-09 16:15:41 UTC
With the advent of dynamic provisioning, we have deprecated the ability to recycle persistent volumes.