IdP packaging for Linux (deb/rpm)
Etienne Dysli-Metref
etienne.dysli-metref at switch.ch
Tue May 12 04:39:34 EDT 2015
I see in the list archive that this topic has already been discussed a
long time ago
(http://shibboleth.net/pipermail/dev/2011-November/000219.html) and most
respondents seemed happy to have a package if there would be one.
The reason I'm bringing this up again is I'm currently writing a Puppet
module to manage deployment of IdPv3 and, though executing shell
commands like the IdP installer from that tool works, it's really ugly.
This stuff belongs more in a package pre/post-install scripts than in a
Puppet configuration and would make my module much simpler. Moreover, I
think the rise of configuration management software (Puppet, Chef,
Ansible, SaltStack, etc.) and the kind of infrastructure automation they
enable adds new weight to the importance of packaging software in a way
these tools handle. If you don't have DEB or RPM packages available,
automated deployments and upgrades become more painful (i.e. manual,
can't be repeatedly tested). And tomorrow it's going to be building
Docker or LXC containers with this...
So is packaging the IdP (as DEB or RPM) something you [Shibboleth
developer] could consider doing or have you already decided against it?
I mean "only" producing the packages as part of a release, not having
the IdP included in common Linux distributions and abiding by their
packaging policies.
Cheers,
Etienne
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: OpenPGP digital signature
URL: <http://shibboleth.net/pipermail/dev/attachments/20150512/0b52a11e/attachment.sig>
More information about the dev
mailing list