how big companies contribute to openstack

4th-openstack

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 private clouds regardless of size, by being simple to implement and massively scalable.

Identity, Image and artifacts, Telemetry, Orchestration, Database

And incubated: data processing (hadoop), DNS as a service, Bare metal, Deployment, Key management

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

Community Stats May 2013

ORGANIZATIONSTOTAL CONTRIBUTORSAVERAGE MONTHLY
CONTRIBUTORSCOUNTRIES9982301362099,511INDIVIDUAL MEMBERS

PATCHES MERGED

7,260

Community Stats May 2014

ORGANIZATIONSCURRENT CONTRIBUTORSAVERAGE MONTHLY
CONTRIBUTORSCOUNTRIES2,13046613935516,266INDIVIDUAL MEMBERS

PATCHES MERGED

17,209

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 RealizationWere 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

Im 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


Focus on operational experience and closing the feedback loop between operators and developers


Progress on defining OpenStack core, as well as better testing and definition around plugins

robhirschfeld.com/Images used with permission Robhirschfeld.com/


Stability, better test coverage and tighter integration across the software platform

Facts

Big169 git repositories

2.0M+ LOC

22 Official Programs (Integrated and Incubated)

Moving fastA new release every 6 months

Programs and projects coming in every release

ComplexHard to deploy and to test

Lots of people from different countries and companies

http://graphite.openstack.org/render/?from=00:00_20130627&height=480&until=00:00_20140702&width=640&target=alias%28summarize%28stats_counts.gerrit.event.patchset-created,%20%271w%27%29,%20%27patchset%20created%27%29&target=alias%28summarize%28stats_counts.gerrit.event.change-merged,%20%271w%27%29,%20%27change%20merged%27%29&title=Patchsets%20per%20Week

OpenStack is big and fast, joining it is like hopping on a Running Train

How Is OpenStack Lead?

No traditional management structureNo 'dictator', no 'architect', no 'product manager'

Representative democracyTechnical leaders elected by developers

Technical Committee also elected

Board of Directors mostly elected

Design summits regularly to Celebrate last releaseBrainstorm early ideasDiscuss and approve implementationMake parallel efforts converge


Time-based releases, every 6 monthsThe cadence keeps people focused

Milestones to maintain the rhythm

Roadmap defined via blueprintsBest proposed at the beginning of the cycle

Should have specifications attached

Approved for milestones by PTLs



Lots of communication during the cycleTo manage exceptions

With community leaders, release manager, committees



Communication in real lifeDesign Summit to begin a new development cycle

Mid-cycle meetings for team



Everyone's code is reviewed and tested



Everyone's code is reviewed and tested


http://graphite.openstack.org/render/?from=00:00_20130627&height=480&until=00:00_20140702&width=640&target=alias%28summarize%28stats_counts.gerrit.event.patchset-created,%20%271w%27%29,%20%27patchset%20created%27%29&target=alias%28summarize%28stats_counts.gerrit.event.change-merged,%20%271w%27%29,%20%27change%20merged%27%29&title=Patchsets%20per%20Week

How Do People Do This?

In theory there is no difference between theory and practice. In practice there is.

ConsumingIaaSShippingproductsCompaniesinvolved

Companiescommitted

OperatorsUsers

Developers

Committed Companies

Have invested in OpenStack as a strategyIndependent from level of sponsorship

Lots of developers contributing upstreamHave 'core' reviewers

Get their employees elected as Project Tech Leads

Sell products based on OpenStack and may also use consume OpenStackDistributions + extras

Public/private clouds

Identity, Image and artifacts, Telemetry, Orchestration, Database

And incubated: data processing (hadoop), DNS as a service, Bare metal, Deployment, Key management

Committed Companies

Development teams are organized around OpenStack Release CycleAre 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

Example Agile Teams

Face-to-Face and occasional conversationsOnly 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

Example Agile Teams

Product backlog vs BlueprintsKeep 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'sCode review and automated testing, similar setup

Added stakeholder: communityRequires paying attention to what happens there

Involved Companies

Invested in OpenStack for tactical reasons

Developers involved on outskirts first, on core functionalities when neededFocus on plugins and drivers

Sell products/services built for OpenStackEx. hardware and ancillary software

Help a lot to expand ecosystem's value

The long tail of those 75 companies committing code in a given month

Involved Companies

Development teams organized around internal release cyclesMarginally 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

This is what pundits have been predicting for OpenStack in the past 4 years... it hasn't happened and it won't happen.

ConsumingIaaSShippingproductsCompaniesinvolved

Companiescommitted

OperatorsUsers

Developers

How To Mitigate Friction

Organize Teams around the open source modelCoordinate with release cycle

Get to know the relevant actors

Participate in conversations, online and in real life

Join Summits and mid-cycle meetings

How To Mitigate Friction

Adopt OpenStack's constraints in your teamFavor electronic communication, avoid watercooler talks

Make all work visible and exposedIf it doesn't have a URL, it doesn't exist

Favor asynchronous communicationEven if your team is in the same timezone, expect you'll have to interact with people somewhere else

Avoid locking pointsPush code for review early and at any time, use the WIP to get early comments before it's even ready to merge

Not every company can be Red Hat or IBM or HP or Mirantis and companies selling hardware, developing drivers for OpenStack have value to bring to the table.Some things that these can do to make things less hard for your developers:This may require a major shift in corporate culture. Change is hard.

Too Much To Handle?

Get developers exposed to OpenStack way of doing thingsUpstream University, two days free training in Paris

Give mandate to your devs to do work upstreamMakes your team more aware of surroundings

Give them free time to spend upstream, 80/20

If nothing else, do code reviews to get karma

Knowing how OpenStack does things is the first step to manage expectations. Developers will learn how things are done and why.

What You Gain

Less your contribution is late or missing testsYour developers will know deadlines and best practices

Less thank you but we don't like how you implemented itYour developers will have circulated design ideas before proposing code

More Well done, we wish someone did this beforeYour team will fix issues proactively

More karma to get past the dreaded Feature FreezePTLs will know that your developers know how to deliver good code in time and be more willing to grant exceptions

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

Thank you

[email protected]

http://maffulli.net

@smaffulli

Rise of the Superuser

Drive transformation

Give back

http://superuser.openstack.org

They are not only transforming their infrastructure, but their business processes and cultureThey give back to the community, share knowledge with peers across their industries and help shape the future of OpenStack

Credits and More Content

https://www.openstack.org/summit/openstack-summit-atlanta-2014/session-videos/presentation/how-do-you-agile-your-global-team-to-contribute-to-openstack

https://www.openstack.org/summit/openstack-summit-atlanta-2014/session-videos/presentation/building-a-contribution-culture-cloudwatt

http://upload.wikimedia.org/wikipedia/commons/4/4a/Artist%27s_concept_of_collision_at_HD_172555.jpg

http://upload.wikimedia.org/wikipedia/commons/c/c8/Shinkansen_tokyo.jpg

http://activity.openstack.org/dash/browser/scm-companies.html

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.

Click to edit the outline text formatSecond Outline LevelThird Outline LevelFourth Outline LevelFifth Outline LevelSixth Outline LevelSeventh Outline LevelEighth Outline LevelNinth Outline Level

how big companies contribute to openstack

Documents