►
From YouTube: Opening Remarks - Steve Wong, VMware
Description
Opening Remarks - Steve Wong, VMware
A
A
My
point
is
that
what
is
viewed
as
modern
changes,
every
10
or
20
years
as
tech
and
new
ideas,
surface
things
like
ai
and
machine
learning,
now
present
a
new
opportunity.
Examples
in
the
sensor
space
include
occupancy
sensing
that
not
only
detects
somebody
entered
the
room
but
identifies
who
that
person
is
and
what
their
role
is.
Industrial
automation
that
can
not
only
tell
that
a
pump
is
running
but
predict
impending
failures
before
they're
allowed
to
happen.
A
A
Also,
there
are
opportunities
related
to
new
types
of
edge
devices
that
improve
our
environment,
but
I
think
the
bigger
payoff
here
relates
to
just
doing
existing
stuff
in
a
better
way
suppose
we
could
improve
the
efficiency
of
manufacturing
or
transportation
operations
by
just
two
percent.
These
kinds
of
advances
improve
quality
of
environment,
standard
of
living
and
quality
of
life.
A
I
came
across
this
recently
if
you
process
data
intensive
workloads
such
as
image
recognition
in
a
public
cloud,
the
downside
could
go
beyond
just
latency
and
added
points
of
failure.
It
might
bring
with
it
wasteful
energy
burn
and
even
given
that
you're,
adding
extra
hardware
in
these
long-term
compute
supply
chains
can
contribute
to
long-term
e-waste,
running
pipelines
of
4k
30
frame.
A
second
video
all
the
way
up
to
public
cloud.
Might
be
wrong
on
many
levels.
A
The
elephant
in
the
room
here
relates
to
the
original
design
of
kubernetes.
It
was
designed
for
large
data
centers.
Achieving
efficiency
and
availability
by
by
running
workloads
on
centrally
pooled
hosts
with
good
network
interconnects,
and
lots
of
interchangeable,
compute
hosts
edge
is
actually
decentralized,
often
with
I
o
and
location
constraints
causing
one-to-one
relationships
with
the
workload
in
a
particular
cluster
host
that
that
has
to
run
on
to
be
useful.
A
People
have
come
up
with
kubernetes
projects
to
make
kubernetes
better
suited
for
edge,
and
we
have
a
talk
on
cube
edge
today
related
to
this,
but
they've
always
been
questions
about
how
to
map
kubernetes
to
edge
whole
clusters
at
edge
worker
nodes.
Only
crds
controlling
edge
workloads,
some
are
asking
if
edge,
might
actually
be
a
new
type
of
cloud
calling
for
a
completely
new
type
of
orchestrator,
but
it
isn't
just
the
orchestrator.
If
you
think
people
talking
about
throwing
out
kubernetes
for
a
new
orchestrator
right
edge
hold.
A
My
beer
heretics
are
now
actually
charging
a
challenging
docker,
including
this
guy,
who
founded
docker,
there's
a
relatively
new
form
of
container
called
web
assembly.
That
has
some
very
interesting
characteristics
related
to
edge,
for
example,
smaller
size
when
moved
when
the
packaging
is
moved
on
the
network
significantly
lower
startup
latency
cross,
cpu
compatibility,
lower
resource
demand
for
the
runtime,
but
web
assembly
also
brings
it
in
with
it
some
limitations.
A
So
first
they
challenge
kubernetes
itself
now
docker
next
thing
you
know
they
they're
going
to
be
alleging.
Maybe
the
world
isn't
flat.
You
know
we
have
a
talk
on
this
web
assembly
thing
later
in
the
afternoon
and
I
really
would
like
you
to
be
there
as
we
dig
into
the
suitability
of
webassembly
at
edge,
because
this
could
be
the
next
big
thing.
A
So
I
promised
you,
I
tell
you
the
real
theme
of
today's
event
and
that
theme
is
community
sharing
ideas,
sharing
things
we
build
together
and
in
that
theme
of
community,
let
me
start
with
a
community
anti-pattern
that
plays
into
edge.
You
know,
I
think,
we're
all
aware
of
recent
world
events
that
are
causing
high
levels
of
mistrust
across
certain
borders.
Governments
have
been
banning
black
box
commercial,
closed
source
products
from
critical
infrastructure,
and
this
trend
continues
or
is
strengthening.
A
I
submit
to
you
that
in
the
linux
foundation
in
cncf,
we
have
a
system
that
has
been
proven
to
work
and
a
key
element
of
that
is
the
code
of
conduct
that
helps
people
from
different
countries.
Different
companies
get
together.
This
code
of
conduct
applies
to
all
events
and
I'm
not
going
to
lecture
you
on
the
full
extent
of
that
code
of
conduct
here,
but
I
do
want
to
point
out
one
particular
application
of
this
code
of
conduct.
That's
relevant
to
today's
event.
A
The
cncf
and
kubernetes
slack
channel
have
had
some
recent
discussions
regarding
the
mask
roles
for
this
event,
and
it's
been
a
difficult
situation
with
imperfect
knowledge
and
actual
changes
and
conditions.
You
know,
for
example,
if
the
virus
in
the
wild
out
there
today
is
different
from
two
years
ago.
A
I
guess
I
get
off
because
I'm
a
speaker
and
I'm
a
long
distance
away
from
you,
but
I
I'm
asking
you
to
understand
that
when
people
are
involved,
they
don't
have
this
big
bang
flip
of
opinion
like
a
computer,
would
where
instantaneously
everybody
flips
their
attitude
on
masks
and
we
have
people
with
different
attitudes.
So,
let's
just
accommodate
them
here
you
know
arguments
over
docker
or
webassembly,
or
the
best
kubernetes
form
factor
are
thoroughly
encouraged
at
today's
event.
But
when
it
comes
to
masks
no
no
debates,
the
rule
says
you
wear
them.
A
A
A
The
reason
for
these
discussions
is
that
at
a
conference
nobody
is
always
right,
or
always
the
smartest
people
in
the
room
on
all
topics,
and
you
get
smarter
yourself
by
talking
to
people
who
have
a
little
bit
more
experience
in
little
niches
and
that
isn't
going
to
take
place.
Listening
to
speakers
like
me
or
the
people
that
follow
me,
that's
going
to
take
place
up
in
the
hallway,
as
you
have
these
conversations,
so
I
just
want
to
point
out
that,
along
this
theme
of
community
one
more
session,
I
want
to
plug.