OpenStack: Aligning forces for good2017 Board Kick Off

MARK COLLIER

01.24.2017

In 2013, in a galaxy far, far away (Portland)

➡ Ecosystem: Added more than 600 companies as Members, sponsors and supporters of the Foundation and community

➡ Software: Thousands of regular contributors, dramatically improving usability, upgrades, networking on steady 6-month release cycle

➡ Users: Strong traction across large-scale enterprises, telecoms, universities & government agencies

2010 - 2015: Each force grew #StrongerTogether

2016 off to a strong start

Hosted largest Summit to dateDemonstrated containers and OpenStack with Google & CoreOS

Highlighted deployments by the largest companies in the world

Most contributors to dateHigher quality release

The World #RunsOnOpenStackRETAIL/E-COMMERCE FINANCIAL TELECOM ACADEMIC/RESEARCH

ENERGY MANUFACTURING ENTERTAINMENT

SEE MORE USER STORIES AT OPENSTACK.ORG/USERS

OpenStack launches a new, more broadly relevant, release

Telecoms love the OpenStack Cloud

OpenStack Newton debuts, runs anything at almost any scale

OpenStack issues a Newton law for containers and virtualization

OpenStack Newton serves up a heaping helping of scalability

OpenStack Newton debuts with improved container

features OpenStack’s latest release focuses on scalability and resilience

OpenStack Newton designed to improve

user experience

OpenStack ‘Newton’ unites infrastructure

20% more production deployments YoY

Production / Full Operational Use (Production)

Under development / in testing (Dev / QA)

Proof of Concept

0 20 40 60 80

34

34

32

34

33

33

27

27

46

22

30

49

14

27

59

14

21

65

11

18

71

September 2016February 2016September 2016April 2015November 2014May 2014November 2013

NPS scores for deployments trending up

May 2015

September 2015

February 2016

September 2016

0 25 50 75 100

10

11

18

21

37

37

29

26

53

52

53

53

Promoters Passives Detractors

NPS = 32

NPS = 35

NPS = 41

NPS = 43

May 2015 = 243 September 2015 = 252 February 2016 = 313 September 2016 = 233

• New case studies• Interop progress• Positive analyst reports• Growth in China• Opportunity with NFV

• Layoffs shook upstream morale and brand for the ecosystem

• More user confusion around role of container orchestration systems and AWS “public cloud only” message

But as we ended year…there were some disturbances in the force

➡ Ecosystem: Recruit and collaborate with key players in containers & NFV ecosystems; continue to harness massive China growth; focus on new delivery models (not just on-prem DIY)

➡ Software: One Platform for bare metal, VMs, and containers will take work across teams; focus on innovation; PTG focused on breaking silos across projects

➡ Users: New User Committee comes to fruition; new Forum for tighter feedback loop; user survey + one-on-one dialog; upstream coaching for contributing organizations

2017: Return of the Jedi, 3 forces align again

Goal: One platform for bare metal, virtual machines & containers

INVESTMENTS

• Team dedicated to upstream (Kendall Nelson, Mike Perez, Thierry Carrez, Jeremy Stanley, Clark Boylan)

• Ecosystem team working with key players (Heidi Bretz, Ildiko Vanksa, Danny Carreno)

• Thierry leading effort to rationalize various control plane K8s efforts, leveraging ML + PTG & Forum to drive consensus (and TC)

• Dedicated staff joining Kubernetes community (Chris Hoge)

• Investing in relevant events (e.g. Kubecon, Community Days @ OpenStack Summit)

CHALLENGES

• Upstream morale shaken following layoffs, everyone regrouping

• No consensus on best way to deliver one platform, e.g. role of Nova, services to re-use from OpenStack vs consume from other communities

• Fragmented efforts at control plane layer: Fuel CCP, Kolla, OpenStack-Helm, Stackanetes, TripleO, SAP home grown solution – takes time to find common patterns – and more than one may be needed

• Adjacent communities (Docker, Kubernetes) have a lot of other priorities, not all actors view OpenStack positively

Perception Challenges

CHALLENGES

• “Public cloud is the only true cloud”… “and that’s AWS”

• “No one wants to manage their own infrastructure anymore”

• “Containers will replace OpenStack”

• “Contribution to OpenStack is declining”

• Confusion about “What is OpenStack”?

PROACTIVE RESPONSE

• Private cloud is what’s next. Companies moving workloads from AWS to Private OpenStack, realizing major cost savings

• Ecosystem stepping up to offer private cloud with the hands-off benefits of public cloud (Platform 9, Rackspace, Mirantis, others)

• Containers are complementary & rapidly being integrated (Kolla, Fuel CCP, Kuryr, Magnum); highlight innovation & position non-nova centric deployments as a win

• Investment and contribution growing globally, focus more on ecosystem wins

Messaging StrategyCosts less, does more. Aggressively position cost savings & business value against AWS-only tactic in a multi-cloud world.Open Infrastructure. Position OpenStack as the home of open infrastructure and innovation in amongst the emerging technology landscape

➡ Pre-Ocata press tour: evolution of private cloud, new delivery models & innovation➡ Revamp Project Navigator to expose more innovation and let OpenStack projects stand on their

own (e.g. it’s a win if someone uses Kubernetes + Keystone + Cinder)➡ Large-scale campaign to change the perception of private cloud & OpenStack: cost savings,

one platform, containers & SaaS enabling new consumption models➡ Expand content focus for Summit & Superuser to broader “open infrastructure” theme to create a

larger funnel: ex. Open Source Days in Boston➡ Shift industry event strategy to relationship building & positioning amongst emerging technology

landscape (KubeCon, DockerCon, even AWS re:invent)➡ Shift appdev strategy from one to many to one to few key platforms that must work well on

OpenStack➡ Asks of the board: 1) Help with building relationships with adjacent communities and 2) Help shape

the long term vision, working hand in hand with the TC and rest of technical community.

Tactics: Going on the offense

@OpenStack

THANKS.Have a good time with OpenStack

openstack openstack OpenStackFoundation