Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.
How Big Companies Contribute to
OpenStack
Stefano Maffulli, OpenStack Community Manager
OpenStack Mission
To produce the
ubiquitous open source cloud computing
platform
that will meet the needs of public and pr...
Four years in
 More than 70 OpenStack User Groups exist and 9,400+
new members have joined in the last year
 Community m...
Community Stats – May 2013
ORGANIZATIONS
TOTAL CONTRIBUTORS
AVERAGE MONTHLY
CONTRIBUTORS
COUNTRIES
998 230 136
209
9,511
I...
Community Stats – May 2014
ORGANIZATIONS
CURRENT CONTRIBUTORS
AVERAGE MONTHLY
CONTRIBUTORS
COUNTRIES
2,130 466 139
355
16,...
Trends and Themes in Year Four
 Maturity of use cases, across more traditional industries
like financial services and ret...
Trends and Themes in Year Four
 Focus on operational experience and closing the
feedback loop between operators and devel...
Trends and Themes in Year Four
 Progress on defining OpenStack core, as well as better
testing and definition around plug...
Trends and Themes in Year Four
 Stability, better test coverage and tighter integration
across the software platform
Facts
 Big
 169 git repositories
 2.0M+ LOC
 22 Official Programs (Integrated and Incubated)
 Moving fast
 A new rel...
How Is OpenStack Lead?
 No traditional management structure
 No 'dictator', no 'architect', no 'product manager'
 Repre...
How Is OpenStack Lead?
 Time-based releases, every 6 months
 The cadence keeps people focused
 Milestones to maintain t...
How Is OpenStack Lead?
 Lots of communication during the cycle
 To manage exceptions
 With community leaders, release m...
How Is OpenStack Lead?
 Communication in real life
 Design Summit to begin a new development cycle
 Mid-cycle meetings ...
How Is OpenStack Lead?
 Everyone's code is reviewed and tested
How Is OpenStack Lead?
 Everyone's code is reviewed and tested
How Do People Do This?
 In theory there is no difference between theory and
practice. In practice there is.
Consuming
IaaS
Shipping
products
Companies
involved
Companies
committed
Operators
Users
Developers
Committed Companies
 Have invested in OpenStack as a strategy
 Independent from level of sponsorship
 Lots of developer...
Committed Companies
 Development teams are organized around OpenStack
Release Cycle
 Are deeply involved in the decision...
Example Agile Teams
 Face-to-Face and occasional conversations
 Only online conversations are valued
 Standup meetings ...
Example Agile Teams
 Product backlog vs Blueprints
 Keep the pace, releases scheduled around 6months cycle
 Upstream fi...
Involved Companies
 Invested in OpenStack for tactical reasons
 Developers involved on outskirts first, on core function...
Involved Companies
 Development teams organized around internal release cycles
 Marginally involved in decision making
...
Consuming
IaaS
Shipping
products
Companies
involved
Companies
committed
Operators
Users
Developers
How To Mitigate Friction
 Organize Teams around the open source model
 Coordinate with release cycle
 Get to know the r...
How To Mitigate Friction
 Adopt OpenStack's constraints in your team
 Favor electronic communication, avoid watercooler ...
Too Much To Handle?
 Get developers exposed to OpenStack way of doing things
 Upstream University, two days free trainin...
What You Gain
 Less “your contribution is late or missing tests”
 Your developers will know deadlines and best practices...
November 3-7, 2014 – Paris!
Registration and sponsorships now open!
Call for speakers is open.
Book your travel early, roo...
All text and image content in this document is licensed under the Creative Commons Attribution-Share Alike 3.0 License
(un...
Rise of the Superuser
 Drive transformation
 Give back
 http://superuser.opensta
All text and image content in this document is licensed under the Creative Commons Attribution-Share Alike 3.0 License
(un...
How Big Companies Contribute to OpenStack
How Big Companies Contribute to OpenStack
How Big Companies Contribute to OpenStack
How Big Companies Contribute to OpenStack
How Big Companies Contribute to OpenStack
How Big Companies Contribute to OpenStack
How Big Companies Contribute to OpenStack
Upcoming SlideShare
Loading in …5
×

How Big Companies Contribute to OpenStack

1,868 views

Published on

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.

  • Be the first to comment

  • Be the first to like this

How Big Companies Contribute to OpenStack

  1. 1. How Big Companies Contribute to OpenStack Stefano Maffulli, OpenStack Community Manager
  2. 2. OpenStack Mission To produce the ubiquitous open source cloud computing platform that will meet the needs of public and private clouds regardless of size, by being simple to implement and massively scalable.
  3. 3. Four years in  More than 70 OpenStack User Groups exist and 9,400+ new members have joined in the last year  Community members are located in 139 different countries around the world  More than 1,200 user surveys have been completed, detailing OpenStack deployments
  4. 4. Community Stats – May 2013 ORGANIZATIONS TOTAL CONTRIBUTORS AVERAGE MONTHLY CONTRIBUTORS COUNTRIES 998 230 136 209 9,511 INDIVIDUAL MEMBERS PATCHES MERGED 7,260
  5. 5. Community Stats – May 2014 ORGANIZATIONS CURRENT CONTRIBUTORS AVERAGE MONTHLY CONTRIBUTORS COUNTRIES 2,130 466 139 355 16,266 INDIVIDUAL MEMBERS PATCHES MERGED 17,209
  6. 6. Trends and Themes in Year Four  Maturity of use cases, across more traditional industries like financial services and retail “The software in the games themselves allows users to play a game and immediately share video of what you have done in the game with the rest of the world.” - Joel Johnston “AT&T has 120 applications deployed on OpenStack in 7 data centers” – Toby Ford, AVP IT Operations Strategic Realization “We’re running a serious business on this technology, and this is what we have to do to remain competitive and flexible in this environment.” – Glenn Ferguson, Head of Private Cloud Enablement “I’m trying to lead a revolution to help empower people when they come to work in technology.” - Chris Launey, Direct Cloud Services and Architect at Walt Disney Company
  7. 7. Trends and Themes in Year Four  Focus on operational experience and closing the feedback loop between operators and developers
  8. 8. Trends and Themes in Year Four  Progress on defining OpenStack core, as well as better testing and definition around plugins Images used with permission © Robhirschfeld.com/
  9. 9. Trends and Themes in Year Four  Stability, better test coverage and tighter integration across the software platform
  10. 10. Facts  Big  169 git repositories  2.0M+ LOC  22 Official Programs (Integrated and Incubated)  Moving fast  A new release every 6 months  Programs and projects coming in every release  Complex  Hard to deploy and to test  Lots of people from different countries and companies
  11. 11. How Is OpenStack Lead?  No traditional management structure  No 'dictator', no 'architect', no 'product manager'  Representative democracy  Technical leaders elected by developers  Technical Committee also elected  Board of Directors mostly elected
  12. 12. How Is OpenStack Lead?  Time-based releases, every 6 months  The cadence keeps people focused  Milestones to maintain the rhythm  Roadmap defined via blueprints  Best proposed at the beginning of the cycle  Should have specifications attached  Approved for milestones by PTLs
  13. 13. How Is OpenStack Lead?  Lots of communication during the cycle  To manage exceptions  With community leaders, release manager, committees
  14. 14. How Is OpenStack Lead?  Communication in real life  Design Summit to begin a new development cycle  Mid-cycle meetings for team
  15. 15. How Is OpenStack Lead?  Everyone's code is reviewed and tested
  16. 16. How Is OpenStack Lead?  Everyone's code is reviewed and tested
  17. 17. How Do People Do This?  In theory there is no difference between theory and practice. In practice there is.
  18. 18. Consuming IaaS Shipping products Companies involved Companies committed Operators Users Developers
  19. 19. Committed Companies  Have invested in OpenStack as a strategy  Independent from level of sponsorship  Lots of developers contributing upstream  Have 'core' reviewers  Get their employees elected as Project Tech Leads  Sell products “based on” OpenStack and may also use consume OpenStack  Distributions + extras  Public/private clouds
  20. 20. Committed Companies  Development teams are organized around OpenStack Release Cycle  Are deeply involved in the decision making process  Know how and with whom to communicate  Do a lot of code reviews  Help fix things when they break  Provide resources to the community  Give back a lot and visibly, get good karma  Spend karma to get things done, faster
  21. 21. Example Agile Teams  Face-to-Face and occasional conversations  Only online conversations are valued  Standup meetings with audio/video, even for in-office people  Use internal mailing lists, wiki, instant messaging  Regular meetups in person to socialize, outside work  In-person sprints to develop code
  22. 22. Example Agile Teams  Product backlog vs Blueprints  Keep the pace, releases scheduled around 6months cycle  Upstream first, avoid maintaining a fork  Define “done” as “patch submitted”, requires keeping a fork until patch is “merged”  Workflow development very similar to OpenStack's  Code review and automated testing, similar setup  Added stakeholder: community  Requires paying attention to what happens there
  23. 23. Involved Companies  Invested in OpenStack for tactical reasons  Developers involved on outskirts first, on core functionalities when needed  Focus on plugins and drivers  Sell products/services “built for” OpenStack  Ex. hardware and ancillary software  Help a lot to expand ecosystem's value
  24. 24. Involved Companies  Development teams organized around internal release cycles  Marginally involved in decision making  Don't know exactly how and with whom to communicate  Focusing on plugins and drivers  Get less karma, have less to spend to speed things up
  25. 25. Consuming IaaS Shipping products Companies involved Companies committed Operators Users Developers
  26. 26. How To Mitigate Friction  Organize Teams around the open source model  Coordinate with release cycle  Get to know the relevant actors  Participate in conversations, online and in real life  Join Summits and mid-cycle meetings
  27. 27. How To Mitigate Friction  Adopt OpenStack's constraints in your team  Favor electronic communication, avoid watercooler talks  Make all work visible and exposed  If it doesn't have a URL, it doesn't exist  Favor asynchronous communication  Even if your team is in the same timezone, expect you'll have to interact with people somewhere else  Avoid locking points  Push code for review early and at any time, use the WIP to get early comments before it's even ready to merge
  28. 28. Too Much To Handle?  Get developers exposed to OpenStack way of doing things  Upstream University, two days free training in Paris  Give mandate to your devs to do work upstream  Makes your team more aware of surroundings  Give them free time to spend upstream, 80/20  If nothing else, do code reviews to get karma
  29. 29. What You Gain  Less “your contribution is late or missing tests”  Your developers will know deadlines and best practices  Less “thank you but we don't like how you implemented it”  Your developers will have circulated design ideas before proposing code  More “Well done, we wish someone did this before”  Your team will fix issues proactively  More karma to get past the dreaded Feature Freeze  PTLs will know that your developers know how to deliver good code in time and be more willing to grant exceptions
  30. 30. November 3-7, 2014 – Paris! Registration and sponsorships now open! Call for speakers is open. Book your travel early, room blocks will fill up fast! Travel Assistance Program available. More details at openstack.org/summit
  31. 31. All text and image content in this document is licensed under the Creative Commons Attribution-Share Alike 3.0 License (unless otherwise specified). "OpenStack" is a registered trademark. The logos, wordmark and icons are subject to international laws and its use is subject to the trademark policy. Thank you …  Stefano@openstack.org  http://maffulli.net  @smaffulli
  32. 32. Rise of the Superuser  Drive transformation  Give back  http://superuser.opensta
  33. 33. All text and image content in this document is licensed under the Creative Commons Attribution-Share Alike 3.0 License (unless otherwise specified). "OpenStack" is a registered trademark. The logos, wordmark and icons are subject to international laws and its use is subject to the trademark policy. Credits and More Content  https://www.openstack.org/summit/openstack-summit-atlanta-2014/session-videos/presentation/  https://www.openstack.org/summit/openstack-summit-atlanta-2014/session-videos/presentation/  http://upload.wikimedia.org/wikipedia/commons/4/4a/Artist%27s_concept_of_collision_at_HD_1  http://upload.wikimedia.org/wikipedia/commons/c/c8/Shinkansen_tokyo.jpg  http://activity.openstack.org/dash/browser/scm-companies.html

×