►
From YouTube: Network Service Mesh WG - 2018-06-08
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
Forgive
everyone,
maybe
five
more
minutes
or
soda
to
settle.
If
everyone
wants
to
go
ahead
and
add
their
there,
we
go.
Look
at
that
John's
adding
his
name
in
you
want
to
add
your
attendance
on
the
the
Google
Doc,
which
I
can
post
into
the
chat
here
just
a
sec.
Let
me
grab
the
girl
just
to
make
it
easier:
Chat,
Chat,
Chat,
Chat,
Chat,.
A
C
D
A
C
B
I
think
we
should
get
started
mm-hmm,
so
I
think
we
will
so
if
you're
not
looking
at
the
the
Google
Doc
with
the
agenda
and
everything
I
posted
it
into
the
chat
for
the
meeting.
It's
also
directly
on
the
network
service,
mesh
repo
web
site,
github
page
as
well
so
I
think
we
usually
like
to
start
with,
as
ed
likes
to
surreptitiously
call
it
agenda
bashing.
So
there
we
go
so
feel
free
to
scroll
through
I.
B
Okay,
otherwise
I
think
we'll
just
jump
right
in
and
we'll
kind
of
review
action
items
from
from
last
week,
as
he
Frederick
has
joined,
all
I
did
was
I
just
went
through
last
week's
meeting
minutes
and
I
just
grabbed
the
action
items
in
the
order
that
they
were
that
they
were
mentioned
in
the
agenda
story.
So
Frederick
you
had
an
action
item
to
enable
the
wiki
and
github
and
documentation
there
is
there.
Is
there
any
update
on
that.
E
Also
I
was
thinking
about
it.
Well,
I
was
labeling,
it
a
thought
came
to
mind.
What
is
that
perhaps
like
we?
We
do
want
to
keep
some
information
on
the
wiki,
but
if
there's
something
that's
version
specific
like
how
do
you
use
it
or
API
specific
related
stuff,
the
magic
probably
go
within
the
repository
as
well,
if
someone's
using
Roo?
Let's
say
we
have
two
versions
that
are
in
use.
The
savers
are
like
one
in
version
two
that
are
not
compatible,
but
that
people
are
billing
on
top
of
them.
E
B
A
My
experience
spin
and
this
this
you
know
basically
we're
at
the
right
point
frankly
for
what
we're
doing
right
now,
which
is
wiki's,
are
really
easy
to
edit
and
so
they're
great
as
you're
just
trying
to
document
as
you
get
going
as
projects
mature,
wiki's
turned
into
terrible
actual
documentation,
and
so
you
eventually
you
get
to
a
point
where
you
do
real
real
adult
Docs
for
the
project.
But
I.
Don't
think
we're
like
to
the
point
where
we
need
to
put
energy
into
that
right
now,
and
so
wiki
is
probably
the
right
way.
Yeah.
E
We
can
always
migrate
as
well
like
it's
exactly
with
a
wiki
just
just
for
those
who
are
not
familiar
with
github
wikis
they're,
just
they're,
just
a
secondary
git
repo,
and
we
can.
We
can
pull
things
out
of
that
easily
and
stick
them
into
a
documents
directory
in
the
main
repo.
When
we
choose
to
do
so.
Yeah.
B
B
F
C
B
B
F
Sent
an
email
this
morning,
so
we
had
some
feedback
but
I
think
it
I
think
it
really
helped
everybody.
If
we
had
an
email,
I
mean
even
just
like
I,
don't
understand.
This
is
good
because
then
we
can
actually
add
add
more
content,
or
this
is
not
clear.
Those
type
of
comments
are
really
helpful,
I
think
Fran.
What
do
you
think
yep.
B
A
I'm,
sorry
about
that,
no
I
was
gonna
comment.
You
know
in
response
to
crimes.
Comment
like
I
am
cooking
some
sort
of
trying
to
communicate
some
other
ideas.
I've
got
some
preliminary
stuff
that
is
really
not
fully
baked,
but
it's
all
being
done
in
the
open.
A
So
there's
literally
a
network
service
mesh
folder
that
that
all
of
you
can
read
and
so
forth,
and
and
that's
literally
when
I
pick
up
a
pen,
that's
where
I
pick
up
a
pen
so
like
some
of
the
stuff
that
Prem
was
talking
about
with
sort
of
network
service,
mesh
wirings
and
things
like
that.
Is
there
it's
not
baked
so
that.
C
C
B
Excellent,
yes,
why
I
suggest
so
thanks
John
for
pointing
it
out
and
Chris
for
starting
the
discussion.
I
haven't
looked
at
that
this
morning,
yet
on
the
mailing
list,
but
but
yeah.
Let's,
let's
see
what
we
can
do
on
the
mailing
list
this
week
with
this
with
this
discussion
and
see
what
we
can
wrap
up
and
then
you
know,
I'd,
like
I,
think
we
should
propose
if
we
can
do
that.
B
B
Sound
good
to
everybody,
yep,
excellent,
okay,
so
we'll
keep
moving
along
in
the
agenda
here.
So
I
thought
you
know
we
usually
do
a
section
now
on
review
of
development
activity,
so
I
I
wrote
these
so
Frederick.
If
you're,
ok,
I
can
lead
this
section
this
week.
I
filled
all
this
in
this
morning,
so
I'm
I'm
can
I
go
over
it.
Ok,
so
but
yeah
oh
yeah,.
E
B
Ahead
and
add
it
at
the
end,
if
you
want
in
the
agenda
while
we're
going
through
the
top
part
or
whatever
you're
you're
good
with
so
so
I
thought
I
would
welcome.
We
had
new
contributors
this
week.
That
would
be
interesting
too,
so
he
and
I
going
to
perhaps
butcher
sir
goobies
name.
Do
you
know
how
to
browse
search?
Couey's
name
did
I
get
that
right.
B
You're
asking
me
for
pronunciation,
help
we're
all
doomed
we're
all
in
trouble.
Okay,
so
I
apologize,
but
welcome
to
the
new
contributors
that
had
some
right.
It's
a
single
syllable,
that's
true!
So
the
other
thing
I
did
was
I.
Have
these
things
I?
Have
these
handy
links
that
I'll
try
to
put
up,
keep
updated
so,
for
example,
this
one
I
did
this
right?
B
You
can
see
the
issues
that
were
closed
this
week,
so
you
can
get
a
sense
for
for
kind
of
what's
being
closed
and
then
I
added
another
one
for
pull
requests
that
were
merged
in
the
last
week
as
well.
So
so
there
is
work
happening.
We
can
see
code
in
all
of
its
glory.
Being
you
know,
reviewed
and
pushed
around
and
I
think.
That's
that's
pretty
good.
So
people
want
to
get
a
sense
for
what
what's
being
worked
on.
B
B
These
so
I
have
a
patch
for
that,
thanks
to
pratik
in
Frederick
for
reviewing
that
I
think
I've
addressed
all
of
their
comments,
except
for
the
refactoring
one
which,
which
Frederick
I
had
proposed
on
that
that
PR,
that
I
could
push
a
refactoring
one
after
this
merges.
If
you're,
ok
with
that,
but
this
this
should
correctly
handle
the
the
deletion
case
for
us.
B
So
once
PR
72
merges
we'll
be
doing
some
integration
testing
as
part
of
our
Travis
runs
as
well.
So
if
people
are
interested,
it
would
love
to
get
some
feedback
on
that
one
as
well,
and
then
the
last
one
was
sir
GUI
pushed
PR
79
this
morning
around
unit
tests
for
CRT
validation
as
well
and
he's
looking
for
he
pinged
me
this
morning
and
indicated
he
was
looking
for
some
feedback
on
the
approach
there
as
well.
So
does
anyone
have
any
other
ongoing
work?
I
know
Frederick.
B
E
Okay,
yeah
just
a
couple
other
things
that
we
should
start
working
on,
so
I
noticed
that
this
is
something
I
noticed
from
just
working
a
large
number
of
did
repos.
So
when
you're
working
in
or
on
go-go
project,
specifically
when
you're
working
and
go
one
of
the
issues
that
people
run
into
is
the
is:
how
do
you
set
up
your
initial
development
environment
and
how
do
you
integrate
with
the
deployment
or
a
dependency
tools
properly
as
well?
E
So
so
we
knew
we
need
to
work
out
a
way
to
minimize
some
of
these
issues
that
we
have
sort
of
examples.
You,
if
you
put
your
you're,
a
repo
in
the
wrong
spot
in
your
go
path
or
it's
not
in
a
go
path,
and
then
you
try
running
dip
on
it.
Then
you
sometimes
can
get
some
weird
stuff
going
on
with
it.
So
in
terms
of
how
it
builds
how
it
generates
code,
it
you
end
up
generating
code
that
ends
up
in
the
wrong
package
or
or
even
worse.
E
A
A
I,
guess
would
may
be
a
good
idea,
and
this
is
a
good
thing
for
a
wiki.
Frankly,
is
these
sort
of
ways
you
can
hurt
yourself
I
recognize
from
the
CI
is
telling
you
that
you've
done,
though
I
do
vaguely
recall
all
from
putting
in
the
self
enduring
stuff
that
there
was
an
attempt
to
try
and
make
the
error
message
is
really
really
self
explanatory,
because
I
have
a
personal
thing
against
error
message
that
says
bad
thing
happened
and
doesn't
tell
you
anything
else
about
what
to
do
now.
A
E
I
was
gonna
recommend
as
well
as
we
do
two
things
number
one
is
we
we
document
as
well
as
we
can
and
every
time
I
get
a
new
user
who
has
problems
with
it
once
they
fix
it,
then
their
job
is
to
update
the
wiki
in
a
way
that
they
would
have
understood
until
no
one's
starting
to
ask
that
question
anymore.
The
second
thing
is,
we
need
to
add
into
the
build
script
when
they
do
when
you
run
the
build
locally.
E
A
B
A
Yeah
I've
also
just
dropped
a
link
in
an
example
of
self
documenting
error
in
the
build
SH,
where
basically,
it
dies
for
what
even
if
you're
reading
the
script
is
probably
obscure,
reason
and,
and
then
it
basically
says,
do
this
to
fix
your
problem.
You
know
it
essentially,
you
know
it
dies
because
the
vendor
issue
and
then
it
tells
you
how
to
fix
it.
Yeah.
E
I'm
part
of
a
part
of
my
plan
as
well
is
to
is
to
try
to
eliminate
these
kind
of
roadblocks
to
prevent
people
from
joining
in
the
first
place.
So
if,
if
anything
like
this
comes
up,
you
know
definitely
feel
free
to
contribute
towards
it
or
contact
contact
me
and
I'll
help
come
up
with
a
with
a
way
to
mitigate
some
of
these
some
of
these
issues.
So
especially
if
it's
around
how
dependencies
work
or
go
reeling
in
a
tolling
or
anything
like
that,
like
definitely.
F
F
F
F
F
B
B
F
B
F
A
Thing
I
would
also
really
strongly
commend
if
possible,
it's
not
always
possible.
It
is
you
know.
Basically,
you
can
get
the
how
do
detect
error,
how
to
fix
error
in
the
same
place
in
whatever
script
people
are
running
whenever
you
can
do
that,
that's
golden
because
it
becomes
the
world
explodes
brief
message
about
how
to
make
the
world
stop
exploding.
Yes,
exactly
that's
the
best.
If
you
can
do
it,
you
can't
always
cool.
E
Yeah,
so
since
we're
talking
about
that
particular
space
as
well
so
with
the
mini
cube,
that
was
that
was
discussed
earlier
or
on
will
be
discussed
and
I,
maybe
I
think
we
just
have,
but
with
with
work
with
the
integration
stuff.
One
of
the
things
that
we
need
to
check
with
mini
cube
is:
is
it
possible
to
pick
the
the
CNI
plugin
and
the
the
STM
and
inject
it
into
into
mini
cube
and
the
reason?
E
The
reason
for
this
is
that
when
people
are
developing,
they're
gonna
want
to
develop
against
their
own
STM's
to
test
and
I'm,
not
sure.
If
many
cube
has
the
ability
to
inject
an
SDN
in
solo,
which
may
be
problematic
from
a
from
a
testing
side,
you
know
first
under
do
you
want
to
run
the
EPP
if
it
doesn't
give
you
an
easy
way
to
inject
the
ant
program
into
we're
gonna
run
into
problems.
So
if
it
doesn't
then,
and
there's
a
couple,
other
approaches
a
weekend,
we
can
try
out.
A
A
It's
probably
the
case
that
she
said
we
wanted
to
make
sure
that
we
are
open
to
testing
across
whatever
sort
of
CNI
or
Sdn
people
want,
so
that
when
as
we're
doing
development,
because
the
goal
is
to
support
multiple
different
approaches
to
the
data
plane
that
we
can
get
something
that
prevents
us
from,
you
know
for
you
from
unknowingly
breaking
one
data
playing
or
another
as
we're
going
through
this
process.
Yeah.
B
So
I
definitely
agree
as
well
it.
It
appears
like
because
I
looked
at
this
previously
I
think
mini
mini
cube,
does
support
CNI.
So
so
we
should
be
able
to
do
it
there.
But
but
having
said
that,
I
agree
that
we
definitely
want
to
make
sure
that
that
cube
ATM,
that
we
can
that
we
have
some
testing
for
that
method
as
well,
and
that
we
can
can
utilize
that
to
well.
E
To
be
more
to
be
more
accurate,
see
and
I
will
be
present
in
mini
cube,
but
can
you
change
the
CNI
driver?
And
that's
that's
really
the
question.
So
that's
that's
something
that
we
need
to
look
into
and
and
the
reason
for
changing
it
is
unless,
unless
you're,
okay
doing
everything
with
the
default
driver
which
might
be
flannel
or
it
might
even
be
a
might
even
be
a
linux
bridge
that
drops
things
into.
E
B
E
A
E
E
They
need
to
use
that
network
that
that
namespace
then
we
use
that
particular
Hammad's
and
that
allows
you
to
have
restarts
without
losing
the
the
state
or
allows
you
to
add
multiple
pods
or
multiple
containers
on
top
of
that,
and
without
jeopardizing
the
main
one.
So
as
long
as
we
can
discover
that
the
names
basement
that
pause
and
then
we're
we're,
then
we're
good
to
go
and
that's
that's!
That's
not
difficult
to
do
you
know,
even
if
you
don't
have
any
kubernetes
axis,
you
can
always
do
docker,
PS
and
work
it
out
programmatically.
So.
F
F
E
F
F
F
A
So
here's
the
thing
I've
actually
don't
through
it
I
can
reconstruct
it.
Given
ten
minutes
and
started
up
a
docker
container
from
within
a
docker
container,
you
can
go
fishing
in
proc
to
find
out
your
namespace.
You
can
then
get
that
namespace
removed
in
the
docker
container
or
translate
it
back
to
a
name.
You've.
A
We
get
that
information
from
whatever
is
sending
the
company
connection
requests
call
to
the
NSM
all
right,
so
we
don't.
This
is
part
of
the
reason
that
the
NSM
was
done.
This
way
is
there's
a
ton
of
information,
there's
a
ton
of
problems
that
people
are
having
but
they're
trying
to
push
in
various
places
that
we
literally
don't
have
because
of
the
way
the
architectures
felt.
So
the
fact
that
you've
got
someone
from
inside
the
pod
making
the
call
at
the
NSM
saying
please
do.
E
A
It
may
be
that
it's
a
perfectly
lovely
and
good
thing
that
would
be
wonderful
for
the
universe
is
just
not
a
thing.
That's
in
our
critical
path.
You
know,
and
a
lot
of
that
was
intentional.
I
spent
a
lot
of
time
looking
at
like
what
you
would
put
me
on.
A
texture
together,
I
put
a
lot
of
time,
thinking
about
not
having
to
go
ask
for
changes
of
unknown
on
lines
in
order
for
to
work
and
I.
A
Think
and
of
course,
one
discovers
has
one
codes,
but
I
think
that
we
actually
work
just
fine
with
zero
changes
to
the
system.
Somebody
if
you're
gonna
handle
physical
objects
that
have
to
be
returned,
as
eventually
gonna
have
to
fix
the
deallocate
problem
in
the
device
plugin,
but
but
in
that
would
be
beneficial
to
us,
but
I,
don't
think
we're
by
any
means
the
most
important
people
who
care
about
that
problem.
So
yeah.
D
A
Yeah
definitely
it's
definitely
definitely
something
I
had
thought
about
as
a
problem,
because
otherwise
you
do
have
to
go
and
get
all
kinds
of
new
holes
poked
in
the
wall,
through
various
paths
and
and
I
know
that,
from
what
I've
been
reading
from
the
people
who
actually
seem
to
be
gatekeeping
on
device
plug
and
stuff,
they
seem
really
leery
to
be
passing
what
they
deem
unnecessary
data
around.
So.
E
A
Explore
different
paths:
I
did
a
mechanical
exercise.
I
just
didn't
write
it
down.
So
please
do
write
down
the
action
item
to
make
sure
that
I
actually
do
write
it
down
this
time,
because
I've
done
the
exercise
twice
now-
and
this
is
about
two
third
time
so
apparently
the
only
bit
I'm
retaining
in
my
head
is
that
the
solution
exists.
Yes,
so.
E
E
So
there's
a
couple:
there
there's
there's
two
areas
on
this
number.
One
is
what
do
we?
What
do
we
test
against
the
second
one
is:
how
do
we
set
it
up
so
that
people
can
test
against
the
FG
ends
that
they
that
that
they
want
to
test
against,
and
specifically,
we
want
to
make
sure
in
the
long
run,
that
we
have
a
set
of
integration
tests,
that
people
can
run
to
tell
whether
or
not
the
rest
en.
E
Works
or
works
or
not,
and
of
course,
with
some
I'll,
have
to
be
some
options,
but,
like
suppose,
you
have
an
SDN
that
doesn't
support
the
excellent
for
some
reason
and,
of
course,
that
test
path
doesn't
make
sense,
but
an
order,
negotiation
that
relates
that
would
so,
but
yeah
I
think
I.
Think
right
now,
because
of
the
the
makeup
of
the
of
the
team.
I
think
that
getting
a
VPP
in
the
path
just
for
the
initial
set
of
testing
is
probably
going
to
be
is
probably
going
to
be
the
best.
E
But
I
want
to
be
a
bit
careful
with
this,
because
one
of
the
there's
there's
an
important
part
on
optics
and
I've
I've
drilled,
listened
to
and
over
and
over
again
is
that
we
want
to
be
careful
not
to
be
seen
as
like.
This
is
a
BPPV
sub-project
learn
our
legato
sub
project.
It's
a
project
that
uses
legato,
it's
a
project
that
has
support
for
VPP,
but
is
not
part
of
those
projects
and
it's
trying
to
be
part
of
a
bigger
part
of
a
bigger
echo
system.
E
A
I'm
Phatak
lee
in
agreement
here
and,
and
basically
it
is
really
crucially
important
support
for
multiple
ways
of
doing
the
data
plane
and
the
sooner
we
get
to
that
that
multiple
paths
support
the
more
confident
we
will
be
in
the
fact
that
we
actually
do
that
successfully
right.
My
experience
has
been
when
you
have
a
system
where
you're
supposed
to
be
able
to
plug
in
for
implementations
of
a
thing
until
you
get
that
second
implementation,
don't
really
know
whether
you've
done
that
right,
yeah.
A
C
A
Basically,
it's
not
like
the
great
control
plane
in
the
sky,
because
I
think
that,
as
a
matter
of
personal
technical
opinion
and
people
are
absolutely
allowed
to
disagree
with
me
that
they,
you
have
to
be
very
cautious
with
great
brains
in
the
sky,
because
they
often
scale
poorly
and
so
I
tend
to
think
of
the
honestest,
the
local
control
plane
running
on
each
node,
which
is
not
to
say,
we
won't
discover
something
where
we
need
a
great
brain
in
the
sky
as
we
go
along.
A
E
E
A
I
think,
quite
honestly,
the
way
I've
been
thinking
about
it.
It's
not
the
only
way
to
think
about
it
is
as
we're
building
out
the
NS
on.
You
know
we're
building
it
out
in
certain
plugins
and
effectively
the
you
know.
We
there
will
come
a
point
where
there
is
the
the
plug-in
that
talks
to
the
data
plane
and
whether
that
plug-in
is
talking
to
the
data
plane
directly
was
talking
to
some
NSM
that
sums
SDM
is
talking
to
the
airplane.
A
You
know,
I
think
we
need
to
be
able
to
support
multiple
plugins
that
talk
to
data
plane
and
and
we
need
to
be
pretty
agnostic
as
to
whether
we're
just
locally,
manipulating
a
data
plane
or
asking
some
Sdn
to
do
it.
For
us.
B
A
B
C
So
I
just
created
a
simple
Google
poll:
I
just
sent
it
to
Edie
I
like
to
see
I
need
to
add
something.
So
just
three
simple
questions:
one
is
the
time
zone
from
where
the
participant
is.
Dialing.
Second
thing
is
whether
they
open
for
Alton,
alternating
the
calls
meaning
between
mornings
and
evenings
and
the
third
one
is
basically
a
picked
up.
A
few
time
slots
based
on
the
previous
history,
so
I'm
going
to
send
out
the
poll
once
a
dad
hit,
provides
the
feedback.
H
He
asked
me:
I
did
try
trotting
a
colleague
who,
if
you
haven't
heard
from
him
I
guess
he
hasn't
picked
I
interest
I,
don't.
A
Think
so,
because
I
mean
what
are
the
other
options
we
may
want
to
add
to
the
poll
is
so
that
this
whole
conversation
started
because
Mike
brought
up
the
issue,
quite
rightly
that
Friday
is
a
weekend
for
some
people
right,
and
we
all
know
that
International
scheduling
of
all
kinds
is
complicated
and
problematic,
and
so
Prem
being
yo
being
Prem
stepped
up
immediately
to
volunteer
to
do
a
poll
that
didn't
have
Friday
on
it
and,
and
so
one
of
the
things
we
do
have
to
decide
as
a
community
is.
A
Is
this
time
slot
working
for
us
and
do
we
want
to
move
it
off
of
its
current
lash
line?
You
know,
but
that's
something
we
need
to
talk
about.
I,
don't
think
we
have
anyone
come
Wheatly
right
now
who
has
a
problem,
but
you
know
if
we,
you
immediately
decide
we'll
go
to
do
that
right.
You
just
why
these
work.
Well,
that's.
B
B
Absolutely
and
I'm
definitely
you
know
we
definitely
need
to
make
that
happen,
but
but
but
but
on
the
other
hand,
as
you
know,
I
and
and
I
will
I
am
old.
You
know
like,
for
example,
we've
been
talking
about
this
for
four
weeks
and
I
know
Mike's
been
trying
to
get
someone
who
says
they
want
to
come,
but
can't
come
if,
after
four
weeks
of
trying
to
get
that
person
to
indicate
to
somebody
like
when
they
can
attend
and
everything-
and
we
don't
hear
anything
at
some
point-
we
just
move
on
yeah.
E
C
C
B
We
do
that
so
so,
basically,
we'll
cuz,
we
have
the
previous
AI
to
have
everybody
continue
the
discussion
on
the
mailing
list.
So
then,
next
week
we'll
we'll
do
another.
You
know
it
might
make
sense,
actually
prem
next
week
to
try
to
focus.
Maybe
you
know
half
the
meeting
towards
the
use
case
document
again,
assuming
we
have
a
pretty
lively
discussions
week.
Do
you
think.
C
A
Also
got
some
comments
during
the
meeting
from
Daniel
Pinero
at
Bell
Canada,
which
is
also
and
Lukas
comments.
I
think
are
really
good
and
some
of
the
comments
either
I
misunderstand:
what's
going
on
to
me,
you
see
a
stock
or
he
misunderstands
what's
going
on
the
use
case,
doc
I'm,
not
sure
which
custom
he's
like
we
need
to
be
it's
important
that
we
can
do
XYZ
and
I'm.
Looking
at
the
going
I
thought
we
could
I'm
so
confused.
A
F
C
B
A
The
dissection
is
all
this
this.
This
has
always
been
about
sort
of.
You
know
the
it's
the
whole
idea
with
no
resurface
mesh,
it's
very
cool,
but
it's
a
little
bit
different
than
folks
have
looked
at
the
stuff
in
the
past,
and
it
was
just
to
provide
some
space
for
people
to
sort
of
talk
through
the
concept
it
feels
like
people
are
getting
good
traction
on
the
concept
and
so
I'm,
okay
with
that's
probably
cuz
I,
haven't
been
here.
The
last
two
weeks.
A
And
I
didn't
call
you
out,
among
other
people,
when
I
was
pressing
appreciation
at
the
network
service
mesh
meeting
that
present
a
try
that
the
Signet
working
meeting.
That
presentation
would
not
have
been
nearly
as
clear
if
you
had
not
been
insisted
on
precise
expression
of
the
idea.
So
I
do
appreciate
that
yeah.
H
So
I
think
maybe
the
I,
don't
it.
Maybe
if
you
and
I
could
just
get
some
more
time,
I'm,
not
sure
we
need
to
take
everybody's
time.
No.
A
I
know
waited
to
do
that
because
I've
been
finding
it
very
valuable,
but
I
suspect
that
it's
valuable
for
you
and
it's
valuable
for
me,
but
it
may
not
so
much
be
valuable
for
an
audience.
Yeah.
C
A
So
I
think
what
you're
saying
is
you
have
something
that
is
speaking
BGP.
This
is
essentially,
you
have
some
SD
on
this
interacting
with
BGP,
and
how
do
we
actually
interact
correctly
and
in
my
off-the-cuff?
Is
that
whatever
or
data
plane
plug
in
for
n
SM
you
had?
It
would
be
the
thing
that
would
be
causing
that
to
happen.
So
you
know,
let's
just
take
a
for
instance,
right
and
and
I.
Please
note
this
marionette
I
make
even
and
even
make
any
sense.
You
know,
let's
say
that
whatever
you're
doing
involves
locally
manipulating
it.
A
You
know
you
want
to
do
this
in
the
way
that
both
locally
manipulated
data
playing
and
advertising
a
bunch
of
routes
to
bgp
right,
and
so
you
build
an
honest
em
plug-in
that
locally
manipulates
the
data
plane
and
advertises
a
bunch
of
routes
to
BGP.
That's
awesome,
but
I,
don't
think
MSM,
the
common
and
SM
thing.
That's
that's
across
every
MSM
I.
Don't
think
that
necessarily
is
something
that
should
interact
with
BGP
itself.
Does
that
make
sense.
C
C
So,
to
put
it
in
simple
terms,
what
I'm
trying
to
say
here
is
assuming
that
you
start
on
a
clean
slate
with
with
the
serviced
mesh
right
with
a
network
signal
swish.
What
you're
trying
to
do
is
you're
trying
to
create
the
the
me
excellent
canals
between
the
pots
and
then
once
that
is
done.
Basically,
the
channels
gets
exposed,
and
how
is
it
happening
is
basically
based
a
bit
of
the
parts
requirement
as
well
as
what
is
the
requirement
from
the
next
erna
connectivity
right.
G
C
When
we
bring
in
the
external
connectivity,
what
is
the
important
is
oneness
the
Potts
requirement
for
Asus
meaning
or
the
application
requirement
asses?
There
is
also
a
requirement
that
is
coming
from
the
external
world
on
what
has
to
be
exposed
and
what
should
not
be
exposed
right
that
might
be
driven
by
policy,
but
when
we
talk
about
policies
related
to
that
of
network,
what
matters
as
matters
relates
to
what
each
of
the
parts
have
to
be
exposed
to
external
nodes
and
which
of
the
parts
should
not
be
exposed
right.
C
A
So,
in
my
mind,
there's
sort
of
two
things
that
are
going
on
here.
It
feels
to
places
that
you
might
have
what
you
might
think
of
routing
and
it's
in
the
system.
One
thing
one
place
you
may
have
it
is
inside
the
pod.
It
may
be
by
virtue
of
having
gotten
a
connection
to
a
network
service.
It
may
need
to
have
some
routes
to
selectively
send
some
of
its
traffic
to
that
network
service.
So
a
really
simple
example
of
this
is
imagine.
The
network
service
I've
been
connected
to
is
a
is
basically
secure.
A
Intranet
connectivity
right
so
I
think
that
lets
me
connect
securely
to
my
internet
force.
Whatever
the
definition
of
secure
is
right,
and
so
it
may
be
that
when
I
get
that
connection,
I
should
also
be
receiving
a
set
of
routes.
That
say,
okay,
here
are
the
prefixes.
You
should
be
the
network
service,
that
is
from
the
hog,
the
network,
server
statistics,
your
internet
connectivity,
alright,
that's
sort
of
what
I'm
calling
the
inside
the
pod
routing
and
in
I'm.
A
Thinking
of
that
is
something
that
comes
back
via
the
you
know,
connection
accept
message,
so
you
know
the
far
end.
The
network
service
endpoint
accepts
the
connection.
It
understands
what
addressing
it
would
like
people
to
have
when
it
talks
to
them
what
kind
of
traffic
should
be
sent
to
it,
etc,
and
that
comes
back
to
the
NSM
which
can
set
that
stuff
to
the
pod.
That's
kind
of
how
I've
been
thinking
about
that
right
now.
A
Now
then,
there's
the
second
area
that
you
mentioned,
and
that
is
literally,
if
I
have
a
pod
of
this
trying
to
connect
to
a
network
service
and
I
have
a
bunch
of
different
network
service
endpoints
that
could
provide
it
that
service.
How
do
I
decide
which
one
to
connect
it
to
right
and
and
that's
that's,
what
I
think
of
as
sort
of
the
policy
II
the
sort
of
connection
policy
stuff
I've
been
actively
calling
it.
You
know
network
service,
wiring
and
thinking
of
it
as
analogous
to
is
Tio's
virtual
service
or
route
rules
concept.
A
Okay,
but
I
think
we
look
at
those
two
things.
Then
you
can
start
asking
yourself
sort
of
like
how
do
you
connect
those
to
other
systems?
Does
that
make
sense
to
everybody?
I.
E
Okay,
thank
you
yeah
one,
just
just
to
inject
something
real,
quick.
One
thing
that
we're
probably
going
to
have
to
build
out
is
we're.
Probably
gonna
have
to
add
something
for
that
that
term
some
of
these
into
a
into
a
shared
library
the
Destin's
can
pull
in.
So,
for
example,
we
wouldn't
talk
about.
How
do
you
add
our
route?
You
know
in
order
to
add
around
you
have
to
spin
up
a
container.
E
That
container
has
to
have
that
admin
then
ask
to
run
the
correct,
netlink
commands
or
or
otherwise
whatever
other
adi
calls
against
the
colonel.
In
order
to
said
properly
and
this
this
would
be
a
really
good
area
to
have
a
single
location
or
set
of
utilities
that
can
they
can
do
this.
On
behalf
of.
A
Not
to
say
it's
the
only
right
way
to
do
it.
The
way
I
had
been
thinking
about
this
was
not
actually
to
have
the
SDNS
do
that
the
way
of
thinking
about
it
would
be
the
network
service
mesh
likely
or
the
way
I've
been
thinking
about
that
was
the
NSM.
The
the
NSM
is
the
one
that
operates
on
the
stuff
that
goes
into
the
pod,
based
upon
the
response
that
it
got
from.
A
You
know
the
things
that
it's
interacting
with
right,
so
if
it,
if
it,
you
know,
gets
back
in
this,
the
NSM
understands
from
its
pure
and
s/m
on
the
other
end,
for
example,
that
you
know
these
are
the
things
that
should
be
passed
back,
and
I
was
seeing
that
coming
to
the
except
connection.
I
actually
have
a
picture
for
this
that
might
help
one
second.
E
Yeah
and
it
could
be
the
MSM
as
well,
it
could
be
some
may
be
some
set
of
labels
or
or
other
information
that
gets
tagged
in
that.
That
says,
please
inject
us
on
my
behalf
and
that's
that's
fine
as
well.
We
just
have
to
have
a
mechanism
that
that
performs
this
because
you
know,
like
the
use
case,
the
prem
cave,
where
you
have
bgp.
E
You
have
a
new
route
that
you
need
to
support,
but
there's
no
easy
way
for
for
a
NSM
based
library
or
demon
running
within
the
container
to
inject
to
inject
in
unless,
unless
you
have
a
sidecar
and
now
I
think
we
Steve
we're
looking
at
eventually
putting
in
the
size
card
that
would
have
net
admin,
and
then
we
could
do
with
your
there.
Yeah.
A
I
mean
one
of
the
things
that
occurs
to
me.
There
is
that,
so
what
I
think
about
this?
You
would
be
all
this
stuff.
So
let's
go
back
to
the
VPN
example,
not
because
it's
the
only
example,
but
it's
it
sort
of
it's
instructive
right.
So,
if
I'm
acting
to
connect
to
secure
Internet
connectivity
service
and
that
ends
up
giving
me
a
connection
to
some
VPN
gateway
pod
somewhere
else,
then
it
is
encased.
A
I
would
expect
to
be
getting
my
Road
updates,
not
from
an
SDN
but
from
that
VPN
gateway
park,
because
it's
the
one
that
actually
knows
my
Sdn
may
or
may
not
know.
You
know
unless
it
happens,
to
be
intimate
with
the
VPN
gateway,
pod
and
so
I
think
that
what
you
did
call
out
is
the
need
to
be
able
to
dynamically
update
some
of
that
information
from
the
far
end
of
the
connection
to
the
the
originator
of
the
connection
over
time.
Does
that
make
sense,
yeah.
E
That's
that's
what
I'm,
trying
to
to
point
out
like
I,
actually
don't
care
where
the
information
comes
from
as
long
as
we
provide
an
easy
way
for
people
to
perform
these
operations
that
that,
then
we
can
expose-
and
we
just
make
it
very-
very
easy
to
to
inject
these
things
in
and
we
can.
We
need
to
work
out
how
we
want
to
expose
them
and
how
much
control
we
want
to
maintain
our
versus
how
much
we
want
to
to
allow
them
to
be
explicitly
called,
but
ultimately,
I
think
that
that's
that's
what
we
need
is.
E
A
And
that
was
kind
of
how
I've
been
thinking
about
the
problem
doesn't
mean
it's
the
only
answer,
but
the
coordinate
II
through
the
ASM
was
definitely
how
I've
been
thinking
about
the
problem
cool,
so
we're
at
the
top
of
the
hour.
I
do
want
to
be
respectful
of
folks
time.
I
do
a
pretty
well
of
you
coming
and
all
the
folks
who
are
starting
to
participate
in
push
code.
That's
awesome
and
I
will
see
you
all
next
week.
Yep
sounds
good.
Everyone.