Bug 1399065

Summary:	[RFE] /var/lib/pulp growing on satellite
Product:	Red Hat Satellite	Reporter:	Vladimir Dulava <vdulava>
Component:	Content Management	Assignee:	satellite6-bugs <satellite6-bugs>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Katello QA List <katello-qa-list>
Severity:	low	Docs Contact:
Priority:	unspecified
Version:	6.1.10	CC:	bbuckingham, bkearney, mhrivnak, vdulava
Target Milestone:	Unspecified	Keywords:	FutureFeature
Target Release:	Unused
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2017-02-27 13:26:02 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:
Embargoed:

Description Vladimir Dulava 2016-11-28 08:36:12 UTC

Description of problem:
/var/lib/pulp on our satellite server keeps growing.  This is where the synced rpms from Redhat are. Customer wants to have some way to purge old or unused rpms on a regular schedule to manage the growth of this filesystem.

Version-Release number of selected component (if applicable):
Sat 6

How reproducible:
100%

Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:
Customer wants the synced repository not to contain old version of packages and requested this RFE to be open.

Comment 1 Michael Hrivnak 2016-12-12 19:48:02 UTC

Pulp has a feature that does this for RPMs, and is an optional setting on the yum importer. See "retain_old_count" here: http://docs.pulpproject.org/plugins/pulp_rpm/tech-reference/yum-plugins.html#yum-importer

Katello would need to expose that option.

For any other similar functionality, for example with other data types, the user must be given the opportunity to choose what kind of pruning should happen. Pulp's default is to retain content by default, which is an important guarantee.

I'm moving this to the "Content Management" component, so that katello can evaluate any other desired pruning scenarios, and make pulp RFEs as required.

Comment 2 Brad Buckingham 2017-01-05 01:18:03 UTC

In Satellite 6.2, there are a couple of features that may be set on repositories that may be useful in managing space:

1. 'Mirror on Sync':  With this feature, each time a repository is synchronized, if a new version of a package is downloaded, the old version is removed.

2. 'On Demand' (Download Policy):  With this feature, the content will only get downloaded to the filesystem when a client requests it.

Would either of these features address the customers needs?