My favorite quote is:
Ops’ job is NOT to keep the site stable and fast [but]
Ops’ job is it to enable the business (this is the dev’s job too)
The business requires change
They go on by presenting the dilemma of discouraging change in the interest of stability or allowing change to happen as often as it needs to. This is where they introduce their tools and culture for lowering the risk of change.
In this post I want to share with you how we use some of the tools John and Paul mention.
- Testing Dash Metrics with Cucumber (Bradley Taylor) – A short article showing off a Cucumber feature for monitoring with Nagios.
- Kanban vs. Scrum (Henrik Kniberg) – A great, 26 page long PDF about the similarities and differences between Scrum and Kanban. Absolutely worth reading!
- Reconnoiter (Theo Schlossnagle) – Theo and his OmniTI Labs are working on a new monitoring and trending application – a combination of Nagios, Cacti and the like with the goal to ease administration and scale efficiently. No releases yet but looks promising.
So most companies shoot middle of the road – granting access to a select group of individuals and ensuring there’s some decent logging to monitor usage and proper sick leave and vacation coverage. The question I’d like to help you answer is which individuals should have access. And, of course, like any sane individual, I’ll start my answer with ‘It depends…’ – it depends on the degree of configuration management your environment has.