Re: [Pulp-dev] Lazy for Pulp3

@ipanova, +1 to your names, I updated the epic. FYI, I updated the epic in several ways to allow for the "cache_only" option in the design. I added a new task to add "policy" also to ContentUnit so the streamer can know what to do: https://pulp.plan.io/issues/3763 Other updates to allow for

Re: [Pulp-dev] Lazy for Pulp3

we could try to go with: policy=immediate -> downloads now while the task runs (no lazy). Also the default if unspecified. policy=on_demand -> All the steps in the diagram. Content that is downloaded is saved so that it's only ever downloaded once. policy=cache_only -> All the steps in the

Re: [Pulp-dev] Lazy for Pulp3

On Mon, Jun 4, 2018 at 12:45 PM, Bryan Kearney wrote: > On 05/31/2018 06:36 PM, Jeff Ortel wrote: > > > > > > On 05/31/2018 04:39 PM, Brian Bouterse wrote: > >> I updated the epic (https://pulp.plan.io/issues/3693) to use this new > >> language. > >> > >> policy=immediate -> downloads now while

Re: [Pulp-dev] Lazy for Pulp3

The config we used in pulp2 can be seen here: https://docs.pulpproject.org/user-guide/deferred-download.html#squid In that scenario we used a reverse proxy to do TLS termination, but I think squid will do the TLS termination in this case. We haven't configured squid like that before so we'll have

Re: [Pulp-dev] Lazy for Pulp3

On 05/31/2018 06:36 PM, Jeff Ortel wrote: > > > On 05/31/2018 04:39 PM, Brian Bouterse wrote: >> I updated the epic (https://pulp.plan.io/issues/3693) to use this new >> language. >> >> policy=immediate  -> downloads now while the task runs (no lazy). Also >> the default if unspecified. >>

Re: [Pulp-dev] Lazy for Pulp3

On Thu, May 31, 2018 at 11:39 PM, Brian Bouterse wrote: > I updated the epic (https://pulp.plan.io/issues/3693) to use this new > language. > > policy=immediate -> downloads now while the task runs (no lazy). Also the > default if unspecified. > policy=cache-and-save -> All the steps in the

Re: [Pulp-dev] Lazy for Pulp3

On 05/31/2018 04:39 PM, Brian Bouterse wrote: I updated the epic (https://pulp.plan.io/issues/3693) to use this new language. policy=immediate  -> downloads now while the task runs (no lazy). Also the default if unspecified. policy=cache-and-save   -> All the steps in the diagram. Content

Re: [Pulp-dev] Lazy for Pulp3

I updated the epic (https://pulp.plan.io/issues/3693) to use this new language. policy=immediate -> downloads now while the task runs (no lazy). Also the default if unspecified. policy=cache-and-save -> All the steps in the diagram. Content that is downloaded is saved so that it's only ever

Re: [Pulp-dev] Lazy for Pulp3

On Wed, May 30, 2018 at 4:50 PM, Brian Bouterse wrote: > > > On Wed, May 30, 2018 at 8:57 AM, Tom McKay wrote: >> >> I think there is a usecase for "proxy only" like is being described here. >> Several years ago there was a project called thumbslug[1] that was used in a >> version of katello

Re: [Pulp-dev] Lazy for Pulp3

No opinion on name; foreman will name it whatever they want on the front end user experience. Devs working on pulp-2 to pulp-3 foreman transition may desire maintaining existing names. Yes, I'd say everything but step 14 in that diagram. In addition, I would ensure that the squid cache size is

Re: [Pulp-dev] Lazy for Pulp3

Actually, what about these as names? policy=immediate -> downloads now while the task runs (no lazy). Also the default if unspecified. policy=cache-and-save -> All the steps in the diagram. Content that is downloaded is saved so that it's only ever downloaded once. policy=cache -> All the

Re: [Pulp-dev] Lazy for Pulp3

On Wed, May 30, 2018 at 8:57 AM, Tom McKay wrote: > I think there is a usecase for "proxy only" like is being described here. > Several years ago there was a project called thumbslug[1] that was used in > a version of katello instead of pulp. It's job was to check entitlements > and then proxy

Re: [Pulp-dev] Lazy for Pulp3

I think there is a usecase for "proxy only" like is being described here. Several years ago there was a project called thumbslug[1] that was used in a version of katello instead of pulp. It's job was to check entitlements and then proxy content from a cdn. The same functionality could be

Re: [Pulp-dev] Lazy for Pulp3

On Tue, May 29, 2018 at 9:31 PM, Dennis Kliban wrote: > On Tue, May 29, 2018 at 11:42 AM, Milan Kovacik wrote: >> >> On Tue, May 29, 2018 at 5:13 PM, Dennis Kliban wrote: >> > On Tue, May 29, 2018 at 10:41 AM, Milan Kovacik >> > wrote: >> >> >> >> Good point! >> >> More the second; it might be

Re: [Pulp-dev] Lazy for Pulp3

Looks good. Made a few minor edits. On 05/25/2018 02:11 PM, Brian Bouterse wrote: A mini-team of core devs** met to talk through lazy use cases for Pulp3. It's effectively the same lazy from Pulp2 except: * it's now built into core (not just RPM) * It disincludes repo protection use cases

Re: [Pulp-dev] Lazy for Pulp3

On Tue, May 29, 2018 at 11:42 AM, Milan Kovacik wrote: > On Tue, May 29, 2018 at 5:13 PM, Dennis Kliban wrote: > > On Tue, May 29, 2018 at 10:41 AM, Milan Kovacik > wrote: > >> > >> Good point! > >> More the second; it might be a bit crazy to utilize Squid for that but > >> first, let's answer

Re: [Pulp-dev] Lazy for Pulp3

On Tue, May 29, 2018 at 10:41 AM, Milan Kovacik wrote: > Good point! > More the second; it might be a bit crazy to utilize Squid for that but > first, let's answer the why ;) > So why does Pulp need to store the content here? > Why don't we point the users to the Squid all the time (for the lazy

Re: [Pulp-dev] Lazy for Pulp3

Good point! More the second; it might be a bit crazy to utilize Squid for that but first, let's answer the why ;) So why does Pulp need to store the content here? Why don't we point the users to the Squid all the time (for the lazy repos)? -- cheers milan On Tue, May 29, 2018 at 4:25 PM, Brian

Re: [Pulp-dev] Lazy for Pulp3

On Mon, May 28, 2018 at 9:57 AM, Milan Kovacik wrote: > Hi, > > Looking at the diagram[1] I'm wondering what's the reasoning behind > Pulp having to actually fetch the content locally? > Is the question "why is Pulp doing the fetching and not Squid?" or "why is Pulp storing the content after

Re: [Pulp-dev] Lazy for Pulp3

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 wrote: > > > On 05/16/2018 01:02 PM, Brian Bouterse wrote: > > A mini-team of @jortel, @ttereshc, @ipanova, @dkliban, and

Re: [Pulp-dev] Lazy for Pulp3

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"