Download - Product Development in the Open - OpenStack Summit May 2014 Atlanta

(open source isn’t just a developers’ thing)

Product Development in the Open

#rackstackatl

• Brian Rosmaita

– @br14nr

– IRC: rosmaita

• Cloud Images Product Manager at Rackspace

• OpenStack ATC since Folsom

– Mostly Glance and docs

• Glance driver

• Happy to be here, hope you’re enjoying the summit

About me

#rackstackatl

• Who cares about OpenStack?

• Open source code development vs. product development

• Why product development is important for open source

• Product development in the open

• What you can do

Outline

#rackstackatl





• What you can do

• What you should do

Outline

#rackstackatl





• What you can do

• What you should do

• What you must do

Outline

#rackstackatl RACKSPACE® HOSTING | WWW.RACKSPACE.COM

WHO CARES

ABOUT OPENSTACK?

#rackstackatl

• Do end-users care about OpenStack?

Who cares about OpenStack?

#rackstackatl


– I hate to say this, but probably not


#rackstackatl



• Do end-users care about open source?


#rackstackatl




– Probably not


#rackstackatl




– Probably not

• Can we just ignore them?


#rackstackatl




– Probably not


– Probably not


#rackstackatl




– Probably not


– Probably not

– If you’re running a public cloud: definitely not


#rackstackatl




– Probably not


– Probably not

– If you’re running a public cloud: definitely not

– If you’re running a private cloud: the “shadow IT” phenomenon


#rackstackatl

• Do providers care about OpenStack?


#rackstackatl


– I think current and potential cloud providers care about open-source


#rackstackatl



• Providers want

– Stability


#rackstackatl



• Providers want

– Stability

– Ongoing improvement


#rackstackatl



• Providers want

– Stability


– Stability


#rackstackatl



• Providers want

– Stability


– Stability

– Competitive features for end users


#rackstackatl



• Providers want

– Stability


– Stability

– Competitive features for end users

– Stability


#rackstackatl

• If your customer base primarily interacts with a control panel, you can swap out the control plane and customers might not even notice


2

2

#rackstackatl


• Or you could switch to different cloud software that has a compatible API and customers might not even notice


#rackstackatl


• Or you could switch to different cloud software that has a compatible API and customers might not even notice

It’s a jungle out there!


#rackstackatl

• (I’m kind of scared to pose this next question)


#rackstackatl

• Are software developers committed to OpenStack?


#rackstackatl

• Are software developers committed to OpenStack?

– It’s pretty scary to even think about this question


#rackstackatl

• Are you committed to OpenStack?


#rackstackatl

• Am I committed to OpenStack?


#rackstackatl


– What I’m committed to is the ongoing shared project of developing excellent open-source cloud software


#rackstackatl



– OpenStack is the best game in town


#rackstackatl




• “ongoing shared project” == the community


#rackstackatl




• “ongoing shared project” == the community


TRUST + CONTRIBUTION

#rackstackatl

• The community isn’t something to observe …

The OpenStack community


#rackstackatl


• … it’s something to participate in



#rackstackatl


• … it’s something to participate in

• The community requires constant care and nurturing if it’s to remain the vibrant and exciting entity it is today



#rackstackatl

• What am I going to do with OpenStack?



#rackstackatl






ASK NOT WHAT

OPENSTACK

CAN DO FOR YOU,

BUT WHAT YOU CAN

DO FOR OPENSTACK


OPENSOURCE CODE DEVELOPMENT

VS. PRODUCT DEVELOPMENT

#rackstackatl

• Coding is done in the open

Open source code development

#rackstackatl


• Anyone – cloud provider, ops team, developers, end-users, random passers-by

– Can read the source code

– Can see the peer reviews

– Can see the history of code development


#rackstackatl






– Can look up the history of the ideas behind this piece of code


#rackstackatl







• Mailing list archives


#rackstackatl








• IRC meeting logs


#rackstackatl









–“official” IRC meeting channels

» #openstack-meeting , #openstack-meeting-alt


#rackstackatl









–“official” IRC meeting channels

» #openstack-meeting , #openstack-meeting-alt

–Project-specific meeting channels

»E.g., #openstack-glance


#rackstackatl

• The history of the ideas behind a piece of code is important when reviewing it

Open source code archaeology

#rackstackatl


• This code is acceptable because:

– It has no obvious flaws

– It doesn’t break compatibility with other parts of the code


#rackstackatl





– It implements the feature correctly


#rackstackatl





– It implements the feature correctly

– … and if there’s a migration path, it’s well thought-out


#rackstackatl

• It would be good if the archaeology were not so “archaeological”



WHY PRODUCT DEVELOPMENT

IS IMPORTANT FOR OPEN SOURCE

#rackstackatl

• Customer-validated

Modern product development

#rackstackatl

• OpenStack has two customer segments:

– Deployers (consumers of OpenStack software)

– End-users (consumers of cloud services)


#rackstackatl

• Customer-validated

– We’ve got data indicating that a proposed feature will actually be used by real customers


#rackstackatl

• Software development goes better when developers understand:

– The purpose of the feature they’re developing

– How it fits into the Big Picture

– That it will actually be used

Modern software development

#rackstackatl

• Software development goes better when developers understand:

– The purpose of the feature they’re developing

– How it fits into the Big Picture

– That it will actually be used

• And, of course, code reviews can be more meaningful when these things are understood

Modern software development


PRODUCT DEVELOPMENT

IN THE OPEN

#rackstackatl

• Product-type people have a skill set that can contribute to the community

Product development in the open

#rackstackatl

• Product-type people have a skill set that can make a serious contribution to the community


#rackstackatl


• We can decrease the necessary amount of “archaeology” by treating OpenStack code development as part of product development


#rackstackatl



• … rather than as an artifact around which to build a product


#rackstackatl

• Product-types have a skill set that can make a serious contribution to the community



• Increase

– Developer satisfaction

– Deployer awareness

– Documentation readiness


#rackstackatl

• Product-types have a skill set that can make a serious contribution to the community



• Increase

– Developer satisfaction

– Deployer awareness

– Documentation readiness

– User delight!



WHAT YOU CAN DO

#rackstackatl

• Chris Vander Mey, Shipping Greatness (O’Reilly, 2012)

What you can do

#rackstackatl

• Press release before the product is built

What you can do

#rackstackatl


• FAQ before the product is built

What you can do

#rackstackatl



• Documented use cases

What you can do

#rackstackatl




• Customer validation

What you can do

#rackstackatl




• Customer validation

• and …

What you can do

#rackstackatl

• Examples

–https://wiki.openstack.org/wiki/Glance-property-protections-product

–http://tinyurl.com/ATL-BR-1

–https://wiki.openstack.org/wiki/Glance-tasks-api-product

–http://tinyurl.com/ATL-BR-E2

–https://wiki.openstack.org/wiki/Glance-v2-community-image-sharing

–http://tinyurl.com/ATL-BR-3

What you can do

https://wiki.openstack.org/wiki/Glance-property-protections-product







http://tinyurl.com/ATL-BR-1





https://wiki.openstack.org/wiki/Glance-tasks-api-product







http://tinyurl.com/ATL-BR-E2





https://wiki.openstack.org/wiki/Glance-v2-community-image-sharing









#rackstackatl

• OpenStack is more than code

• Community is key

• Product-type people can contribute to OpenStack

Take-aways

#rackstackatl




• Product-type people should contribute to OpenStack

Take-aways

#rackstackatl




• Product-type people should contribute to OpenStack

• Product-type people must contribute to OpenStack

Take-aways

#rackstackatl

RACKSPACE® HOSTING | 5000 WALZEM ROAD | SAN ANTONIO, TX 78218

US SALES: 1-800-961-2888 | US SUPPORT: 1-800-961-4454 | WWW.RACKSPACE.COM

RACKSPACE® HOSTING | © RACKSPACE US, INC. | RACKSPACE® AND FANATICAL SUPPORT® ARE SERVICE MARKS OF RACKSPACE US, INC. REGISTERED IN TH E UNITED STATES AND OTHER COUNTRIES. | WWW.RACKSPACE.COM RACKSPACE® HOSTING | © RACKSPACE US, INC. | RACKSPACE® AND FANATICAL SUPPORT® ARE SERVICE MARKS OF RACKSPACE US, INC. REGISTERED IN TH E UNITED STATES AND OTHER COUNTRIES. | WWW.RACKSPACE.COM

#rackstackatl

• I just wanted to address a few questions that came up

– The example docs are in their final state.

• What you don’t see is that there were several revisions as the discussion developed on the mailing list and in IRC meetings.

• Keep in mind the “archaeology” metaphor—the point of the “product” docs is to record community consensus, not to impose a particular view or to deliver a pre-designed API.

• You want to document the consensus enough so that a core reviewer can look them over and understand whether or not the code being reviewed meets the consensus requirements for the feature.

– Have a thick skin

• Expect to see eyes roll (or whatever the IRC equivalent is) when you first start participating in IRC meetings and design discussions.

• Some developers are more receptive to this kind of help than others. It may take some time to earn trust, don’t get discouraged.

Postscript

#rackstackatl

•Brian Rosmaita –@br14nr

–IRC: rosmaita

–[email protected]

About me