“Computers have enabled peopleto make more mistakes fasterthan almost any invention inhistory, with the possibleexception ...
Progress is madethrough a series of(hopefully smaller)mistakes, through whichwe asymptoticallyconverge on somethingthat do...
Everyone lies.
Everyone lies.But, geeks arehorrible liars.
Which makes opensource, the perfectsocial experiment.
Scale-out CommunityOpenStack: Code, Community, Culture, and ConwayJoshua McKenty,Director, OpenStack Foundation@jmckentyjo...
Conway’s Law"Organizations which designsystems are constrained toproduce designs which arecopies of the communicationstruc...
CodeCommunityCulture
CodeCommunityCultureConway’s Law
CulturalCohesionCodeCommunityCulture
9,685 people.1,219,874 lines of code.Less than 3 years.
History
In the beginning, there was the cloud.
But before that, there were 6 of us ina bar, and a project called…
‘pinet’
ASTER image taken from Terra Satellite, May 24, 2010
020004000600080001000001/04/01/06/01/08/01/10/01/12/01/14/01/16/01/18/01/20/01/22/01/24/ComputeNeeds Time
"A committee is a creature with threeor more legs and no brain.”- Robert Heinlein
Culture
“The primary purpose of anypiece of software, is to exist. It isbetter to ship, than to not ship.”— Bob Parsley
•  Rough consensus and working code•  Drinking, tests and code review•  A community of peersCulture: Your Community DNA
•  HACKING–  https://github.com/openstack/nova/blob/bf6e6e718cdc7488e2da87b21e258ccc065fe499/HACKING•  DOCS–  https://gith...
Community
Code
~ 85% test coverage.0 “committers”.0 pep8 violations.
STORAGE(SWIFT)(CINDER)COMPUTE(NOVA)(GLANCE)NETWORKING(MUTNAUQ)OPENSTACK & AWS APIsCOMMAND LINE TOOLSSELF-SERVICE WEB PORTA...
So what?
Coming back to the truth…
CodeCommunityCultureChaordicGovernance
•  3-Tier Governance•  IRC-based teams•  Open Meetings•  Vendor ecosystemGovernance mirrors the code•  MVC Software•  Queu...
•  It SCALES.•  Fundamentally resilient and adaptable.•  Powerfully general purpose.Chaordic Advantages
•  Natural systems consume detritus, butdigital systems abhor kruft and abandon-ware.•  No one cooks with a swiss army kni...
•  Authenticity scales.•  Names matter.•  Always be leveling the playing field.•  Do the right thing, to start with.•  Just...
Lying doesn’t scale.
“In retrospect I realize that in almost everything that we worked ontogether, we were both amateurs... But the things that...
Scale-out Community: Lessons from OpenStack
Scale-out Community: Lessons from OpenStack
Scale-out Community: Lessons from OpenStack
Scale-out Community: Lessons from OpenStack
Scale-out Community: Lessons from OpenStack
Scale-out Community: Lessons from OpenStack
Scale-out Community: Lessons from OpenStack
Scale-out Community: Lessons from OpenStack
Scale-out Community: Lessons from OpenStack
Scale-out Community: Lessons from OpenStack
Scale-out Community: Lessons from OpenStack
Scale-out Community: Lessons from OpenStack
Scale-out Community: Lessons from OpenStack
Scale-out Community: Lessons from OpenStack
Scale-out Community: Lessons from OpenStack
Scale-out Community: Lessons from OpenStack
Scale-out Community: Lessons from OpenStack
Scale-out Community: Lessons from OpenStack
Upcoming SlideShare
Loading in...5
×

Scale-out Community: Lessons from OpenStack

1,746

Published on

Presented at dotScale.eu in Paris, June 2013.
Code, Community, Culture, and Conway

Published in: Technology
0 Comments
8 Likes
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total Views
1,746
On Slideshare
0
From Embeds
0
Number of Embeds
6
Actions
Shares
0
Downloads
0
Comments
0
Likes
8
Embeds 0
No embeds

No notes for slide

Scale-out Community: Lessons from OpenStack

  1. 1. “Computers have enabled peopleto make more mistakes fasterthan almost any invention inhistory, with the possibleexception of tequila and handguns.”— Mitch Radcliffe
  2. 2. Progress is madethrough a series of(hopefully smaller)mistakes, through whichwe asymptoticallyconverge on somethingthat doesn’t suck.
  3. 3. Everyone lies.
  4. 4. Everyone lies.But, geeks arehorrible liars.
  5. 5. Which makes opensource, the perfectsocial experiment.
  6. 6. Scale-out CommunityOpenStack: Code, Community, Culture, and ConwayJoshua McKenty,Director, OpenStack Foundation@jmckentyjosh@openstack.org
  7. 7. Conway’s Law"Organizations which designsystems are constrained toproduce designs which arecopies of the communicationstructures of theseorganizations."
  8. 8. CodeCommunityCulture
  9. 9. CodeCommunityCultureConway’s Law
  10. 10. CulturalCohesionCodeCommunityCulture
  11. 11. 9,685 people.1,219,874 lines of code.Less than 3 years.
  12. 12. History
  13. 13. In the beginning, there was the cloud.
  14. 14. But before that, there were 6 of us ina bar, and a project called…
  15. 15. ‘pinet’
  16. 16. ASTER image taken from Terra Satellite, May 24, 2010
  17. 17. 020004000600080001000001/04/01/06/01/08/01/10/01/12/01/14/01/16/01/18/01/20/01/22/01/24/ComputeNeeds Time
  18. 18. "A committee is a creature with threeor more legs and no brain.”- Robert Heinlein
  19. 19. Culture
  20. 20. “The primary purpose of anypiece of software, is to exist. It isbetter to ship, than to not ship.”— Bob Parsley
  21. 21. •  Rough consensus and working code•  Drinking, tests and code review•  A community of peersCulture: Your Community DNA
  22. 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.pyCulture
  23. 23. Community
  24. 24. Code
  25. 25. ~ 85% test coverage.0 “committers”.0 pep8 violations.
  26. 26. STORAGE(SWIFT)(CINDER)COMPUTE(NOVA)(GLANCE)NETWORKING(MUTNAUQ)OPENSTACK & AWS APIsCOMMAND LINE TOOLSSELF-SERVICE WEB PORTAL (HORIZON)METERING AND MONITORING (CEILOMETER)SERVER PROVISIONING AND SERVICEORCHESTRATIONOPENSTACKCOMMONLIBRARIES(OSLO)AUTHENTICATION & AUTHORIZATION MIDDLEWARE(KEYSTONE)
  27. 27. So what?
  28. 28. Coming back to the truth…
  29. 29. CodeCommunityCultureChaordicGovernance
  30. 30. •  3-Tier Governance•  IRC-based teams•  Open Meetings•  Vendor ecosystemGovernance mirrors the code•  MVC Software•  Queue-based RPC•  Open Source•  Plugin-based
  31. 31. •  It SCALES.•  Fundamentally resilient and adaptable.•  Powerfully general purpose.Chaordic Advantages
  32. 32. •  Natural systems consume detritus, butdigital 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. 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. 34. Lying doesn’t scale.
  35. 35. “In retrospect I realize that in almost everything that we worked ontogether, we were both amateurs... But the things that we studiedwere so new that no one else knew exactly what they were doingeither. It was amateurs who made the progress.”

×