OpenStack Summit 2015 Tokyo – Day 3

By Gema Gomez

Today was the last day of the OpenStack’s Summit Main Conference here in Tokyo. 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 attended some networking sessions 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 was 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: 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 having full test suite results (not just the tests used for the certification itself) 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

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