[Pulp-dev] Lazy for Pulp3
jsherril at redhat.com
Wed May 16 18:52:25 UTC 2018
On 05/16/2018 01:02 PM, Brian Bouterse wrote:
> A mini-team of @jortel, @ttereshc, @ipanova, @dkliban, and @bmbouter
> met today to discuss Lazy use-cases for Pulp3. The "initial" use cases
> would all be delivered together as the first implementation to be used
> with Pulp 3.0. The ones for "later" are blocked on other gaps in
> core's functionality (specifically content protection) which should
> come with 3.1+.
> Feedback on these use cases is welcome. We are meeting again on this
> upcoming Monday, after which, we will writeup the work into Redmine.
> We'll email this thread with links to the Redmine plan when it's
> available for comment.
> Initial use cases are:
> * pull-through caching of packages (squid)
> * parallel streaming of bits to multiple clients (squid)
> * Pulp redirects to squid when content is not already downloaded (pulp)
> * streaming data and headers (streamer)
> * After streamer downloads the content, the new Artifact is created
> and associated with the correct ContentArtifact (downloader)
> * to use a configured downloader, configured by the correct remote.
> This would correctly configure authentication, proxy, mirrorlists,
> etc. when fetching content (streamer)
> Use cases to be implemented later. Currently blocked because Pulp
> itself doesn't verify client entitlement for content currently.
> * authentication of the client to verify they are entitled to the
Could I suggest to consider:
* The ability to delete all downloaded content in a repository
(basically null out the content). I've been using this rhel7 repo for
years, and likely all the old content is not needed anymore.
I've seen this requested from time to time over the past couple years.
> Pulp-dev mailing list
> Pulp-dev at redhat.com
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Pulp-dev