Ben Kepes of Clouderati fame joined us for the first ever DevOps conference in Israel - and spoke about the driving force behind DevOps in organizations today.
Presented at DevOps Con Israel 2013
DON'T PANIC: GETTING YOUR INFRASTRUCTURE DRIFT UNDER CONTROL, ERAN BIBI, Firefly
DevOps - Keepers of the Keys to the Kingdom
1. DevOpsCon Israel
@benkepes
Diversity Limited
January 2013
DevOps – Keepers of the Keys to
the Kingdom
http://www.flickr.com/photos/jamesjordan/2751393381/
14. “Code that has been written but not yet deployed
is very similar to inventory, you’ve paid the cost
to develop the software but are not yet getting
any of the benefit from it”
- Mark Imbriaco, GitHub
18. “This extremely high level of automation and the work
practices that go with it, together offer a revolutionary
step-change in the way that we engineer complex
systems:- a revolution that companies like Google and
Netflix have embraced; a revolution that the rest of us
ignore at our peril.”
- WT Payne,
http://www.businessweek.com/articles/2012-12-17/google-s-gmail-
outage-is-a-sign-of-things-to-come
20. “Systems that contain and absorb many small
failures without breaking and get more resilient
over time are ‘antifragile’… We actively try to
break our systems regularly so we find the weak
spots… as a result we tend to survive large-scale
outages better than more fragile services.”
- Adrian Cockcroft, Netflix
34. “Every developer must think of the end user. Committing a
piece of code is far from being done. It needs to work in
all kinds of weird use cases. And it’s not only QA’s job to
find all the bugs. Good developers want to ensure that
the new features are not only coded, but tested and
ultimately released to their users. Only then the task is
really done.”
- Matthias Marschall
35.
36. “Having a nice script on your own box is not enough. Every
sysadmin needs to make sure it’s possible to re-create
each part of the infrastructure at any time. When that
slick, new script is under version control, written in a way
others can understand and modify it, is their task really
Done.”
- Matthias Marschall
37. Think like a team
http://www.insuranceage.co.uk/IMG/661/176661/tug-of-war-team.jpg?1305125190
38. “DevOps teams do not run under the constraint of individual
profiles. They have to take broader responsibilities:
everyone needs to care about getting valuable features
into the hands of their users, and everyone should pro-
actively find ways to contribute to the solution of any
release blocker, no matter what the problem is. They
work with ‘Us’ spirit rather than ‘Them/their’.”
- Isha Suri
40. “…QA among the developer teams can ensure
better code performance by having a stringent
focus on code issues and those related to the
general site reliability. Plus, by being more
operationally aware of the production context
that our code lives within, developers can also
design and build better software.”
- Isha Suri
42. “…this is possible only by increasing
communication with operations teams will
we developers learn about these concerns
and incorporate them into our designs and
every day coding decisions.”
- Isha Suri