Shinken also seems like an abandoned project. It would be great to move to icinga2 so
we’d be on a live project, and that’s in Debian stable. It would need very similar
management to shinken if we went that route since it would be a cloud-internal service
(possibly improved over what we do now?). I don’t believe that opening the prod firewall
to nrpe interactions happening with Cloud VPS is wise.
Wikimedia Cloud Services
On Feb 25, 2019, at 11:06 AM, Filippo Giunchedi
On Mon, Feb 25, 2019 at 6:40 PM Giovanni Tirloni <gtirloni(a)wikimedia.org
If we poke roles in the firewall so Icinga can reach the VMs and we
define the monitoring::service stuff in Puppet, is that all we need to
shutdown Shinken? Do you think there would be any concerns with going
I'm not sure, what checks does shinken do ATM that we'd need to port over to
icinga? Right off the bat it seems simpler to me to fire up a icinga stretch VM and move
over the checks and their puppetization to that VM instead, what do you think?
I'm asking about this because soon we'll see requests about removing
more and more Jessie support from the Puppet codebase  and there's no
exit strategy from Jessie for Shinken (it's not available in Stretch
unless we want to package things ourselves, which I tried and failed).
Ouch! I didn't realize there's no shinken in stretch :( though it seems like a
great occasion to get rid of it!
Cloud-admin mailing list