DevOpsDays has now finished, but had a great time...
In a change to the normal Developer Conferences that I attend, I have just finished up at the DevOpsDays London Conference. More and more I have hearing about how you can better improve the deployment of applications and software by closely combining both the Developer and Operations teams. This is a relatively new idea to me, and I was very interested to hear, from people who have done this, what can be achieved!
This was a very "different" conference to what I have attended in the past, but in this case, "different" is a good thing! The format was similar, in the sense that there were prepared session on each morning from various speakers, but each afternoon was given over to Open Spaces (more on this below). I had never been to an Open Space session before, and I was very intrigued. Turns out they are a GREAT way to learn! In addition, just before lunch time, there were a series of Ingite talks (again, more on these below).
Overall, I got a lot from this conference. After two days of hearing what can be done in terms of Configuration Management, Automated Deployments, Team Collaboration, my mind is buzzing with how some of these principles can be taken back to the office. As to how many we will be able to implement, that is another question, but the fact that I now know that some of them exist, is half the battle!
What follows are some rough notes taken across the duration of the two days.
In total, across the two days, there were seven prepared sessions. Details on these can be seen below:
- Niek Bartholomeus
- "DevOps for Dinosaurs"
- This was a really great introduction to what DevOps is, and what it is trying to achieve. The talk centered around the work that Niek had done in a company that he worked at to bring DevOps processed into being. It was really great to hear the experiences from someone who had been through the process.
- John Clapham
- "Checking DevOps Vital Signs" -In this talk, John explained how in applying DevOps to his organisation, they attempted to garner some metrics so that they could accurately "measure" how it was helping. This is a big stumbling block for DevOps. i.e. how do you prove that the system is working, and actually providing value. They chose to do this by measuring several vital signs (Cycle Time, Shared Purpose, Motivation, Collaboration, Effectiveness). The first is reasonably simple to measure, but the others not so much. They opted to collect this information in the form of a questionnaire.
- David Mytton
- "StartOps: Growing an Ops Team from 1 founder"
- Again, another interesting session, where David explained the decisions that he had taken in establishing his business. He was in a position where he had to be pragmatic in adopting the tools and processes that he did. As the company grew, he was able to adopt different tools and services, to ensure that the company was heading in the right direction.
- Slides will appear here
- Some interesting posts here
- Deri Jones
- "Adding Business Metrics"
- Thomas Falkenberg and Nils Probson
- "DevOps and the traditional Enterprise IT"
- A very open, and honest, discussion of how the team at Payback had slowly, over the period of two years, implemented a culture of DevOps. They found that they are now in a position where Dev and Ops teams have common goals. However, this can only be achieved by:
- Working together
- One step at a time
- Change takes time and patience
- An important takeaway from this talk "The term DevOps helped form a common language, a mantra. i.e. if the business has a problem, then the company, both the Dev and Ops, need to work together to fix the issue
- Sam Eaton
- "DevOps and the hell of a Thousand Different Platforms"
- This was an amazing talk! Sam is clearly enthusiastic about this topic, and this flowed through in his talk. I later found out that this was his first public talk, which certainly didn't show! He had some very interesting ideas, the best of which was the "FailCake". Basically, in collaborating between Dev and Ops, it is "ok" to make mistakes, but these have to be discussed immediately within the team, without associating blame. They best way they have found to do this is by bringing cake to the meetings!
- Gene Kim
- "How can we better sell DevOps"
- This was a VERY inspiring session. Gene Kim, an author of the hugely popular "The Phoenix Project" book, explained how to best sell DevOps within the enterprise. I would highly encourage you to take a look at the slides linked below as they explain, in detail, the barriers that exist Dev and Ops team, and how they are perceived from either side.
For me, this was the stand out part of the conference. I had never been to an Open Space before this conference, but I will definitely be looking to attend others. I am also going to suggest that this is something that we should be looking to include within DDD events.
The format is reasonably simple. Anyone can suggest a topic to be discussed in an Open Space. This can be asking for an answer to a question. Providing a demonstration of a piece of software, or technology. Pretty much anything.
With the sessions proposed, these are then organised "roughly" into order, and people "vote" with their feet, and go to the sessions that interest them. This then takes the form of an open discussion, where anyone is free to talk, ask questions, and provide input.
We were told that Open Spaces follow three main principles:
- Whenever it starts is the right time
- Whatever happens is the only thing that could have
- It's over when it's over
All I can say is...
Amazing! I got so much out of these sessions. So many snippets of information, and suggestions.
Before attending DevOpsDays, I hadn't heard of Ignites. Turns out this form of talks (which were held on both days just before lunch time) are similar to the 20 x 20 talks that I have seen at DDD events. Basically, there are a set number of slides, each of which are timed to automatically transition to the next slide. The speaker has to keep up with each transition, as they can't go back to a previous slide. Topics here ranged from a custom-built tool for automatic deployments to being conscious of the server farms that you are using and their carbon footprint.
Well done to everyone who was brave enough to do one of these Ignites, I still think the format is very difficult, and I wouldn't like to do one myself.
Some of the slides that I am aware of from these Ignites can be found here:
During the various sessions, and Open Spaces, there were a number of recommendations made. These included blogs, podcasts, books, etc. I have captured the ones that I could below. If I have missed anything, or if there are any that you would like to add, please feel free to get in touch.
IRC Channels and Application Recommendations
- The Phoenix Project
- You can get a free 170 page excerpt here
- DevOps for Developers
- Getting Real
- The Toyota Way
- DevOps Cookbook (Not released yet)
- The Goal
- Agile Coaching