@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: > 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 <jsher...@redhat.com> wrote: > >> 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: >>> 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 >>> Pulp-dev@redhat.com >>> https://www.redhat.com/mailman/listinfo/pulp-dev >> >> >> >> _______________________________________________ >> Pulp-dev mailing list >> Pulp-dev@redhat.com >> https://www.redhat.com/mailman/listinfo/pulp-dev
signature.asc
Description: OpenPGP digital signature
_______________________________________________ Pulp-dev mailing list Pulp-dev@redhat.com https://www.redhat.com/mailman/listinfo/pulp-dev
