Last week was all about OpenStack and making sure my team from Linaro/ARM was present on all the relevant sessions. There was only two of us there and with so many sessions happening at the same time, it became obvious that we would only be able to cover so much ground, so we decided to focus on the topics that are important for us this cycle.
Some of the most interesting conversations for me happened outside the sessions themselves. I found out about the 3rd party CI team and decided to join them on their weekly meetings from now on. This is important for Linaro because one of our main priorities is to get 3rd party CI for OpenStack set up on AArch64 hardware.
We were also working on the automatic set up of tempest for RefStack users. Right now the set up of tempest has a very steep learning curve. We want to make this as low as possible so that people can start testing without having a very deep understanding of tempest. See point 3 of action items on this etherpad. Having changed test environments and test clouds my fair share of times, this is a topic very close to my heart. There is a lot of engineering time going into configuring tempest properly on all sort of different environments, so trying to minimise this should save time in the long run to many teams.
As discussed on the previous post, the first two days were about Kolla and ramping up on the project’s priorities for us. The Kolla meetings were well organised and driven, making us feel like we were using our time wisely by being there.
Some interesting topics from these discussions:
- Integration testing between kolla-ansible, kolla and k8s: https://etherpad.openstack.org/p/kolla-pike-ptg-cross-repo-infra
- Kolla-kubernetes 1.0.0 requirements: https://etherpad.openstack.org/p/kolla-pike-ptg-k8s-release-roadmap
- How to move an installed cloud to a kolla containerized version: https://etherpad.openstack.org/p/kolla-pike-ptg-brownfield
- Multiarch and ARM64 containers: https://blueprints.launchpad.net/kolla/+spec/multiarch-and-arm64-containers, https://marcin.juszkiewicz.com.pl/2017/02/22/my-work-on-kolla
- DPDK running with kolla: https://blueprints.launchpad.net/kolla/+spec/ovs-dpdk
During the horizontal teams days, I attended mostly Ironic sessions. This is a comprehensive summary of the discussions (https://etherpad.openstack.org/p/ironic-pike-ptg-ongoing-work).
One of the main issues in Ironic is to get good reviewers/core developers involved in the project. They were having very interesting discussions around how they may or may not have enough time to review things that are not in their current roadmap, but they feel like they should make the time for this. Becoming core developer of any OpenStack project does require a lot of time and dedication. Reviews of code from others, not only the code that you may be interested in is required. Also, Ironic has a variety of core developers that may review code from very different angles, all those are valuable, but there is a feeling that people contributing may find them a bit of a hit and miss when trying to get a patch landed.
The Ironic team is going to work on a list of recommendations for new contributors to be able to join the efforts in a more seamless way.
There were also discussions about how to deprecate the Ironic client and move to the new OpenStack client over the coming cycles.
The Ironic UI is a good place for new contributors to make a positive impact in the project. There is a list of features on a google doc that are there for new contributors to work on, the person to coordinate with on irc is TheJulia.
I also attended a couple of Nova sessions. My take from those was about quotas and how quotas may be breaking compatibility on Pike, for more information see etherpad. another interesting topic was the Nova REST API discussion, see etherpad.
Overall I am quite pleased with how the PTG was organised and run. It was up to the different PTLs to decide how to run the sessions and the ones I attended were mostly productive.
One problem I had, during the horizontal days, is that I could only really focus on one project. Other years I have attended the midcycles for Interop WG and separately for Infra/QA, and that gave me time to be part of both conversations, whilst now I have to choose just one horizontal team, so my involvement with Interop and Infra/QA was minor this cycle, due to the need to focus on Kolla. Funnily enough, the weekly IRC meetings for Interop and Kolla also coincide, so I have been having to choose between the two for a few weeks now. Having to choose between horizontal teams is not my preferred choice, I would have preferred to be able to attend Interop and Infra/QA even if it meant travelling an extra time.
I was however able to attend the Ironic meetings, which I wouldn’t have if I hadn’t been in Atlanta last week, as our involvement with that projec is not big enough to justify going to a midcycle for it.
Another lesson learnt, I didn’t need to be there on Friday, since the sessions I was interested in pretty much winded down on Thursday.
I would have liked to have a t-shirt from this event, but we got project mascot stickers instead. My laptop surely liked this, as it doesn’t wear t-shirts well.
It was overall a great week and I got a voucher for ODS in Boston that I intend to use.