[katello-devel] Content views operations optimization

[Ivan Necas]

----- Original Message -----
> Would it be possible write a plugin, that would allow publishing one repo
> through more paths? It seems that would solve all this problems, without
> increasing of complexity. What we would need do in Katello is separating the
> repository (as the content container) and the paths (entry points) it's
> available on (repo has many entry points).
> 
> Doesn't make sense to do that in core pulp? There is already possible to
> publish the repo via http and/or https, which is just 2 entry points for the
> same repo as well.

>From quick scan of pulp and runcible, it seems that this would be already
possible with today's pulp, just adding new distributor to the repo
when promoting the repos (and removing the distirbutor when replacing
the old content view version)

-- Ivan

> 
> I believe this would radically reduce the content view promotion time, as
> well as improve the stability (less things that can go wrong). Majority of
> the long-running operations then would happen in Library, when publishing
> new version of content view, where even when something goes wrong, no actual
> systems are affected.
> 
> -- Ivan
> 
> ----- Original Message -----
> > I just had a thought on this. Katello could write a pulp distributor plugin
> > that takes a repo ID at publish time and simply copies the published repo
> > on
> > disk. I still recommend against this approach and wouldn't include it in
> > pulp itself, but it is one of the benefits of the plugin design. Writing
> > something like that, including the Katello calls to publish to that
> > distributor in certain cases, is probably less than a day of work.
> > 
> > Sent from my iPhone
> 
> _______________________________________________
> katello-devel mailing list
> katello-devel at redhat.com
> https://www.redhat.com/mailman/listinfo/katello-devel
>