Operability.IO , coming to London September 24-25, is an event about DevOps from the operations point of view, exploring topics like software operability; IT operating models; and how to plan, organize and recruit for modern IT operations in light of all the new processes, tools and techniques that are changing the industry forever.
It all started three years ago when NoOps came to the scene, and quickly became one of the dumbest marketing terms ever coined, as John Allspaw so clearly put it:
— John Allspaw (@allspaw) February 1, 2012
Time went by and we kept seeing these ideas spread, and not just from marketers, but techies alike. We then wrote a very short post titled “It Takes Two to DevOps,” pointing out that learning the syntax of a configuration management tool and spinning a few EC2 instances is not the same as knowing how to build and operate systems, and we started getting quite a lot of feedback.
But the world around us kept pushing the idea of DevOps — mainly as a way for developers to get rid of operators — and we pushed back with our own perspective in the form of a 6,000 word ebook. We wanted to show that a key goal of DevOps is to ensure that software runs well in production, especially in the context of regular deployments.
The increasing prevalence of complex, distributed software systems calls for approaches that anticipate and expect failures, transient behavior, emergent states and unpredictability. Making software run well in this dynamic, interconnected world is the focus of software operability.
We realized that while content about technical solutions abounds, the same cannot be said for the topics we knew were both key and being ignored by the majority of the events out there. And so Operability.IO was born.
In order to make sure the event is true to its vision and goals we decided not to do a call for presentations, and instead personally invite people we believe can bring the right perspectives and experiences to the table.
There are really two threads here. One is about all the ways we can use tools and processes to operate software better. The other is about how the software itself can be made more operable.
Operable? Inoperable? Teams and systems, monitoring, alerts correlation, infrastructure as code and ops scarcity are the topics of day one. Speakers will share a mix of theory, practice, experience and ideas from both the technology and people perspectives.
In day two we will look at how you build the best ops team possible. How you scale your team, deal with incidents and solve differences are some of the topics we have scheduled. Where is the fine line between software and teams? Do security and/or mobile change anything?
Come and join us to hear the answers to those and more questions.