Bug 1084483

Summary:	RFE function for delta publish of rpm repos
Product:	[Retired] Pulp	Reporter:	Magnus Jernberg <magnus.jernberg>
Component:	rpm-support	Assignee:	pulp-bugs
Status:	CLOSED UPSTREAM	QA Contact:	pulp-qe-list
Severity:	high	Docs Contact:
Priority:	low
Version:	2.4 Beta	CC:	skarmark
Target Milestone:	---	Keywords:	FutureFeature, Triaged
Target Release:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Enhancement
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2015-02-19 01:13:01 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 Magnus Jernberg 2014-04-04 12:57:20 UTC

Description of problem:
When publishing a RPM repository containing loads of repos, the publish function is turning out as a bottle neck in our continuous delivery workflow. One reason for this is that the publish will republish the complete repository.
I would like the publish step to consider the changes made to the repo and only recalculate the metadata for those rpm's.


Version-Release number of selected component (if applicable):
2.3 and 2.4

How reproducible:
load your repo with 100 000 RPM's and publish.

Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:
The time spent calculate the metadata in a publish should only be dependent on the added and deleted rpms in the repository.


Additional info:

Comment 1 Brian Bouterse 2015-02-19 01:13:01 UTC

Moved to https://pulp.plan.io/issues/226