[Pulp-dev] Lazy for Pulp3

Tatiana Tereshchenko ttereshc at redhat.com
Thu May 17 09:21:39 UTC 2018


Thanks Justin!

+1 to consider this use case, I can confirm that many users asked for that.

Tanya

On Wed, May 16, 2018 at 8:52 PM, Justin Sherrill <jsherril at redhat.com>
wrote:

>
>
> 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
>    content
>
>
>
> 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 listPulp-dev at redhat.comhttps://www.redhat.com/mailman/listinfo/pulp-dev
>
>
>
> _______________________________________________
> Pulp-dev mailing list
> Pulp-dev at redhat.com
> https://www.redhat.com/mailman/listinfo/pulp-dev
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://listman.redhat.com/archives/pulp-dev/attachments/20180517/f6c375c3/attachment.htm>


More information about the Pulp-dev mailing list