For what it is worth, at heart pulp3 is a django app. So, following the advice for HA and django apps generally works. A lot of it is driven by the particulars of your use case.
My use case is a little different than yours I'm sure. But in terms of HA for now I'm good with a balancer and nodes in multiple azs, an RDS db with failover, and regular db backups. In my case, the pulp3 server is far enough behind the scenes that even if there were to be a several hour outage, the impact would be minimal. YMMV. Others can chime in with pulp3 specifics. On Fri, Nov 15, 2019 at 11:41 AM Bin Li (BLOOMBERG/ 120 PARK) < [email protected]> wrote: > Does pulp3 support active/active or active/passive configuration? What is > the strategy to restore the pulp3 service on a different server if the > primary is down? Do we have any documentation on this topic? > > Thanks > _______________________________________________ > Pulp-list mailing list > [email protected] > https://www.redhat.com/mailman/listinfo/pulp-list -- J.
_______________________________________________ Pulp-list mailing list [email protected] https://www.redhat.com/mailman/listinfo/pulp-list
