►
Description
In this lightboard session, Steve Tegeler walks through four important Developer Abstractions in a sofware defined data center: Infrastructure as a Service, Docker API, Kubernetes and Cloud Foundry, and talked about the corresponding VMware products in each category.
A
Hi,
my
name
is
Steve
pegler
I'm,
a
senior
director
systems,
engineering
and
VMware's
cloud
native
apps
business
unit,
and
this
light
board
session
is
all
about
developer,
abstractions
and
notice.
I've
got
developer
in
quotes.
You
know,
I
could
mean
a
lot
of
different
things
to
a
lot
of
people,
but
fundamentally
I'm
talking
about
someone
that
checks
in
code
and
creates
software.
It
could
be
anything
from
the
actual
application
that
may
be
running
to
an
internal
IT
service
that
needs
to
be
created
to
service
those
application
developers.
A
But,
as
you
can
see,
I've
got
four
different
types
of
developer
abstractions.
Here.
First
one
is
infrastructure
as
a
service.
Second
one
would
be
the
doctor.
Api
third
is
kubernetes
and
fourth
is
cloud
foundry
and
you
know
in
IT.
Sometimes
we
find
a
need
for
all
four
of
these
potentially
and
I
want
to
talk
about
the
difference
between
each
one
of
these
and
and
really
the
level
of
effort
required
for
the
end
application
owner
to
deploy
their
app.
A
A
Some
of
the
public
cloud
providers
have
a
Mis
and
so
forth,
but
fundamentally
I
got
an
application
that
needs
to
be
installed
on
a
base
level.
Vm
I
normally
require
something
like
configuration
management
to
do
that
activity.
So
not
only
is
the
configuration
management
going
to
install
the
app,
but
the
configuration
management
is
also
going
to
prep,
that
operating
system
load
all
the
tools
and
the
libraries
and
software
that
you
may
need
and
then
finally,
I'm
gonna
orchestrate
this
entire
stack
was
something
called
infrastructure
as
code.
A
So
that's
gonna
be
require
me
to
go
use
what
we
call
infrastructure
primitives,
so
a
virtual
machine,
a
network
I
have
to
define
maybe
subnet,
masks
and
IP
addresses
security,
firewall
rules
and
those
types
of
things,
basically
infrastructure,
primitives
and
then
I,
deploy
it
to
an
is
so
VMware
has
a
solution.
In
this
case,
if
this
is
if
this
is
what
you
need,
we've
actually
got:
two
we've
got
VMware
integrated,
OpenStack
and
V
real
Automation
today.
That
can
help
out
with
that.
A
A
Let's
just
call
them
service
dependencies.
So
if
I
need
access
to
data,
if
I
need
to
present
that
container,
a
certain
way
out
of
the
host
or
so
forth,
I
need
to
basically
architect
the
service
dependencies.
There
then,
the
final
step,
because
I'm
just
interacting
with
a
docker
API,
which
is
you
know,
think
of
it
as
running
an
individual
container,
so
to
speak,
I'm
going
to
need
to
basically
orchestrate
the
running
of
the
container
or
containers
now
normally,
when
someone's
interacting
with
the
docker
API.
A
The
reality
is
oh
and
sorry,
and
so
VMware's
technology
and
in
the
case
of
a
docker
docker,
providing
a
docker
api
is
something
called
vSphere
integrated
containers.
Now
Vic
is
an
interesting
technology
which
you
can
see
in
a
different
light
board,
but
fundamentally
the
service
or
the
demarcation
between
the
teams
is
the
docker
API
okay.
A
So
what
we
do
see,
though,
in
the
data
centers,
is
a
need
to
go
from
just
dealing
with
the
docker
API
we
actually
want
to
orchestrate,
and
we
want
to
manage
multiple
containers
at
a
time,
because,
really
that's
what
makes
up
the
entire
application.
You
may
have
a
couple
of
web
servers.
The
load
balancer
and
a
database
now
you
need
to
orchestrate
all
those
things
together.
So
that's
where
something
like
kubernetes
comes
into
play,
and
so
the
difference
here
is
that
I've
got
my
app
I
am
going
to
build
the
container
here.
A
I
still
have
that
same
process,
I'm
going
to
architect
some
dependencies
and
kubernetes
gives
me
a
method
to
do
this,
so
it
has
constructs
that
I
can
use
to
basically
define
how
this
app
is
going
to
be
stitched
together.
Once
that's
done,
though,
then
I
can
pass
that
directly
to
the
kubernetes
api
and
the
kubernetes
cluster
will
be
responsible
for
running
this
application.
For
me,
okay,
and
so
the
solution
there
from
VMware
and
pivotal,
is
something
called
PKS.
A
Okay,
now
on
to
the
final
solution
here,
which
is
Cloud
Foundry,
so
Cloud
Foundry
is
even
more
simple.
So
in
this
case,
I
have
an
application.
I
have
an
application
artifact!
Think
of
it
like
a
jar
file
or
whatnot.
All
I
have
to
do
with
Cloud
Foundry
is
deploy
that
application
or
basically
deployed
in
a
cloud
foundry
in
cloud
foundry
will
take
care
of
building
the
containers.
A
It
knows
a
lot
of
the
dependencies
will
help
scale
it
and
so
on
and
so
forth,
so
it
and
and
that
product
so
to
speak,
would
be
something
called
pivotal
application
service.
Now
these
are
all
great.
So
these
are
all
the
different
VMware
functions
here
that
that
help
with
these
different
developer
abstractions.
But
the
thing
is
here:
these
all
need
to
run
somewhere
right
if
you
take
PKS
in
particular,
there's
a
load
balancer
defined
up
here.
Eventually
that
needs
to
run
on
some
sort
of
load,
balancer
or
load
balancer
technology.
A
A
This
is
NSX,
and
this
is
V
Sam,
and
the
idea
is
that
with
each
one
of
these
technologies
here,
I
can
take
and
I
can
map
the
native
call
it
language
or
the
native
primitives
and
uber
Nettie's
like
load
balancer
and
security
policy
and
whatnot
and
I
can
map
those
down
into
the
software-defined
data
center
very
easily
same
thing
with
Vic
it
can
run
and
it
can
uses
some
of
the
native
constructs
in
the
SDC.
Of
course,
these
two
I
as
platforms.
A
A
Operations,
and
so
the
existing
operations
can
mean
a
bunch
of
different
things.
It
can
mean
any
anything
from
existing
technology,
so
think,
V
realize
operations,
log
insight,
those
types
of
things.
It
could
mean
those
technologies,
it
could
mean
human
beings,
it
could
mean
processes
right,
even
just
the
individual
processes.
So
if
I
can
use
the
same
processes
in
the
same
tools,
but
just
to
provide
a
different
way
to
consume,
there's
huge
what
we'll
call
economies
of
scale,
meaning
I,
don't
have
to
deploy
a
unique
infrastructure
for
each
and
every
one
of
these
things.
A
I
can
leverage
a
common
infrastructure.
Now,
whether
that's
an
actual
you
know
the
same
server
or
the
same
cluster
is
to
be
determined,
but
at
least
it's
the
exact
same
technology
that
you
can
apply
the
exact
same
operations
to
now.
Not
only
do
I
have
existing
operations
for
the
sddc.
A
lot
of
the
tools
that
VMware
has
are
elevating
themselves
and
they'll,
be
able
to
expand
capabilities
and
monitor
a
lot
of
these
things
as
well.
A
So,
hopefully
that
gives
you
a
good
idea
of
these
different
think
of
them
as
like
IT
services
that
you
could
provide.
As
as
maybe
a
via
VMware,
administrator
or
Architect,
these
are
the
different
ones
and
they
all
map
easily.
On
top
of
technology
that
you
are
already
know
and
already
comfortable
with
thanks
for
watching.