The first DevOps conference in Israel turned out to be a great success.
With a room filled to capacity, and even people sitting on the floor just to take part - the energy level just hit the roof.
First thing first - in this post I'm going to focus only things that were covered in the main hall, as I wasn't able to attend all tracks.
Main take away (In 140 Characters)
- Ben Kepes - Keepers of the Keys to the Kingdom - IT as manufacturing pipeline, undeployed code as wasted goods in inventory
- Ran Tavory - DevOps a Jungle of Tools - Infra management and application deployment are two distinct things
- Uri Cohen - One Does Not Simply Walk Into DevOps: There are three parts to DevOps. Culture & Processes, Infrastructure as Code, Application as Services.
- Clive Foley - We Tried to Build a DevOps Team and All We Got was this Lousy T-shirt - Having a DevOps team that is responsible for DevOps, is the wrong way to run DevOps
- Yosef Dinerstein - Continuous Deployment with Node.js over Azure - Microsoft Azure is not a .Net shop anymore
Common takeaways (Some, in slightly more than 140 Characters)
- NoOps? What's the role of IT in a DevOps world? The role of IT is to build tools and infrastructure that will allow developers to run their stuff straight into production.
- DevOps is about culture not tools.
- Applications need to be designed as loosely coupled services, otherwise it becomes impossible to manage continuous changes.
- It’s about accountability - Developers need to be accountable for running their code in production.
- Why do most applications in the cloud run outside of PaaS <- most people build their own kind of *private* PaaS
- Will (public) PaaS makes ops obsolete? <- heated debate - my personal view, probably in 3-5 years if nothing gets in the way <- Avishai you can relax, you have plenty of time before you'll need to find a new Job :)
- How to convince your management that DevOps is the right thing? – It’s about culture. You need to get the buy-in from top management. A useful way to get that buy-in is through the "build-it and they will come" approach. Once people "see the light" it’s much easier to get their buy-in for an idea.
Quotes of the day:
If it moves graph it, if it matters alert it (Allspaw)
You build it, You run it (Werner Vogels)
Done means Released (Jez Humble)
"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
Final Words - DevOps as a Movement
The are three elements that makes a movement IMO - Frustration->Disruption->Passion
DevOps certainly fits into all three.
- Frustration (Pain) - many of us have been frustrated by not being able to do our Job, but rather get stacked by someone else’s job.
- Disruption (Cure)- DevOps leads to a complete disruption on many fronts - the way we design our apps (Services), the way our organization works (breaking up silos), the way we run our business (agile, continuous delivery)
- Passion (Tell the world) – as a human being when we go through such pain and we feel that we’ve found a cure for that pain, we get passionate about it and we want to share it with others who share the same pain. DevOps seems to be that cure.
To put it in Seth Godin’s words
Leaders make movements, movements make change.
Now it’s your turn to become a leader or a messenger, and there are now many tools to make your job easier - you can start by proposing meetups, sessions, blogging, tweeting, and of course RT... or if you’re too shy for all that, just click Like or simply RSVP to the next event..
Where do we go from here?
There are currently two scheduled (local) events that are worth noting in this context:
- Check out the next Carburetor podcast - Ran Tavory, Ori Lahav and Myself will be sharing thoughts from the event on DevOps
If you have a great story that you want to share suggest a new DevOps meetup on the IGT Meetup page and we’ll take care of the rest..