Docker

[Paul Caskey]

Good question!

I think Docker/containerization is just part of a bigger discussion about architecture and processes.

The overall idea is to bring Shibb (and other apps) into a CI/CD architecture.  

Externalize your configs in a get repo.  

Config mgmt., change mgmt., repeatability, etc.

Infrastructure as software (this is where Docker shines), automated deployment, versioning, etc.

IdP nodes as cattle (to be replaced at any time without concern), not pets.

And so on...

Containerization is a critical piece of that architecture, but definitely just a piece to the puzzle.

After many discussions throughout this community, we feel like it is the right thing to do and that's why the classes are taught using containers.


Thanks!



-----Original Message-----
From: users <users-bounces at shibboleth.net> On Behalf Of Donald Lohr
Sent: Wednesday, September 16, 2020 10:41 AM
To: users at shibboleth.net
Subject: Docker

I was asked today by one of our folks in a Shibboleth class, if we are using docker with our Shibboleth IdP deployment.  We aren't.

What's good about it and bad about it? Basically why would I want to use it?

Thanks,
Don

-- 
D o n a l d   L o h r
I n f o r m a t i o n   S y s t e m s
J a m e s   M a d i s o n   U n i v e r s i t y
5 4 0 . 5 6 8 . 3 7 3 0

--
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