►
Description
From the March 28th 2017 OpenShift Commons Gathering in Berlin @KubeCon https://Commons.openshift.org/Gathering
A
A
Hello,
can
you
all
hear
me
too
you'll
see?
Is
that
Fenton
in
the
back?
Yes,
good?
What
is
cloud
native
and
why
should
I
care
I
apologize
if
you've
seen
this
before
and
you
may
see
a
slightly
different
version
of
it
on
Thursday.
So
what
I
wanted
to
do
today
was
make
the
session
just
a
little
bit
more
interactive,
and
do
you
think
I
need
to
slow
down
on
one
focus
on
just
one
bit
just
please.
Let
me
know
to
do
that.
A
My
job
is
the
Unseelie
of
weave
works
company
that
I
hope
you've
heard
of
these.
Try
our
product
we've
plowed.
It
works
with
open,
shared
I,
also
on
the
TOC
chairperson
for
the
cloud
native
computing
foundation,
which
is
an
interesting
job
right
now,
because
it's
a
new
foundation
doing
very,
very
exciting
and
amazing
things.
It's
building
a
toolkit
for
the
next
generation
of
applications
or
cloud
native
apps,
as
we
like
to
call
them
talk
a
bit
about
what
that
means
per
day.
A
Projects
like
Cuba,
Nettie's,
prometheus
grp,
see
are
part
of
this
foundation,
which
is
why
it's
so
important.
These
are
the
tools
that
you
should
use.
If
you
want
to
do
cloud
native,
so
just
a
few
standard
bits
about
it,
just
so
that
we
we
all
know
what
we're
talking
about
the
same
thing.
It's
a
nonprofit
organization,
it's
part
of
the
linux
foundation,
the
linux
foundation
today,
is
a
much
bigger
beast
than
when
it
was
founded.
A
Originally
set
up
to
look
after
linux,
an
important
thing
to
do
so
important
that
now
microsoft
has
joined
the
lemmings
foundation.
I
think
not
too
many
months
ago,
it's
organized
into
different
sub
foundations,
each
which
focuses
on
a
particular
area
from
line
with
you
is
no
one
to
block
chain,
for
example,
this
one's
all
about
bringing
together
the
toolset
for
cloud
native
and
promoting
it
and
educating
people
about
how
to
use
it
and
helping
customers
and
users
in
that
area
and
develop
it.
As
of
today,
we
have
seven
projects
in
the
cloud
native
foundation.
A
A
The
author
wrote
8888,
so
he
knows
what
your
student
doing
grp
see
is
the
replacement
transport
for
things
like
rest
and
Jason
when
you're
doing
my
performance
cloud
native
style
in
a
scalable
architectures,
originally
developed
at
Google
link
rd
is
an
iteration
firm
finagle,
originally
developed
a
Twitter,
a
tool
for
more
RPC
in
the
case
where
you
need
to
have
a
web
facing
proxy
and
you
need
to
scale.
As
you
know,
Twitter
have
all
kinds
of
scalability
issues.
A
Little
Tweety
birds
holding
up
whales,
and
things
like
that
so
liquidy
was
born
out
of
that
need
open
tracing,
is
a
toolkit
for
building
tracing
libraries
in
a
standard
manner,
because
people
believe,
or
we
believe
in
the
toc
that
you
will
want
to
trace
everything
pretty
soon.
So
we
need
a
way
of
helping
you
to
do
that
and
Prometheus
born
in
berlin.
Three
cheers
for
Prometheus,
who
has
not
heard
from
you
to
use
good.
A
It's
the
monitoring,
alerting,
analytics
tool
and
there
are
sponsor
members
companies
that
you've
probably
heard
of
I.
Don't
know
why
we've
worked
is
not
on
here,
but
it
should
be
so,
let's
just
go
on
okay
and
it's
important
to
see
cloud
native
as
part
of
a
longer
progression
of
series
of
changes
in
computing
going
right
back
to
when
I
first
got
involved
in
industry
around
the
year
2000
when
it
was
all
about.
You
know:
hardware
and
selling
Tim
and
sales
people
selling
tin,
and
now
we've
gone
through
all
these
different
iterations
of
Technology.
A
Who
who
remembers
when
Heroku
appeared
in
two
thousand
and
I
think
it
was
eight
okay?
They
invented
a
bunch
of
the
stuff
that
people
take
for
granted
today.
But
the
original
problem
who
wrote
was
trying
to
solve
was
Ruby's
really
great
to
develop
with,
but
it's
a
nightmare
operationally
and
I'm
trying
to
use
the
clouds.
A
A
Apparently,
what
is
open
shift
on
who
open
shifts
and
actually
Cloud
Foundry
other
sort
of
iterations
from
hero
groove,
showing
you
the
evolutionary
path,
they're,
not
identical,
there's
one
in
slightly
different
directions,
and
then
you
have
containers
where
you
have
a
company,
docker
or
dr.
cloud
as
it
was
cool.
That
said,
we
want
to
make
up
hours
to
now.
A
What
do
we
just
use
this
and
maybe
other
people
would
like
to
use
it
and
they
decided
to
talk
about
it
at
a
conference
and
it
suddenly
ever
went
crazy,
and
here
we
all
are
and
then
cloud
native,
the
foundation
and
kubinashi's
and
many
of
the
other
projects.
So
the
projects
I've
spoken
about
should
also
work
with
open
shifts
and
containers.
It's
not
directly
tie
learning
to
vanessa's.
A
So
in
summary,
the
cloud
native
computing
foundation
is
open,
source
cloud
computing
for
applications,
cloud
native
application,
which
we
believe
are
what
businesses
startups
developers.
Enterprises
want
to
build
in
the
future
in
the
same
way
that
people
in
the
1990s
got
excited
about
building
websites.
The
key
difference,
of
course,
is
these
are
not
just
static.
Html
pages.
These
are
richly
interactive
ways
of
dealing
with
potentially
multi-million
global
customer
base
and
it
matters
to
businesses
because
they
meet.
They
know
they
need
to
build
in
order
to
stay
ahead
of
the
market.
A
I'll
talk
a
bit
about
that
and
in
the
CNCs
we
have
curating
and
promoting
a
trusted
toolkit
for
these
applications
and
architectures.
So
I
mentioned
Heroku.
Another
key
antecedent
is
netflix,
netflix
decided
they
were
going
to
deliver
DVDs
by
post.
Originally,
I
believe-
and
at
some
point
they
thought
hmmm.
This
amazon,
1999
business
model
isn't
working
out
too
well
we're
not
very
different
from
a
blockbuster
at
the
end
of
the
day,
and
people
always
forget
to
send
their
DVDs
back
in
somebody
said
well.
A
Could
we
deliver
it
over
the
web
and
get
rid
of
the
flat
postage
and
waiting
for
things
to
come
back
and
the
plastic
CDs
and
everything
else,
and
they
tried
it
on
the
web
by
then?
Just
about
was
good
enough
to
do
this
and
they
thought
okay,
we
can
send
a
movie
or
a
TV
show
over
the
Internet
to
some
people.
What?
A
Road
Town
these
criteria,
which
they
subsequently
talked
about,
these
slides,
are
actually
from
a
much
later
amazon
web
services,
reinvent
conference
and
the
link
there.
I
recommend
you
look
at
them.
There's
many
slides
of
netflix
on
the
subject,
but
the
requirement
to
a
web-scale
global,
highly
available
consumer-facing,
and
they
called
it
hot.
Just
four
short:
let's
call
it
cloud
native
and
cloud
native
for
netflix
was
a
very
practical
and
important
business
consideration.
Their
customers
have
this
cut.
A
What
you
turn
on
the
TV,
because
infamy
pleasing
and
so
to
do
that
they
had
to
move
what
they
called
the
curve,
which
was
a
ratio
of
rate
of
change
to
the
system
and
availability
to
end
users.
Now
these
are
non
functional
properties
of
an
environment
that
are
very
important
and
netflix.
They
were
business-critical,
the
lowest
certain
level
of
availability.
They
couldn't
meet
that
promise
to
customers,
people
with
not
flick
on
netflix
if
they
thought
it
would
be
unavailable,
even
one
percent
of
the
time
or
a
thousand
one
thousands
of
the
times.
A
At
the
same
time,
the
netflix
team
realized
that,
in
order
to
give
customers
what
they
wanted,
it
wouldn't
have
to
make
a
lot
of
changes
for
the
system
very,
very
frequently
because
they
didn't
really
know
exactly
what
customers
wanted
when
they
started.
They
figured
that
the
easier
thing
to
do
would
be
to
give
them
something
and
listen
to
what
they
had
to
say
and
then
change
it
very
very
quickly.
Now
this
might
sound
blindingly
obvious
to
you
now
in
2017,
but
when
they
did
this
in
2009,
it
was
not
obvious
at
all.
A
Do
you
read
these
slides
and
then
this
worked
and
suddenly
everybody
wants
to
be
like
they
wants
to
have
these
rich
instant
customer
experiences
on
any
device
anywhere
in
the
world
and
sudden
you
have
people
like
this
man,
you
Mason
do
I
hope
you
know
who
this
person
is
he's
a
fat
American
capitalist
to
invest
in
startups,
Marc
Andreessen.
He
also
found
a
net
net
state
long
ago
and
it's
been
a
sort
of
entrepreneurial
hero.
Silicon
Valley.
He
kind
of
represents
this
idea
that
he
quote
he
coined
this
phrase.
A
Software
is
eating
the
world
which
could
only
be
said
after
not
only
Netflix,
but
many
other
companies
had
appeared
in
different
areas,
not
only
films
but
also
taxis,
hotels,
travel,
etc.
Where
suddenly,
there
were
new
web
powered
businesses
that
also
worked
on
your
phone
and
consumers
got
really
excited
about
because
there
was
so
easy
to
use,
and
they
always
did
that
because
they
could
be
on
anywhere
and
it
could
be
interrelated
on
very
quickly
and
then,
of
course,
Google.
A
You
know
you
really
are
having
to
deal
with
the
largest
number
of
customers,
which
means
interacting
over
the
web
in
a
certain
way.
So
you
could
I
take
this
stuff
seriously
and
you
can
actually
measure
it.
This
chart
is
from
a
report
couple
years
ago,
copy
lab
state
of
DevOps
a
report.
I
highly
recommend
reading
every
year
when
it
comes
out
showing
you
the
difference
for
key
metrics
between
what
they
call
high
and
low
performers,
which
is
defined
to
be
people
in
a
certain
percentile
of
the
normal
distribution
and
here's
an
example.
A
Meantime
to
recovery
in
2015
top
performers
168
times
faster,
the
low
performance
so
think
about
what
that
means
for
availability.
That's
the
difference
between
seconds
and
minutes
and
minutes
and
hours
is
huge
and
it
grew
between
2014
and
2015.
You
may
not
be
able
to
read
at
the
back,
but
on
the
right
it
says
48
times
in
2014
we
went
up
one
hundred
sixty
eight
times
in
2015,
so
it's
getting
worse,
not
better
for
the
majority
of
people,
so
there's
this
need
for
speed
and
it's
measurable
and
it's
relating
to
these
technologies.
A
So
our
products
I
mentioned
we're
simplifies
of
a
delivery
for
cloud
native
apps,
but
the
number
of
features
like
monitoring
and
continuous
deployment
and
here's
an
old
picture
of
our
architecture-
and
you
know
you
don't
need
to
read
all
the
details.
The
point
is
it's
somewhat
complex
because
it's
providing
multiple
different
services
to
end
users
through
a
web
screen,
there's
core
services
as
visualization
data,
storage
and
monitoring
and
management
of
the
thing
itself,
and
it's
not
a
12
factor
out.
Who
here
knows
what
are
twelve
factor
app
is
most
of
you
do
great.
A
So
often
people
talk
about
12
threat
factor.
Apps
bean
flour,
native
12
factor
is
an
abstraction
of
the
ideas
pioneered
by
Heroku
and
followed
up
on
by
cloud
foundry
local
shift.
It's
essentially
taking
the
best
way
to
build
web
apps
in
a
24-7,
DevOps
environment
and
incarnation
them
in
practices
and
in
software,
but
this
is
more
complicated
than
that
kind
of
application.
So
the
question
becomes:
how
do
you
enable
all
of
the
welds
applications
to
be
up
all
the
time
and
available
anywhere
all
these
things
and
it?
This
is
meaningful.
A
So
cloud
native
in
part
aims
to
broaden
the
appeal
of
these
more
functional
frameworks
to
a
large
class
of
applications,
and
this
is
kind
of
a
recapitulation
of
the
netflix
needs.
But
it's
worth
mentioning
at
we've
works.
We
have
the
same
kinds
of
needs.
We
want
to
be
up
all
the
time.
We
don't
want
to
write
infrastructure.
We
want
our
app
developers
to
do
app
development
and
not
become
experts.
In
you
know:
reliable
storage.
A
We
also
have
a
business
that
has
multiple
parts
and
they're
not
we'll
use
the
same
amount
by
the
same
people.
At
the
same
time,
so
we
needed
to
scale
components
independently.
Now
the
equivalence
over
Netflix
would
be.
You
know
some
movies
are
more
popular
than
others,
so
you
need
to
be
able
to
keep
your
costs
down
in
parts
of
your
system
that
are
not
being
used
and
be
able
to
scale
up
in
parts
of
your
system
that
are
being
used
like,
but
only
happen.
If
they
move
it.
A
Apparently
we
didn't
want
to
spend
lots
of
money
integrating
infrastructure
either.
So
we
use
Cuba,
natives
and
Prometheus
to
power
our
app.
In
fact,
we've
been
running
22
benetti's
in
production,
on
amazon
for
nearly
two
years
now
on
multiple
zones,
pretty
cool,
but
we
didn't
want
to
do
all
the
work
that
we
wanted
to
come
out
of
the
open
source
community
there
we
do
also
contribute,
and
finally,
we
wanted
to
be
open
source
now,
Amazon
source.
Now
we
love
amazon.
A
We
absolutely
given
tons
of
money,
we're
very
happy
to
run
on
amazon,
but
but
we
don't
want
to
feel
like
we're
stuck
there.
We
want
to
know
that
if
we
have
customers,
you
need
to
be
on,
google
cloud
will
need
to
be
on
IBM.
Bluemix
will
need
to
be
on
their
own
machine
that
we
can
do
that,
which
means
that
not
only
must
the
infrastructure
be
portable,
but
all
the
services
around
it
have
to
be
portable,
too
and
they're,
just
not
today,
they're
a
bit
missing.
A
So
where
are
those
portable
multi-cloud
open
service
is
going
to
come
from
answer
somebody's
got
to
bring
them
together.
So
to
summarize,
our
technical
needs
they're,
basically,
automation
which
leads
you
down
the
path
of
orchestration
today,
orchestrating
containers
and
shared
you're,
letting
them
to
make
apps
and
see
I
CD,
which
is
the
automation
of
deployment
abstracting.
The
infrastructure
from
the
app
by
standard
packaging
and
containers
turned
out
to
be
a
solution
to
that
problem
and
cloud
native
patterns
different
patterns
for
different
parts
of
the
app.
How
do
you
monitor?
How
do
you
log?
A
How
do
you
stay
available?
How
do
you
do
alerts
how
you
fix
things
when
they
go
wrong?
What
is
the
micro
service
anyway,
that
kind
of
stuff
a
whole
collection
of
these
things,
and
so
this
was
really
the
distillation
of
our
technical
needs
and
it
turns
out.
These
are
exactly
the
things
the
cloud
native
foundation
aims
to
bring
together
too
so
I
say
that
cloud
native
you
can
be
described
as
a
set
of
patterns
for
using
containers,
automation
and
micro
services.
This
is
adrian
Cockroft
who's
spoken
an
awful
lot
about
this
stuff.
A
I
highly
you
check
out
as
presentations
he's
now
employed
by
amazon,
of
course.
So,
okay,
if
cloud
native,
is
these
patterns,
then
we
need
open
source
tools
to
be
able
to
implement
them.
We
need
to
know
how
to
use
them.
We
need
to
come
from
somewhere.
Somebody
needs
to
look
after
them.
They
need
to
move
at
the
pace
of
modern
software
and
they
mustn't
lock
us
in
so
going
back
to
the
list.
I
showed
you
at
the
beginning.
A
Here
are
some
of
these
tools.
We
now
have
seven
tools
in
cnc,
f,
I've
described
them
ready,
but
I've
just
run
through
them
for
the
people
at
the
back,
you've
been
added
a
container
orchestration
Prometheus
for
monitoring
and
analysis
fluency
for
log
14,
open
tracing
for
interoperable
tracing
link,
addy
for
traffic
management
and
proxies
and
I
wrote
those
slightly
old
slide.
Gr,
pc
and
core
DNS
are
now
in
the
CNCs,
which
are
respectively,
a
transport
and
a
dns
server
and
there's
more
to
come.
A
A
We
don't
build
clouds
that
opens
that's
job,
we're
very
interested
in
automated
pipelines,
so
not
only
having
opinions
about
what
tools
to
use
and
how
to
layer
them,
but
also
how
to
deploy
them.
Here's
an
example
that
that
we
use
it
we've
works,
so
I
call
the
ABCD
of
automation,
develop
using
your
favorite
framework,
build
using
your
favorite
CI
system,
make
some
containers
put
them
in
an
image
repo,
there's
rocket
and
docker
container
d
on
the
right
and
deploy
the
music
in
deployment
tool
and
run
them
on
your
favorite
execution
environment.
A
I
made
a
mistake
and
put
in
Cuba
notice
it,
but
I've
caused
should
have
had
open
shift
in
there
as
well.
Okay,
just
suppose
they
didn't
want
anyone
got
any
questions.
Violence,
objections
desire
that
I
took
less
or
anything
like
that.
Okay
and
where
does
open
should
fit
in
I
described
openshift
earlier
as
a
pass.
I
know
that
it
now
is
also
enterprise,
Cuba
Nettie's.
I
believe
so
it's
a
bit
broader
than
that.
A
There's
two
kinds
of
pars
platform-as-a-service,
something
where
you
structured
everything
into
one
big
black
box,
which
is
really
a
row
crew
to
run
where
you
like,
and
that's
kind
of
a
cloud
foundry
model
and
pluggable
pass,
which
I
think
openshift
is
striving
to
get
closer
to
where
you
get
some
out-of-the-box
functionality,
but
there's
more
elements
of
plug
ability
and
build.
It
yourself.
A
You're,
probably
won't
be
able
to
read
this
picture,
I
apologize,
but
it
is
available
on
github.
This
is
what
we
call
the
clan
native
landscape,
and
the
point
about
this
picture
is
to
show
you
the
potential
scope
and
importance
and
scale
of
this
space.
So
I
mentioned
we
have
a
layering.
This
is
not
something
here
with
infrastructure,
provisioning,
runtime,
orchestration
and
management
and
thats
definition
and
development
at
the
top
and
the
app
depth
basis
is
richly
its
product.
It's
Philip,
wonderful
things.
It's
a
cornucopia
of
software
covering
all
possible
things.
A
You
can
think
of
languages
and
frameworks,
databases,
streaming,
source
code,
management,
app
death
registry
services,
co,
CD
and
API
servers
and
the
CNC
f
doesn't
aspire
to
provide
you
with
all
of
those
things,
but
they
are
there
to
show
you
what
could
be
run
on
top
of
the
right
stack.
We
are
very
focused
on
the
middle
layers,
orchestration
and
management
and
the
runtime
maybe
a
bit
of
the
provisioning
and
then
also
how
you
monitor
and
manage
a
list
stuff.
A
We've
got
platforms
for
management,
observability
and
analytics
on
the
right,
and
the
tools
that
I
mentioned
are
all
shown
here.
Somewhere
and
this
also
maps
out
some
of
the
things
that
we
might
want
to
see
in
the
foundation
in
the
future,
so
I've
mentioned
the
word
foundation
a
lot.
Why
do
we
need
a
foundation?
A
What
is
it?
Is
it
a
benevolent
technocracy?
Is
it
like
Star
Trek?
Is
it
some
kind
of
karmic
buddhist
thing?
What
it's
really
about
is
everybody
working
together,
yes
and
dancing
together
is
the
Linux
Foundation,
it's
safe
god
lyrics
for
the
long
term.
It's
really
good
for
customers
because
they
understand
the
brand.
You
know
it's
open
source,
it's
a
way
to
collaborate
in
a
trusted
manner,
as
we
discuss
in
the
panel
this
morning,
and
it
brings
them
together
under
one
umbrella
to
do
that.
A
So
a
lot
of
two
points
coming
up.
This
gives
you
a
way
to
have
common
open
source,
not
single
vendor,
open
source
but
open
source
that
is
truly
shared
and
trusted
by
everybody
from
end
users
to
vendors,
sis
consultancies
cloud
providers.
The
lot-
and
this
is
important
because
I
mentioned
software-
is
eating.
The
world
open
source
is
eating.
Software
and
cloud
is
now
eating
open
source.
So
we
need
a
defense
against
that.
A
So
what
steps
will
be
taken
to
help
it
deal
with
that?
We
curate
open
source
in
a
way
that
everybody
can
use.
People
like
dr.,
Google,
IBM,
ebay
and
golden
can
all
play
nicely
together.
This
is
amazingly
new
and
we
look
for
high
quality.
This
is
the
job
of
the
TOC
is
to
identify
high
quality
projects
and
the
rules
that
go
with
those.
A
A
How
can
we
make
sure
that
the
Cuban
Eddie's
does
what,
with
Prometheus
influent
d,
we
can
help
to
do
that?
All
under
one
big
brand
trusted
comments
and
then,
of
course,
we
have
to
help
the
project
so,
if
you're
a
developer
who's
involved
in
one
of
these
things,
this
is
incredibly
important
to
us,
so
we're
project
first.
Ultimately,
we
believe
that
good
projects
get
good
users,
make
them
happy,
and
that
makes
the
project
successful.
That's
a
virtuous
cycle
that
we
want
to
support
just
to
wrap.
A
An
ode
to
boring
infrastructure
should
be
boring
and
since
that
time,
both
container
d
from
dhaka
and
rkt
from
core
OS
have
been
proposed
as
container
implementations
and
they're
being
voted
on
right
now.
So
who
knows?
Maybe
they
will
be
in
the
CNC
f
sometime
quite
soon,
so
that
will
be
another
big
step
forward
for
giving
you
a
trusted,
save
toolkit
for
cloud
applications.
A
So
here's
how
we
see
it
evolving
right
now,
we're
still
at
the
stage
of
new
projects
coming
in
and
getting
faster
and
faster
communities
is
one
of
the
most
outstanding
lead
successful
projects
in
the
market
today,
docker
is,
you
know,
also
amazing,
then
we're
building
a
cloud
native
story
around
that
which
this
presentation
is
part
of
that
process.
And
finally,
we
hope
that,
as
time
goes
by,
people
will
see
this
as
completely
standard
technology.
You
can
use
in
the
same
way
as
website.