<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=us-ascii">
</head>
<body>
<div dir="auto" style="direction: ltr; margin: 0; padding: 0; font-family: sans-serif; font-size: 11pt; color: black; ">
So every time you push a configuration change - you restart?<br>
<br>
</div>
<div dir="auto" style="direction: ltr; margin: 0; padding: 0; font-family: sans-serif; font-size: 11pt; color: black; ">
Or do you push the configuration files and then restart the necessary services?</div>
<hr style="display:inline-block;width:98%" tabindex="-1">
<div id="divRplyFwdMsg" dir="ltr"><font face="Calibri, sans-serif" style="font-size:11pt" color="#000000"><b>From:</b> users <users-bounces@shibboleth.net> on behalf of Lipscomb, Gary <glipscomb@csu.edu.au><br>
<b>Sent:</b> Wednesday, August 5, 2020 7:01:03 PM<br>
<b>To:</b> Shib Users <users@shibboleth.net><br>
<b>Subject:</b> RE: load balancing 2 shibboleth IdP servers</font>
<div> </div>
</div>
<div class="BodyFragment"><font size="2"><span style="font-size:11pt;">
<div class="PlainText">[EXTERNAL EMAIL]<br>
<br>
Same here,<br>
We use puppet to keep all our configurations in sync<br>
Same configuration into devel then qa/uat then production. Full change control process.<br>
<br>
-----Original Message-----<br>
From: users <users-bounces@shibboleth.net> On Behalf Of Joseph Fischetti<br>
Sent: Thursday, 6 August 2020 03:09<br>
To: Shib Users <users@shibboleth.net><br>
Subject: Re: load balancing 2 shibboleth IdP servers<br>
<br>
>During upgrades we upgrade the passive site first, evaluate, then make<br>
>it active. Makes it easy to switch back to the old environment in case<br>
>of any major showstoppers.<br>
<br>
Same<br>
Does anybody have a good mechanism for keeping things in sync? Things like attribute resolvers/filters and metadata providers?<br>
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.<br>
<br>
--<br>
For Consortium Member technical support, see <a href="https://wiki.shibboleth.net/confluence/x/coFAAg">
https://wiki.shibboleth.net/confluence/x/coFAAg</a><br>
To unsubscribe from this list send an email to users-unsubscribe@shibboleth.net<br>
--<br>
For Consortium Member technical support, see <a href="https://wiki.shibboleth.net/confluence/x/coFAAg">
https://wiki.shibboleth.net/confluence/x/coFAAg</a><br>
To unsubscribe from this list send an email to users-unsubscribe@shibboleth.net<br>
</div>
</span></font></div>
</body>
</html>