This feature should be available on both a server or a node. It would allow the server or node to act as a caching proxy. For now, lets call this lazy loading. In this model, the server (or a node), would have recent copies of the metadata. However, it would not actually sync the package from the feed location until they are requested by a client. This would allow for only the content being used to be pulled down to the file system and for repositories to be created by only downloading the metadata.
Comment 2pulp-infra@redhat.com
2015-07-24 17:30:17 UTC
The Pulp upstream bug status is at NEW. Updating the external tracker on this bug.
Comment 3pulp-infra@redhat.com
2015-07-24 17:30:18 UTC
The Pulp upstream bug priority is at High. Updating the external tracker on this bug.
Verified in Satellite 6.2 Beta Snap 6 Compose 1.
While lazy sync still has some outstanding issues, I am satisfied that is has already fulfilled this RFE.
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.
https://access.redhat.com/errata/RHBA-2016:1501
Comment 11pulp-infra@redhat.com
2016-11-28 18:33:00 UTC
The Pulp upstream bug status is at CLOSED - NOTABUG. Updating the external tracker on this bug.