►
From YouTube: Network Service Mesh WG Meeting - 2018-10-12
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
A
A
A
There
is
a
network
service,
mister
demos
that
is
going
to
talk
about
that.
We
also
want
to
to
prepare
and
simultaneously.
We
also
want
to
see
about
getting
some
type
of
podcast
and
the
blog
set
up,
and
we
also
have
a
submission
to
the
Fido
mini
summit
that
was
put
in
by
by
Tom
Herbert
and
so
an
announcement
very
important
announcement.
We
are
having
a
meeting
change
and
so
the
new
meeting
slot
will
be
every
every
week
on
Tuesday
from
8
to
9
and
9
a.m.
8
to
9
a.m.
A
Pacific
time,
and
so,
if
you
show
up
here
on
Friday
you'll
have
missed
the
you'll
miss
the
meeting
next
week
and
I
will
renounce
this
again.
Just
in
case
we
get
someone
new.
So
today
is
our
last
Friday
meeting
and
the
primary
driver
for
this
is
to
get
people
in
from
Europe.
So
a
lot
of
people
in
Europe
are
are
skipping
out
because
of
the
because
of
the
very
bad
time
for
them.
B
And
so
you
know
we
wanted
to
make
sure
we
got
broad
feedback
from
the
community
as
to
sort
of
what
this
demo
would
look
like,
because
it
takes
effort
to
put
together
a
demo
and
it's
good
to
pull
together
towards
them,
and
so
somebody
earlier
this
week
basically
said
we
should
write
down
what
we
think
we
want
to
do
for
the
demo,
and
so
I
took
a
first
schwag
at
drawing
some
pretty
pictures
for
it.
So
we
have
something
to
discuss.
So
don't
consider
this.
The
this
is
what
we're
doing
consider
it.
B
More
of
this
was
a
conversation
starter
on
the
kinds
of
things
that
we
would
hope
to
be
able
to
do
right.
So
the
at
the
high
level
we're
sort
of
looking
at
a
simple
chaining
demo
right
where
you've
got
some
client
pod,
that
is
going
to
consume
a
network
service
and
Becket's
cross
connected
remotely
to
some
network
service
endpoint
that
then
chains
locally
using
them
off
to
some
other
network
service.
B
In
point
now,
it's
important
to
note
I,
don't
suspect
we
will
have
network
service
wiring
for
this,
so
this
will
be
a
little
bit
manual
in
how
it
gets
put
together
in
terms
of
yo.
The
first
NSC
will
actually
be
trying
to
connect
to
the
second
NSC,
but
I
think
it
still
would
be
kind
of
a
cool
demo
at
a
high
level,
because
it
sort
of
shows
how
these
things
can
be
chained
together
by
network
service
mash,
and
this
sort
of
begs
the
question
a
little
bit.
B
What
do
we
use
for
the
network
service
endpoints
here
and
we've
got
a
couple
of
options
for
that?
One
of
them
is
I
know
that
the
the
vnf
CNF
guys
are
putting
together
some
chains
of
be
enough.
We
could
definitely
do
some
of
that
and
I
think
that
would
be
cool,
but
I
wanted
to
sort
of
also
point
out
another
option
that
we
would
have
in
slightly
too.
B
Which
would
be
something
that's
roughly
the
story.
We
tell
about
saris
via
secure
corporate
Internet
gateway
story,
where
you
know.
Basically,
you
get
a
client
pod
that
gets
connected
to
a
firewall
that
then
connects
to
a
VPN
gateway,
and
this
is
kind
of
a
cool
story.
People
seem
to
like
the
VPN
gateway
story,
and
so
that
was
one
idea
that
I
wanted
to
throw
out
there.
And
then
you
know
if
we
go
on
the
next
slide.
B
B
If
we
succeed
in
getting
auto
healing
going,
could
we
use
that
in
order
to
show
something
like
oh
I,
kill
off
one
of
the
replicas
and
I
see
that
it
comes
back
now?
Obviously
this
is
all
coming
in
layers
because
we
don't
really
know
how
much
we're
going
to
succeed
in
accomplishing
in
time
for
the
Q
con
demo.
B
But
my
experience
has
been
that
if
you
set
up
your
goals
and
layers,
then
you
eventually
get
to
some
some
piece
in
that
stack
or
you
don't
succeed,
and
then
you
fall
back
to
the
one
before
and
you
win.
So
we
do
other
approaches
have
other
interesting
ideas
or
comments
or
I
mean
we're
really
trying
to
figure
out
stuff.
We
can
come
together
as
a
community
to
pull
towards.
C
I
actually
saw
this
chime
in
and
reiterate
that
I
that
I
really
like
the
approach
I
like
the
layered
approach.
These
seem
like
reasonable
things
to
to
strive
towards
and
I
kind
of,
particularly
like
slide
two,
because
it
ties
directly
into
the
narrative
that
a
few
of
us
have
the
you
know.
I've
been
I've,
been
giving
it
various
events
in
that,
so
it
that
one
seems
particularly
relevant
just
because
it
ties
into
the
central
narrative
that
we've
been
telling
I
would.
B
D
You
have
them
both
both
running
together,
so
I
think
there's
two
conditions.
One
is
you
know,
ships
in
the
night,
NSM
plus
kubernetes,
working
independently,
which
I
think
is
a
useful
case.
Then
there's
also,
where
does
kubernetes
networking
intersect
with
NSM,
because
that's
pretty
more
useful
in
certain
just
my
point
of
view.
B
And
feel
free
to
try
and
tell
me
if
I'm
wrong,
we
got
a
lot
of
people.
The
community
would
like
to
pick
up
a
shovel
at
help
and
they're
trying
to
figure
out
exactly
which
shovel
to
pick
up
in
which
we're
really
good
dig
a
hole,
and
so
my
hope
is
that
by
figuring
out
for
the
demo,
we
can
break
it
up
into
pieces
that
various
people
can
work
on.
So
we
can
work
a
lot
up
together
as
a
community
in
parallel.
B
E
Yeah
yeah
a
couple
of
things
number
one:
does
the
direct
mammoths
wait
between
I
guess,
the
pods
and
the
nodes
on
the
right?
Does
that
somehow
I
mean
could
people
if
we're
seeing
like
imagining
cross
connects?
Are
we
maybe
doing
something
there
that
people
I
mean
if
our
job
is
to
sort
of
reinforce?
The
notion
of
cross
connects
to
connect
pods
and
a
network
service,
and
we
compromising
that
picture
that
people
come
away
with.
B
E
Yeah
I
guess
visually.
You
know
we
dropped
down
to
the
data
plane
to
you
know
cross
connect.
If
you
will
the
client
pod
on
the
left
and
node
one
and
the
NSC
pod
on
the
right
in
no
is
that
is
the
mem
F
sort
of
consistent
with
this
notion
of
you
know,
dropping
down
into
the
data
plane.
Or
did
we
just
claim
that
the
mem,
if
between
the
two
NSCs
in
on
the
right
and
no
is
in
fact
you
know
a
cross
connect?
If
you
will.
B
B
B
B
F
I
could
I
mean
I,
see
it
from
a
little
bit
different
angle,
because
one
of
the
kind
of
a
key
point
at
least
III
saw
on
the
Signet
working
during
the
segment
and
a
signal
networking
meeting
is
that
I
mean
we
are
talking
out
to
the
CNI.
What
my
concern
is
that,
if
we
somehow
try
to
show
an
SM
and
the
CNI
together,
it
might
send
people
a
wrong
message
that
we're
trying
to
do
something
with
the
existing
CNI
I
think
I
mean,
at
least
in
my
opinion.
F
B
G
Think
it
is
one
of
them
we're
looking
at
doing
it
in
two
different
ways.
Now
I
think
we
have
to
direct
mammoth
connections
similar
to
what
you're
showing
on
no
no
to
here,
but
we're
also
we're
also
looking
into
doing
this
kind
of
snake
testing,
where
we
always
switch
a
context
switch
through
VPP
between
chains,
but
that's
mainly
so
we
can
compare
memory
f2v
host
it's
in
such
those
direct
connections,
they're
good,
but
they're
there.
It's
kind
of
cheating
when
comparing
to
it
to
be
used.
B
G
B
G
A
B
A
B
H
One
so
I
mean
I
still
want
to
see
if
I
can
actually
just
take,
I
mean
I'm
just
want
to
do
something
simple,
initially
partially
it's
to
educate
myself,
because
you
know
my
understanding
of
kubernetes
isn't
anywhere
near
as
profound
this
others
in
this
group,
and
so
I
want
to
keep
it
simple,
just
to
make
it
easier
to
set
out
and
something
that
that
people
can
leverage
or
maybe
I,
don't
know,
I
hope
I
can
get
even
that
done.
But
that's
my
goal
is
to
just
do
you
really.
A
Yeah
something
I
can
do
is
I
can
set
up
the
initial
deployment
and
pod
structures
and
set
up
the
initial
entry
points
so
to
make
it
easy
for
people
to
start
working
on
on
those
independently,
so
basically
come
up
with
half
on
two
nodes
set
it
up
so
that
one
pod
lands
on
window.
The
other
two
pods
land
on
the
other
node
entry
points
are
are
clear,
so
you
know
basically
set
up
some
structure
for
people
to
start
implementing
things
and
that
will
lead
into
the
next
part,
which
is
how
do
we
land?
A
How
do
we
land
VPP
on
that
particular
on
a
peculiar
system?
So
we
can
start
setting.
We
can
start
working
towards
getting
this
set
up
in
the
in
the
CI
system
as
well,
which
there's
already
been
a
lot
of
work
towards
that.
So
just
be
a
matter
of
of
leveraging.
Some
of
that
work.
That's
been
done
by
the
other
members
of
the
community.
F
We
PP
VPP
will
come
will
come
with
as
within
the
dead
data
plane.
So
it's
bundled
so.
Basically
all
you
need
is
just
to
start
a
poor
data
playing
port
and
a
VPP
will
start
as
a
sidecar
container
and
serves
pretty
much
all
the
requests
from
the
local
NSM
on
the
same
node.
So
it
did.
The
only
thing
is
that
I
mean
your
hosts
must
support
huge
pages
and
the
couplet
should
be
able
to
discover
them,
because
that's
the
requirement
is.
B
A
No,
that's
that's
perfect,
so
yeah
well,
we'll
make
you
so
what
makes
is
that
then,
but
now
I'll
start
setting
up
the
of
the
proper
deployments
and
kubernetes
and
so
on
in
order
to
in
order
to
make
it
easier
for
people
to
join
in,
because
I
I
get
the
feeling
a
lot
of
people.
It's
like
even
just
landing.
Your
pod
securities
can
be,
can
be
fun
when
you
have
experience.
E
B
Would
be
lovely
to
do
is
just
to
be
able
to
let
people
visualize
the
topology
of
network
services.
You
know
the
connections
between
network
services
awesome
and
the
other
thing
that
was
running
through
my
head
is:
if
we
get
the
auto
healing
working,
which
is
just
definitely
a
stretch
at
this
point,
but
if
we
got
it
working,
if
you,
if
you
would
let
people
kill
off
network
service
endpoints
in
the
chain
sort
of
video
game
style,
so
they
could
see
the
auto
billing
working.
That
would
be
unbelievably
epic.
B
A
If
you
want
to
go
with
an
easy
integration,
there's
a
there's,
a
gopher
batch
game
and
they
backs,
and
the
kubernetes
team
actually
has
a
physical
arcade
game
where
you
bash.
The
Gophers
and
a
commitment
kills
containers
that
represent
these
gopher,
though
we
could,
if
we
reached
out
to
them
and
so
show
that
we
had
this
amazing
demo,
that
that
did
that
maybe
they'd
be
kind
enough
to
lend
us
some
hard
work
release
T.
This
is
the
software
to
run.
B
A
A
A
A
Where
you
can
see
the
see
the
result,
please
pardon
the
the
theme
just
picked
a
random
team
that
sort
of
looked
half
good,
but
there's
some
problems
with
the
structure
of
the
theme
that
that
I'm
not
particularly
happy
with
that
I
leave
to
either
change
or
replace
later
on,
especially
around
the
wording.
So.
A
The
thing
was
written
for
by
making
your
text
be
more
sparse
and
longer
and
increasing
increasing
margin
size.
So
you
looks
like
you
wrote
a
lot
more
than
you
really
did,
which
makes
the
which,
which
gives
us
the
wall
of
text
effect
when
you
read
the
introduction,
so
I
need
to
make
some
changes
on
that,
but
the
thing
that
I
would
love
some
some
help
on
is
in
two
areas.
A
So
one
is
the
there's
some
new
sections
that
were
added
in
on
the
bottom,
which
are
the
parts
that
that
relate
to
the
C
and
F
itself.
So
the
first
question
is:
are:
does
this
look
good
as
it
looks
efficient,
read
them
comment
on
them.
Please,
if
you've
seen,
if
you
think
there
should
be
any
changes,
a
pull
request
is
is
more
than
more
than
welcome
and
we
can
start
working
on
this
on
this
documentation
to
get
it
up
speed.
A
But
it's
something
that
would
be
really
really
helpful.
If
someone
has
the
time
to
do
so,
would
be
to
read
through
each
of
those
and
modify
them,
and
so
that
they're,
using
technologies
and
databases,
and
so
on
that
are
much
more
relevant
to
the
CMS
community.
So,
for
example,
I
doubt
that
anyone
in
the
CMS
community
is
going
to
be
making
a
ruby
based,
CNF,
more
likely
will
CC
go,
maybe
some
rests
or
or
so
on,
and
so
these
things
need
to
be
refactored
to
be
more
relevant
to
the
to
the
CNF
community.
A
And
the
third
thing
is
that
there
may
be
sections
or
things
that
I
did
not
talk
about
additional
additional
rules,
and
and
so
on,
that
that
we
should
look
at.
And
so,
if
there's
something
that
is,
that
is
missing
that
you
strongly
think
should
should
be
a
part
of
it.
That's
good.
Let's
start
the
conversation
on
on
that,
so
we
can
talk
about
like.
Is
it
appropriate?
What
should
which?
What
message
should
we
put
forward
or
so
on?
A
A
A
A
F
Right
I
pushed
PR
which
introduces
the
VPP
data
VPP
based
data
plane.
At
this
point
it
has
a
fairly
limited
functionality
in
a
sense
that
it
interconnects
just
local
ports.
So
along
the
dot
PR,
there
was
some
changes
done
to
the
data
plane
API,
but
they
were
done
in
agreement
with
add
so
it
won't.
It
doesn't
contradict
to
what
ad
is
working
like
on
the
global
data
plane
API.
So
it's
it's
safe
to
use
like
if
you
decide
to
develop
anything
in
that
area,.
F
Yeah
thanks
and
as
I
mentioned
earlier,
the
model
is
the
following.
So
in
the
port
data
play
input,
it's
kind
of
a
controller.
There
are
two
containers.
One
container
runs
a
latest
cpp
code
with
a
very
default
configuration,
so
there
is
not
too
many
changes
and
then
there
is
another
container
that
runs
the
agent
so
agent,
it's
some
sort
of
interface
between
the
NSM
and
VPP
it
it.
It
runs
the
jar
PC
server,
which
is
which
is
serving
that
API
I
mentioned
earlier.
F
It's
working
perfectly
in
my
in
my
test
environment,
but
in
CI
it
won't
work
right
away
because,
as
I
said,
it
requires
the
huge
pages
configuration
without
huge
pages.
Vpp
will
not
work
so
once
it's
done
hopefully
soon
on
the
packet
packet
dotnet,
then
we'll
be
able
to
do
the
CI
and
test
them
in
this
year.
I
E
B
A
B
Which,
I
think
is
good
as
much
better
at
parallel
jobs,
basically
fanning
out
jobs,
and
one
of
the
things
I
think
we're
going
to
find.
Is
that?
Because
the
cross
lot
of
CI
stuff
scales
across
a
bunch
of
public
clouds
as
time
goes
on,
we'll
get
CI?
You
know
on
not
only
just
some
packet
on
that,
but
we'll
also
get
it
on
AWS
and
GCE
Azur,
and
all
these
other
places
and
so
being
able
to
easily
parallelized
I
think
Circle
C
is
probably
going
to
be
better
for
it.
A
C
B
B
F
F
A
A
Thank
you,
and
it
is
this,
also
be
something
good
that
we
can
document
in
the
like.
When
once
we
once,
we
get
better
documentation
for
for
data
planes
as
they
start
to,
as
we
start
to
build
that
out.
This
is
something
that
we
should
probably
make
sure
that
we
that
we
add
in
I'm
not
sure
what
the
right
way
to
track.
That
is,
though,
considering
we,
we
don't
have
a
place
to
landed
yet
maybe
shoot
for
it
anyways
other
than
that.
A
Great,
thank
you
very
much.
Andre,
let's
see
for
the
action
items,
I
I
haven't
updated
the
action
or
the
the
agenda
board
this
week,
I'm
gonna
jump
back
into
grooming
and
maintaining
the
the
project
board
against
it's.
It's.
It's
proved
valuable
in
the
past.
So
when
action
item
for
me
is
going
to
be
getting
the
edge
of
the
board
back
back
on
track
and
we'll
start
using
it
again
on
starting
Tuesday
anyways
before
we
before
we
finish
up,
is
there
anything
else
that
anyone
like
to
discuss
before
we
before
we
yield
back
time.
G
G
Well,
it's
quite
quick
I!
Guess
it's
we're
working
on
getting
the
single
chain
with
multiple
Network
functions
up
and
running
in
three
different
configurations.
So
we
have
the
vnf
that
that
connecting
and
context,
which
is
between
VPP
and
the
network
function
for
each
each
network
function
in
a
chain
and
for
CNS.
G
We
have
both
both
the
context,
switch
that
we
discussed
a
little
while
ago,
and
we
have
that
directly
connected
MMI
F
interfaces
and
and
I
think
right
now
we're
just
finishing
up
some
some
modifications
to
the
scripts
to
fully
support
them
with
with
the
configuration
we
need,
then
we're
going
to
run
some
benchmarks
and
then
we've
just
started
doing
some
templating.
Okay,
getting
the
templating
started
to
actually
make
this
a
little
easier
to
run
for
anyone
without
having
to
go
through
all
of
our
quickly
put
together
bash
grits.
F
F
Basically
you're
using
Ben
API
to
talk
to
the
VP
of
EDP
right.
Yes,
yes,
would
it
be
possible
to
share
those
scripts,
because
basically,
the
sequence
or
in
the
Google
code
would
be
very,
very
similar.
So
instead
of
you
know,
scratching
my
head
and
trying
to
figure
out
how
it
should
be
done,
I
mean
I
could
probably
use
that
as
a.
I
I
Everything
to
send
this
CNCs
C&S
repo,
so
we
have
a
confess
of
it-
is
under
a
comparisons.
Folder,
there's
three
main
subfolders
I,
don't
know
if
we've
renamed
my
'kathy,
the
new
folder,
but
it's
been
seen
at
the
edge
brooklet
and
that's
where
the
most
recent
there's
actually
be
comparison.
Sets
that
we've
done
it
better,
but
all
of
the
best
rips
and
everything
else
you
can
see
some
other.
E
I
Levels
that
we're
adding
thanks
dude,
but
you
keep
you
on
there
that
scene.
It
has
third
good
at
the
bottom,
that's
going
to
be
the
most
relevant
stuff,
including
the
bbb-be
switch.
So
that's
the
host
level
configuration
and
which
will
have
a
lot
of
information
on
the
mm.
I
have
another
set
up
at
the
house
level
and
then
inside
of
the
V
edges,
which
is
maybe
maybe
the
wrong
name.
But
it's
a
network
function
for.
I
G
A
Okay,
so
again
before
I
close,
it
out
just
a
reminder
again
show
up
next
Tuesday
Matt,
not
next
Friday
same
time,
different
just
every
day
of
the
week,
so
so
the
next
meeting
then
we'll
be
on
the
16th
and
I
will
contact
Prem
to
get
that
all
changed
upon
the
calendar
and
add
one
thing
that
we
should
do
as
well
is
make
sure
that
there's
no
issues
with
zoom
to
zoom
has
a
specific
time
schedule
that
the
meeting
comes
up.
I
will
I
will
go.