IdP management solutions

[Jim Fox]

Presently we manually copy files to the production servers as needed.
Fortunately they don't change very often.  We do automate updates
to local metadata and attribute release policies.

With version 3 I expect to move to Ansible.  We've been using it
for other software installs and it is very capable.

Jim


On Tue, 3 Feb 2015, David Langenberg wrote:

> Date: Tue, 3 Feb 2015 14:00:15
> From: David Langenberg <davel at uchicago.edu>
> To: Shib Users <users at shibboleth.net>
> Reply-To: Shib Users <users at shibboleth.net>
> Subject: Re: IdP management solutions
> 
> Presently, we use SVN to manage the deployment.  We have two repositories.  One for configs which the IdP loads on startup via the Subversion
> resource [1], and one for the distribution & dependencies.  It's not ideal, but it does work.  We are looking to move off of this setup and onto
> one that uses versioned Docker images + Git to manage the image build+config changes.  
> Dave
> 
> [1] https://wiki.shibboleth.net/confluence/display/SHIB2/IdPConfigResource
> 
> On Tue, Feb 3, 2015 at 11:56 AM, Benjamin Cherian <benjamin.cherian at villanova.edu> wrote:
>       For those that have been using IdP for a while, what solution(s) are you
>       using to manage instances of IdP and changed made to the configuration. Do
>       you use a VCS like Git or SVN, or another tool like Chef or Ansible? What
>       does your setup look like how does your deployment process look like?
>
>       Currently we're looking to setup a load balanced solution with 2 IdP
>       servers in both dev and production. We want a solid solution for managing
>       when we add new RPs, change attribute filters, and make other
>       configuration changes.
>
>       Thanks,
>       Ben Cherian
>
>       --
>       To unsubscribe from this list send an email to users-unsubscribe at shibboleth.net
> 
> 
> 
> 
> --
> David LangenbergIdentity & Access Management
> The University of Chicago
> 
>