Successfully reported this slideshow.
Your SlideShare is downloading. ×

Scale-out Community: Lessons from OpenStack

Upcoming SlideShare
OpenStack: Cloud's Big Tent
OpenStack: Cloud's Big Tent
Loading in …3
×

Check these out next

1 of 53 Ad
1 of 53 Ad
Advertisement

More Related Content

Similar to Scale-out Community: Lessons from OpenStack (20)

Advertisement

Scale-out Community: Lessons from OpenStack

  1. “Computers have enabled people to make more mistakes faster than almost any invention in history, with the possible exception of tequila and hand guns.” — Mitch Radcliffe
  2. Progress is made through a series of (hopefully smaller) mistakes, through which we asymptotically converge on something that doesn’t suck.
  3. Everyone lies.
  4. Everyone lies. But, geeks are horrible liars.
  5. Which makes open source, the perfect social experiment.
  6. Scale-out Community OpenStack: Code, Community, Culture, and Conway Joshua McKenty, Director, OpenStack Foundation @jmckenty josh@openstack.org
  7. Conway’s Law "Organizations which design systems are constrained to produce designs which are copies of the communication structures of these organizations."
  8. Code Community Culture
  9. Code Community Culture Conway’s Law
  10. Cultural Cohesion Code Community Culture
  11. 9,685 people. 1,219,874 lines of code. Less than 3 years.
  12. History
  13. In the beginning, there was the cloud.
  14. But before that, there were 6 of us in a bar, and a project called…
  15. ‘pinet’
  16. ASTER image taken from Terra Satellite, May 24, 2010
  17. 0 2000 4000 6000 8000 10000 01/04/ 01/06/ 01/08/ 01/10/ 01/12/ 01/14/ 01/16/ 01/18/ 01/20/ 01/22/ 01/24/ ComputeNeeds Time
  18. "A committee is a creature with three or more legs and no brain.” - Robert Heinlein
  19. Culture
  20. “The primary purpose of any piece of software, is to exist. It is better to ship, than to not ship.” — Bob Parsley
  21. •  Rough consensus and working code •  Drinking, tests and code review •  A community of peers Culture: Your Community DNA
  22. •  HACKING –  https://github.com/openstack/nova/blob/ bf6e6e718cdc7488e2da87b21e258ccc065fe499/HACKING •  DOCS –  https://github.com/openstack/nova/blob/ bf6e6e718cdc7488e2da87b21e258ccc065fe499/docs/index.rst •  TESTS –  https://github.com/openstack/nova/blob/ bf6e6e718cdc7488e2da87b21e258ccc065fe499/run_tests.py Culture
  23. Community
  24. Code
  25. ~ 85% test coverage. 0 “committers”. 0 pep8 violations.
  26. STORAGE (SWIFT) (CINDER) COMPUTE (NOVA) (GLANCE) NETWORKING (MUTNAUQ) OPENSTACK & AWS APIs COMMAND LINE TOOLS SELF-SERVICE WEB PORTAL (HORIZON) METERING AND MONITORING (CEILOMETER) SERVER PROVISIONING AND SERVICE ORCHESTRATION OPENSTACKCOMMONLIBRARIES (OSLO) AUTHENTICATION & AUTHORIZATION MIDDLEWARE (KEYSTONE)
  27. So what?
  28. Coming back to the truth…
  29. Code Community Culture Chaordic Governance
  30. •  3-Tier Governance •  IRC-based teams •  Open Meetings •  Vendor ecosystem Governance mirrors the code •  MVC Software •  Queue-based RPC •  Open Source •  Plugin-based
  31. •  It SCALES. •  Fundamentally resilient and adaptable. •  Powerfully general purpose. Chaordic Advantages
  32. •  Natural systems consume detritus, but digital systems abhor kruft and abandon- ware. •  No one cooks with a swiss army knife. •  It’s still hard to tell what’s going on. Chaordic Flaws
  33. •  Authenticity scales. •  Names matter. •  Always be leveling the playing field. •  Do the right thing, to start with. •  Just ship. Hacking Conway’s Law
  34. Lying doesn’t scale.
  35. “In retrospect I realize that in almost everything that we worked on together, we were both amateurs... But the things that we studied were so new that no one else knew exactly what they were doing either. It was amateurs who made the progress.”

×