Contributing to DefCore

I started attending the IRC meetings of DefCore (InteropWG) during fall last year. I found the topic of cloud interoperability fascinating and tried to learn as much as possible to be able to start contributing. I was clueless for a while until I understood the basic concepts and what the DefCore Committee was trying to achieve and how. Figuring out what interoperability means in a project as complex as OpenStack.

There is a very interesting article written by Mark Voelker that I think is an excellent explanation of what we do.

My first commit happened on April 20th, 2016. I managed (with a lot of help from everyone in the team) to score Keystone’s capabilities. I had to look at the Keystone APIs, understand them, look at tempest tests using those APIs and understand them and also talk to the Keystone PTL to make sure I wasn’t assumming anything wrongly. I learnt a lot in the process and I would encourage any quality engineer working with OpenStack out there to take on the challenge of scoring a project in the coming releases.

Now I am working on a new commit, the DefCore Test Specification. There is a lot of fruitful discussion around the topic and I am learning a lot trying to summarize and make sense of everybody’s opinions/experiences whilsts trying to do what I think is right also. Any comment/review welcome, please contribute your thoughts!