Hi! I'm currently trying out pulp with a plan to deploy it in production. However even though I read all the docs I haven't found any good information about HA possibilities and backups.
Only thread on this list seems to be: https://www.redhat.com/archives/pulp-list/2013-February/msg00006.html Only "clustering" solution I managed to came up with is to create a node which will mirror all the repositories of master server. In case the master fails I'll just redirect all the clients to the second server by configuration management. I'd however have to also update all the repositories feeds during the switch to point to right places. Also usability of a load balancer in this scenario would be limited as the secondary node would often lack the updates from master during sync. As the active scenario didn't seem useful I tried to create a A/P setup. First thing I tried was just rsync'ing the /var/lib/pulp contents to another server set up as pulp server. When I started the http/qpidd on the passive node I got no errors and the repositories seemed to work fine. Is this approach OK or is there something I can break badly? It'd be nice to see the cat living once I open the lid... If there is anybody else with some different HA setup I'd really love to hear about it. // Mat _______________________________________________ Pulp-list mailing list [email protected] https://www.redhat.com/mailman/listinfo/pulp-list
