►
From YouTube: Keynote Edge Native is the new Cloud Native Modern Apps at the Edge, Marco Nicosia, VMware Tanzu
Description
Keynote - Edge Native is the new Cloud Native - Modern Apps at the Edge, Marco Nicosia- VMware Tanzu
Edge computing is the next evolution of cloud. Over the last decade, we’ve learned a lot about running applications on elastic clouds. Infrastructure Operators and Developers can apply much of what we’ve learned to Edge deployments, so that you can be confident that the same app is up to date and secure at many locations simultaneously. The two concepts we’ll cover in this quick talk are disposable infrastructure and using abstractions to enable t-shirt sizing at the Edge.
A
Okay,
so
my
name
is
marco
and
I
work
at
vmware
on
tonsi,
my
my
job
is:
I'm
the
product
line
manager
for
tons
of
edge,
I'm
on
craig
mcluckie's
team,
and
he
talked
last
year.
I
hope
you
watched
that
video.
It
was
a
lot
of
fun
wanted
to
kind
of
pick
up
where
he
left
off.
This
is
the
only
slide
that
has
the
word
vmware
in
it.
A
It's
just
his
quote
and
wanted
to
spend
a
couple
of
minutes
reviewing
what
he
was
talking
about
and
since
sometimes
we
were
very
early
in
our
journey.
Maybe
give
you
a
little
bit
of
an
update
and
kind
of
share
with
you,
some
of
the
themes
that
we're
trying
to
resolve
in
a
way
that
I
think
will
hopefully
be
useful
to
you
all
in
that.
If
you're
in
this
room,
you
are
my
friend
because
we're
all
trying
to
figure
out
edge,
some
of
you
may
be
very
early
in
your
journey.
A
So
I
wanted
two
key
themes:
good,
the
font
is
too
small
for
all
of
us
to
read
that's
kind
of
on
purpose
like
I
don't
want
you
to
really
read
the
screen.
The
slides
will
be
uploaded
later,
but
I
thought
what
would
be
helpful
is
to
expand
on
what
craig
was
talking
about
and
kind
of
explain
what
our
challenges
are
for
helping
figure
out
how
to
work
on
the
edge
for
relatively
large
companies
and
the
two
things
that
I
really
wanted
to
drill
into
your
mind
today
is
like.
A
If
you
are
able
to
do
these
two
things,
I
think
you
will
find
your
journey
to
edge
to
be
a
lot
easier
and
the
first
theme
is
to
think
of
edge
as
a
cloud
right.
We
are
we're
really
trying
to
think
of
when
we
deploy
to
all
infrastructures
that
we
would
like
to
get
to
the
point
where
a
developer
can
push
software
an
application
or
other
software
to
the
edge.
The
same
way
that
they're
pushing
to
public
cloud.
A
It's
taken
us
what
10
12
years
to
figure
public
cloud
out,
so
the
most
important
thing,
and
I'm
not
going
to
read
every
every
line
on
the
slide,
is
make
sure
to
treat
your
edge
sites
like
they're
ephemeral,
right
prepare
for
disaster
in
the
same
way
that
amazon
taught
us
like
don't
rely
on
that
vm.
A
Don't
don't
expect
it
to
be
there
tomorrow
morning,
if
you,
if
you
lo,
if
you
lose
it,
just
be
able
to
create
a
new
one,
try
to
do
the
same
thing
with
your
edge
sites,
so
an
interest,
an
interesting
thing
that
comes
up
a
lot
when
we
talk
with
it,
people
who
are
trying
to
figure
out
how
to
instrument
their
stores
is.
How
do
I
backup
and
restore
my
edge
site?
It's
like.
Do
you
really
want
to
do
that?
A
Don't
don't
don't
back
up
and
restore
edge
if
you
lose
it
just
throw
it
away
and
start
over
again.
Did
you
keep
persistent
theta
there?
Maybe
you
shouldn't
keep
persistent
data
at
the
edge
where
somebody
can
spill
a
coke
on
top
of
your
machine
right
find
another
way,
and
similarly
the
second
theme
is
use
abstractions
to
push
apps.
A
I
don't
know
about
you,
but
I
I
really
enjoy
using
puppet
chef
terraform
a
bunch
of
these
tools,
and
I
feel
pretty
confident
now
that
I
can
use
any
variety
of
systems
to
push
my
app
pretty
pretty
productively
to
one
site
like
the
primary
site.
Maybe
I'm
even
good
at
pushing
to
dr
and
I'm
good
at
switching
back
and
forth.
A
I
know
about
you,
but
I
don't
want
to
push
to
a
thousand
sites
if
I
have
a
thousand
stores
or
ten
thousand
sites.
If
you
use
an
application
platform,
then
it
will
be
a
lot
easier
for
you
to
implement
something
like
gitops
right
and
by
the
way
I
really
uncomfortable
with
the
term
git
ops.
I
feel
like
it's
not
very
descriptive,
for
what
we're
trying
to
do
right.
You
want
to
use
a
cd
system
that
was
aware
of
a
source
code
control
system.
That
knows
how
to
push
that.
A
It's
too
many
words,
but
if
you
can
find
a
better
term
than
git
ops,
please
share
with
me.
I
would
like
to
know
so
what
are
some
of
the
challenges
that
you
will
find
for
these
things?
A
So
one
of
the
big
ones
that
I
want
to
call
out
today
is
when
you're
developing
edge
sites,
it's
really
worthwhile
to
get
people
to
stop
thinking
about.
We
need
five
nines.
All
of
us
have
just
spent
the
last
10
years,
12
years
getting
out
of
the
data
center
into
public
cloud.
We
are
very,
very
good
at
kubernetes,
especially
running
in
highly
available
mode.
My
own
documentation.
I
looked
at
my
own
product
one
day.
It
says
if
you're
not
running
in
highly
available
mode,
you're,
not
supported
period.
A
Can
I
make
it
so
that
these
sites
are
disposable
so
that
I
don't
need
to
depend
on
them
100
of
the
time,
but
that
if
I
do
need
high
availability,
I
know
how
to
invest
on
that
appropriately,
so
that
my
spend
and
my
value
are
kind
of
manageable,
because
anything
you
do
will
be
multiplied
by
the
number
of
sites
you're
at.
So
this
isn't
maybe
the
best
place
to
put
three
rack
mount
servers
underneath
everybody's
coffee
machine
and
similarly
for
for
the
application
platform.
A
What
we're
really
trying
to
do
is
trying
to
figure
out
what
does
edge
native
mean
right?
I
think
we've
all
gotten
pretty
comfortable
with
the
idea
of
cloud
native,
but
what
is
an
edge
native
app?
What
does
it
mean
to
be
edge
native?
Maybe
it
means
that
it's
a
durable
to
poor
latency.
Maybe
it's
what
we
call
effective
for
what
we
call
submarine
mode
right.
Sometimes
the
submarine
goes
under
the
ship.
Sorry,
under
the
water,
it's
offline
for
a
long
time,
craig
called
this
periscope
mode,
which
I
like
to.
A
Maybe
it
has
a
very
thin
connection:
we've
all
gotten
pretty
used
to
being
in
the
cloud
where
we
have
infinite
bandwidth
and
it's
always
reliable.
That's
not
going
to
be
that
way.
Now,
a
lot
of
people
are
converting
to
public
consumer
grade
internet
as
opposed
to
team
one
lines
frame:
relays-
mac,
that's
not
there!
So
we're
still
working
on
that
and
by
the
way,
you'll
notice
that
there's
only
one
word
in
the
whole
presentation
that
is
highlighted,
and
I
actually
highlighted
it
twice,
which
is
security.
A
Everything
else.
In
my
talk
you
could
pretty
much
discard.
If
we
all
get
security
right,
then
maybe
we'll
do
a
better
job
of
succeeding
at
the
edge
and
then
super
briefly.
What
are
the
kind
of
key
technologies
that
I
think
are
worthwhile
here?
The
highlights
that
I
would
like
to
to
cover
on
the
technologies
like
I'm.
I'm
actually
really
appreciative.
Thank
you
so
much
for
bringing
up
like
the
exhaustive
list,
because
I
made
sure
not
to
put
any
names
of
technologies
in
mind.
So
we
complement
each
other.
A
Well,
thank
you,
but
I
think
one
of
the
things
that
we're
discovering
is
that
for
edge,
almost
everybody
has
existing
workloads
and
I've
been
very
careful
not
to
insult
anybody.
Don't
call
them
legacy.
Workloads
like
these
are
the
workloads
that
are
running
the
phone
system,
they're
running
the
lights,
they're
running
the
cash
registers.
It's
not
legacy!
Those
things
need
to
continue
running
so
one
of
the
big
priorities
we're
finding
when
we
go
out
and
talk
with
people
like
what
do
you
need?
How
do
you
want
to
be
successful
at
the
edges?
A
That's
fine,
but
don't
take
down
the
phone
system.
The
cash
registers
still
need
to
run
so
whatever
we're
doing
we're
layering
in
and
I'm
super
excited
about,
the
kubernetes
api.
I
think
it's
like
conveniently
perfectly
wonderful
to
deploy
a
thousand
times,
but
don't
disrupt
the
vms
right,
make
sure
that
they're
still
able
to
run
make
sure
that
they
still
have
their
storage
make
sure
that
they
can
migrate.
A
If
there's
a
hardware
failure-
and
so
I
feel
like
that's
something-
that's
super
important
when
thinking
about
running
at
the
edge
is
like
don't
push
the
other
stuff
aside,
don't
try
and
replace
it
and,
I
would
also
say,
under
key
technologies
related
to
the
application
platform,
and
if
you
want
to
talk
about
this
afterwards,
I
would
really
love
to
hear
it
is
we're
discovering
that
while
everybody
feels
like
they
have
a
really
good
idea
about
how
to
deploy
the
api,
how
to
get
kubernetes
up
and
running
how
to
do
all
these
things,
then
I
say
yeah.
A
But
how
are
you
going
to
distribute
your
container
images
and
everybody
hits
a
big
pause
right?
It's
it's!
It's
a
challenge
right.
You
can't
just
have
a
container
registering
in
the
cloud
and
expect
everything
to
reach
out
to
the
cloud
like
sometimes
you're
not
going
to
be
able
to
do
that
or
sometimes
you
won't
have
the
bandwidth.
How
will
you
know
when
it's
finished
replicating?
This
is
turning
out
to
be
like
a
pretty
considerable
challenge,
so
it's
part
of
our
journey.
I
wanted
to
share
that
with
you.
A
I
also
don't
want
to
keep
you
from
the
rest
of
the
talks
so
myself,
my
onc
will
be
outside
at
the
at
the
table
when
you
want
to
want
to
chat,
and
if
these
are
interesting
ideas
to
you
or,
if
you're
curious,
to
learn
more
about
how
we're
choosing
to
solve
them.
Like
I
didn't
put
any
prescriptive
stuff
in
this
deck,
please
come
and
meet
us
alright.