<html> <head> <meta http-equiv="Content-Type" content="text/html; charset=utf-8"> </head> <body text="#000000" bgcolor="#FFFFFF"> I think it kind depends in how pulp would do it. Thinking of the yum example, all the information is there in an upstream yum repo for pulp to import the 'publication' as is. If it can be done 'naturally' with a yum repo, there wouldn't be anything special around pulp -> pulp, it'd just be yum_repo -> pulp. However we'd need a pulp dev to chime in here :) Justin <div class="moz-cite-prefix">On 05/14/2018 12:08 PM, Bryan Kearney wrote: </div> <blockquote type="cite" cite="mid:84b2dad9-c2c6-e606-3295-d745e960895e@redhat.com"> <pre wrap="">@Justin, I think that makes sense for Pulp->Pulp. For Matthias, I think he needs Native->Pulp which would not have a publication. -- bk On 05/14/2018 11:42 AM, Matthias Dellweg wrote: </pre> <blockquote type="cite"> <pre wrap="">Mirroring the metedata exactly is also very important for Debian Repositories, because of the way the metadata is signed in lieu of the whole content. So it would be very beneficial, if this could be provided as a 'service' of the pulp core platform somehow. Matthias On Mon, 14 May 2018 11:31:52 -0400 Justin Sherrill <a class="moz-txt-link-rfc2396E" href="mailto:jsherril@redhat.com"><jsherril@redhat.com></a> wrote: </pre> <blockquote type="cite"> <pre wrap=""> From my understanding of pulp 3, this would maybe involve the ability to 'import' a publication. Would that make sense? Justin On 05/09/2018 08:22 AM, Bryan Kearney wrote: </pre> <blockquote type="cite"> <pre wrap="">One of the themes I heard yesterday at the Red Hat Summit was around having a pulp server mirror the upstream RPM repo metadata exactly. The use case is that two pulp servers are behind a load balancer mirroring the same repo. The users would like to be able to flip a yum client acrross the two servers. Running createrepo to make unique repos causes issues for the clients that appear to be errors. I assume this pattern would not be unique for other package clients that cache metadata. So, when looking ahead to pulp 3 I would ask that this be taken into consideration. I can provide more info / use cases if necessary. -- bk _______________________________________________ Pulp-dev mailing list <a class="moz-txt-link-abbreviated" href="mailto:Pulp-dev@redhat.com">Pulp-dev@redhat.com</a> <a class="moz-txt-link-freetext" href="https://www.redhat.com/mailman/listinfo/pulp-dev">https://www.redhat.com/mailman/listinfo/pulp-dev</a> </pre> </blockquote> <pre wrap=""> _______________________________________________ Pulp-dev mailing list <a class="moz-txt-link-abbreviated" href="mailto:Pulp-dev@redhat.com">Pulp-dev@redhat.com</a> <a class="moz-txt-link-freetext" href="https://www.redhat.com/mailman/listinfo/pulp-dev">https://www.redhat.com/mailman/listinfo/pulp-dev</a> </pre> </blockquote> </blockquote> <pre wrap=""> </pre> <fieldset class="mimeAttachmentHeader"></fieldset> <pre wrap="">_______________________________________________ Pulp-dev mailing list <a class="moz-txt-link-abbreviated" href="mailto:Pulp-dev@redhat.com">Pulp-dev@redhat.com</a> <a class="moz-txt-link-freetext" href="https://www.redhat.com/mailman/listinfo/pulp-dev">https://www.redhat.com/mailman/listinfo/pulp-dev</a> </pre> </blockquote> </body> </html>