I'd like to keep this conversation on the mailing list for the benefit of the community as a whole.
Child pulp nodes require that you run a full Pulp installation on those servers. So I don't think this will satisfy your requirement of not running mongodb. With that in mind, I am not sure how consumers are managed when using nodes. Perhaps someone else can answer that question. -Dennis On Wed, Feb 15, 2017 at 1:24 PM, Rene L <[email protected]> wrote: > Hi Dennis, > > thank you for your fast answer. The rsync distributor sounds "ok" for me, > but we´ve to do some workarounds. > > When I choose the child-server concept, i can manage every child-server > and consumer directly on the parent, right? > > Tuz > > 2017-02-15 19:11 GMT+01:00 Dennis Kliban <[email protected]>: > >> One solution is to use a shared filesystem for /var/lib/pulp. Mount that >> filesystem on whatever host you want serving the content and then >> configure httpd to serve it. >> >> Another solution is to use the rsync distributor[0]. The rsync >> distributor was added in 2.10. It allows Pulp to publish content to remote >> servers. >> >> [0] http://docs.pulpproject.org/plugins/pulp_rpm/tech-reference/ >> rsync-distributor.html >> >> >> -Dennis >> >> On Wed, Feb 15, 2017 at 12:18 PM, Rene L <[email protected]> wrote: >> >>> Hi Guys, >>> >>> by the way first, great work! Thanks for this. >>> >>> I've a question about the node/multi-server deployments. We´ve the >>> requirement that repositories will be available on the consumers, but we >>> won't run a full pulp server - primary the mongodb - on each consumer. >>> >>> Is there a way with the build in functionality? >>> >>> Kind regard, >>> >>> Tuz >>> >>> >>> _______________________________________________ >>> Pulp-list mailing list >>> [email protected] >>> https://www.redhat.com/mailman/listinfo/pulp-list >>> >> >> >
_______________________________________________ Pulp-list mailing list [email protected] https://www.redhat.com/mailman/listinfo/pulp-list
