►
From YouTube: Network Service Mesh Meeting 2020-01-07
Description
Network Service Mesh Meeting 2020-01-07
B
B
B
B
B
B
B
B
Ok,
let's
get
started
so
welcome
to
the
next
network
service
mesh
meeting.
We
have
this
particular
meeting
every
Tuesday
at
8
a.m.
Pacific
and
we
also
participate
in
the
CN
CF
telecom
user
group,
which
occurs
every
first
Monday
at
8
a.m.
Pacific
and
every
third
Monday
at
3
a.m.
Pacific
good
for
Asian
time.
We
also
are
participating
in
the
CN
CF
networking
working
group,
which
is
recently
been
rebooted.
It
meets
every
two
weeks
on
Tuesday
at
11:00
a.m.
B
the
last
meeting
was
on
December
19th
I
need
to
ask
Lee
Cal
coat
when
the
next
one
for
this
year
is
going
to
start.
So
we
can
get
the
cadence
up
on
that
again
and
with
that
we
have
a
couple
major
events.
So
the
first
question
is:
do
we
want
to
keep
FOSDEM
2020
on
the
list
is?
Are
we
doing
anything?
Are
we
doing
anything
there?
I,
don't
think
so.
B
Ok,
highly
encourage
you
go
to
the
FOSDEM
still,
even
though
we
don't
have
a
presence
there.
I
would
say
it's
a
very
fun
event.
We
have,
we
have
cube
con
coming
up
and
with
cube
con.
The
call
for
proposals
is
already
closed.
The
notifications
should
go
out
within
a
couple
of
weeks
is
so
we
are
we.
We
have
several
call
topics
that
have
been
that
have
been
shared
into
into
the
proposals
and
Taylor
has
a
has
comprised
a
list
of
people
who
have
self
selected
themselves
into
into
the
list
and.
B
C
I
know
it's
on
the
list
of
things
that
need
to
happen.
This
week
is
I.
You
know
effectively
getting
a
prospectus
together,
getting
a
CFP
out,
etc.
So
definitely
need
to
get
that
moving,
because
time
is
running
a
little
bit
short.
But
the
good
news
is
we've
done
this
once
before,
so
it
should
be
quite
doable.
E
B
B
B
We
did
this
announcement
last
time.
I
will
do
it
again,
one
more
time
we
donated
the
$2,300.
We
got
from
the
registration
fees
of
the
last
NSM
con
to
the
cnc
of
diversity.
Scholarship,
I
believe.
The
intention
is
to
do
that
again
and
the
Mex
in
the
semcon
how
we
will
have
that
enumerated
in
the
prospectus
as
to
what
exactly
we
will
do
with
that.
B
But
please,
if
there's
any
talk
that
you're
interested
in
or
you
want
to
share
with
others,
we
have
the
NSM
Khan
playlist
and
a
YouTube
channel
that
has
the
the
set
of
talks,
so
these
are
specifically
for
NSM
Khan.
The
cube
Khan
NSM
talks
are
on
the
CNC
F
channel,
so
you'll
have
to
be
a
rummage
through
the
CNC
F
channel.
Therefore,
for
those
ones
the
and
with
that
we
have
the
social
media
community
team,
you
seen
that
you
have
the
floor.
Hi.
C
E
So
I've
had
some
help
with
keeping
things
moving
over
the
past
three
weeks
or
so,
and
in
the
past
three
weeks,
we've
gained
21
new
Twitter
followers
and
19
new
LinkedIn
followers
and
have
posted
about
32,
tweets
and
retweets,
including
the
NSM
cotton
EU,
2020
announcements.
The
two
calls
today
and
there
was
an
article
kubernetes-
continues
to
shine
that
featured
NSM
and
we
also
posted
videos
of
each
individual
NSM
talks.
So
that's
going
to
be
both
on
our
twitter
and
linkedin
and
just
this
morning
posted
a
recap
of
the
0.20
release.
E
So
the
plan,
once
we
have
the
link
for
the
CFP
for
NSM
con,
will
go
ahead
and
share
that.
If
we
are
meeting
sponsors
to
sign
up,
we
can
go
ahead
and
share
that
and
let
them
know
that
it's
open
and
share
the
link
on
how
sponsors
can
get
involved
and
any
retweets
that
mention
us
in
the
press
and
oh,
but
the
contributor
podcast
is
the
URL
available
for
that
one
I.
B
B
C
B
Think
my
preference
would
be
for
it
to
be
to
be
a
new
repo,
something
that
we
can
then
pull
in
so
I'm
yeah,
with
the
conversations
that
that
we've
that
we've
had
on
cloud
tests
is
there's
no
dependency
on
anything
else.
So
it
should
be
something
trivial
to
to
pull
out
and
I.
Certain
I
have
interests
to
run
it
in
other
context
outside
of
NSM
ins
as
well.
D
C
Thing
as
well
so
I
wanted
to
make
sure
we
brought
this
up
as
a
matter
of
conversation,
we
probably
want
to
do
a
time
permitting
sort
of
have
a
general
conversation
about
where
we
might
want
to
go
in
terms
of
generally
breaking
things
into
separate
repos
and
in
sort
of
the
timing
of
it.
The
cloud
test
seemed
like
a
very
obvious
choice
because
it
was
low
impact
and
you
can
see
how
that
goes,
but
there's
also
a
question
of
how
we
end
up
doing
CI
when
we
have
multiple
repos
as
well.
D
D
C
Things
that
came
to
mind
I
mean
we
talked
last
year
about
the
path
stuff
I'm
sort
of
busily
poking
at
the
refactor
work,
for
that
I'm
I
was
hopeful
to
have
it
done
over
the
break
that
might
break
ended
up
being
more
like
a
break
which
is
probably
healthy
overall
and
so
I
probably
still
have
about
another
week
on
I'm.
Getting
some
of
that
code
done
that
that
will
be
exciting
as
it
comes
together.
C
D
D
Wouldn't
call
it
a
problem,
but
this
this
challenge.
Let's
say
it
is
essentially
how
do
you
make
a
be
able
to
connect
to
both
B
and
C,
without
really
understanding
that
there's
B
and
C?
It
just
says:
I
want
to
connect
to
each
and
every
one
of
these
existing
at
least.
Does
my
interpretation
of
the
other
program
I
think
that
it
depends
on
the
way
you
you
were
gonna
need
it.
It
can
kind
of
suggest
the
solution,
so
I'm
obviously
suggesting
a
solution
here,
but.
D
C
A
It's
just
pretty
simple.
Actually
at
the
moment,
at
the
current
state
of
NSM,
we
have
a
point-to-point
connections
and
network
service
endpoint
provide
the
pair
of
IP
addresses
to
connect
between
one
point
and
and
we're
gonna
see
itself.
So
idea
is
to
think
about
for
NAC
to
provide
not
a
point-to-point
connection
but
the
network.
So
we
will
have
dedicated
network
service
endpoint.
A
C
Know
and
Internet
resource
mesh
is
still
just
doing
the
V
wires,
but
somebody
is
writing
an
NSC
that
gives
you
the
l3
network
that
you're
interested
in
yeah,
yeah,
yeah
I,
think
that's
actually
I
think
that's
actually
definitely
the
thing
I
I.
Think,
though
part
of
it
is,
you
still
have
whatever
network
service
endpoint
that
is
providing
that
you
may
have
different
off
of
them
in
different
places
that
need
to
connect
to
each
other
with
V
wires
as
well.
Yeah.
C
The
lovely
thing
is
that
I
think
it
can
be
explored
in
all
kinds
of
different
ways.
I
mean
one
of
the
nice
things
about
never
service
mesh
is
that
there
is
no
one
true
way
to
solve
that
problem.
Which
again,
is
you
know
if
somebody
thinks
of
a
smarter
way
to
approach
it,
they
could
just
write
the
network
service
in
points
in
a
way
they
go.
D
E
D
C
A
C
It's
just
also
you
might
want
to
reach
out
I
know.
Ilya
is
in
contact
with
him.
You
may
want
to
reach
out
to
him
because
I
know
he's
also
thinking
in
this
area.
So
you
know,
I
put
it
I'm
perfectly
delighted
to
have
people
explore
multiple
ideas,
oh,
but
it
is
better
if
people
who
are
going
to
explore
the
same
idea
discover
they're,
exploring
the
same
idea
in
collaborate.
D
My
only
as
we
just
spoke
in
the
morning
like
my
morning
earlier
call,
let's
say
my
only
concern.
Okay,
it's
also
concern
but
kind
of
think
that
that
I
would
like
to
make
sure
that
we
keep
the
API
as
generic
as
possible
and
not
in
kind
of
in
the
in
an
attempt
to
solve
a
particular
use
case
to
to
make
just
kind
of
you
know
some
solutions
that
are
meant
to
solve
the
particular
use
case.
I'm.
C
I
have
two
principles
that
actually,
in
my
way,
I
think
about
code
that
that
actually,
that
support
that
the
first
is
you
should
keep.
Your
API
is
simple
and
few
and
in
general
and
then
the
second
one
is
that
you
should
avoid
unnatural
acts.
Yeah
I
know,
we've
all
been
in
that
place
for
you're
sort
of
hacking
on
a
piece
of
code
trying
to
get
it
work
and
hacking
on
a
piece
of
code
trying
to
get
it
work
to
work,
and
you
go
to
bed
and
you
get
up
the
morning.
C
B
C
D
Okay,
so
maybe
maybe
why
we
are
here
on
this
picture
and
also
in
relation
with
something
that
under
I
mentioned
I
had
a
discussion
today
with
one
person
I.
Think
that
you
had,
you
probably
can
remember
this
PR,
where
we
were
trying
to
have
multiple
quagga
or
routers
interconnected
in
a
mesh.
If
you
remember
this
problem
in
the
examples,
okay,
whatever.
Oh
sorry,.
C
D
So
we
were
discussing-
and
this
topic
of
IPs
I'm
on
static
assignments,
etcetera,
etcetera,
came
up
and
I
think
that
that
currently
we
are
more
or
less
bound
to
having
IP
over
the
connection.
We're
kind
of
requesting
it
each
and
every
time
which
should
be
probably
changed.
I
haven't
checked
the
code
lately,
but
I
think
that
it
was
because
we.
C
C
D
So
I
think
that
at
some
point
you
have
to
think
a
little
bit
more
about
how
do
we
want
the
eyepiece
being?
Because
what
we
have
today
is
an
eye
Pam
implementation
in
the
SDK,
because
that's
that's
that's
where
it
lives
today
is
something
it
does
this
job
for
whatever
we
wanted
to
to
use
it,
but
probably
people
would
like
to
be
able
to
to
assign
IP
addresses
in
in
other
ways,
I'd
say:
yeah.
C
I
mean
you
could
totally
do
all
kinds
of
different
IPM
implementations
that
are
different
than
the
one
that
we
did
in
the
SDK
I
think
the
SDK
one
was
done,
is
sort
of
the
simplest
available
and
I've
even
got
some
interesting
thoughts.
I've
thought
a
little
bit
about
this
problem
space
as
well,
particularly
around
doing
DL,
3
domains,
and
it
turns
out,
like
we
have
all
kinds
of
interesting
characteristics
that
make
IPAM
for
us
in
the
l3
radically
simpler
than
it
is
generally
thought
to
be
as
a
problem.
C
B
C
B
Okay,
well,
if
there
is
no
further
questions,
its
last
chance
to
unmute
yourself,
but
if
you
didn't
amuse
yourself
by
accident,
if
there
are
no
further
questions
or
comments
for
the
agenda,
then
we
will
have
this
same
meeting
again
same
time
next
week
and
then
want
to
thank
everyone
for
attending
our
first
one
of
the
year
and
here's
to
a
fantastic
year
for
for
the
community.
That's
coming
up
so
I'll
catch!
You
all
later
see
you
say
yes,.