load balancing 2 shibboleth IdP servers

[Joseph Fischetti]

So every time you push a configuration change - you restart?

Or do you push the configuration files and then restart the necessary services?
________________________________
From: users <users-bounces at shibboleth.net> on behalf of Lipscomb, Gary <glipscomb at csu.edu.au>
Sent: Wednesday, August 5, 2020 7:01:03 PM
To: Shib Users <users at shibboleth.net>
Subject: RE: load balancing 2 shibboleth IdP servers

[EXTERNAL EMAIL]

Same here,
We use puppet to keep all our configurations in sync
Same configuration into devel then qa/uat then production. Full change control process.

-----Original Message-----
From: users <users-bounces at shibboleth.net> On Behalf Of Joseph Fischetti
Sent: Thursday, 6 August 2020 03:09
To: Shib Users <users at shibboleth.net>
Subject: Re: load balancing 2 shibboleth IdP servers

>During upgrades we upgrade the passive site first, evaluate, then make
>it active.  Makes it easy to switch back to the old environment in case
>of any major showstoppers.

Same
Does anybody have a good mechanism for keeping things in sync?  Things like attribute resolvers/filters and metadata providers?
I find myself testing in test, verifying, and then updating each of our prod servers and reloading their services one by one.  It's cumbersome and error prone.

--
For Consortium Member technical support, see https://wiki.shibboleth.net/confluence/x/coFAAg
To unsubscribe from this list send an email to users-unsubscribe at shibboleth.net
--
For Consortium Member technical support, see https://wiki.shibboleth.net/confluence/x/coFAAg
To unsubscribe from this list send an email to users-unsubscribe at shibboleth.net
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://shibboleth.net/pipermail/users/attachments/20200805/4976c45c/attachment.htm>