►
From YouTube: CNCF Network Service Mesh Meeting - 2019-09-10
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
We
have
enough
people
here
so
yeah,
let's
get
started
so
welcome
to
the
next
network
service
message
meeting.
So
we
have
this,
but
every
week
we
have
this
particular
meeting.
We
have
two
others
which
are
currently
on
hey
Dizz,
which
is
the
document
use
case
meeting.
We
may
reconvene
them
as
as
needed.
We
have
the
CNCs
Telecom
user
group,
which
we
join
in
on
which
occurs
every
first
Monday
at
8
a.m.
and
every
third
one.
They
ask
for
a.m.
Pacific
and
of
course,
this
call,
which
occurs
every
two
Li
at
8
a.m.
A
so
we
have
some
major
events
coming
up.
We
have
ons
Europe,
which
is
occurring
in
Antwerp
with
for
accepted
talks.
We
have
open
source
summit
in
Leon
with
one
except
to
talk
by
Ivana
and
Radha
sauce.
We
have
cube
Khan
and
cognitive
cond
in
North
America
in
San
Diego,
and
so
we
have
announced
network
service
mesh
con
as
a
day.
0
event,
please,
please
register
the
there's
limited
space
and
there's
also
a
call
for
proposal.
A
C
D
C
A
B
B
C
B
A
A
E
Day,
thank
you
awesome.
So
this
week,
I
was
able
to
post
about
and
I'll
start
backwards,
the
OVS
orbit.
Podcast
everything
is
clickable.
So
if
you
have
a
Twitter
account,
please
feel
free
to
click
through
on
these
meeting
notes
and
retweet,
like
all
that
good
stuff
to
promote
the
OVS
Twitter
podcast,
that's
been
published,
there's
also
an
announcement,
a
reminder
of
the
network
service
mesh
in
the
CNF
testbed
session
at
open
networking
summits.
This
month,
I've
also
posted
for
a
call
for
CFPs
for
network
service
mesh
con
@q
con
north
america.
E
There
was
also
a
posts
that
I
retweeted
about
the
CAF
webinar
intro
to
network
service
mesh
that
will
be
on
October,
2nd
details
on
how
to
RSVP
are
available
in
that
tweet.
That's
linked
in
the
meeting
notes
and
I
also
created
a
thread
for
all
of
the
Q
Khan
sessions
that
mentioned
network
service
mesh
that
one
got
a
lot
of
traction:
I
tagged
10
people
to
that
one
and
then
didn't
really
realize
that
when
I
created
comments
with
each
session
listed
than
those
10,
people
would
be
tagged
again.
E
So
that
was
a
learning
experience,
but
it
also
got
a
lot
of
eyes
on
network
service
mash.
So
if
you're
curious
as
to
which
sessions
will
be
at
Keuka
North
America
in
November,
that
tweet
is
one
place,
you
can
find
those
things
and
it's
also
a
reference
point.
If
we
want
to
copy/paste
the
URLs
dates
and
times
into
these
meeting
notes,
we
can
do
so.
It's
all
together.
There
and
I
also
posted
a
reminder
of
today's
working
group
session.
There
was
a
really
good
comment
from
an
account
that
said:
look
ins
and
network
service
mesh.
E
D
D
F
C
F
Yeah
I
think
it's
just
to
add:
I
guess
we're
doing
a
few
workarounds
right
now.
I
guess
it.
In
particular,
the
kernel
driver
we're
loading
from
the
host
and
just
pretty
much
having
a
privileged
container,
which
can
then
access
it
and
do
using
that
DB
DK
plugin
for
VPP
were
able
to
attach
VPP
to
the
interface
and
and
and
do
whatever
we
need
to
do
one.
There.
F
An
alternative
it's
walking,
yeah
and
I
think
we
discussed
that
briefly
today
as
well,
that
we
probably
need
to
look
into
some
better
way
of
doing
it
and
I
guess
there
are
quite
a
few
options:
multiple
at
least
one
of
them.
Where
we
can
we
can.
We
can
do
this
in
a
bit
of
a
prettier
way
than
we're
doing
right
now.
I
think
my
biggest
concern
is
just
we
need
to
have
it
ready
for
ons
as
well.
I
mean.
C
C
The
hardware
nixed
off
I'll
probably
go
and
revisit
that
spec
here
and
and
pretty
it
up
with
a
little
bit
more
recent
stuff
because
that'll
handle
not
only.
How
do
you
get
the
NIC
in
there,
but
how
do
you
have
something
that
will
call
properly
in
an
orderly
way?
The
right
API
is
to
set
up
the
particular
VLANs
and
whatnot
correctly
for
you,
so
you
actually
get
the
network
service
that
you
went
there
yeah.
G
C
D
At
least
for
me
this
this,
this
step
is
valuable
because
we
kind
of
stumbled
in
some
unexpected
problems.
Maybe
I
ever
think
about
setting
the
PDK.
Do
you
need
privileged
container?
How
do
you
isolate
a
specific
device
because
we
currently
are
not
really
able
to
do
that?
It
just
Maps
whatever
is
out
there.
So
it's
it's
a
bit
of
the
beginning
of
the
learning
curve,
I
think
at
least
for
me,
so
yeah
I
mean
whatever
we
have
in
the
higher-level
specs,
surely
be
able
to
take
advantage
of
this
work.
In
any
case,
that's
my
point.
B
B
All
right,
I'm,
yeah
so
and
there's
also
one
in
the
repo
but
I
need
to
get
that
one
updated
with
what
we
did
here.
B
It's
a
little
bit
off
anyways,
so
most
of
the
as
you
can
see,
most
of
the
use
cases
that
were
focused
on
are
going
to
be
around
innocent
for
the
next
couple
of
months,
and
what
Michael
and
Nicolai
were
just
talking
about
is
that
second,
one
in
September
of
the
innocent
physical
net
gateway
that
we're
planning
on
using
as
the
example
that
we
talked
about
this
and
a
tutorial
luxury
type
thing,
as
well
as
the
talk
that
Nick,
client
and
I
are
doing.
So.
B
That's
the
I
guess
the
big
one
that
we're
trying
to
have
ready
for
ons
and
we're
also
in
the
middle
of
refactoring.
A
lot
of
different
things
in
the
CNF
test
bed,
including,
like
what's
listed,
is
about
the
use
cases
we're
also
working
on
the
provisioning
of
machines
and
and
clusters,
as
we're
finishing
some
work
on
that
we're
also
doing
in
the
scene,
50
I
project
and
switching
over
will
B's
and
cubes
break.
B
But
this
part
is,
something
would
probably
will
see
for
own
us
moving
towards
on,
at
least
on
the
kubernetes
side,
splitting
up
the
use
cases
into
reusable
components
and
Michael
Denver,
and
a
few
of
us
have
been
working
on
this
and
it's
right
now
in
a
different
branch,
but
ideally
we're
going
to
at
least
have
the
NSM
packet
filter
use
case
ready
by
OH&S.
In
this
new
set
up,
and
probably
if
timing
is
right,
then
we
can
also
get
the
this
physical
NIC
gateway
use
case
that
we're
also
working
on
depending
on
where
things
are.
B
Think
by
the
time
we
hit
November
we'll
be
able
to
focus
on
it
and
other
people
and
if
Nokia's
not
available,
and
that
hybrid
kubernetes
up
in
psyches
case
is
the
one
that
we
were
trying
to
get
accepted
with
nikolai
yang
you
and
a
bunch
of
other
folks,
and
ideally,
we
can
still
target
getting
that
up.
If
we
can
get
some
OpenStack
help
on
a
some
of
the
VP
p
GP
tunnel
issues
that
we're
running
into
that'd
be
one
of
the
main
things,
and
that
could
be
a
talk.
B
They
have
a
container
experience
kit
that
Michaels
already
tested
and
on
packet,
so
we're
hoping
to
pull
some
of
that
stuff
in
as
well.
The
last
thing,
if
folks
are
interested
in
getting
involved,
then
let
me
know
put
it
pretty
far
out
for
January
and
kind
of
thinking
about
Mobile
World
Congress
in
Barcelona,
which
is
in
February
next
year,
would
be
a
GSM
5g
type
of
use
case
and
ideally
within
the
sim.
B
A
B
H
B
A
If
it's
that's
fantastic,
so
this
we
did
have
a
very
minor
present
at
the
last
at
the
last
rule,
Mobile
World
Congress.
So
basically
at
the
cisco
booth
they
had
I
had
a
micro
booth
there
with
some
people
talking
about
upcoming
things
that
cisco
has
been
involved
with,
but
giving
it
to
something
where
we
can
actually
have
some
something
that's
working
there
I
think
would
be
absolutely
fantastic,
so
I'd
love
to
I'd
love
to
make
that
happen.
A
A
C
The
SDK
evolution
work
finally
landed
last
week.
This
is
not
only
stuff
that
is
going
to
make
it
easier
to
write
fragments
of
your
services
of
your
and
network
service
endpoint,
but
it
also
set
up
in
a
way
that
gives
you
internal
tracing
so
that
you
can
sort
of
see
the
progression
through
the
mini
pieces
as
well,
which
can
be
very
helpful
in
figuring
out.
What's
going
on,
particularly,
you
have
tiny
issues
on
requests
and
also
is
set
up
in
such
a
way
that
any
logs
inside
your
SDK
fragments
show
up
in
the
spans.
C
So
it
should
make
things
quite
a
bit
easier
to
sort
of
run
through
the
SDK.
Now
there
is
a
need
there
for
better
Docs
and
then
there's
also
a
matter
that
we
need
to
discuss
either
now
or
we
can
discuss,
approve
it
down
around
multi-goal
multigo
modules
in
the
main
repo.
What
are
the
problems
for
having
with
the
SDK
that
I
think
a
number
of
people
have
hit?
C
Is
the
SDK,
because
it's
in
the
main
repo
tolls,
a
bunch
of
requirements,
you
don't
actually
need
via
go
modules,
which
sort
of
makes
things
harder
than
they
have
to
be,
and
so
we're
sort
of
looking
at
solutions
to
them.
The
two
that
have
come
to
mind
is
it's
possible
to
have
multiple
go
modules
in
the
same
repo
or
it's
possible.
We
could
break
the
SDK
into
its
own
repo.
A
Yeah
I
mean
my
my
preference
would
be
to
to
eventually
to
do
one
of
two
things
that
absolute
best
case
scenario
would
be
to
convince
the
other
go
team
to
do
some
analysis
of
what
they
we
actually
need.
So
in
other
words
downloaded
and
do
like
a
pre
compile
step,
but
I,
don't
think
we're
gonna
get
that
anytime
soon.
So
I
think
that
having
a
it's,
the
problem
is
not
the
size
of
it,
even
though
that
will
be
the
problem
for
some.
The
biggest
problem
we're
gonna
run
into.
A
Is
that
when
you
pull
in
something
that
has
a
very
large
number
of
dependencies,
then
you're
now
creating
a
and
a
burden
on
the
integration
of
that
library,
with
others
and
you're,
limiting
the
scope
of
what
others
can
upgrade
to
potentially
unnecessarily
considering
that's
most
of
the
dependencies
that
are
not
being
used.
So
the
biggest
one
that
I
can
think
of
from
the
SDK
side
is
the
kubernetes
dependency.
So
I'm,
not
a
hundred
percent
positive.
Yet,
but
I.
Don't
think
that
we
have.
A
A
It's
not
very
go
mod
friendly,
so
you
have
to
put
a
list
of
like
15
different,
replace
to
actually
scope
at
exact
versions
and
once
you've
done
that,
then
it'll
it'll
work,
but
it
basically
turns
into
a
magic
incantation
that
feels
fragile
to
me.
So
I
think
that
these
I
think
this
will
go
away
if
we
were
to
split
it
off.
So
those
are
my
those
are
my
primary
concerns
at
this
point.
Yeah.
C
D
I
mean
I:
do
you
know
that
we
have
a
lot
of
projects
already
in
the
same
so,
for
example,
our
wonderful-tasting
written
by
andre,
you
know
I
mean
it
I
think
that
it
should
live
its
own
life
in
a
separate
repo.
We
have
also
AWS
and
various
SDKs
for
the
public
clouds
there,
which,
which
are
just
inherently
there,
because
we
have
scripts
and
whatever
whatever
is
needed,
to
do
our
CI
and,
as
you
said
then,
when,
when
someone
he
wants
to
utilize
our
SDK,
they
essentially
are
depending
on
AWS,
whatever,
which
I.
C
Thinking
it
been
I'm
very
curious
in
the
short
term,
let's
start
trying
to
move
some
of
these
some
towards
go
multi
modules,
because
there
are
some
complications
for
breaking
things
in
the
separate
repos.
This
particular
moment
in
time,
because
we're
doing
some
things
with
API
refactoring
that
make
it
a
little
more
complicated.
So
particularly
around
like
the
multi
data
playing
supporting
the
kernels
and
moving.
E
C
Strings
instead
of
enums,
but
if
we
get
to
multi
Bill
Maher
roles,
then
once
the
API
settles
down
a
little
bit
for
V
pros
or
that
it
becomes
relatively
easy
to
break
these
things
into
separate,
repos
and
I.
Think
it
makes
a
lot
of
sense,
plus
the
the
go
module
separate.
Go
modules
will
force
us
to
think
about
the
the
interdependencies
between
pieces
of
things
like
so,
for
example,
right
now,
if
we
were
to
break
the
SDK
into
its
own
repo.
C
D
A
There's
one
experiment
I'd
like
to
try,
which
is
having
a
small
kubernetes
repo
that
we
import.
It's
not
really
through
identity
is
what
it
is,
is
all
the
replaces
stuck
into
a
go
mod
and
that's
all
it
is
that
way
we
can.
If
we
try
to
include
it
in
will,
will
that
force
the
the
go
modules
to
properly
load
properly,
because
if
it
can't,
if
it
does
this,
you
know
it
this
whole.
A
C
C
C
C
C
C
C
So
we
appreciate
them.
Ok,
so
we
do
have
a
discussion.
That's
still
ongoing
about
movie
moving
some
of
the
remote
mechanism,
Stoffer
on
vni
selection,
into
the
innocent
order
from
the
network
service
manager.
I,
think
everybody
agrees.
It's
kind
of
a
good
idea.
It's
just
a
matter
of
sort
of
working
out
exactly
what
we
want
to
do
and
when
and
how
and
there's
some
refactoring
going
on
in
the
data
plane
that
hopefully
will
make
that
simpler.
So
do
we
have
rata
slop?
C
J
C
J
J
C
Some
of
the
initial
confusion
was
VP
is
able
to
collect
metrics
at
a
speed
that
almost
no
system
is
able
to
consume
them,
yeah
what
they
thought
we
were
asking,
which
was
every
time
you
update
your
metrics.
Would
you
send
us
a
RPC
message,
like
sometimes
people
ask
for
things
you
like
I?
Don't
think
you
really
want
that
because
they
collect
metrics
so
fast
in
so
many
metrics
and
we
sort
of
said
hey
how
about
just
every.
C
So
often
you
give
us
a
summary
that
made
a
lot
more
sense
to
them
so
because
they
can
literally,
they
can
throw
off.
Unbelievable
they're
also
meant
so
much
metric
that
they're
actually
innovations
in
DBP
to
make
it
possible
to
make
them
more
consumable
that
way.
So,
rather
than
providing
metric
events,
they
actually
will
allow
you
to
share
memory
where
they
will
update
metrics,
because
it's
the
only
way
you
can
possibly
keep
up,
but
obviously
that's
not
what
we're
gonna
want
to
do
here.
We're
just
gonna
bet
some
cheer
PC
messages.
C
I
C
C
15
69
so
essentially
doing
a
similar
kind
of
thing
to
refactor
data
plane
in
the
hope
of
a
much
simpler
to
work
with,
and
also
hopefully
make
it
easier
for
various
people
to
build
their
own
video
plane
with
or
without
the
agent,
because
I
expect
I
mean
you
guys
have
done
a
great
job
with
the
kernel
40
playing
that's
a
great
stuff
forward,
but
I
suspect,
particularly
as
we
start
looking
at
hardware.
Next
support
where
the
hardware
names
may
have
special
features.
A
C
A
C
A
I
C
There
were
a
couple
things
that
I
came
across
I
wanted
to
discuss
past
sort
of
in
progress
things.
What
is
we
just
had
someone
to
open
an
issue?
Saying,
hey
I
went
to
go,
try
and
get
the
latest
of
this
thing.
You
know
we
don't
and
you
don't
have
it
yet
and
what
I
realized
when
I
went
to
go.
Look
at
that
is
in
our
production
repos.
We
have
a
tag
for
the
branch
like
a
tag
master.
D
C
C
D
C
A
C
Because
we
want
to
be
able
to
get
whatever
is
most
recent.
The
master
latest
shouldn't
point
to
that
of
master.
That
way
lies
behind
this
yeah,
so
okay,
so
the
question
is:
who
wants
to
pick
up
getting
the
0.1
tags
pushed
and
the
latest
tax
push
20,
but
the
0.1
for
the
stuff
that,
from
the
0.1
release.
G
D
G
D
C
C
C
D
C
C
C
C
D
D
C
G
A
That's
good
idea
and
part
of
it
is
like
who's.
Jeff
is
an
example,
so
Jeffrey
Jeffrey
was
out
for
some
other
things
that
he
needed
to
to
take
care
of,
and
so
he's
back
now.
So
he
may
have
intentions
of
doing
some
more
things.
So
I,
don't
I'm,
not
comfortable,
just
outright
canceling
I'm
at
this
point,
without
having
a
good
discussion
with
them,
but
yeah.
We
definitely
two
to
reach
out
and
then
I.
Didn't
it's
okay
as
well
like
to
to
put
them
on
on
hiatus.
A
But
if
they're
gonna
be
on
hiatus
for
longer
than
some
period
of
time,
then
we
should
probably
remove
them
from
the
calendar,
and
that
doesn't
mean
that
they're
gone
forever.
It
just
means
because
we
can
always
start
them
up
again
as
needed,
but
yeah,
let's,
let's
reach
out
to
use
Jeffrey
on
the
call
I'm
not
seeing
them
on
the
cult.
So,
let's
reach
out
to
Jeffrey
and
let's
reach
out
to
to
rocky
and
she's,
praying
on
the
call
yeah
yeah,
let's
reach
out
to
them
and
ask.