OpenStack has seen success with deployments, products, and services. To ensure long term health and success, Red Hat promotes an "upstream first" mindset where investments are prioritized in the OpenStack community. This includes designing, developing, testing, and contributing all code upstream. It brings benefits like influence, quality, security, and interoperability. Horizontal teams work across projects in areas like release management, infrastructure, documentation, and more. Individuals can help by becoming active contributors and serving as liaisons between teams.

1. OPENSTACK: UPSTREAM FIRST
RUSSELL BRYANT - @RUSSELLBRYANT
TECHNICAL DIRECTOR, OPENSTACK
OFFICE OF TECHNOLOGY
https://redhat.slides.com/rbryant/openstack-east-august-2016

2. OPENSTACK SUCCESS

3. OPENSTACK SUCCESS
Deployments
Products
Services
Training
...

4. PRIORITIZING FOR SUCCESS

5. PRIORITIZING FOR SUCCESS
The long term health and success
of the OpenStack community.

6. UPSTREAM FIRST
A mindset of prioritizing
investment in the community.

7. UPSTREAM FIRST CODE

8. UPSTREAM FIRST CODE
WHAT?
design, dev, test
all upstream
VALUE
influence
maintenance
quality and security
interoperability
RISKS OF FORKING
quality
user expectations
technical debt
interoperability

9. DEVELOPMENT
BEYOND FEATURES
Code Reviews
Bug Triage and Fixing

10. DEVELOPMENT
MY FIRST SIX WEEKS IN PATCHES

11. DEVELOPMENT
MY FIRST SIX WEEKS IN PATCHES
1 - Trivial doc fix
2 - Small bug fix
3 - API docs and code cleanup
4 - My new feature
5-15 - Cleanup and fixes mostly unrelated to my feature

12. HORIZONTAL TEAMS

13. HORIZONTAL TEAMS
OpenStack has 58 official project teams
A lot of support and coordination required
Horizontal teams work across all projects
How can you help?

14. RELEASE MANAGEMENT
Mission
Coordinating the release of OpenStack deliverables, by defining the
overall development cycle, release models, publication processes,
versioning rules and tools, then enabling project teams to produce
their own releases.

15. RELEASE MANAGEMENT
How can you help?
Be aware of the release cycle:
http://releases.openstack.org
Serve as a liaison.

16. HORIZONTAL TEAM LIAISONS
Serve as the primary interface between a horizontal team
and a project focused team.

17. INFRASTRUCTURE
Mission
Develop and maintain the tooling and infrastructure needed to
support the development process and general operation of the
OpenStack project.

18. INFRASTRUCTURE
CI nodes
http://grafana.openstack.org/dashboard/db/nodepool

19. INFRASTRUCTURE
Day (last week) Nodes Used
Monday 14,868
Tuesday 19,310
Wednesday 21,329
Thursday 24,930

20. INFRASTRUCTURE
How can you help?
(besides donating cloud capacity)
More long-term half to full-time contributors.
Across all time zones.
Manage both code and systems.
Serve as a liaison.

21. DOCUMENTATION

22. DOCUMENTATION
Mission
Provide documentation for core OpenStack projects to promote
OpenStack. Develop and maintain tools and processes to ensure
quality, accurate documentation. Treat documentation like
OpenStack code.

23. DOCUMENTATION
Fantastic team developing great content.
http://docs.openstack.org/
If we don't document features, they might as well not exist.

24. DOCUMENTATION
How can you help?
Need more active and engaged subject matter experts.
Serve as a liaison.
Contributions can be raw source content.
1 Open a bug with some bullet points.
2 Provide a link to a blog post explaining the feature.
3 Write a patch and get doc team editorial help.
4 Write a patch and incorporate doc team feedback yourself.

25. MORE HORIZONTAL TEAMS
Oslo
QA (devstack, grenade, tempest)
Stable branch
Vulnerability Management
I18n

26. LIAISON OPPORTUNITIES
API Working Group
Logging Working Group
Inter-project liaisons
Cross-project specs
https://wiki.openstack.org/wiki/CrossProjectLiaisons

27. FURTHER UPSTREAM
Consider projects upstream from OpenStack.
Recent example for me - Open vSwitch

28. FURTHER UPSTREAM
Reported contributions from OpenStack community members to
projects that somehow touched OpenStack.
Doug asked the openstack-dev mailing list.
86 projects listed.
https://doughellmann.com/blog/2016/06/23/openstack-
contributions-to-other-open-source-projects/

29. BEYOND DEVELOPMENT
Give your teams time to help make OpenStack successful.
Product Working Group
Join discussions and review proposals.
Share your experience.

30. OPENSTACK SUCCESS

31. UPSTREAM FIRST

32. twitter.com/RedHatNews
youtube.com/redhat
facebook.com/redhatinc
THANK YOU!
plus.google.com/+RedHat
linkedin.com/company/red-hat