In the fast-paced world of OpenStack development, we often focus on short-term needs like bug fixes and new features. The Oslo Program takes a longer view of the health and sustainability of the project. Our mission is to make OpenStack more maintainable by addressing cross-project code reuse and architectural issues. In this presentation we will cover the origins of Oslo and the processes and tools the team uses to improve OpenStack from the bottom up, making it easier to deploy, more approachable for new contributors, and sustainable for long-term use.
%in Midrand+277-882-255-28 abortion pills for sale in midrand
Taking the Long View: How the Oslo Program Reduces Technical Debt
1. Taking the Long View:
How the Oslo Program
Reduces Technical Debt
Doug Hellmann and Mark McLoughlin
Kilo Design Summit
November, 2014
2. Mission
To produce a set of python libraries containing code
shared by OpenStack projects. The APIs provided by
these libraries should be high quality, stable,
consistent, documented and generally applicable.
3. Project Motivation
• Consistency for deployers
• Consistency for developers
• Identify and foster common patterns
4. Our Motivation
"I cannot imagine the future, but I care about it. I know
I am a part of a story that starts long before I can
remember and continues long beyond when anyone
will remember me. I sense that I am alive at a time of
important change, and I feel a responsibility to make
sure that the change comes out well. I plant my
acorns knowing that I will never live to harvest the
oaks.”
http://longnow.org/clock/
5. Early Days
• Aug 2010 - Jay Pipes registers “openstack-common” on launchpad
• Nov 2010 - Todd Wiley adds plugin handler code to Bexar
• Dec 2010 - Jay Pipes adds early configuration library
• Summer 2011 - Brian Lamar starts database modules
• Oct 2011 - First summit session at Essex summit
6. Essex - Folsom
• Nov 2011 - Jason Koelker creates openstack-common repository; Mark
McLoughlin proposes configuration management module
• Essex Release - Common libraries included in release notes
• Folsom Summit - "managed copy and paste" concepts; work on pbr
library begins
• Aug 2012 - Project granted PTL for Grizzly
7. Grizzly
• Mark McLoughlin elected the team’s first PTL
• Adopt name “Oslo”
• Team grows
• Define our mission statement
• Release oslo.config library
• Rename openstack-common repository to oslo-incubator
8. Havana - Juno
• Havana - Release oslo.messaging; improve incubation tools
• Icehouse - oslo.messaging adoption; evolution of tools and processes;
oslo.db team forms
• Juno - Major graduation push results in 7 new libraries; Liaison program
started
9. The Oslo Team
• Generalist code reviewers
• Specialist API maintainers
16. Graduation Changes
• Clean up configuration options
• Provide configuration-free API?
• Plug leaky APIs
• Expand/contract API to meet needs of consumers
• Name the library