Openstack CI infrastructure Overview

  • -

Openstack CI infrastructure Overview

Openstack is one of the largest OSS projects today with hundreds of commits flowing in daily. This high rate of change requires an advanced CI infrastructure. The purpose of the talk is to provide an overview of this infrastructure, explaining the role of each tool and the pipelines along which changes have to travel before they find their way into the approved Openstack codebase.
Talk delivered by Anton Weiss at Openstack Day Israel 2016 :!agenda/cjg9

  • 0

Devops Enablers vs. DevOps Engineers

A lot has been said and written in these last 3 years in an attempt to define what DevOps really stands for. One thing most of us agree upon is that DevOps is not a job definition – it’s a culture, a mindset, a software manufacturing practice which is focused on breaking the walls between the developers and the operations. And it is a very cool and hip practice, one that everybody likes and everybody wants a piece of.

So job postings for “DevOps engineers” pop up each day like mushrooms after a summer rain.

And we adapt ourselves to the new realities and start calling ourselves DevOps engineers, even though half a year ago we were called CM, or integrators, or system engineers, or whatever.

I myself just signed a new contract for “DevOps” role. And yes – I’m going to do DevOps. But I know that if we want DevOps – everybody in the company has to do DevOps. So my natural goal is that every engineer in the company becomes a DevOps engineer. And that got me  thinking – if everyone is a DevOps engineer –  how will my role be different from all the rest?

I think I have found the right term:

I’ve always liked thinking of what we’re doing at work (you know, providing process automation, building CD pipelines, etc)  as ‘enablement’ – as this enables all the other players of software development life cycle to do their work with more quality, efficiency, visibility and ease.

And that’s exactly what DevOps is for.

So if everybody wants DevOps, we’re going to enable the DevOps.

We’ll be the DevOps Enablers!


Originally posted at


  • 0

GO is now open source!

ThoughtWorks have been industry acknowledged experts in everything related to the practices of Continuous Integration and Delivery throughout the last decade. They were the creators of CruiseControl which was a de-facto standard tool for CI before all the new tools arrived. Neverthless their own commercial Conitnous Delivery platform named ‘Go’ has never come close to the popularity of even Bamboo or TeamCity ( not to mention Jenkins ).

Two days ago they announced they are making Go open-source, obviously as an attempt to increase market share. I gave GO a test-drive a couple of years ago and it seemed like a good tool back then. Now it’s open-source I’ll definitely want to look at it again. I promise to update on my impressons.