Oct 29 2015

OpenStack Summit 2015 Tokyo – Day 3

Today was the last day of the OpenStack's Summit Main Conference. Tomorrow there are still developer's sessions ongoing for hacking code and continuing pending conversations, however the bulk of people goes home after today. I did some networking today due to the amount of down time I had, I even got a few minutes to send a postcard from Japan home. 

In the morning I attended two QA working sessions: one of them about resource configuration and the other one about tempest-lib service clients. It was quite interesting to get a heads up of where things are going with tempest and get help from the tempest PTL with a little problem I was having running tempest. It felt like a very productive morning. 

Later I took a bit of time to socialize with one of the ladies that we met at the Women of OpenStack event on Monday. It was lovely to get to talk to her and learn about Japanese work culture. I am looking forward for her to visit the UK and be able to meet again. 

Afterwards I attended a session about debugging the virtualisation layer, by someone at RedHat. I found the talk interesting and I personally learnt quite a bit about how to more efficiently diagnose issues and figure out exactly where things are going wrong. The speaker also shared his blog: http://kashyapc.com/. I have decided to add his blog to the list of blogs I follow.

Towards end the day I attended a double RefStack session about the future of RefStack and the long term strategy. The RefStack team and the DefCore committee are interested in seeing full test suite results (not just the tests used for DefCore certification) for data analysis purposes. As they stand the tempest tests are sometimes unreliable or they may be testing a capability that nobody is interested in implementing, this is all valuable input into the capability review process. There will also be the ability to have "companies" not just "users" on the RefStack website, so that people can upload "official" runs to their respective companies and still provide other runs / keep them for history reasons. When the data is associated with a user, it belongs to them. Once the data is moved to their company, then it stops being theirs and starts to be owned by the company. 

It's been an awesome day. And after dinner I saw with a hint of disappointment the tear down of the main event:

Tear Down

Tear Down

I am heading home soon with a lot of ideas and energy to make them happen… #WeAreOpenStack

Oct 28 2015

OpenStack Summit 2015 Tokyo – Day 2

This morning we started early (7am!) with the Women of OpenStack breakfast session. We had some good discussions around how to help women in technology voice their concerns/ideas and how to make our work more visible to the world. As always it was a pleasure to meet a group of such talented individuals. We took some pics, here's my favourite:



The rest of the day was spent working with another member of the tailgaters group from Rackspace trying to hack on some tests (in our case today it was about trying to set ourselves up to be able to do that going forward). We attended a few DefCore sessions and discussed what is coming to RefStack with Catherine. She was kind enough to show us some neat improvements that are planned for this cycle.

We even made time to go for lunch to a ramen restaurant that served us delicious food I had never tried before. 

At the end of the day I also attended a QA session that was about figuring out the future of the tempest cli and what new options would be useful for end users of tempest going forward. 

It was a great day packed with sessions and hacking/talking about the best approach to testing for the tailgaters group going forward and trying to decide what direction to try to make progress on first. 

Oct 27 2015

OpenStack Summit 2015 Tokyo – Day 1

Today was the first day of ODS for the new release of OpenStack. The day started with a great keynote and I was happy to see a few women on the list of speakers. There was so much good content going on that I struggled to decide what sessions to attend.  

For me, the day was about getting to meet people I have been talking to during this cycle but didn't know, such as the DefCore committee. DefCore is a project that aims at establishing a set of capabilities that define what an OpenStack deployment is. This is quite difficult to do with a product that is a composition of so many different projects and it requires a lot of stable and automated testing in order to be doable. I will post the conclusions from all the discussions I attend to during the week at the end of the summit. Today the scene was set for further conversations where we will get to discuss whether the current process meets the integrators and OpenStack users needs or not (and caters for developers as well), and how to make modifications to it. 

I also attended a brillian workshop where neutron was explained and troubleshooting of problems was described in detail. I enjoyed very much learning how other people diagnose neutron issues and what tools they use and got some ideas. For instance, I didn't know easyOVS makes life so much easier when reading neutron logs. 

I attended a QA session that was about tempest plugins and they were describing/talking extensively about Grenade, a project for testing OpenStack upgrades between releases.

The day ended with a visit to the marketplace for some networking and to be able to see what all the OpenStack players are up to. There was also sushi and beer!


The Marketplace

The Marketplace #WeAreOpenstack

Aug 14 2015


I started testing OpenStack at Canonical a while ago. The project is so interesting that I wanted to spend some of my spare time contributing to it. However, it was not until last ODS in Vancouver that I really got engaged in upstream work and started to believe that I could make an impact on the overall quality of OpenStack. I had never attended the OpenStack Developer Summit before, I enjoyed my days in Vancouver and managed to do a lot of networking with other like minded people. 

I kept asking roughly the same kind of questions in different test related meetings: what are we doing about coverage, how are we planning to improve the stability of the APIs, where can we contribute new test cases that are generic (as opposed to project specific). I wasn't the only one asking these questions, there was a critical mass of engineers from different companies attending the same meetings and interested in the same topics. This is how we all met and decided to do something about it. We had lunch together and started talking about our challenges when it comes to testing OpenStack, what things we can or cannot do with the existing tools/test suites and what projects are the better suited for us to contribute to so we can improve the quality of OpenStack. That is how the OpenStack tailgaters team was born.

I learnt about the Big Tent (video and article) and what it means for the existing test suites and quality of OpenStack itself. Basically there are a few projects that are mature and part of every cloud out there or adhering to the OpenStack governance guidelines and contributing that are considered the "core" of OpenStack, and there is the rest of the projects. There is no "integrated release" anymore. I am not sure what this will mean in the long run, but to me it feels like a step in the right direction to enhance the quality of OpenStack.

If you want to get in touch with the tailgaters (the guys that are trying to add value by making OpenStack more testable and adding new end to end test cases), the options are:

  • IRC, freenode, channel #openstack-tailgate.
  • Weekly IRC meetings at 5pm UTC on Thursdays, in our freenode channel.
  • There is a mailing list that you can request to be added to.