I’ve just made it back from DevOpsDays in Ghent, Belgium. This was my first DevOpsDays event, and the atmosphere was celebratory as it was the fifth anniversary of the first, and sadly Patrick Dubois’s last event as the main organiser as he is stepping down.
Thanks go to Patrick and the rest of the organisers who had gone to incredible lengths to look after the attendees, including shuttle buses from the hotel, a generous breakfast both days and even an fantastic evening meal on the Monday. This meant that we could make the most out of meeting people and discussing each other’s experiences.
Also, Ghent is one of the prettiest cities I have ever seen.
There was some retrospecting on the last five years of the devops movement, and plenty of discussion around the culture surrounding the area. From the developer biased turnouts at local events I was surprised to find myself very much in a minority as someone whose origins are in development. There was discussion around whether we are all developers now, which I felt were inevitable as the terms ops and dev are in the title of the event. It feels to me that it is much more useful to describe people’s responsibilities as engineering rather than focussing on ops and dev as separate roles, particularly as doing otherwise undervalues the years of experience that many people have in each area.
As highlighted by Gareth Rushgrove in issue 1 of DevOpsWeekly, “It’s safe to say Devops means different things to different people”, and that led to a few inevitable meta discussions about the meaning of the term. Speaking time was split between organised speakers and an open session format, with a fun ignite segment in between to wake us up after lunch. I was surprised at people were more focussed on culture than on technology, but in retrospect this makes sense with a conference which is centered around a subject variously understood to mean collaboration and respect.
The open sessions were a great opportunity to get a grass roots view of what is going on in the companies the attendees came from. It was fascinating to find that no one was running Docker (at least at any scale), despite the conference’s ‘Docker… Docker… Docker’ meme highlighting the excitement around the technology. Similarly no one was able to say they are using immutable infrastructure in their organisations. Deployable images were mentioned a number of times, although this was conflated with immutable infrastructure.
I was surprised and pleased to learn that plenty of people want to improve their Linux repository management, making server builds deterministic whilst still updating packages from upstream repositories. @mini_inny mentioned aptly as a versioned package repository for Debian, but it does not support RPMs (yet). Thinking beyond OS packages, and more around products, Ringo De Smet talked about his product in development ReleaseQueue, which promises to allow you to version the collection of packages, recipes, gems, jars, wars and whatever else your product needs to run (the ‘bill of materials’), providing private URLs where appropriate for repository clients (such as apt-get). This is a very smart approach, since it is the product that we care about, and I look forward to seeing whether it would suit us.
I was pleased to have caught the session about Ops Learning (especially with regard to development practices) and will be exploring some of the ideas such as pull requests for operations code review, fun side projects such as implementing something specific in a new language, reading other people’s pull requests and Ops focussed hack days.
Logging was a well attended session, with many people using and advocating Elasticsearch / Logstash / Kibana, some using Graphite and StatsD, and some using Reimann for alerting and statistical modelling.
Tuesday’s talk about “The Cognitive Neuroscience of Empathy” was excellent, and a fascinating insight into how we are hard wired to exhibit empathy with our peers through mirror neurons. The conclusions that you should praise more, trust more and treat others as you expect to be treated seem like excellent goals.
I also took quite a bit away from Brian Troutwine’s talk about “Automation with Humans in Mind”, (see the article on InfoQ for a wordier summary) particularly about what good automation looks like, and how it is important to understand what you are building—abstraction is necessary but you shouldn’t be ignorant (sentiments echoed the evening before in hotel bar discussions).
I think one of my favourite things though has to be introducing a BuzzFeed employee to What if programmers used BuzzFeed-style commit messages.