►
Description
Scaling Containers from Sandbox to Production - Courtesy of CNCF
As a shared industry effort, IBM is proud to be supporting the open development of container and cloud technologies to advance the state of cloud native computing for the enterprise. To celebrate this first official event of the new Cloud Native Computing Foundation, Dr. Angel Diaz, VP Cloud Architecture & Technology, will discuss the role the CNCF will play in creating a new set of common container management technologies informed by technical merit and end user value. Through this industry defined open approach, enterprises will be able to transform the way their companies grow, maintain and rapidly expand container and micro-service based applications across multiple clouds to scale from sandbox to production.
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
Good
morning,
everyone,
how
are
you
you're
good?
It's
like
it's
like
it's,
like
being
you
know
at
home.
You
know
for
vacation
with
my
family
like
Thanksgiving
or
Christmas,
or
something
with
my
family
I'm,
surrounded
by
so
many
folks
that
I've
been
working
with
for
so
many
years
and
I'm
so
humbled
to
be
here,
and
you
kind
of
ask
yourself.
You
know
why
well
think
about
it.
A
25
years
of
Linux,
holy
cow,
I
mean
I,
just
got
a
couple,
gray
hairs,
one
or
two
right,
just
just
a
couple,
but
I
mean
when
you
think
back
to
those
days
when
all
this
started
I
mean.
Do
you
remember
the
euphoria
to
use
that
word
that
you
experience
when
you
have
slackware
and
you're
through
linux
on
your
box
and
they
had
the
adapter
for
your
scuzzy
adapter.
A
A
Speed
is
a
currency,
it's
a
currency
that
that
that
developers
value
it's
a
currency,
that
business
people
certainly
value,
speed
and
change
in
the
ability
to
go
fast
and
change.
The
second
is
choice
with
consistency,
okay,
the
ability
to
build
applications
with
speed
and
change,
but
have
choice
as
to
how
you
deploy,
where
you're
deployed,
where
you
how
you
enter
the
application
building
part,
whether
it's
at
a
high
level,
event-driven
architecture,
application,
a
simple
container
that
you
provide
that
others
use
an
API.
A
reusable
object,
store
somewhere
right
choice
with
consistency.
A
You
want
to
be
able
to
have
a
market
place
across
the
third
concept,
which
is
an
open
cloud
architecture.
So
those
are
the
three
kind
of
points
I'd
like
to
cover,
but
I'm
going
to
Center
that
discussion
around
an
atomic
element.
I
like
to
think
about
things
as
compositions
things
built
on
other
things.
In
fact,
that's
how
we
and
IBM
are
building
our
cloud.
A
Whether
you
want
to
have
the
ability
to
scale
up
capacity
run
your
code
on
multi
cloud
environments,
because
guess
what
we
are
going
to
live
in
a
multi
cloud
environment.
You
know
there
was
at
one
point
when,
when
the
web
was
being
worked
by
Tim
berners-lee
and
we're
writing
all
these
standards,
there
were
companies
that
thought
they
would
be
one
web,
one,
one
centralized
kind
of
set
of
stuff
right,
it's
a
little
crazy
back
then
right.
We
also
used
to
fight
over
the
blink
tag.
Remember
the
blink
tag.
You
know
that
was
really
important.
A
We
had
a
fight
over
that
it
was.
It
was
funny
sitting
in
these
working
groups
and
listening
to
the
vendors
you
know
kind
of
fight
over
over
over
whether
or
not
the
building
text
should
be
proprietary
and
and
but
you
should
keep
that
in
context,
as
we
think
about
coat
right
now.
What
really
matters?
What
really
should
be
interoperable?
A
So
those
those
are
some
of
the
basic
use
cases
for
containers,
but
as
you
try
to
build
speed
and
the
ability
to
change,
and
as
you
want
to
have
this
choice
with
consistency,
you
need
to
kind
of
move
a
little
bit
beyond
this
basic
capability
and
so
I'm
going
to
spend
a
moment
talking
about
some
of
the
elements
that
certainly
our
clients
certainly
I,
think
all
of
us
are
developing
and
that
are
really
important
for
empowering
the
atomic
element.
That
is
container
technology.
A
The
ability
to
acquire,
build,
deliver,
run
and
maintain
the
lifecycle
of
these
elements
right,
because,
if,
if
we
don't
focus
on
these
different
atomic,
these
different
steps
in
the
life
cycle
and
if
we
don't
build
choice
with
consistency.
And
if
we
don't
think
about
this
upfront,
we're
going
to
be
in
a
no
different
place
on
where
we
were
with
VMs
right,
the
M
sprawl.
What
what
version
of
what
is
running?
Where
right?
A
What
happens
if
I
shut
this
thing
down
right,
for
example,
so
acquiring
say,
containers
whether
it's
from
a
public
source,
a
commercial
source
of
private
source
certification
of
containers
right?
All
of
that
is
really
important
when
you
think
about
container
technology
building
them.
How
do
you
automate?
You
know
this
is
discussion
of
essentially
building
all
the
automation
you
need
for
an
application
into
a
single
units,
so
you
can
have
that
12
factor
application
right.
How
you
do
that
and
how
we
standardize
around
the
automation
process
is
extremely
important
for
building
delivering.
A
You
know
one
of
the
folks
that
one
of
the
biggest
problems
that
we're
certainly
trying
to
work
on
is
the
notion
of
managing
vulnerabilities
in
containers.
As
you
start
having
things
nested
within
stuff,
how
do
you
know
that
you're
building
an
application
that
is
indeed
a
trustworthy
that
doesn't
have
vulnerabilities
right?
That's
an
example
of
something
you
need
to
consider
when
you
deliver
containers
in
this
chain
and,
of
course
running
them.
How
do
you
run
them?
You
want
to
run
them
on
bare
metal.
Now,
we've
got
a
great
example
of
containers.
I.
A
A
These
are
all
important
parts
of
kind
of
technology
that
you
need
in
a
life
cycle
of
a
container
technology
that
is
not
fully
understood,
I
think,
certainly
in
the
open
source
community,
we're
building
on
that
and
and
certainly
needed
by
our
clients
and
stuff
that
a
lot
of
us
who
provide
a
container
base
or
cloud
native
based
capability
delivered
to
our
clients.
But
you
see
here's
the
kicker.
A
But
we
need
to
look
at
the
elements
under
this
and
the
elements
on
top,
because
if
we
do
not
build
an
open
architecture
from
the
top
and
the
bottom,
all
these
different
pieces
that
we
heard
about
before
and
I'll
talk
about,
specifically
some
of
them
you're
going
to
get
stuck
you're
not
going
to
have
that
choice
of
consistency.
You're
not
going
to
be
able
to
build
that
life
cycle
in
a
way
that
allows
multi
cloud
deployments
or
in
a
way
that
is
truly
open
across
topologies.
Well,
there's
public-private,
dedicated
okay.
A
Now,
as
you
start
to
do
that
patterns
start
to
emerge,
and
you
go
to
the
next
step
of
speed,
right
and
and
change,
and
that
is
this
notion
of
event-driven
architectures
and
micro,
service-oriented
applications
and
man.
You
know
we
have
been
talking
about
the
concepts
of
micro
services
in
computer
science
for
a
very
long
time
right.
You
know,
I'm
a
computer
scientist
for
many
decades
and-
and
you
know,
I
get
excited
every
couple
of
years
because
something
happens
you
know,
I
was
excited
back
when
we
were
doing
the
Dom
or
HTML
because
think
about
it.
A
You
know
the
Dom
was
an
API
driven,
event-driven
type
of
infrastructure
for
force,
a
human
Center
type
applications.
People
started
pushing
that
into
the
back
ends,
though
right
I
was
excited
with
service-oriented
architecture
and
I
still
AM,
because
the
concept
of
you
know
creating
these
reusable
services
were
really
really
cool,
but
each
one
of
these
kind
of
technologies
had
major
impacts
in
the
industry,
but
never
kind
of
really
reach
that
Nirvana
right.
That
Nirvana
of
what
some
folks
call
citizen
development
where
you're
you're
you
know
Mom.
A
Let's
say:
let's
assume
that
your
mom
is
like
mine
in
Puerto
Rico
who's,
not
very
techincal
right
can
build
an
application.
My
mom
sends
me
emails
in
all
caps.
I,
don't
know
why,
but
she
does
okay
and
so
she's
yelling
at
me
constantly,
but
she's
not
yelling
at
me,
but
for
some
reason
the
all
caps
on,
but
imagine
empowering
someone
like
my
mother
to
build
an
application
that
is
the
citizen
developer.
A
That's
what
we're
trying
to
get
to
write
the
ability
to
kind
of
create
a
business
process,
the
east,
because
an
applications,
business
process
that
suits
you
so
we're
at
another
moment
in
time,
where
we're
going
to
try
to
do
this.
However,
I
am
much
more
optimistic
now
than
I
ever
was
because
we've
got
operations
in
mind
now
right.
We
have
this
history
of
openness.
A
That
gets
us
to
a
point
where
you
can
actually
start
to
do
these
things
so
where
we're
going
to
head
I
believe
with
the
cloud
native
computing
foundation
and
the
open
source
that
we're
building
is
exactly
that.
So,
let's
cover
some
of
the
components
you
already
heard
about
the
open
container
initiative.
I.
Remember
very
fondly
pacing
around
my
my
room
in
my
house
on
a
Sunday
right
before
we
launched
this
right,
making
sure
that
we
had
the
wording
and
the
press
release
right
and
all
the
right
folks.
A
But
this
is
an
important
element
because
you
need
to
have
right
interoperability
at
the
base.
Runtime
specification,
image,
specification
and
I
think
we're
doing
good
here,
there's
some
bumps
in
the
road
and
so
forth,
but
we're
doing
Phil.
Are
we
doing
good
here?
We
good
okay,
good
Thank,
You,
Phil
Hill
spends
a
lot
of
time
working
in
that
community
for
us
now,
compute,
storage
and
network
come
on
folks.
We
do
not
want
to
reinvent
over
and
over
and
over
again
base
capability
around
compute
storage
and
network
right.
A
Why
not
build
your
container
or
your
cloud
native
capability
on
existing
API
is
an
existing
code
and
that's
exactly
what
we're
doing
in
IBM
and
a
lot
of
folks
are
doing
this
as
well
in
the
industry
right.
But
it's
important
to
reiterate
this.
You
know
it's
amazing,
to
see
what
has
happened
with
OpenStack
and
I
would
argue
that
OpenStack
was
probably
the
first
of
what
I
would
call
the
modern
day
open
source
to
toe
open
governance
models.
A
It
kind
of
started
this
this
this
realization
again
that
open
source
and
that
open
governance
and
meritocracy
and
the
way
you
behave
and
the
way
you
have
influenced
a
community
really
really
matters
I
mean
I'm,
so
humbled
when
I
go
to
a
and
again
this
is
like
you
can
think
of
it
as
a
data
center
technology.
Right
you
go
to
one
of
these
conferences.
You've
got
9,000,
people
showed
up
for
Austin
at
Austin
for
the
OpenStack
conference
right,
I
think
the
next
one
is
Barcelona.
A
I
was
talking
to
Jonathan,
who
runs
the
foundation
and
they're
expecting
between.
You
know
eight
to
ten.
They
don't
know
right.
So
so
that's
an
amazing
phenomenon
and
it's
an
amazing
code
base
and
it's
in
its
it's
been
used
by
so
many
so
many
clients
I
mean
walmart
runs
hundreds
of
thousands.
Of
course
we
run
thousands
of
thousands,
of
course
right.
A
So
if
you
can
build
your
capability
on
this
open
infrastructure,
that
means
you're
getting
choice
with
consistency
at
the
ground
level
and,
of
course
we
heard
about
these
about
cloud
foundry
and
the
advent
of
of
the
platform.
Because
again
it's
another
entry
point
right
when
you
think
about
how
you
build
with
speed
and
usability.
Have
these
different
entry
points
you
have
base
level,
compute,
storage
and
network
and
patterns
and
dupatta
deployments
within,
say
OpenStack.
A
The
cloud
foundry
Foundation
and
you
know
hats
off
to
the
folks
at
pivotal,
who
helped
bring
this
forward
right,
is
doing
an
amazing
job
in
helping
not
just
vendors
but
growing
ecosystem.
The
cloud
foundry
user
base,
conferences,
etc
are
just
huge
with
excitement
and
lots
and
lots
of
applications.
I
mean
I'm,
real,
proud.
We
I
think
the
largest
Cloud
Foundry
deployment
in
the
world.
A
We've
got
48
days,
centers
across
the
world
and
our
IBM
cloud
and
and
we
our
bluemix
platform,
gives
you
capability
for
OpenStack
containers
and
also
cloud
foundry,
and
we
have
literally
you
know
it
gets
a
20,000
new
developers
a
week
signing
up
to
bluemix
using
these
different
capabilities
right
and-
and
why
is
that?
Why
is
that?
It's
because
of
speed
and
the
ability
to
change.
Remember
that
speed
and
the
ability
to
change
right,
build
your
code.
A
Push
it
out,
go
into
production,
build
your
coat
push
it
out,
go
into
production,
same
environment,
your
test
in
your
production
environment
right,
and
what
we're
doing
here
in
the
cloud
new
to
the
cloud
native
computing
foundation
with
Cooper,
Nettie's
and
Prometheus.
We
spoke
about
that
earlier
and
where
we're
going
to
head.
So
we
spoke
about.
You
know
this.
A
This
idea
of
kind
of
a
call
for
more
participation
for
building
out
this
vision
of
where
we're
headed
with
microservices
and
exposing
you
know,
say
more
transactional
apps
as
api's
like
we
used
say
in
Cloud,
Foundry
applications
or
others.
I
really
encourage
you
all
to
get
involved
and
participate
because
we're
at
the
cusp
hear
of
something
quite
special.
A
So
when
you
think
about
this
basis,
the
centers
of
gravity
that
builds
out
the
architecture
right,
your
compute
storage
and
network,
your
containers,
your
pass,
all
of
this
built
together
AP,
is
standardized
how
you
expose
function
for
user
reusability,
right
the
open,
API
initiative,
which
is
essentially
a
initiative
to
standardize
swagger
right
as
one
way
of
exposing
interfaces.
You
start
to
have
all
of
the
elements
you
need
to
do
micro
services
to
do
the
next
step
right
to
satisfy
my
mother,
the
citizen
developer
right.
A
So
in
comes
open,
whisk,
you
know
IBM's,
if
I'm
so
proud
to
be
with
IBM
I've
been
you
know
it's
funny.
When
you
go
to
a
you,
go
to
conferences
or
you
know,
I
spend
half
my
time
in
Silicon,
Valley
half
my
time
in
New
York
is
it?
Can
you
meet
somebody
and
say
hey,
you
know
who
are
you?
Oh
I'm
angel
and
so
I'm
sewing
sewing
I've
been
with
this
company
that
company
this
company
that
company
they
have
this
long
list
of
companies
that
they've
been
with
and
like
what
about
you
I'm
like.
A
Let's
see,
1997
I
joined
IBM
out
of
college
after
I
got
my
PhD
in
computer
science
joined
IBM,
Watson
Research
Center.
Well,
you
know
IBM,
you
can
have
so
many
different
careers,
because
if
you
look
at
all
the
stuff
that
I've
done,
it's
like
50
companies,
right
and
and
so
there's
a
lot
of
innovation
that
goes
on.
A
Ok
at
a
company
like
IBM,
not
just
these
big
centers
of
gravity,
so
from
an
open-source
perspective,
there's
a
place
that
I
encourage
you
look
at
call,
developerworks
open
and
if
Jeff
is
here,
Jeff
can
tell
you
more
about
that.
But
that's
where
we
put
our
our
kind
of
emerging
open
Technology.
Some
of
it
will
have
great
ecosystems
around
it
like
say
no
dread
or
open
whisk.
Some
of
it
might
not
and
we're
gonna
have
to
kill
it.
But
you'll
have
clarity.
You
have
clarity
as
to
which
open
source
is
taking
off
and
open.
A
Whisk
is
one
of
them.
An
open
whisk
is
an
open,
event-driven
architecture.
Okay,
that
allows
you
to
very
easily
build
these
kind
of
server
list.
Applications
expose
them
as
api's
build
rule
sets
reusable
rule
sets,
have
you
know,
application,
chaining
work
and
multi
cloud
environments.
We've
run
this
on
OpenStack
on
multiple
clouds.
A
Event-Driven
infrastructure,
the
how
you
expose
API,
is
how
you
define
rules
that
will
allow
this
ability
to
to
cater
to
the
citizen
developer,
to
my
mother,
right
and,
and
so
I
suggest
that
if
you
can
check
out
open
whiskey,
if
you
have
it
right
and
get
involved,
because
it's
hopefully
going
to
help
out
there.
So
what
about
us
well
go
to
bluemix
net?
That's
where
you
can
access
all
of
our
technology
from
a
container
perspective.
Remember
that
life
cycle
I
spoke
about
right.
We
give
that
to
you.
We
build
our
capability
on
OpenStack
using
dr.
A
A
You
know
that
right,
some
people
get
enamored
with
new
shiny
application
sitting
on
a
public
lat
which
are
important
good
to
do
right.
But
man,
if
you've
got
transactional
data
transactional
information
sitting
here
on
the
mothership
right.
Imagine
the
kinds
of
applications
you
can
build
their
right.
If
you
can
build
cloud
native
applications
on
premise
connecting
to
those
systems
of
record
right
on
systems
like
say
linux,
one
right
like
my
t-shirt,
peace,
love
and
Linux
one
is
that
cute
right?
A
A
It's
freaking,
unbelievable
right,
and
you
expose
that
you
know
as
an
API
into
this
microservices
event-driven
world
right
and
you
create
new
applications
right
all
governed,
all
managed
to
this
life
cycle.
That's
kind
of
what
we're
doing
an
idea
and
that's
what
we're
headed
this
notion
of
hybrid
cloud.
Multi-Cloud.
No
application
is
an
island,
so
I'll
leave
you
where
I
started
right.
A
It's
about
speed.
It's
about
change
is
about
choice
with
consider
see.
Consistency
is
about
building
an
open
architecture
right
and
if
we
do
these
things,
you
will
always
have
that
sense
of
euphoria.
You
will
always
have
that
feeling
of
when
you
first
use
slackware
right
or
red
hat
or
your
favorite
distribution
to
create
your
linux
box
or
you
first
open
a
web
browser
because
you
are
building
on
the
shoulders
of
giants.
A
You
will
be
able
to
innovate
where
it
matters
to
you
right
and
for
whatever
company
you're
working
for
so
please
I
encourage
you
to
try
all
of
our
container
and
cloud
native
capability
on
bluemix
dinette.
It
is
very
easy
to
use.
Go
there
now,
check
it
out
and
I.
Most
importantly,
encourage
you
right
to
join
these
communities
to
be
active
participants,
whether
your
users
providing
feedback
or
whether
you're
a
developer
with
that.
Thank
you
very
much
for
your
time.
I
look
forward
to
chatting
with
you
all
as
the
day
progresses.
Thank
you.