[Pulp-list] Replication between Pulp installation

Dennis Kliban dkliban at redhat.com
Mon Jun 29 19:32:11 UTC 2020

Pulp 3 does not have a concept of "nodes". This feature was deprecated in
later releases of Pulp 2. Users of Pulp 3 should create normal Pulp
installations anywhere they wish to have a mirror of their master. These
mirrors should have Remotes with a URL pointing to a Distribution hosted by
the master Pulp. These remotes should then be used to sync content from the
master Pulp. The current limitation of this approach is that you must
create a new Publication in each Pulp. In case of RPM repositories, that
means that metadata will be slightly different on each server. We are
working to resolve this issue by adding an ability to mirror metadata[0].
The goal is to deliver this feature in the Fall of 2020.

[0] https://pulp.plan.io/issues/6353

On Mon, Jun 29, 2020 at 11:29 AM Pablo Martinez Schroder <
pablo at docecosas.com> wrote:

> Hi, I cannot find an automatic way to implement replication between
> different Pulp installations. My use case is I have a data center (let's
> call it master) where all the RPM repositories are stored. We also have
> some other data centers where we want to have a replica of those
> repositories but right now I cannot see a way to achieve it with Pulp 3. Am
> I missing something?
> With Pulp 2 I could use the Children/Parent nodes relationship, is there
> anything similar or some suggestion of what approach would be better with
> Pulp 3?
> Thanks in advance.
> _______________________________________________
> Pulp-list mailing list
> Pulp-list at redhat.com
> https://www.redhat.com/mailman/listinfo/pulp-list
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://listman.redhat.com/archives/pulp-list/attachments/20200629/21612bcf/attachment.htm>

More information about the Pulp-list mailing list