OpenStack Summit November 2014 Paris

OpenStack is a project that in a fairly short amount of time has attracted in its ecosystem most of IT giants, becoming one of the largest collaborative software development efforts ever seen. We'll explore how collaboration works in OpenStack and how companies contribute to the project, what drives their motivations. There will also be time to see examples of how development teams are setup internally at some of these companies in order to maximize effective contributions.

OpenStack QA ensures the upstream stability and quality of OpenStack.

You are interested in the quality of OpenStack? We need you!
You are an developer or quality engineer? We need you!
You are an operator running a cloud and want to ensure your cloud works fine? We need you!

This talk is a starting guide for new contributers and will cover all aspects
of the QA program. We will talk about testing concepts, low hanging fruits
and how you can give feedback to the team.

Neutron is one of the most important and challenging OpenStack projects.  Getting started as a Neutron contributor will put you at the center of the OpenStack revolution. In this session you will get an overview of the Neutron architecture and the tools (Git, Gerrit, Launchpad, Jenkins) you'll need to know to start contributing. We will also walk you through the development process from new feature proposal, to coding best practices, to change testing before submitting, and finally how to handle the review process and community interaction. By the end, you will be ready to start hacking on Neutron.

As the OpenStack community has exploded in size, certain processes and
procedures were put in place in order to allow for more effective
governance and management of the myriad projects that comprise the
OpenStack ecosystem. Tooling was developed around blueprint and design
development, source code management, code reviews, and team
communication, all with the ostensible goal of providing more consistent
and transparent management of project direction.


However, with the introduction of these many processes and tools came a
burden to new contributors as well as a need for mentorship programs to
nurture and guide individuals and organizations into being good
OpenStack community citizens. This talk is a guide to navigating these
processes and tools. It's designed as a tool to help new folks get
introduced to the community, as well as a guide for old hats to mentor
others.

We will cover the following topics:

• The OpenStack community and governance


• Tools we use in the community


• Review and code best practices


• Tips and techniques for best interacting with community members


• Embracing the ebb and flow of corporate and individual agendas

Jay will present the above guide, with Geoff Hollingworth from Ericsson
providing real-world experience in how applying these recommendations
can change a company's experience with the OpenStack community.

Working your way upstream is not easy. In this talk, I will explore how a team of software engineers in HP went from being closed-source enterprise developers to being a full house of ATCs and one core team member. I will look at the personal, departmental and institutional waterfalls that had to be flattened to achieve this.

Back in the day, we forked Diablo and worked feverishly behind closed doors to run v1 of our public cloud. Today we work upstream and run weeks behind trunk with only a handful of proprietary patches. We also offer a "Community Edition" release every 6 weeks that uses TripleO technology to encapsulate some of the learnings we got from running trunk at scale.

Working within a closed-source organization can be a very sterile method of development. Open Source, on the other hand, is anything but. Balancing the delicate relationship between enterprise-level development and upstream community groups is a study in extreme patience, and often involves way too many bald yaks and multi-coloured bike sheds.

Anne and Lana have been doing exactly this at both Rackspace and other organisations. The symbiotic and cyclical relationship between enterprise and upstream has forced them both to forge a new way of approaching their roles. This talk discusses the holistic view that is required when working with both internal and upstream development teams, and includes some dreams about getting the two to overlap just that little bit more.