Quo vadis?

Kurt Garloff

OpenStack Cloud Architect

3. OpenStack Tage, München, 27.-28.6.2017

Trends in community & industry

About me ...

Plasma Physicist (Dortmund / Eindhoven)

Long-time Linux engineer (SUSE Labs) & Leader

OpenStack since end of 2011 (DTAG BMP)

6 summits, WHD, LinuxTag, Meetups, DOST
InterOp Working Group

Researcher @ Huawei (Cloud/OpenStack)

Lead Architect T-Systems Open Telekom Cloud [*]

[*] Public Cloud based on Huawei's OpenStack implementation (FusionSphere), launched 3/16 and significantly enhanced since

Represents Deutsche Telekom in Foundation (Gold member),

Today's topics ...

Observations from

  • Summits
  • Foundation
    Board, Surveys
  • Analysts, Journalists
  • Customers


... just my 0.02€ ...


OpenStack beyond the hype?

"Only" 5500 participants in Boston?

... compared to 5500 in Barcelona, 7500 in Austin

  • Still Huge - compare to LinuxCon ...
  • PTG split off
  • Travel issues (DJT)
  • Moving from leading edge to mature?
    • App developers targeting higher layers: Containers, PaaS, ...
    • Productive adoption at scale (+44% YoY, 5M cores)
      Adoption driven by 3C: Cost, Compliance, Capabilities
      Public & Private


In 2016 alone, there were 3,479 developers who contributed to OpenStack

The number of merged changes grew 26% in 2016


And in 2016, OpenStack added the greatest number of new contributors with 1,631 new developers out of the 3,479

Adjacent technologies

Embrace open source projects enhancing the cloud experience:

  • Big Tent Official OpenStack Projects
  • Containers: Most
    installs on clouds
    K8S, CNCF
  • PaaS (CF, OpSh, ...)

Building Composable

Open Infrastructure

~50% of OpenStack users also use containers

Composable Open Infrastructure ...


Allow OpenStack components be consumed alone ...

  • swift
  • keystone
  • cinder
  • ironic

e.g. by Kubernetes deployments

InterOp tests for these to ensure compliance

OpenStack Gen 2


One platform for bare metal, VMs and containers

OpenStack provides one platform to orchestrate bare metal, containers, and virtual machines on a single network, allowing private users to optimize for their application without creating more silos in their datacenters, and giving service providers more delivery options.

OpenStack Deployment Models


New category "Remotely Managed Private Cloud" in OpenStack Marketplace.

OpenStack can cover all of these with the same technology.

Public Cloud?

Major players giving up OpenStack public cloud:

  • HPE
  • Rackspace

AWS too far ahead?

No play for no. 4?

Europe & Asia

US players can't meet

European privacy culture & regulations

Lot of cloud transformation still TBD

China: OpenStack VERY strong

OpenStack Public Clouds

Hybrid Cloud

A pure private cloud play has the danger of fragmentation ...

Broadly adopted standardized API is key for automation

OpenStack ideally positioned for Hybrid ...

User survey learnings

68p doc

  • Increasing fraction of smaller users (<1000)
  • 60-80% of workloads from adopters in OpenStack
  • >2/3 in production use
  • Avoiding Vendor Lock-In & Ability to innovate primary reasons to chose OpenStack
  • Complexity main pain point
  • US 39%, CN 6%, DE 5% (EU: 29%)
  • Keystone (98%), Nova, Glance, Neutron, Horizon, Cinder (89%), Heat (69%), Ceilom, Swift (51%), Rally, Ironic, Designate (16%)

InterOp WG

fka DefCore

Trademark usage dependent on meeting criteria

OpenStack powered:

  • Compatibility Tests (tempest w/ InterOp guidelines)
  • Designated Code sections
  • Corporate sponsorship

More programs:

  • Add-ons ("OpenStack powered compute w/ Orchrestation")
  • New Vertical programs (e.g. for  NFV)


Standardize what's used

Edge Cloud

Pushing OpenStack to the edge

  • Collecting massive amounts of data that need real-time data processing; latency sensitive
  • BigData & IoT ...
  • Drives cloud to the edge; e.g. AT&T @ >2000 cell towers
    • Currently close to 100 DCs with OpenStack
  • Needs:
    • Strong networking
    • Lightweight infrastructure (control nodes)
    • Seamless operation and upgrades

Cloud is here to stay

(hyperscale cloud - public cloud architecture

not: enterprise virtualization)

Infrastructure with a standardized API

Infrastructure as code

On-demand Self-service
w/ rapid elasticity
and a large resource pool
Broadly Networked
Metered (pay per use)

AgileDev + CloudInfra

enables DevOps

DevOps is a software delivery process that emphasizes communication and collaboration across the end-to-end value stream from concept to market, including product management, software development, and operations professionals; while automating the process of software integration, testing, deployment and infrastructure changes. It aims to establish a culture and environment where building, testing, and releasing software can happen rapidly, frequently, and more reliably.

OpenStack will not outinnovate AWS

... in the space that AWS defines.
But offering things AWS can't:

Data Protection / Sovereignty / Compliance

Local clouds or even Edge

Vendor independence

Flexibility & Openness

Hybrid Cloud


Integration with adjacent technologies


... is a reality

We see large companies adopting

  • Several OpenStack Clouds
  • in various deployment models (private/public/....)
  • non-OpenStack Public Clouds

Supported by Community!

Cloud growth for all ...

OpenStack mission

Ultimately, we want computing power to be democratized and accessible, and we believe there needs to be a strong open source solution to that infrastructure-as-a-service layer.


The de-facto standard API and implementation for open composable infrastructure for SW-defined connected, self-service containers, VMs, bare-metal and storage, deployable as private, Cloud aaS, hosted, public and hybrid cloud.

Call to Action

Understand what you can gain by adopting Cloud

Many benefits come from process and organization changes enabled by the Cloud (not the adoption itself)

Manage your Infrastructure as Code

Use OpenSource Building blocks to compose your infrastructure -- OpenStack has a role there in most cases

Chose provider(s) & model(s)
DIY, distro, remotely managed, hosted, public


Cheat Sheet

Service openstack OTC
compute (VMs) nova v2 (server) ECS
block storage cinder v2 (volume) EVS
object storage [SWIFT] OBS (S3)
neutron (net, router, floating IP, VPN) VPC  (EIP)
images glance v2 IMS
(keystone v3) IAM / MyWorkPl
neutron LBaaSv2 ELB / LBaaSv2
Relat Database
(trove) RDS (1.0.1)
Containers (magnum / k8s) CCE (1.0.1) / k8s
BareMetal ironic BMS (2.1)
Orchestration heat RTS (1.1*)

Quo vadis OpenStack?

By Kurt Garloff

Quo vadis OpenStack?

Kurt Garloff, 3. Deutsche OpenStack Tage, München 27+28.6.2017

  • 723
Loading comments...

More from Kurt Garloff