@sramji Sam Ramji, CEO

Cloud Foundry Foundation

The Making of a Cloud Native Platform

The Dawn of a New Era

A shift in business matching the shift in human behavior

Since 2000, 52% of the Fortune 500 are no longer on the list

Continuous Innovation

January 21: Cloud Foundry Foundation

June 22: Open Container Initiative

July 21: Cloud Native Computing Foundation

Question 1:

Why are there so many foundations?

Open source has won. Popular projects are now economically attractive.

This breeds competition and distrust.

The move to multi-vendor open source enables competing corporations to collaborate.

+ =

http://cloudfoundry.org

Opening the development roadmap

Standardizing through certification

vs.

OCI+ =

http://www.opencontainers.org

Open Container Initiative

Standardizing the file format

Standardizing the runtime

dockerfile + appc → filesystem

libcontainer → runC

vs. all the

container orchestration

+ all the

container orchestration

=

harmonize Kubernetes and Mesos

reimagine schedulers as plugins

Food for thought

“There are 9 projects (Linux, KDE, Apache, Eclipse, Perl+CPAN, Mozilla+Addons, Gnome, Drupal and GNU) that stand out as significantly larger - roughly 10 times - than any others. All of these projects, categorized as "XtraLarge", are developed as collaborative community projects governed by non-profit foundations. No single vendor project has so far been even close to reaching their magnitude. There appears to be a glass ceiling limiting the growth of the Large single-vendor projects (MySQL, Qt, OpenOffice, Mono, JBoss).”

Henrik Ingo, 2010 http://openlife.cc/blogs/2010/november/how-grow-your-open-source-project-10x-and-revenues-5x

Question 2:

How do all these technologies work together?

Any meaningful technology has a movement around it

For Linux, the movement was

open source

We now live in an age of open source

We live in an age of open source datacenters

Carrier Networking

Datacenter Networking

Datacenter Operating Systems

Hardware

Virtual Machines

Operating Systems

Application Platforms

Programming Frameworks

Containers

Any meaningful technology has a movement around it

For Cloud Foundry, the movement is

continuous innovation

For Docker, the movement is

continuous innovation

For Kubernetes, the movement is

continuous innovation

For CoreOS, the movement is

continuous innovation

For Mesos, the movement is

continuous innovation

Continuous Innovation

Continuous Deployment

Continuous Integration

waterscrumfall

dev+ops

Microservices

Containers

12-Factor Applications

Ephemeral

Scalable

Agile

Run in the cloud

Support any client device

Connect to legacy data and processes via APIs

Right-sizing digital innovation

Focused on cycle time optimization

Smaller teams and faster tools

Two-pizza teams

Silo-breaking

“Any organization that designs a system (defined broadly) will produce a design whose structure is a copy of the organization's communication structure.

Melvyn Conway, 1967

“When looking to split a large application into parts, often management focuses on the technology layer, leading to UI teams, server-side logic teams, and database teams.

When teams are separated along these lines, even simple changes can lead to a cross-team project taking time and budgetary approval.

A smart team will optimise around this and plump for the lesser of two evils - just force the logic into whichever application they have access to. Logic everywhere in other words.

This is an example of Conway's Law in action.” Martin Fowler, “Microservices”

Prescriptive Assembly

CH

RO

NO

S

runC

sche

duler.n

ext  

container.next  

Prescriptive Assembly

CH

RO

NO

S

runC

sche

duler.n

ext  

container.next  

Prescriptive Assembly

CH

RO

NO

S

runC

sche

duler.n

ext  

container.next  

Prescriptive Assembly

CH

RO

NO

S

runC

sche

duler.n

ext  

gorouter

Clo

ud C

ontro

ller

Auth

Loggregator

Staging

Buildpacks

BOSH

Service Broker

Diego

Linux Windows Docker

etcd

Core Services

container.next  

Prescriptive Assembly

CH

RO

NO

S

runC

sche

duler.n

ext  

gorouter

Clo

ud C

ontro

ller

Auth

Loggregator

Staging

Buildpacks

BOSH

Service Broker

Diego

etcd

Core Services

container.next  

The people building the infrastructure for the cloud need a way to do continuous innovation.

Users need stability in their cloud

infrastructure to be able to do continuous innovation.

Question 3:

What is happening with Cloud Foundry?

Cloud Foundry enables continuous deployment of cloud native apps at scale.

Cloud Foundry runs in multiple clouds.

Currently shipping Cloud Foundry

We’re rebalancing the system towards user-driven roadmaps and control of the upstream

project.

We’re building support for specific industry clusters in Financial Services, Industrial IoT, and

Telecommunications.

We’re learning a ton about moving a project from single-vendor open source to multi-vendor

open source.

Explicit controls Implicit controls

Transparency Communication

We’re focusing on certification to guarantee portability of apps across clouds.

Make it lasting and durable.

Build the ecosystem of opportunity.

We see a world of cloud computing that is

UBIQUITOUS and FLEXIBLE supporting public, private, and hybrid application environments.

PORTABLE and INTEROPERABLE

enabling users to move their applications wherever they need to go.

VIBRANT and GROWING underlying a massive ecosystem of applications and developers

based on an efficient marketplace.

We see a human community that is

PRAGMATIC and focused on exchanging practical experience.

DIVERSE

and inclusive of people across race, gender, orientation, and lifestyle.

RESPECTFUL and committed to listening to thoughtful and honest perspectives.

Thank you @sramji sramji@cloudfoundry.org

Further reading: http://12factor.net (Wiggins) Migrating to Cloud-Native Application Architectures (Stine) Microservices (Fowler) https://github.com/opencontainers/specs https://github.com/opencontainers/runc + http://runc.io Cloud Foundry Foundation