Bug 1386885

Summary:	[RFE] Extend the Pruning Functionality to Include "Inactive" Namespaces
Product:	OpenShift Container Platform	Reporter:	Steven Walter <stwalter>
Component:	RFE	Assignee:	Michal Fojtik <mfojtik>
Status:	CLOSED DEFERRED	QA Contact:	Xiaoli Tian <xtian>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	3.3.0	CC:	aos-bugs, dlbewley, erich, jokerman, mbarrett, mmccomas, stwalter
Target Milestone:	---	Flags:	erich: needinfo? (stwalter)
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:	2018-03-12 13:54:36 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 Steven Walter 2016-10-19 18:33:57 UTC

1. Proposed title of this feature request

 Extend the Pruning Functionality to Include "Inactive" Namespaces

 

3. What is the nature and description of the request?

 As an administrator, I have developers who create a bunch of projects but they don't clean up after themselves.   How can I delete their inactive projects?  (ideally, if inactive for 1 week or something like that).

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

 Minimize administrator needing to perform mundane or repetitive cleanup tasks to keep a stable environment

5. How would the customer like to achieve this? (List the functional requirements here)

 Working out details for what "inactive" means for a project. Otherwise, most likely rolled into an oadm prune-style command.

6. For each functional requirement listed in question 5, specify how Red Hat and the customer can test to confirm the requirement is successfully implemented.

 Run "oadm prune projects/namespaces" and have unused projects be deleted

7. Is there already an existing RFE upstream or in Red Hat bugzilla?

 No

8. Does the customer have any specific timeline dependencies?

 None specified

11. Would the customer be able to assist in testing this functionality if implemented?

 Likely

Comment 2 Steven Walter 2017-01-09 18:47:13 UTC

" I think it's open to interpretation what inactive means. The concern was that users are creating lots of test projects that they abandon, and there is no obvious way to tell which ones are in use and which ones may be pruned.

It probably comes down to a policy problem to some extent, but it would be useful if there were some sort of project "auditor" function. Some things it might do

- validate git repo referenced by buildconfigs
- validate imagestreams referenced by buildconfigs
- detect lack of traffic to any routes for X days
- detect lack of routes or services
- detect orphan projects; projects owned by users who have been termed in external auth store (LDAP) or blacklist

That's it off the top of my head. "

Comment 4 Eric Rich 2018-03-12 13:54:36 UTC

This bug has been identified as a dated (created more than 3 months ago) bug. 
This bug has been triaged (has a trello card linked to it), or reviewed by Engineering/PM and has been put into the product backlog, 
however this bug has not been slated for a currently planned release (3.9, 3.10 or 3.11), which cover our releases for the rest of the calendar year. 

As a result of this bugs age, state on the current roadmap and PM Score (being below 70), this bug is being Closed - Differed, 
as it is currently not part of the products immediate priorities.

Please see: https://docs.google.com/document/d/1zdqF4rB3ea8GmVIZ7qWCVYUaQ7-EexUrQEF0MTwdDkw/edit for more details.