Operations Teams need to provide eight critical services to the developers and users of their environment. At my current employer, I use open source software to provide these services that allow our developers to be more productive and our customers to experience stable, responsive service.
Source Code Management
Keep all of our bespoke software, configurations and notes under strict version control.
|Pros:||Fast Stable Many developers familiar with it due to Github's popularity|
|Cons:||Steep learning curve Somewhat cryptic commands|
Build, test, version and package our software so that it may be quickly and safely deployed to our staging environment
|Pros:||Easy Integration with GIT Nice GUI Flexible enough to meet our needs|
|Cons:||Configuration limited to GUI Written in Java*|
Spin up nodes to become part of the processing farm and decommission nodes no longer required
|Sofware:||Custom scripts using [Fog](http://fog.io)|
|Pros:||Simple scripts Easy to customize Support multiple cloud providers|
Ensure that all nodes are automatically and correctly configured and remain in a known configured state
|Pros:||Easy configuration language Well supported Active community|
|Cons:||Have to learn said configuration language Requires serious investment of time|
Check on services and nodes to ensure that things are behaving as expected before the customer notices
|Pros:||Can be easily auto-configured by Puppet Well understood Nagios syntax Works well with nagios checks and plugins|
|Cons:||Requires serious investment of time and constant care|
Collect system metrics for assessing performance and capacity planning. Some organizations have monitoring perform this role, but I have very strong opinions on this being kept separate.
|Pros:||Light, fast daemon on each box Flexible server Many plugins availble|
|Cons:||Separate process to run Requires a lot of disk and disk I/O|
Centrally collect, store and monitor system and application logs
|Pros:||Rsyslog provides flexible configs MongoDB backed server performs well Easy front end for log viewing|
|Cons:||Takes a while to learn Mongo Harder to pull/backup then text logfiles|
Allow developers and technical staff to deploy and monitor application activity. Since each infrastructure is unique, it makes sense to build a custom solution to this problem.
|Pros:||Sinatra makes it easy to write simple web applications Mcollective is extremely fast ActiveMQ is very flexible and resilient|
|Cons:||Sinatra is not a full featured as Rails Mcollective requires a change of thinking about command/control ActiveMQ is Java*|
- I list Java as a con because we do not have extensive in-house Java expertise and it rquires us to install something we would not have normally