Unifying DevOps Model – Who generates the generators?

In modern Build/DevOps environments, we use a lot of tools, each with its own configuration model. In this session, targeted at build managers and devops enigneers, we will be using a tool agnostic, DSL-based model to configure and model a complete environment and generate all necessary artifacts (like Jenkins jobs/pipelines, Icinga configurations and documentation) out of this central model, effectively bringing the DRY pricinple to DevOps. By using a dynamic, strongly typed model, we get all the benefits of modern development, like IDE support, validation and automated tests.

This session will show principles as well as an exemplary implementation.

Objective: People who attend this session will learn about the basic principles of a unifying model-based DevOps/Build management approach as well as useful open source tools and ideas to start implementing their own solutions.

Prerequisites: Attendants should have basic knowledge of administrating either a build systems like Jenkins and/or common DevOps tools like Puppet or Ansible. Basic programming skills are useful, but not strictly necessary.

You can view Stephan’s slides below:

Stephan Pauxberger CLL17 Slides

Track 1
Location: Date: May 17, 2017 Time: 3:00 pm - 3:45 pm Stephan Pauxberger, ipado