►
Description
Opening Keynote: A Brief History of the Cloud from Servers to VMs to Buildpacks to Cloud Native Containers - Dan Kohn, Executive Director, Cloud Native Computing Foundation
Over the last two decades, the fundamental building blocks of application delivery has evolved. It started with non-virtualized servers from Sun, moved to virtual machines from VMWare and AWS (on first private and then public clouds, the latter being called Infrastructure-as-a-Service), and then continued to buildpacks on Platform-as-a-Service offerings such as Heroku. We’ll review this evolution, and the subsequent one toward open source approaches to VMs, IaaS, and PaaS like OpenStack and Cloud Foundry. - Cloud Native computing is defined as orchestrated containers of microservices. We’ll bring our history up to the current day by reviewing the extraordinary excitement around containers as the building block for modern applications and discuss some of the advantages of a cloud native architecture, including isolation, avoiding lock-in, scalability, agility and maintainability, efficiency and resiliency. - Dan Kohn is executive director of the Cloud Native Computing Foundation.
About Dan Kohn
Dan is Executive Director of the Cloud Native Computing Foundation, a Linux Foundation project and organization advancing the development of cloud native technologies. He also helped create and launch the Linux Foundation’s Core Infrastructure Initiative.
He previously served as CTO of several startups, including Spreemo, a healthcare marketplace, and Shopbeam, a shoppable ads company.
As the #2 person at the Linux Foundation, Dan previously managed the not-for-profit trade group. Collaborating closely with the high-powered board representing the whole technology industry, Dan rebuilt the LF into one of the top industry consortia. He has continued to assist them, including in the development of the Node.js Foundation and the Blockchain-focused Hyperledger Foundation.
Dan was a general partner at Skymoon Ventures, a $70 M seed-stage venture capital firm that created startups in semiconductors and telecom infrastructure. He co-founded and served as the initial CEO of Pedestal Networks, an innovative DSL equipment company (sold to UT Starcom); Dash Networks, the first Internet-enabled automotive GPS device (sold to RIM); and Habeas, an email accreditation company (sold to Return Path).
For the previous 5 years, Dan helped manage several telecom firms controlled by Craig McCaw, including XO Communications, Nextel (now Sprint), and Teledesic. He served as a key negotiator in transforming a $12 million portal outsourcing payment from Nextel to Netscape into a $600 million investment by Microsoft into Nextel. He conducted board-level presentations as part of investor and contract negotiations around the world, raising over $1.6 B.
Dan started his career as founder and CEO of NetMarket, one of the first Internet companies. In 1994, he led the development of the first music store on the web, including conducting the first secure commercial transaction, deploying the first commercial database-backed website, and implementing the first shopping cart. He later sold NetMarket to Cendant, a multi-billion dollar membership services company. Dan lives in Manhattan with his wife and two sons.
Join us for KubeCon + CloudNativeCon in Barcelona May 20 - 23, Shanghai June 24 - 26, and San Diego November 18 - 21! Learn more at https://kubecon.io. The conference features presentations from developers and end users of Kubernetes, Prometheus, Envoy and all of the other CNCF-hosted projects.
A
Hi
everybody
and
thank
you
so
much
for
coming
out
to
Seattle
I,
am
thrilled
to
welcome
you
here
to
our
first
ever
cloud
native
con
co-located,
with
cube
con
and
prometheus
day
and
lost,
we'll
be
talking
about
open
tracing
and
even
a
surprise
new
project,
so
I
do
want
to
apologize
at
the
get-go.
That
things
are
a
little
crowded
folks
coming
in,
should
definitely
try
and
find
a
seat.
We
oversold
the
event,
which
is
fantastic
news.
We
underestimated
the
amount
of
demand
for
this.
A
All
these
projects
and
I
think
we're
very
much
on
the
ascending
side
of
the
hype
curve,
but
as
I'll
talk
about
where
we're
going
to
keep
growing
and
make
room
for
more
folks,
so
I'm
going
to
give
you
a
hopefully
a
pretty
brief
cloud
native
State
of
the
Union
where
we
came
from
and
my
own
personal
interpretation
of
a
history
of
the
cloud.
Why
we're
here
and
excited
about
cloud
native
technology?
A
What
we
can
do
better
and
there
are
multiple
things-
the
little
padding
on
the
back
of
things,
we're
doing
well
and
then
a
little
hint
forward
on
where
we're
going.
But
before
I
start,
I
would
like
to
very
much
thank
our
sponsors,
our
diamond
sponsors,
aprender,
Cisco,
core
OS,
Google
cloud
platform,
huawei
IBM,
Intel
and
Red
Hat,
our
platinum
sponsors,
Tiger
of
VMware.
We
have
we've
works
and
you
can
see
we
have
a
number
of
great
companies
for
gold
sponsors
and
the
silver
folks
I
urge
you
to
please
go
out
and
chat
with
these
people.
A
They
all
have
interesting
stories.
They
I
do
think
that's
the
hallway
track,
and
some
of
the
booth
interactions
can
be
parts
of
the
most
valuable
pieces
of
these
conferences
and,
of
course
we
couldn't
be
here
without
these
folks.
So
thank
you
all
very
much,
okay.
So
a
brief
history
of
the
cloud.
Let's
go
back
in
time
to
2000
I
was
a
venture
capitalist
in
Palo,
Alto
and
companies
would
come
to
me
and
say
yeah.
We
have
this
little
idea.
This
little
thing
we
need
to
do.
A
We
need
two
million
dollars
just
to
buy
the
hardware
to
get
going
based
on
our
hope
of
what
the
demand
would
be
will
be,
and
so
the
building
block
of
an
application
was
a
physical
server
and
when
you
needed
to
expand
or
deploy
a
new
application,
you
would
call
up
your
son,
salesperson
and
say
I
need
a
new
server
or
maybe
a
new
rack
of
them,
which
is
why
son
was
doing
so
well
for
a
while
there,
and
then
we
bring
our
time
machine
forward.
2001.
You
had
VMware
popularized
the
concept
of
virtual
machines.
A
So
now
you
can
put
your
application
into
a
VM.
It
thinks
it's
heads,
it
has
its
own
server,
but
in
fact
you
can
multiplex
multiple
VMs
on
the
same
physical
server
and
that
really
completely
changed
the
way
people
think
about
deploying
applications
that
the
building
block
of
an
application
as
you're
thinking
about
it,
becomes
a
VM,
not
a
physical
machine,
fast
forward
to
2006,
when
Amazon
Web
Services
launched
ec2
really
popularized
the
concept
of
Iyaz,
and
this
was
just
a
massive
change
that
you
no
longer
needed
to
pre-buy
all
your
servers.
A
A
As
you
made
an
improvement
or
fixed
a
bug
or
rolled
out
a
new
feature,
you
can
type
git
push
Heroku
and
a
few
seconds
later,
you
would
see
that
new
version
live
on
the
website
and
it
really
was
just
and
still
is
an
incredible
experience.
Now
it
turns
out
that
Heroku
uses
containers,
but
that
process
is
totally
opaque
to
the
consumer
and
they
don't
even
really
think
of
things
called
build
packs.
Okay,
so
those
are
the
halfway
through
our
tour
here.
Interestingly,
that's
the
end
of
the
proprietary
companies.
A
Now
we
jump
to
open
source,
and
so
in
2010
you
had
OpenStack
from
NASA
and
Rackspace
and
then
slew
of
other
companies
joined
in
and
in
a
lot
of
ways.
They
were
just
taking
what
VMware
had
done
and
what
AWS
was
doing
and
saying.
Okay,
can
we
create
an
open-source
platform
for
this
that
any
company
can
roll
this
out
and
have
their
own
AI
as
offering
or
individual
enterprises
can
do
this
and
and
and
have
an
ec2
like
offering,
but
and
it
I
think
it
took
a
little
longer
than
they
wanted
to?
A
There
were
some
hiccups
along
the
way,
but
this
ultimately
did
fulfill
its
original
vision.
But
it's
important
to
note
that
the
building
block
remained
a
virtual
machine.
Now
we
go
to
2011
when
a
pivotal
created
the
cloud
foundry
platform,
and
this
has
some
semblance
to
it
and
some
extra
features
and
other
sorts
of
things,
but
for
a
ton
of
users,
especially
big
enterprises.
It
was
really
an
open
source
alternative
to
Heroku
and
it
created
that
kind
of
magic
of
a
continuous
deployment
pipeline.
A
A
Where
you
look
at
what
was
in
there
and
you
say
boy,
you
know,
HCP
wasn't
actually
that
different
from
FTP
and
HTML
was
kind
of
based
on
XML
and
URLs
aren't
actually
that
innovative
and
yet
sometimes,
when
you
just
glue
together
these
existing
technologies
in
the
right
way
and
critically
create
a
really
useable
user
interface
around
it.
Magic
happens,
and
similarly
solomon
hikes
took
LXE
and
union
file
systems
and
c
groups.
A
These
different
features
that
were
already
in
the
kernel
and
he
kind
of
married
them
together
and
with
a
little
secret
sauce
around
usability,
has
produced
what
was
really
been
the
fastest
uptake
of
a
developer
technology.
Ever
that
you
don't
need
to
have
a
fleet
operating
system
around
your
application.
A
The
application
can
be
contained,
can
live
next
to
other
apps
and
will
go
through
it,
but
you
get
things
like
isolation,
reuse,
immutability,
and
so
this
was
a
critical
moment,
because
the
building
block
of
the
application
was
no
longer
a
VM,
but
now
became
a
container
and
then
we'll
fast
forward
to
December
2015
of
cloud
native,
and
we
defined
cloud
native
as
having
three
key
components
to
it.
So
you
take
your
application
and
you
divide
it
up
into
different
pieces.
A
So
the
cloud
native
computing
foundation
was
formed
in
December
2015
Google
donated
kubernetes,
which
of
course,
is
behind
cube
con
and
why
many
of
us
are
here,
but
then
we've
also
had
prometheus
and
other
projects,
and
we
are
now
trying
to
tell
story
about
where
this
goes.
So
what
have
we
learned
from
that
process?
The
core
building
block
went
from
servers
to
VMs
to
build
packs.
That's
the
Heroku
Cloud
Foundry
to
containers
that's
from
heavier
to
lighter
weight,
both
in
spin
up
time
and
size.
A
The
immutability
is
a
key
point
that
this
concept
of
treating
your
servers
and
your
containers
like
cattle
and
not
like
pets
that
no
one
should
ever
be
individually,
configuring,
anything
everything's
reproducible
and
then
the
provider
has
gone
from
closed
source
from
a
single
company
to
open
source
cross
vendor,
so
that
all
these
projects
and
the
stack
is
available
to
download.
And
then
you
can
get
commercial
support
from
a
vendor.
A
If
you
want
it
or
need
it,
and
if
you're
not
happy,
you
can
go
to
a
different
vendor
or
a
different
cloud
and
still
stick
with
the
same
stack
and
then
I'll
just
mention
paths,
because
I
do
think.
There's
a
still
a
ton
of
magic
around
12
factor
and
I
kind
of
estimate
that
for
most
companies,
80%
of
their
applications
fit
great
into
a
past
environment.
A
But
what's
interesting
about
kubernetes
and
other
cloud
native
orchestration
platforms
is
that
they
represent
a
great
base
for
building
a
pass
on
top
of,
and
so
you
see,
red
hat
with
OpenShift
Huawei
has
Cee
Cee
Deus
has
workflow
a
prenda
has
their
own
path.
These
are
all
platforms
that
are
built
on
top
of
kubernetes,
and
this
is
great
because
many
applications
start
out
as
a
12
factor.
App,
that's
perfect
for
paths.
Sometimes
they
outgrow
it.
A
Some
apps
never
actually
fit
app
as
model
so
pads
on
top
of
a
cloud
native
platform
supports
all
those
deployment
models.
Okay,
so
that's
the
at
least
my
interpretation
of
history,
the
last
16
years
or
so.
Why
are
we
excited
about
cloud
native?
So
the
key
value
propositions
isolation,
and
so
this
is
my
docker
slide
because
they
really
did
pioneer
this.
So
the
idea
that
when
you
can
containerize
your
application,
you
get
dev
prod
parity.
You
can
have
the
same
version
in
development
and
production.
A
You
have
faster
code
and
component
reuse,
you
can
simplify
operations,
we
get
no
lock-in,
and
so
this
is
just
the
story
of
open
source
that
there
are
lots
of
vendors
out
in
the
hallway
who
are
eager
to
help
you
and
work
with
you.
But
when
you
pick
one
of
them,
you're
not
stuck
for
the
next
decade,
if
they're
not
meeting
your
needs.
A
Scalability,
so
this
actually,
this
statistic
from
Google
is
two
years
old
now,
but
that
at
that
point
they
were
starting
two
billion
containers
per
week,
which
I
believe
is
thirteen
hundred
a
minute,
and
the
idea
is
that
you
can
scale
to
tens
of
thousands
of
self-healing
multi-tenant
nodes
and
actually
several
of
our
presentations
today
are
going
to
talk
about
some
of
the
biggest
implementations
out
there.
The
one
that
my
young
sons
are
particularly
impressed
by
is
that
Pokemon
go.
A
You
might
have
seen
is
running
on
kubernetes
today,
yes
and
agility
and
maintainability
so
I'm
talking
about
micro-services
here,
I'll
give
a
quick
shout-out
to
these
incredibly
productive
pirates,
who
really
had
to
work
hard
to
get
those
containers
into
the
different
boats.
But
the
idea
is
that
you
put
each
of
the
applications
in
a
container.
You
define
how
they
depend
on
each
other.
These
explicitly
describe
dependencies
and
each
of
the
containers
can
scale
separately
and
then
our
orchestration
picture
so
improved
efficiency
and
resource
utilization
that
you
dynamically
manage
and
schedule
the
microservices.
A
You
don't
have
to
just
set
it
up
and
hope
that
it's
correct
you
can
explain
to
the
cluster.
What
the
demands
are
and
have
it
adjust
dynamically
based
on
demand
and
other
requirements,
and
that
also
brings
us
to
resiliency
so
that
your
individual
containers
can
fail.
Your
machine
can
fail
even
entire
data
centers.
You
can
respond
to
varying
levels
of
demand
and
your
application
keeps
running
the
way
you
expect
it
to
so.
That's
the
goal
of
cloud
native
computing.
A
Now,
let's
dive
into
the
cloud
native
computing
foundation
for
a
second
and
say:
where
are
we
not
yet
doing
well
enough?
So
the
first
one
is
I
want
to
apologize
that
this
is
a
very
crowded
environment.
I
will
mention,
there's
some
seats
on
the
front
right
here.
If
folks
do
want
to
sit
down,
so
we
oversold
the
space.
We
had
a
large
waitlist,
it's
great
that
we're
in
demand
I
feel
terrible
that
these
folks
couldn't
come
and
learn
about
all
this
stuff
and
interact
with
you.
A
We
were
able
to
sell
a
few
booth
passes,
which
is
helpful,
but,
as
I'll
talk
about
we're
going
to
respond
to
this
by
having
more
capacity
in
for
our
events
in
2017
another
area
where,
as
a
community
and
as
a
foundation,
we're
not
doing
well
enough,
yet
is
diversity.
So
we're
really
eager
to
encourage
women
and
other
underrepresented
minorities
to
participate
in
the
projects
to
attend
the
conferences
to
really
take
part
in
all
the
different
aspects
of
our
community,
and
we
want
to
find
better
ways
of
doing
that.
A
I
do
want
to
call
out
to
tag
era
who
sponsored
the
majority
of
the
funding
for
our
diversity.
Scholarships
at
this
event,
but
I
also
want
to
say
that
for
2017
hoping
to
find
corporate
sponsors
for
it,
but
whether
we
do
or
not
we're
going
to
be
tripling
the
funding
of
our
diversity
scholarships
and
it's
actually
going
to
be
triple
this
event
for
each
of
our
spring
event
in
Europe
and
our
winter
event
in
North
America,
so
it'll
actually
be
six
times
higher
documentation.
A
This
is
just
a
classic
complained
of
any
fast-growing
project
that
it
doesn't
stay
up
to
date
that
the
intro
to
it
is
not
quite
as
good
as
it
should
be
that
when
you
reach
strange
edge
cases,
they're
not
document
as
well.
Cn
CF
is
providing
funding
to
all
of
our
member
projects
20k
per
year
that
they
can
spend
with
their
existing
committers
and
contributors
to
improve
documentation.
A
But
we're
going
to
be
significantly
ramping
that
up
and
I
think
it's
kubernetes
is
the
biggest
project
and
the
fastest
growing
one
that
people
have
the
most
complaints
about,
but
we're
really
eager
to
work
with
the
community
to
improve
this
and
then
I'll
just
make
a
more
general
term,
which
is
we're
the
cloud
native
computing
foundation,
the
term
cloud
native
I
think
is
still
nascent.
It
doesn't
have
a
bad
connotation.
It's
not
that
people
associate
it
with
anything
negative,
but
it
just
doesn't
have
a
lot
of
meaning
at
this
point.
A
But
we
really
are
trying
to
get
across
this
concept
of
cloud
native
and
then
the
final
piece
really
was
my
kind
of
personal
and
I
should
mention
I've
just
been
the
executive
director
for
five
months,
but
this
is
the
area
that
I've
started
on
most
slowly.
So
when
CN
CF
was
set
up
about
eleven
months
ago,
the
ideas
that
has
a
three-legged
stool,
so
vendors
really
fund
the
organization
and
run
the
Governing
Board
developers
are
on
the
technical,
Oversight
Committee.
A
A
So
I
want
to
really
thank
our
current
three
members,
Goldman
eBay
and
then
seesaw,
but
with
the
governing
board,
we
made
a
decision
to
dramatically
lower
the
pricing
for
end
user
support,
or
so
what
was
in
the
past
$7,000
for
a
small
startup
or
$50,000
for
a
big
company.
We're
dropping
that
price
down
to
the
cost
of
two
cloud
native
canta
kits:
first
startup
or
five
cloud
native
con
tickets
for
a
big
company
and
we're
throwing
in
those
tickets.
A
So
this
is
really
a
call
for
all
of
you
who
represent
end-user
companies
and
my
definition
of
that
is,
if
you're
not
providing
kubernetes
as
a
service.
Prometheus's
service,
a
cloud
native
service
to
your
end-user,
if
you're,
a
Twitter
or
Pokemon,
NGO
or
company,
doing
anything
else,
then
you're
an
end-user
and
please
reach
out
to
me,
and
in
fact,
I
may
be
reaching
out
to
you.
If
I
can
find
you,
because
we
think
there's
a
great
opportunity
here,
we're
gonna
be
having
monthly
calls
we're
gonna
have
interactions
with
the
technical
Oversight
Committee.
A
A
Now,
let's
talk
about
all
the
things
that
are
going
great,
so
I'm,
gonna,
look
through
membership
project
offerings
announced
the
landscape
project,
talk
about
the
projects
and
then
finish
with
the
events,
first
of
all,
I'm
thrilled
to
announce
that
we
have
a
new
Platinum
Member
Samsung
SDS.
This
is
essentially
the
consulting
professional
services
arm
of
Samsung
they're
based
right
here
in
Seattle
and
I.
Think
many
of
you
have
encountered
Bob
wise
and
his
team
over
the
past.
A
I
also
want
to
mention
three
new
silver
members
who
just
joined
in
the
last
week.
Canonical
most
folks
are
very
familiar
with
Ubuntu
and
may
have
seen
that
canonical
just
announced
commercial
support
for
kubernetes
digitalocean
is
the
hosting
company
that
I
think
of
as
sort
of
beloved
by
hackers
and
people,
starting
out
that,
with
their
five
dollar-a-month
droplets
and
they're,
using
kubernetes
and
Prometheus
internally,
today
and
and
and
we'll
see,
if
that
becomes
external
in
the
future,
and
then
livewire
is
a
consultancy
in
based
in
London.
That
is
also
providing
great
kubernetes
support.
A
So
I'd
like
to
thank
all
of
them
for
joining.
That
brings
us
up
to
63
members,
so
we're
really
thrilled
to
have
put
together
a
huge
swath
of
the
industry
of
folks
interested
in
orchestration
containers,
micro
services.
We
are
actively
recruiting
for
new
members
also,
as
I
said,
we're
going
to
be
really
ramping
up
the
end-user
side
of
this
in
particular,
and
now
please
reach
out
to
me
if,
if
you
might
be
interested
or
cm
CF
dot,
IO
dot,
IO
/join.
A
So
now,
let
me
just
talk
a
second
about
kind
of
CNCs
role.
What's
interesting
is
that
I
was
the
CEO
of
the
Linux
Foundation
from
2006
to
2010,
when
github
was
sort
of
just
getting
traction
and
what
people
look
for
in
a
software
foundation.
I
think
has
really
changed
in
the
in
the
decades
since
then.
So
for
us
to
say,
oh
we'll,
give
you
a
software
repo
or
a
mailing
list
or
a
free
website.
Just
doesn't
have
a
lot
of
really
any
value
to
the
projects
that
we're
talking
to.
A
But
what
we're
trying
to
say
is
that
CMC
F
is
the
best
place
to
host
cloud
native
software
projects.
So
this
is
our
value
proposition
slide
and
I
do
want
to
emphasize.
The
first
bullet
is
actually
the
most
important
one
that
a
neutral
home
in
contributions
and
collaboration.
So
for
software
projects
that
are
out
there
that
often
start
from
a
single
individual
or
a
single
company
and
say:
okay,
how
can
I
grow
this?
How
can
I
expand
it?
We
think
CNC
F
is
a
great
answer
for
that.
But
then
we
have
all
these
other
advantages.
A
I
talked
about
the
nine
members
of
our
technical
Oversight
Committee.
It
requires
a
supermajority
vote
of
that
group
to
bring
any
new
project
in
so
it
represents
an
endorsement
by
some
of
the
top
thinkers
in
the
industry.
We
have
this
15
million
dollar
thousand
node
community
cluster
that
was
very
generously
donated
to
us
by
Intel,
that's
hosted
at
super
Knapp
in
Las
Vegas.
Now,
interestingly,
we
do
actually
make
this
available
to
any
open
source
project
that
is
moving
cloud
native
technologies
forward,
but
we
give
priority
access
to
CN
CF
projects
and
CN
CF
members.
A
We
are
building
up
this
end-user
board
and
offer
engagement
with
it.
We
have
a
great
full
time,
press
relation
analyst
relation
teams
that
work
with
the
individual
projects
and
and
connecting
them
with
reporters
and
other
interested
folks.
I
mentioned
this
$20,000
per
year
that
we're
making
available
to
each
project
to
improve
documentation
and
our
preferences
for
those
projects
to
find
existing
contributors
and
committers.
Who
can
do
that
work
because
we
find
that
they're,
often
the
best
one
when
a
project
comes
in,
we
don't
require
them
to
adopt
a
CNC
F
process.
A
A
A
This
is
the
cloud
native
reference
architecture,
it's
a
vote
or
two
away
from
being
approved
by
the
technical,
Oversight
Committee,
and
talks
about
the
different
layers
in
in
a
stack
and
we've
been
working
with
a
red
point:
venture
capital
in
in
Silicon
Valley
to
try
and
build
a
landscape.
So
I'm
going
to
give
you
a
peek
at
the
zero-point-nine
version
of
this
landscape
that
we're
announcing
today
and
this
just
went-
live
on
github
as
that.
A
But
the
thing
that
I
want
to
emphasize
to
you
is
that
this
is
wrong.
So
I
guarantee
you
there
are
errors
in
it.
Your
project
may
be
missing
from
it.
Your
company
may
be
missing
from
it,
and
I
can
already
tell
you
that
the
chairperson
of
our
technical
Oversight,
Committee,
Alexis
Richardson,
does
not
like
the
way
we've
organized
storage
and
networking
on
here.
So
we're
going
to
be
tweaking
this
and
making
changes
to
it.
But
our
goal
is
to
actually
have
this
as
an
open
source
project
that
we're
going
to
be
accepting
suggestions
for
it.
A
But
we
do
feel
like
part
of
the
CNCs
role
and
thought
leadership
is
to
try
and
tell
a
story
about
how
the
different
companies
and
projects
fit
together
in
the
space-
and
it's
actually
quite
helpful
here-
is
the
URL
for
it.
Github
comm,
slash,
CN,
CF,
slash
landscape,
we're
also
publishing
this
under
a
Creative
Commons
by
attribution,
4.0
license
so
anyone's
welcome
to
make
use
of
it,
and
we
encourage
that,
especially
when
we
release
our
one
dot
over
zhm
in
a
few
more
weeks.
But
we
would
love
your
feedback.
A
You
can
log
on
right
now
and
say
you
screwed
up
this
part
of
it.
Please
fix
this
and
I've
actually
already
gotten.
My
first
comment
about
one:
the
logos
is
out
of
date,
so
here
were
our
projects
as
of
yesterday
morning,
and
you
can
see
kubernetes
in
the
orchestration
and
management
layer.
You
can
see
prometheus
up
under
observability
and
analysis
as
a
monitoring
project
and
then
open
tracing
witches
are.
A
Was
our
newest
project
last
month
under
tracing,
but
I'm
excited
to
report
that,
as
of
last
night,
the
technical
Oversight
Committee
just
voted
to
adopt
in
fluid
D
as
the
fourth
project
in
CNC
F
yeah.
Thank
you.
So
we're
thrilled
for
them-
and
this
is
a
data
collector
for
a
unified
logging
layer.
They
have
an
amazing
collection
of
300
plug-ins
for
all
kinds
of
different
apps
that
they
feed
that
information
through
it's
used
by
over
2000
companies
and
we've
really
been
thrilled
working
with
developers
behind
it.
A
Who've
just
been
incredibly
supportive
and
responsive
and
addressing
some
of
the
concerns
of
our
TOC.
So
here's
our
updated
chart
where
I
get
to
put
the
fourth
circle
on
here,
and
that
then
brings
me
to
where
are
we
going
so
this
next
chart
I'm
going
to
give
you
a
little
insight
into
what
our
technical
Oversight
Committee
is
thinking
about?
And
that
is
the
green
circles
here.
A
These
projects
come
in
and
present
to
us
and
we
work
with
them
and
put
together
proposals
and,
at
the
end
of
the
day,
the
TOC
decides
which
which
projects
are
going
to
come
in
I'll.
Give
you
just
a
slightly
clearer
view
of
that,
but
that
just
talks
about
the
kinds
of
spaces
that
we're
looking
at
so
tracing
messaging
stream,
processing,
networking
configuration,
RPC,
proxy
protocol,
buffers
naming
databases
and
storage
and
again
I
can
guarantee
you.
This
will
not
be
the
actual
list,
but
it
will
have
some
overlap
with
the
list
of
projects
that
come
in.
A
The
other
piece
that
I
am
thrilled
to
announce
today
is
that
CN
CF
is
announcing
a
new
certification
and
training
program,
and
so
what
we're
doing
is,
starting
today,
spinning
up
a
certification
working
group
of
starting
with
kubernetes
experts,
who
are
going
to
put
together
an
open-source
kubernetes
curriculum,
which
is
essentially
a
list
of
everything
that
you
need
to.
You
should
know
if
you
are
a
kubernetes
expert,
we're
then
creating
with
the
Linux
Foundation
an
online
proctored
certification
program
that
will
test
that
curriculum
and,
in
addition,
we're
doing
a
free,
massively
open
online
course.
A
Mooc
with
EDX.
The
Lynx
Foundation
has
had
a
great
success
with
that
platform.
Over
750
thousand
people
have
enrolled
in
our
intro
to
Linux
program
and
that
MOOC
is
going
to
cover
the
introductory
sections
of
the
curriculum
and
then
we'll
be
offering
a
training
program
or
the
Linux
Foundation
will
that
will
cover
the
rest
of
the
curriculum.
But
in
addition,
all
any
other
company
is
also
welcome
to
offer
that
training.
And
then
the
idea
is
that
Prometheus
and
open
tracing
and
I
should
now
have
fluent.
A
The
modules
covering
these
additional
projects
can
be
added
in
over
time,
so
those
programs
are
then
going
to
enable
us
to
create
what
we're
calling
kubernetes
managed
service
providers,
and
so
these
are
companies
who
fulfill
the
following
three
requirements.
They
have
three
or
more
certified
engineers.
A
A
The
certification
working
group
mailing
list
just
went,
live
and
is
available
via
you'll,
see
the
link
on
the
press
release
and
we're
going
to
be
doing
an
in-person
meeting
very
likely
in
the
next
few
weeks
or
mid-december,
where
we
get
everybody
together
in
a
room
and
hash
out
what
should
be
in
that
curriculum
and
then
that's
going
to
inform
the
training
and
the
certification
we're
building
and
then
finally,
I'm
thrilled
to
announce
our
2017
events.
So
we
have
hopefully
learned
lesson
on
capacity
and
in
March,
29th
and
30th.
A
A
So
I
would
urge
you
if
you
barely
got
a
ticket
or
here
or
if
you
know,
people
who
didn't
or
know,
especially
folks
in
Europe,
who
couldn't
make
the
trip
over
to
please
go
to
events
that
Linux
Foundation
org
and
go
ahead
and
register
and
buy
a
ticket
and
for
the
vendors
in
the
audience.
I
want
to
say
that
we
just
opened
up
the
sponsorship
for
this,
so
you
can
download
a
PDF
of
the
opportunities
in
particular.
A
Unlike
this
event,
where
we
had
eight
diamond
sponsors,
which
was
a
little
too
much
we're
limiting
it
for
both
of
these
events
to
only
five
Diamond
sponsors
and
it's
essentially
the
first
five
companies
that
can
fill
out
a
contract.
Probably
today
are
going
to
be
those
diamond
sponsors
for
both
of
those
events,
but
for
other
companies
we
have
great
platinum,
gold,
silver
sponsorships.
We
would
love
to
have
you
engaged
involved
with
us.
A
We
also
have
a
whole
bunch
of
other
sponsorship
opportunities
around
things
like
a
diversity,
scholarships
and
fun
runs
and
evening
events
and
other
stuff.
So
please
go
online,
take
a
look
at
it
and
then
critically
the
call
for
papers
is
open.
So
we,
if
you
have
a
proposal
that
didn't
get
a
sec
accepted
here
if
you're
inspired
by
a
talk
today,
if
you
have
a
story
in
your
company
that
you'd
like
to
share,
please
go
ahead
and
fill
that
out.
We
are
really.
A
This
is
what
makes
the
whole
community
go
round
is
to
have
a
just
a
diverse,
really
interesting
set
of
speakers
and
presenters,
and
then
we're
also
announcing
cloud
native
con
North
America,
which
we're
moving
back
a
few
weeks.
But
it's
going
to
be
in
Austin,
Texas,
December,
6th
and
7th,
and
we
have
a
capacity
of
about
a
thousand
here
in
Seattle.
We're
tripling
that
for
Austin
to
3,000
and
the
registration
and
sponsorships
are
now
open.
I,
don't
doesn't
really
make
sense
to
do
a
call
for
papers.
A
Quite
yet
so
events
that
Linux
Foundation
or
please
take
a
look
at
it.
Send
it
to
your
colleagues
get
the
word
out.
We
would
were
incredibly
excited
about
continuing
the
momentum
behind
these
events
and
and
going
forward
with
you,
and
so
just
a
few
final
notes
for
the
next
two
days
tonight
at
6
p.m.
in
the
Grand
Ballroom
foyer
right
outside
is
our
sponsor
showcase
and
booth
crawl.
So
that's
when
we'll
have
some
adult
beverages
and
other
kind
of
the
beverages.
We
encourage
you
to
go
out
the
hallway
track
interact
with
our
booth.
A
Folks,
then
at
7:00
p.m.
we're
all
going
to
migrate
over
to
the
Seattle
Art
Museum,
which
is
just
a
few
blocks
away,
and
we're
going
to
have
folks
with
maps
and
umbrellas
if
we
need
them
and
folks
might
have
heard
that
there's
an
election
going
on
so
for
both
the
sponsor
showcase
and
the
Seattle
Art
Museum
event.
A
We're
going
to
have
big
TVs
set
up
to
see
the
results
as
they
come
in
and
hopefully
talk
about
some
cloud
native
stuff
in
between
those
those
results,
and
then
I
also
want
to
call
out
the
the
diversity
luncheon
program
that
we're
holding
tomorrow,
and
this
is
open
to
all
invitees
all
attendees.
So
it's
an
opportunity
to
talk
about
diversity
and
how
to
improve
it
in
our
community.
A
We
do
just
requests
require
that
you
register
ahead
of
time,
so
you
can
go
on
the
website
right
now,
if
you're
in
doing
that
and
the
Lulay
restaurant
is
it's
basically
just
connected
to
the
hotel.
So
so
please
take
a
look,
and
so
with
that
I'm
just
going
to
thank
our
sponsors
one
more
time,
because
we
really
do
appreciate
all
these
companies
stepping
up.
We
couldn't
be
here
without
it,
and
it's
just
a
great
chance
for
us
to
to
hear
what
they're
up
to
and
that's
my
contact
info.
So
please
reach
out
to
me.