Kris Buytaert

Most organisations start their journey towards Continuous Delivery with their development teams, or often their web or mobile teams. I’ve seen many of these journeys fail because “ops” was not included in the picture. The organisation assumed DevOps didn’t need ops. So the team didn’t adapt, didn’t provide the right stacks, couldn’t support the tools. I’ve started a number of successful journeys with the ops teams doing Continuous Delivery of their infrastructure as code. They changed their mindset, allowing them to understand, support and onboard the development teams. This talk will document that approach with some supporting cases and examples.

Taking one step further we'll showcase a on how to do Continuous Delivery of your Infrastructure as Code, obviously with Open Source tools

It is fairly well known to the early adopters , that the devops movement would never have happened if it weren’t for a number of open source enthousiast and contributors to share their code, pains, problems , solutions and expierences at different conferences before devopsdays.

Yet today , there still is a large gap between the developers of different distros and the people that deploy and use them, the ops ..

everywhere you look you will find gaps between the developer and the users.

This talk will be about closing these gaps. It will be about helping out eachother to make Open Source solve even more Business needs. By adopting devops principles

Yet today , there still is a large gap between the developers of different distros and the people that deploy and use them, the ops ..

everywhere you look you will find gaps between the developer and the users.

This talk will be about closing these gaps. It will be about helping out eachother to make Open Source solve even more Business needs. By adopting devops principles