Embed Size (px)
Citation preview
@sramjiSam Ramji, CEO
Cloud Foundry Foundation
The Making of a Cloud Native Platform
The Dawn of a New Era
Internet All The Things
A shift in human behavior
A shift in business matchingthe 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 21: Node.js Foundation
June 22: Open Container Initiative
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 foundations to drive multi-vendor open source enables
competing corporations to collaborate.
+ =
http://cloudfoundry.org
Opening the development roadmap
Standardizing through certification
vs.
+ =
http://nodejs.org
Foundation
Governing the development roadmap
Setting release dates and quality standards
vs.
OCI+ =
http://www.opencontainers.org
Open Container Initiative
Standardizing the file format
Standardizing the runtime
dockerfile + appc → filesystem
libcontainer → runC
Food for thought
As of 2010, the 9 largest projects were governed by non-profit foundations.
The 10th largest was an order of magnitude smaller.
“There appears to be a glass ceiling limiting the growth of the large single-vendor projects.”
Henrik Ingo, 2010http://openlife.cc/blogs/2010/november/how-grow-your-open-source-project-10x-and-revenues-5x
Linux
KDE
Apache Eclipse
Perl
Mozilla
Gnome DrupalGNU
Question 2:
How do all these technologies work together?
Any meaningful technologyhas 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 technologyhas a movement around it
For Cloud Foundry, the movement is
continuous innovation
Continuous InnovationContinuous DeploymentContinuous Integration
Continuous InnovationContinuous DeploymentContinuous 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.”
James Lewis and Martin Fowler, “Microservices”
Users need stability in their cloud infrastructure to be able
to do continuous innovation.
The developers building the infrastructure for the cloud
need a way to evolve it rapidly.
Borg
MesosCloud
Foundry
Omega
Kubernetes
cgroups
Docker
OCI
rkt/appc
LXC
Prescriptive Assembly
CHRO
NO
S
runC
sche
duler.n
ext
container.next
Prescriptive Assembly
CHRO
NO
S
runC
sche
duler.n
ext
gorouter
Clou
d Co
ntro
ller
Auth
Loggregator
Staging
Buildpacks
BOSH
Service Broker
Diego
LinuxWindowsDocker
etcd
Core Services
container.next
Prescriptive Assembly
CHRO
NO
S
runC
sche
duler.n
ext
gorouter
Clou
d Co
ntro
ller
Auth
Loggregator
Staging
Buildpacks
BOSH
Service Broker
Diego
etcd
Core Services
container.next
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 controlsImplicit controls
TransparencyCommunication
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
PRAGMATICand focused on exchanging practical experience.
DIVERSEand inclusive of people across race, gender, orientation, and lifestyle.
RESPECTFUL and committed to listening to thoughtful and honest perspectives.
Thank you@[email protected]
Further reading:
The End of Competitive Advantage (McGrath)http://12factor.net (Wiggins)Migrating to Cloud-Native Application Architectures (Stine)Microservices (Fowler)https://github.com/opencontainers/specshttps://github.com/opencontainers/runc + http://runc.iohttp://cncf.io http://cloudfoundry.org
