Autobahn
Autobahn-software (A-S) and Authobahn-network (A-N) are 2 similar
projects aiming at management's centralization of software and network
development and maintenance. A-S is a set of guidelines and softwares
allowing a master control process to monitor a repository for devs's
commits, compile and run available unit tests,
then create a package and ship it to test for QA, and eventually to
live systems. I'm looking forward to add a forth step in between QA and
live called Zombie. I came across this concept at my current work place
and would like to work more on it. The idea is to quarantine, via
several methods
like iptables, a subset of the live environment such as to create a
closed network only accessible to a specific set of users for final
testing. Unfortunately adding the quarantine layer makes
such environment not ideal for capacity tests, and could possibly
introduce elements of disturbance. The other option would be to
develop and customize the software for self-quarantining, but this is
not ideal and would have higher costs. Yet, it depends what the aim is,
obviously the best condition would be a perfect mirror of the live
environment in terms of settings and hardware, but this is frequently
not possible. The author's idea is no changes should be introduced into
the code and using proper methodologies and software the noise
introduced by the quarantine layer is negligible.
A-N is built on a similar model and aims to glue together several
system administration core softwares like : config management (puppet/cfengine),
nagios, Munin, netflow connection tracking, h-inventory, sms alerting and more.
Adminotaur
Collections of ideas for a fully distributed monitoring system based on nagios and ganglia. More info coming soon.