The Must-Attend

Open Infrastructure Event

The world runs on open infrastructure. At the OpenStack Summit, you’ll learn about the mix of open technologies building the modern infrastructure stack, including OpenStack, Kubernetes, Docker, Ansible, Ceph, OVS, OpenContrail, OPNFV, and more. Whether you are pursuing a private, public or multi-cloud approach, the OpenStack Summit is the place to network, skill up and plan your cloud strategy.

Sydney
November 6-8, 2017

The Must-Attend

Open Infrastructure Event

Join the movement behind the most widely deployed open source cloud platform. Whether you are pursuing a private, hybrid or multi-cloud approach, the OpenStack Summit is the place to network, skill up and plan your cloud strategy.

Sydney
November 6-8, 2017

Event Details


Upstream bug triage: The hidden gem?

Doing upstream bug triage is not a lot of fun—for very little recognition. Wait, are you sure?

In this talk, we'll show you the reasons why that assertion is untrue. You'll hear from Nova contributors that will show you how conducting active bug triage can help you gain knowledge. 

During the session, we'll show some Nova bits, but it doesn't require knowledge of the code base. This talk is targeted to operators and occasional contributors as a way to gain deep knowledge on Nova and to help them integrate with the Nova developer community.

While Nova bugs are the focus, the related points could be applied to any OpenStack project.


What can I expect to learn?

That talk specifically aims to show how doing bug triaging can be the best way to learn a specific OpenStack project and to get social interactions for free. Most of the time, people wanting to contribute to a specific OpenStack project come by the fact they want to implement a specific feature (if they're lucky and have that in mind) or just try to figure out which pieces to contribute. This is a very frustrating experience (mainly in big projects where the tech debt can be high).

On the other side, doing bug triage is not super fancy. But, when you do that, you have to dig into code to check whether it can be reproducable, you have to reach other people to give you more details on the specific involved codebase, and you have to test the bug by yourself.

All those steps make the perfect experience for someone who wants to embark on a project. After a couple of weeks, you gain visibility (because weekly meetings always focus on bugs), recognition (in particular if you decrease the backlog) et technical expertise (because you played so hard that you know all the quirks).

That happened to me on a big project (Nova) and I see that pattern often. I surely think it's nice to prove that to the community so we can somehow give more credits to the people who do the dirty work.

On the plus side, my talk is showing bits of Nova code for the purpose of that talk, which can be interesting for people wanting to know more on nova (in particular the services and some major features).

 

Monday, November 6, 11:35am-12:15pm
Level: Intermediate
Red Hat
Sylvain currently works as a Senior Software Engineer at Red Hat mainly dedicated on Nova (Compute) and is one of the maintainers (called nova-core). His love story with OpenStack began in 2012 as an operator/deployer running Diablo, but as he was too busy to chase and fix bugs, he decided to create some by himself. When he has (unfortunately not that much) free time, he contributes to organize... FULL PROFILE
Red Hat
I'm a software developer working in the OpenStack team at Red Hat. I predominantly work with Nova, where I'm a core reviewer, though I've also been known to tinker with projects all over the OpenStack ecosystem. I previously worked at Intel, where I contributed to OpenStack (Nova and Neutron also) and Open vSwitch (led internal testing and validation efforts). FULL PROFILE