►
From YouTube: CNCF Network Service Mesh Meeting - 2019-06-19
Description
Join us for Kubernetes Forums Seoul, Sydney, Bengaluru and Delhi - learn more at kubecon.io
Don't miss KubeCon + CloudNativeCon 2020 events in Amsterdam March 30 - April 2, Shanghai July 28-30 and Boston November 17-20! Learn more at kubecon.io. The conference features presentations from developers and end users of Kubernetes, Prometheus, Envoy, and all of the other CNCF-hosted projects
B
A
B
One
of
the
things
I
want
to
cover
today
is
so
they're
all
these
CNF
white
papers
and
now
there's
multiple
ones
in
flight
and
Frederic
and
I
had
been
talking
a
bunch
like
months
leading
up
to
this,
and
now
it's
kind
of
fracturing,
because
all
the
vendors
are
getting
involved.
I
kind
of
want
to
talk
about
what
the
strategy
is
for
kind
of
what
the
two
main
white
papers
are
going
to
attempt
to
cover
right
now
and
where
we
might
want
to
insert
NSM.
B
Since
this
is
going
to
be
a
big,
you
know
piece
of
documentation
and
NSM
making
it
into
you
know,
foundation
published
white
papers,
and
we
obviously
want
it
to
be
in
there
in
some
type
of
prominent
fashion
as
an
alternative
for
cloud
native
networking
models,
and
additionally,
I
will
share
here
in
a
second
kind
of
like
some
of
the
content
I'm
putting
together
I'm,
pretty
sure
it's
going
to
go
into
the
first
white
paper,
because
it's
kind
of
the
whole
journey
thing,
but
then
also
on
Watson
I'd,
like
to
kind
of
chat
with
you
to
there's
a
lot
of
the
CI
work.
B
You've
been
doing.
All
of
those
of
us
in
MSM
community
have
been
benefiting
from
so
kind
of
getting
your
take
on
where
you
think
some
of
the
content
I'm
putting
together
should
go
where
some
of
the
CI
you
know,
documentation,
lemmas,
you're,
putting
together
should
go
and
then
kind
of
how
we
fit
in
a
sim
into
either
both
papers
or
maybe
super
prominently
into
one
of
the
papers.
C
Sure
is
good,
and
so
on
my
side,
just
a
quick,
quick
remarks
about
this
I,
don't
know
if
we
need
to
specifically
embed
SM
and
like
in
the
core
kind
of
concepts
may
be
in
some
men
went
through
the
white
papers
or
some
some
some
form
of
appendices
somewhere.
Where
we
talk
about
examples
and
specific,
concrete
implementations,
I
think
that
it's
more
important
for
us
to
more
or
less
embed
the
concepts
of
what
we
are
trying
to
do
within
NSF
in
to
introduce
white
papers.
I
mean
like
to
try
to
avoid
the
usual.
B
Think
it's
gonna
depend
on
the
white
paper
Nikolay
because
at
least
and
I'm
not
sure
which
one
of
them
they're
gonna
live
in
right
now,
but
because
we
seem
to
kind
of
try
to
be
duplicating
efforts
at
the
moment
and
I'm
working
with
Dan
on
time
to
get
some
separation
because
I'll
probably
end
up
helping.
B
What's
both
and
I
want
to
make
sure
that
they
both
can
kind
of
stand
on
their
own,
but
at
least
in
one
of
the
white
papers
like
as
we
get
into
like
there's
been
requests
from
both
Dan
and
our
pit.
That,
like
at
least
one
of
the
white
papers
has
like
you
know
no
BS
like
implementation,
information
right
and
with
the
disclaimer
that,
like
all
of
this
stuff,
is
super
early,
and
we
might
decide
that
these
implementations
are
completely
wrong.
B
B
You
know
in
the
test
bed
on
that
like
look
at
danam,
that
look
at
multi
that
look
at
an
SM
that
look
at
different
networking
models
and
like
talk
about
like
what
performance
looks
like
talk
about
what
you
know
difficulty
in
operation,
it
could
I
mean
at
some
point,
I
think
that
you
know
some
real
real
meat
on
like
what
it
actually
means
to
deploy.
Some
of
this
stuff
is
important
and
it
doesn't
necessarily
have
to
even
go
that's
exactly
why
I
wanted
to
talk
about
us.
D
E
It
seems
like
NSM,
has
a
strong
position
for
declarative
api's,
which
talking
with
people
it
seems
like
them
and
know
how
this
comes
from.
You
know
ed
and
fray
it
some
of
the
problems
that
are
getting
trying
to
be
solved
by
you
know:
multi-source
Eni,
other
T&I
plugins,
some
of
the
other
ways
of
doing
things
and
then
also
with
the
VNS
which
are
being
brought
in
on
some
of
the
papers,
but
the
old
way.
E
You
know
the
journey
and
everything
I
think,
even
if
we
don't
say
MSM,
directly
you're
going
to
be
saying
it
and
you're
going
to
be
talking
about
MSM
in
a
in
a
different
way
like
it
for
all
intents
and
purposes,
because
of
the
way
that
the
declarative,
eight
guys
are
positioned
with
nfm.
It
seems
like
it's
a
first
order,
citizen
anything
yeah.
F
They
the
way
that
I
would
try
to
describe
that
would
be
to
describe
things
and
with
like
cloud
native
principles
and
to
be
able
to
say
we
care
about
things
like
declarative,
api's
state.
What
you
want,
not
how
do
you,
how
do
you
get
there
and
to
be
able
and
let
the
let
the
scheduler
and
infrastructure
render
that
for
you,
so
yeah
and
so
I'll
give
them
an
early
example
as
well.
F
But
I
would
also
argue
that
if
something
else
came
along
that
should
that
is
trying
to
coordinate
that
it's
replicating
like
a
different
project
in
this
space.
But
my
argument
would
be
that,
in
order
for
them
to
be
cloud
native,
they
should
also
follow
similar,
similar
principles
as
well,
and
so
that's
so
I
think,
starting
with
the
principle.
A
Is
important
and
I
usually
roll
under
a
loosely
coupled
right,
because
declarative
API
is
the
reason
we
like
declarative
API
is
is
because
they
loosely
couple
you
to
the
implementation
right,
the
Rianne.
The
reason
that
we
don't
want
to
do
things
like
stick
freaking
eye
keys
and
VLANs
to
the
declarative.
Api's
is
because
they
then
strongly
couple
you
to
things
that
are
implementation
details,
because
you
can
write
incredibly
strongly
coupled
declarative.
Api
is,
if
you
do
it
badly.
A
A
So
the
really
fundamental
principle
to
me
is
loosely
coupled
and
that's
the
thing
in
network
service
mesh
that
I
think
we
do
super
well,
because
the
workloads
may
have
an
opinion
about
the
thing
that
is
most
immediately
before
them,
but
they
have
no
opinion
about,
for
example,
the
tunneling
types
that
go
over
the
network,
because
that's
not
the
workloads
business.
Why
are
you
strongly
coupling
your
particular
CNF
to
a
choice
of
tunnel
that
someone's
going
to
want
to
make
differently
next
year.
B
Yep
so
for
the
SP
LED
white
paper,
I
think
we're
gonna
shift
it
a
little
bit
to
less
about
you
know
some
of
the
rules
like
granular
details
on
the
plumbing
well
I.
Take
that
back,
like
I
kind
of
look
at
this
first
one.
B
It's
like
a
book
report
with
some
technical
meet
to
give
people
who
don't
know
anything
about
cloud
native
and
how
it
maps
to
NFC
and
what
pitfalls
to
avoid
that's
kind
of
what
I'm
going
to
now
try
to
shift
this
first
white
paper
to
and
then
work
with
the
vendors
on
the
second
one
to
kind
of
talk
about,
like
you
know
what
we're
actually
trying
to
do
right
now,
but
so,
unfortunately,
because
we
have
some
crazy,
like
you
know,
rules,
I'm,
rebuilding
a
bunch
of
images
but
I'm
trying
to
create,
like
a
bunch
of
things
that,
like
literally
show
step
by
step.
B
How
something
like
you
know
this
is
the
packet
flow
for
verdi,
o
net
like
and
I've
got
like
what
all
these
numbers
correlate
to
right,
like
packets
received
packet,
split
into
the
buffer,
the
copied
from
the
buffer
to
DMA,
etc,
cetera
et
cetera,
right,
like
the
different
irq
calls
that
are
called
in
between
and
I've
got
like
this
for
most
of
the
majorly
accepted,
like
virtual
networking
things,
I
just
need
to
convert
all
the
images
into
something.
B
That's
not
going
to
get
me
in
trouble,
but
the
goal
here,
then,
is
to
do
that
and
I've
I
can't
show
the
other
images
now,
because
I
haven't
cleaned
them
up,
which
is
kind
of
frustrating
for
me,
but
I'd
also
like
to
get
to
the
point
where
I'm
going
to
build
like
equivalent
images
for
all
the
container
networks.
Stuff
too
right,
like
literally
here,
is
pod
sitting
on
a
host
here.
Is
you
know
where
things
maybe
Nana
door,
where
you
know
I'm,
avoiding
that
this
is
what
you
know.
B
B
You
know
pass
through
the
host
in
and
out
of
it
like,
because
really
that's
what
all
of
us
care
about
in
these
communities
is
how
do
I
get
back
it's
through
that
Nick
have
something
done
to
love
a
packet
and
then
shove
back
out
onto
the
network
and
that's
kind
of
like
I,
think
I'm
gonna
focus
on
unless
some
people
think
that
that
should
go
into
the
other
white
paper,
but
I
just
kind
of
see
this
first
one
as
being
an
explanation
of
the
technologies
and,
like
you
know,
kind
of
like
how
people
start
to
migrate,
you
know
and
integrate
what
they
currently
have
now
and
like
the
NFB
I
space
to
kind
of
taking
on
a
more
cloud
native
approach
and
then
other
than
you
know,
just
high-level
information
to
me.
B
Building
like
some,
you
know
really
granular
data
plane,
diagrams
I
mean
we
want
anything
else
from
an
in
SM
context.
In
this
first
you
know
service
provider,
one
and
I
think
I'm
getting
a
little
resistance
on
just
doing
like
the
five
principles,
because
when
I
try
to
shop
the
other
vendors
or
sorry
the
other
providers
they're,
like
you
know,
we
don't.
Let's
just
get
the
tools.
B
We
need
to
come
up
with
requirements
right
now
and
I
was
like
well,
then
the
vendors
will
just
ignore
us
and
say
that
the
industry
is
fractured
and
just
do
their
own
thing
like
we
just
need
to
come
up
with,
like
some
general
statements
of
you
know,
the
C
and
I
shouldn't
like
be
the
choke
point
where
you
try
to
lock
me-
and
you
know
like
things
like
that,
but
I
don't
know
thoughts
in
it
kind
of
Watson
in
in
your
purview
like
with
this
whole
guide
to
things,
would
we
put
the
limos
in
this
first,
one
which
is
kind
of
just
talking
about
the
journey,
or
what
do
we
put
it
into
the
next
one
which
is
going
to
try
to
just
be
like
very
granular?
C
E
To
say
that
their
implementation
is
cloud
native
and
then
we
use
that
phrase
all
the
time
and
you
know
there's
a
spectrum
of
where
it's
buzz.
It's
a
buzzword,
buzz
phrase
and
there's
just
there's
the
other
side
where
it
does
have
a
definition
and
that's
really
trying
to
tease
out
what
it
is
that
the
users,
so
the
service
providers
actually
want
the
benefits
from
it
and
then
come
get
the
definitions
from
those
benefits
and
then
say:
okay,
if
you
do
this,
then
your
cloud
native,
then
we
can
say
things
like:
okay
is
it.
E
You
know
one
of
them
is
microservices.
It
needs
to
be
something:
that's
a
developed
based
off
of
business
capability
for
each
service,
not
a
bunch
on
within
one
one
box
or
one
container
kind
of
thing,
and
we
know
that.
That's
that's
one
problem
with
you
know
putting
everything
all
in
one,
big
giant,
VM
and
then
saying
that
it's
cloud
made
it
which,
by
definition,
dilemmas
saying
nope,
it's
not!
E
A
C
A
A
A
B
If
you
look
at
like
what
Watson's
written
as
well
right
like
this
is
just
like
a
generic
which
is
good,
I'm,
literally
probably
just
gonna
link
directly
to
this
and
copy
and
paste
that
in
there-
and
you
know
just
reference
it,
but
I'm
Watson's
is
way
more.
You
know
just
like
how
do
you
actually
like
code
to
these
bold
principles
here,
like.
B
A
Well
aware,
the
intermediate
series
that
wants
and
is
actually
pushing
out
is
super
critical.
The
the
reason
I
like
the
cloud
native
definition
and
pulling
from
it
is
it
gives
moral
authority
to
the
kinds
of
things
that
Watson
is
doing.
Does
that
make
sense
yeah.
E
E
Api
is
immutable
infrastructure
and
micro
services
and
then
I'm
making
arguments
for
each
one
of
those
things
so
the
immutable
infrastructure.
Why
and
what
both?
So
you
have
the
benefits
and
from
grabbing
from
all
the
different
authorities
on
the
subject.
So
infrastructure
is
code
books,
all
other
different
types
of
mountain
Natives
descriptions
and
things
like
that.
Declarative
API
is
kubernetes
that
the
kubernetes
literature
has
lots
of
arguments
for
declarative.
Api
is
not
that
outside
of
whether
you're
doing
kubernetes
or
not
so.
A
A
E
E
We
don't
want
to
put
IPs
and
subnetting,
and
these
types
of
things
it's
too
specific,
you're,
saying
right
now,
you're
saying
loops,
coupling
I'm
saying
that's
closer
to
a
knot,
declarative
but
imperative
in
the
sense
of
how
like
here's,
where
there's
a
location,
how
you're
going
to
set
up
this
network
instead
of
what
it
is
you
want
from
the
network
and
it's
like
a
spectrum
and
I
have
my
other
thing:
that
of
seizing
out
of
the
other
papers
like
there's
a
spectrum
of
declarative
where
there's
Sara
at
the
very
highest
level.
E
I
want
the
corporate
intranet
and
there's
the
operators
who
are
composing
things
and
they're
they're,
taking
things
from
they're
taking
pieces
from
cns
Edward
made
that
exposed
somewhat
of
a
declarative,
API
and
they're
composing
them
into
a
higher
level,
one
that
Sara
can
understand
so,
but
the
CNF
makers
they're.
Obviously
doing
things
empirically
but
they're,
exposing
a
declarative
as
in
as
much
as
possible,
loosely
coupled
is
a
you
know
the
best
practice
for
all
the
way
through
on
all
things.
B
E
A
E
So
I
would
simplify
what
I
was
saying
if
I
understand
correctly,
as
like
a
position
on
saying
location
is
not
declarative.
That's
what
it
seems
like
to
me.
It
seems
like
that's
what
your
argument
is
and
that
taking
that
out
as
much
in
as
much
as
you
can
out
of
your
API
out
of
your
descriptions,
CI
everything,
the
bigger
ation,
you
will
make
it
so
that
you
can
have
and
then
now
you
have
all
the
arguments
for
a
declarative,
helps
where
you're
doing
self
building
systems
and
thing.
F
See
part
of
what
you're
gonna
end
up.
Having
is
like
it's
similar
to
the
European
safety
certification.
You
have
like
the
C
II
self
certify
for
the
general
class,
except
the
difference
is
that
when
they
self
certify
they
take
on
liability,
but
in
the
cognitive
that
you
self
certify
yourself
as
cloud
native
either
you
don't
take
on
the
liability
of
your
users,
complexity,
and
so
that's
one
of
the
risks
that
we
have
by
is
basically
how
vendors
or
they
rather
these
cloud
vendors.
F
Would
these
vendors
basically
self-standing
themselves
as
cloud
native
and
and
over
basically,
then,
by
looting,
the
meaning
just
to
sheer
sheer
numbers
and
so
like?
That's
where
they
think,
like
the
definition
become
very
very
important
and
pushing
people
towards
declarative,
loosely
coupled
environments
is
in
order
to
manage
that
complexity
like
that's,
and
and
in
order
to
get
your
system
to
to
render
your
your
infrastructure
based
upon
your
needs,
then
like
we,
we
need
to
push
these
type
of
ideas,
Ford.
F
The
alternative
is
ends
up
happening
is,
as
ed
mentioned,
you
either
end
up
with
a
vendor
selling
you
something
very
large
to
manage
all
those
complexities
because
of
how
they're,
coupled
or
you
end
up
with
somebody
having
to
program
all
these
things
together
or
configure
all
these
things
together
and
manage
things
that
have
been
a
highly
coupled
way.
I.
A
Mean
part
of
it
also
is
like
the
we
need
to
replicate
data
in
multiple
places.
If
you
have
to
go
and
specify,
I
can
send
that
information
for
your
CNS,
but
you
also
have
to
specify
it
for
the
infrastructure
runs
in
now.
You've
had
to
specify
two
things
in
to
play
the
same
thing
in
two
places
that
you
have
to
manually,
keep
in
sync
or
go
do
painful
things
to
keep
in
sync.
F
B
Anyways
I
put
this
into
the
white
paper
and
that's
the
one
that
like
a
lot
of
you,
so
this
is
the
one
that
Watson
Taylor
or
Frederic
myself
Daniel.
We
were
all
working
on
I'm
gonna
continue
to
build
out
these
guys
redo
a
lot
of
these
images
and
then
I'm
also
going
to
try
to
start
making
some
of
these
very
granular
diagrams
for
some
of
the
cloud
native
stuff,
but,
like
I,
said
it's
mainly
gonna
kind
of
be
a
book
report
for
ESPYs
on
you
know.
B
This
is
why
nfe
was
really
hard,
and
this
is
how
we
can
start
to.
You
know,
incorporate
cloud
native
principles
and,
in
my
opinion,
like
starting
to
use
those
even
in
the
vnf
space
right
I
mean
if
you
read
once
again:
where
was
the
talk
definition
containers
says
it
right.
There
exemplify
this
approach
it
and
say
that
you
have
to
be
containerized
to
be
cloud
native
right
like
if
I've
got
beams
that
are
you
know,
minimal,
toil
immutable
and
support.
B
You
know,
declarative
API
is
to
provision
them
then
I
mean
I
would
argue
that
you
could
even
have
bare
metal
stuff.
That
could
quote
unquote
be
potentially
cloud
native,
so
you
know
I'll
kind
of
continue
to
figure
out
where,
like
Thomas
and
gear,
gay
and
all
those
guys
stand
and
work
with
Daniel
on
the
tug
white
paper.
B
What
is
the
path
of
the
packet
actually
look
like
going
through
this
virtual
structure,
and
you
know
how
does
that
map
into
like,
because
I
think
if
they
understand
like
how
some
of
this
stuff
works
and
like
getting
stuff
in
and
out
like
you
know,
imagine
now,
instead
of
this
being
a
generic
VM
like
in
you
know
right
here.
This
is
like
multiple
pod
namespaces
right
and
what
it
means
to
actually
put
interfaces
in
these
pod,
namespaces
and
I.
B
Think
that
things
like
network
service
mesh
will
make
sense
to
them
at
least
the
networking
people
when
they
actually
understand
what
the
path
of
the
packet
means
and
what
it
takes
to
secure
this
traffic
and
ensure
that
you
know
just
you
know,
CCNA
level.
Basic
network
principles
are
being
maintained
even
as
we
move
into
this
space.
F
This
is
a
heads
up,
I
I,
acquired
a
domain
name
or
purchased
a
domain
name,
CNF,
dot,
dot
de
vie
and
one
of
the
things
that
I
intend
to
do
with
it
is
to
eventually
see
if
I
can
get
people
to
write
about
in
movie
specific
technologies.
If
they're
experts
in
so
we'll
see
about
getting,
maybe
someone
might
be
in
to
write
about
SRO
V
or
we
can
find
get
someone
like
like
magic
to
write
about
like
how
do
you?
F
How
do
you
perform
a
good
benchmark
or
so
on
and
just
have
like
a
wide
range
of
topics
that
people
look
and
write
about
these
individual
technologies
and
that
way
people
have
a
central
place
like
what
is
it
like?
What
does
it
mean
to
be
as
Harvey
I'm
feeling
it
like?
The
high
level
definition
is
no.
What
does
it
really
mean
to
be
that,
like
whatever?
What
are
the
details?
So
I
have
a
I,
have
a
landing
page
for
because
I
don't
think.
F
Msm
is
the
appropriate
place
to
store
all
of
this
type
of
low-level
details,
even
though
we
have
to
use
them
and
and
I
think,
but
I
think
that
we
can.
We
can
populate
this.
This
other
place
as
a
landing
has
a
landing
spot,
because
these
details
are
are
important
regardless.
It's
like
whether
they're
NSM
or
you
decide
to
use
multi
or
something
else
like
basically
still
works
like
a
sort
of
B,
regardless
yeah.
B
B
You
know,
bypass
the
colonel
that
just
I
have
to
completely
recent
like
redo
everything
and
make
it
agnostic,
cuz
I'm
not
allowed
to
do
stuff
and
put
it
out
there
that
I've
already
done
in
the
past,
which
that's
a
different
discussion,
but
I
basically
have
it,
for
you
know
the
first
just
but
is
virtualization
right:
para
virtualization,
full
virtualization
type
ones
versus
type
twos,
because
our
Podesta's
to
start
with,
like
we're,
BNF,
SAR
and
then
it'll
talk.
B
I've
got
like
some
pretty
granular
diagrams
on,
like
what
Numa
pinning
actually
means
and
like
what
you
know
it
means
actually
get.
You
know
your
memory
lanes
and
line
with
your
PCIe
lanes
and
stuff
same
thing
like
I'm,
the
VPP
stuff
and
the
OVA
stuff.
B
B
Just
because,
as
anybody
who's
seen
in
the
tug
black
channel,
there's
already
tons
and
tons
of
arguments
on
whether
or
not
we
should
just
be
like
this
purely
you
know,
purist
user
plane,
switching
versus
purist,
like
you
know,
well
maybe
it's
ok
to
go
in
with
kernel
interfaces,
sometimes
like
everybody's
got
an
opinion.
So
the
really
the
goal
of
this
paper
is
to
just
lay
out.
B
All
of
the
information
talk
about,
like
you
know,
like
I've,
got
a
very
long
section
on
what
V
host
user
is
right
and
then
it
would
be
nice
to
just
like.
After
that
say,
this
is
what
minmus
looks
like,
and
this
is
how
you
leverage
these
technologies
as
why
you
might
use
it
here
or
there,
and
these
are
the
pain
points
that
you're
going
to
encounter.
B
When
you
do
use
them,
but
anyways,
you
know
Frederick
II,
D
and
you
know
chat
with
Nicolai
and
stuff,
let's
kind
of
think
on
where
innocent
might
fit
into
some
of
these
papers
or
if
it's
gonna
fit
in
there.
You
know,
Nicolai
is
seems
way
more
of
the
opinion
that
it
just
needs
to
be
like
this
very
you
know
just
kind
of
implementation,
agnostic
approach,
I'll
be
honest,
though
the
vendors
deciding
that
they're
going
to
qualify
what
you
know
the
guiding
principle
should
be.
A
Does
that
make
sense,
because
I
prime
the
fundamental
sin
of
never
virtualization
has
been
the
obsession
with
V
switches,
which
tend
to
be
strongly
coupled
enforce
a
common
set
of
behavior
across
workloads
that
may
or
may
not
need
them,
which
then
radically
increases
the
complexity
of
because
V
switch,
you
cetera,
et
cetera
and
so
I
think
that's
the
really
fundamental
mental
shift
is
crucial
at
us.
I'm
just
have
us
be
one
way
to
get
to
B
wires,
yeah.
B
A
You
a
very
concrete
example:
the
V
switch
attitude
toward
C
and
I
is
why
it
is
that
everyone
is
fighting
over
who's
going
to
own
this
C
and
I,
because
it's
one
shiny
object
to
fight
over.
If
you
start
with
V
wires
as
your
fundamentals,
then
you
can
say:
look
I
actually
do
have
a
need
for
every
switch,
but
it's
something
that
you're
going
to
do
is
see
enough
to
do
these.
Switching
because
be
split.
The
beast,
which
is
no
longer
the
fundamental
piece.
A
The
really
fundamental
thing
that
it
does
change
this
crucial
is
the
way
these
switches
traditionally
have
worked.
Is
you
have
one
per
server
right,
and
so
they
have
a
distinguished
place
that
is
welded
to
the
underlying.
You
know
effectively
the
underlying
server
infrastructure
by
moving
them
to
being
CN
F's.
They
no
longer
have
a
distinguished
place.
You
could
pick
the
one
that
serves
you
and
they're
no
longer
welded
to
the
physical
effort
to
the
underlying
and
server
infrastructure,
nor
is
the
underlying
server
infrastructure
welded
to
them.
B
Sure,
like
I
said
I,
don't
know
like
in
my
OpenStack
world
I
do
Linux
bridges
for
slow
path
and
I
stick
VPP
in
a
container
and
I
run
it
the
way,
you're
saying
even
in
like
their
traditional
in
a
thesis
and
so
like
I,
don't
know
we
just
got
to
be
careful
like
I.
Don't
want
to
like
say
like
concrete.
Like
you
know,
these
switches
are
bad.
A
G
F
G
G
D
B
This
is
what
you're
really
trying
to
circle
around.
Is
that
to
form
a
connection.
I
shouldn't
necessarily
have
the
entire.
Like
you
know,
point-to-point
require
a
standalone,
subnet,
a
standalone
layer
to
domain,
and
you
know
all
this
other
stuff
that
you
typically
have
to
do
in
of
em.
Slash
hypervisor
world
right,
like
I,
can't
make
two
VMs
talk
unless
I
fully
define
this
subnet
and
I
fully
define
all
these
pores.
B
A
I
mean
my
main
line.
Quite
anything
else
right,
it's
gonna
say
well,
the
the
mentality
is
the
fact
that
you
do
have
to
do.
That
is
a
side
effect
of
thinking
that
the
virtual
switch
is
the
fundamental
thing
right.
So
it's
not
you're
absolutely
right
about
what
you
actually
care
about,
but
the
reason
you
want
you
find
yourself
in
this
situation
is
because
traditionally
a
multi-point
l2
domain
was
the
fundamental,
primitive
yeah
cool.
A
So
I
also
dropped
an
item
on
the
agenda
for
this
week
around
the
website.
Rework
stuff,
so
we've
actually
had
a
PR
pushed
a
very
kind
person
at
CN.
Cf
pushed
a
PR
for
reworking
the
look
and
feel
the
website.
If
you
have
time
it
would
be
good
to
take
a
look
just
I'd
like
to
socialize
it
fairly
broadly
before
we
put
it
in.
A
B
And
I
apologize
like
I
have
like
the
intro
paragraph
done.
I
haven't
like
worked
on
the
example
yet
and
I've
just
been
overwhelmed,
so
I'll
do
this
in
PR
soon
to
get
some
of
the
stuff
that
we
had
worked
on
like
a
couple
weeks
ago
on
the
whole
generic.
What
is
an
SM
thing?
Try
to
push
it,
but
this
is
definitely
way
way.
Way
cleaner,
looking
than
it
was
in
the
past.
A
A
A
B
A
A
A
What
is
it
the
bhop
coming
up
that
we're
sort
of
spiking
through
and
working
through,
and
so
what
are
those
things
and
where
do
we,
which
things
depend
on
which
so
we
can
sort
of
put
together
the
tree
of
what
has
to
happen
before
what
so
we
can
start
working
through
it
and
ensuring
this
to
the
NSM
meeting.
I
think
folks
sort
of
thought.
A
G
G
G
A
G
A
A
B
So
one
thing
I
would
suggest
you
ed
ISM.
You've
already
got
some
of
these
as
links,
but
if
there
are
things
like
safety
and
s
here,
right
which
has
dependencies
on
in
it
containers
and
etc
is
in
the
text.
Part
too,
as
these
you
know,
all
eventually
turned
into
URLs
is
to
make
sure
that,
in
let's
click
on
in
our
domain
here
right,
I
may.
B
Like
in
here,
too,
you
know
you
if
we're
gonna
have
this
tree
here,
then
in
like
the
actual
write-ups
there
should
be.
You
know
like
talk
about
what
it
means
to
actually
be
dependent
on
security
and
in
it
containers
and
then
talk
about
how
it
will
also
provide
dependencies
for
floating
in
our
domain,
etc.
Right,
like
I,
mean
the
picture,
gives
you
like
a
quick
like
okay,
I
can
trace
this,
and
you
know
once
this
is
not
not
I.
C
A
A
A
B
Absolutely
and
I
think
because
people
are
probably
only
going
to
click
on
the
ones
that
interest
them.
Having,
like
you
know
the
caveats
of,
did
you
consider
this
now
way,
people
you
know
once
these
specs
actually
are
completed
and
someone
goes
in
and
like
just
tries
to
grab
like
a
single
component
without
getting
everything
it
needs.
You
know,
it'll,
save
you
a
lot
of
those.
You
know
weird
emails
that
we
get
to
the
mailer
asking
like.
Why
couldn't
I
do
this
like?
Well,
did
you
do
this?
First.
E
C
E
A
But
that's
actually
a
really
good
point
and
the
thing
is,
you
know.
Obviously,
priorities
always
super
tricky
and
open
source
community,
because
you
have
much
of
different
people.
Can
collaborate
together
go
different
priorities
right
and
beautifully,
but
open
sources?
You
can
have
different
priorities
right.
Someone
can
say
you
know.
Sr
v6
is
the
most
important
thing
and
we
can
all
say
that's
great
fun
without
it
actually
causing
problems,
and
then
you
know,
but
even
within
that
communities
are
often
very
responsive
to
people.
A
E
B
One
thing
on
a
road
map
too,
though
right
ISM,
we're
still
kind
of
also
ironing
out
what
the
release
schedule
looks
like
and
obviously
that
will
have
a
huge
impact
on
what
a
road
map
it's,
assuming
that
you
actually
are
going
to
put
rough
timelines
on
road
maps
right
like
if
there's
only
going
to
be
like
an
annual
release,
which
that's
probably
not
what
we're
gonna
go
with.
Obviously
I'm.
That
might
mean
that,
like
there's
just
going
to
be
a
certain
number
of
features
that
I'll
come
at
once
and
then
you.
C
B
G
A
Yeah
I
know
this
is
actually
good
because
moving
in
this
direction,
it
makes
me
super
happy
too,
because
I
really
just
want
what
I
really
want
from
my
mixes.
I
want
and
lit
the
stuff
that
I
want
to
direct
into
you
know
into
T
into
our
excuse
in
memory
inside
device
inside
you
know,
see
the
house
and
then
I
want
them
to
things
out
from
T
excuse
and
then
put
whatever
in
cap.
It
was
I
asked
on
it
so
far.
A
B
Of
the
things
that
I've
been
excited
around
this
space,
too,
is
Intel,
is
working
to
standardize
these
drivers
and
when
I
talk
to
a
lot
of
different
like
FPGA
and
smart,
Nick,
vendors
and
stuff.
A
lot
of
them,
who
you
know
aren't
like
just
in
direct
competition
with
Intel,
are
adopting
some
of
these
drivers,
which
means
I,
won't
have
nearly
as
a
hard
time
right,
like
you
know,
Mellanox
versus
metronome
versus
Intel,
trying
to
get
different,
vnfs
driver.
B
B
Alright,
well
anything
else
on
the
technology
tree
wherever
I
put
it
I.
B
A
C
A
B
B
Look
for
me
all
right
cool!
Well,
let
you
said
you
know:
Edie
chat
with
Fredrik
Nicolai,
get
back
to
Daniel
and
I
kind
of,
unlike
what's
your
thoughts
on
like
how
much
or
how
or
which
white
paper
we
might
want
to
see
NSM
pop
in
and
what
type
of
presence
we
wanted
to
have
inset
white
papers.