►
From YouTube: CNCF Network Service Mesh Meeting 2020-01-21
Description
CNCF Network Service Mesh Meeting 2020-01-21
A
A
A
B
B
C
D
A
Okay,
I
read
through
this
and
I
agree
in
general
that
we
probably
can
and
Roley
should
sleep
in
the
example
down,
but
on
the
same
time
we
need
to
probably
have
another
dedicated
example
where
we
can
examine
a
little
bit
of
scaling.
Okay,
that's
not
a
great
scaling,
but
still
is
like
success,
containers
with
the
sidecars
and
etcetera.
So
it's
it's
something.
Probably
it's
not
the
best
way
to
taste
it.
Maybe
we
should
have
something.
That's
dedicated
that
runs
only
on
the
on
the
bare
metals
but
yeah.
So.
B
C
A
A
C
A
D
E
E
A
A
C
A
E
E
B
A
H
C
A
F
D
I
J
E
A
A
A
A
B
A
D
A
A
E
A
A
A
H
H
A
A
J
Yeah,
so
this
is
something
that
I've
discovered
and
so
okay,
so
one
of
the
things
of
we're
going
she
trying
to
do
is
we
had
the
project
board
where
we
had
within
the
network
service
mission
project
itself.
Okay,
we're
gonna,
try
migrating
issues
and
PRS.
They
were
attracting,
then
that
cross,
especially
if
they
cross
and
look
will
repose
onto
a
project
level
on
rather
sorry
an
organizational
level
board
rather
than
the
project
the
whole
board.
E
E
E
F
I
J
And
the
purpose
of
it
as
well
is
as
it's
less
for
this
for
this
group,
although
I
think
it'll
be
helpful
for
this
group.
It's
also
where
we're
gonna
make
an
effort
to
get
the
community
more
involved
over
time.
So
this
will
give
them
an
easy
place
to
to
jump
in
as
well
and
work
out
like
what
what
major
things
are
pending
that
they
can
try
to
to
make
use
of,
and
especially
with
the
SDK
fat.
J
J
E
J
J
J
J
We
also
participate
in
the
sensitive
telecom
user
group
and
I
apologize.
My
mic
not
3
a.m.
Pacific
time.
How
could
the
out
reaction
time
were
a
few
moments?
We
also
participate
in
the
telecom
user
group,
which
occurs
every
first
Monday
at
8
a.m.
with
cific
and
every
third
Monday
at
3:00
a.m.
acidic.
We
also
participate
in
the
CNC
F
Sigma
Network,
which
occurs
every
first
and
third
Thursday
of
every
month
at
11
a.m.
J
J
J
We
also
have
an
sm
con,
which
is
a
Q
Khan
EU,
which
is
co-located
and
events
on
May
30th
highlights
included.
We
have
a
larger
room
and
we
have
prospectus
and
information
for
CF
p
on
the
on
the
website.
It
is
linked
from
here,
so
the
CFP
is
currently
open,
closes
February,
21st,
and
if
you
also,
if
you
posted
a
talk
that
is
NSM
related
and
if
it
does
not
get
into
the
innocent,
may
sorry
to
the
kubernetes
main
track,
we
highly
encourage
you
to
resubmit
it
into
an
assignment
as
well.
J
The
number
of
talks
available
at
at
duke
content
to
be
percentage-wise,
the
number
talks
accepted
is,
is
very
low
just
simply
because
of
the
number
of
slots
they
have,
and
we
also
have
sponsorship
information
there
as
well.
There
is
also
the
open
networking
and
edge
summit
north
america,
which
will
be
in
los
angeles
that
is
coming
up
in
April
April
20
through
21st.
The
CFP
closes
on
Monday
February
3rd,
so
make
sure
you
have
your
talk
ready
to
submit
there
if
you
intend
to
be
in
Los
Angeles
before
before
we
move
on.
A
J
J
It
has
a
couple
of
nice
things,
which
is
where
we're
keeping
track
of
the
issues
and
pull
requests
with
this,
and
so
then
also
that
also
make
it
easy.
So,
if
you're
wondering
about
what
can
you
jump
in
that
that
will
help
push
the
project
forward
in
a
in
a
timely
way,
then
these
are.
These
are
currently
active,
currently
wanted,
PRS
that
that
can
help
guide
you
in
as
well.
So
the
new
SDK,
that's
being
created
should
make
this
stuff
a
lot
a
lot
easier
to
work
with.
J
J
We
are
following
six
more
people
now.
This
is
particularly
interesting,
because
this
is
an
inflection
point.
Where
we
got
more
people
follow
or
following
this,
then
then
I
was
following
others
in
terms
of
the
number
of
changes.
So
that's
that's
a
nice,
an
inflection
point
that
we
just
hit.
We
also
added
12,
more
12,
more
tweets.
J
J
Well
I'll,
add
this
in
as
well
at
7:30
a.m.
pacific
time.
Right
before
this
call,
we
are
holding
an
issues
who
request
meeting
so
these
this
is
purely
for
things
that
are
actively
being
worked
on
they're,
not
architectural
decision
meetings.
Then
we
kept
the
time
down
to
30
minutes
to
prevent
architecture
from
being
discussed,
and
so,
if
you,
if
you
would
like
to
join
in
and
help
ask
questions
or
you'd
like
to
join
in
and
and
trying
to
take
on
an
issue
or
PR,
and
you
need
some
guidance.
This
is
the
meeting
to
do
it.
J
J
We
also
have
some
some
additional
followers
on
on
LinkedIn.
We
have
seven
additional
followers
and
we
cross
posted
everything
from
Twitter
on
Julie
Wow.
Do
you
like
them?
There
are
some
plans
to
to
post
more
about
the
sponsorship.
Rena-San
Conde
you.
So
you
should
see
some
information
on
that
and
when
the
contributor
podcast
comes
out
that
we
will
post
that
as
well
and
with
that
we
we
don't
have
any
hard
items
on
the
agenda.
Is
there
anything
that
anyone
would
like
to
discuss?
I.
A
Would
like
to
call
for
an
update
on
what's
going
on
with
that
Sarah
yeah
I
know
that
the
three
people
that
kind
of
interested
and
driving
this
are
on
the
call
now.
So
maybe
some
update,
if
you
want,
make
an
open,
the
PR
or
whatever
just
I,
think
it's
it's
a
really
important
feature
that
a
lot
of
people
are
hearing
this,
and
so
any
form
of
update
would
be.
K
Some
short
update
for
me,
so
I
finally
managed
to
find
some
time
to
work
on
that
PR,
which
is
success
myself
and
way
better
disappear.
Today,
I,
basically
I
will
buy
some
of
the
latest
master.
Just
the
first
update
beyond
that,
I
introduce
the
new
connection
mechanism,
API
for
the
user
space
and
subsidy
implementation
on
the
on
the
floor.
K
Other
side
as
well
in
terms
of
starts
working
on
the
graceful
release
of
the
function
after
it's
no
longer
needed
being
that
made
a
couple
of
changes
in
regard
to
fixing
some
issues
supported
by
I,
obviously
winter.
Suffice
us
there
are
some
to
do
in
the
cold
yeah.
That's
this
about
this
I
managed
to
find
some
time
to
work
on
that.
Hopefully,
we
continue
to
work
on
that
as
well
and
they're.
Following
this.
L
K
Well,
the
biggest
challenge
I
think
now.
Some
me
that
I
haven't
started
working
on
yet
would
be
the
client
sites
stuff.
So,
for
example,
the
NSM
in
its
psychic
sidecar
needs
to
probably
requests
so
we
interface
so
currently
and
the
master
branch
there's
all
of
hard-coded
stuff
in
there
that
doesn't
allow
for
that
and
what's
currently
included
in
the
pr.
It's
also
kind
of
hard
call
it
at
the
moment
to
request
those
interfaces.
So
we
need
some
higher-level
generic
mechanism
that
will
allow
us
to
request
and
support
this
type
of
mechanism.
K
K
K
Relate
to
various
sections
right
so,
for
example,
the
first
one
is
rated
to
the
third
in
connection
mechanisms
the
floor
order.
Api
then
have
a
3/4
order
itself
and
then
have
some
additional
commit
that
adds
generous
in
the
SDK,
well,
fook
and
so
on.
But
these
are
temporary
and
proof
of
concept.
Changes,
that's
different.
If
you
have
to
refactor
so
I,
don't
know
it's
just
a
matter
of
preference
at
the
moment,
probably
at
this
stage
to
be
sure
to
keep
everything
in
a
single
PR.
D
K
L
But
my
feeling
is
I
actually
kind
of
take
a
different
approach
to
this.
If
we're
looking
for
some
collaboration
and
to
get
some
traction
here
amongst
a
number
of
developers,
it
might
make
sense
to
figure
out
how
we
can
break
apart,
what
you
have
into
smaller,
more
consumable
PRS,
but
maybe
I'm
in
the
minority
here
I,
don't
know
what
others
are
thinking
right
now
or
maybe
present
make.
You
feel
strongly
for
a
reason
that
I'm
not
aware
of.
J
So
I
have
some
advice
on
this
as
well
that
well,
if
presume,
it's
not
ready
for
it
helped
because
of
current
state.
It's
something
that
could
use
some
help
is
potentially
with
so
we're
migrating
things
from
the
network
service
to
mesh
primary
repo
into
an
SDK
set
of
SDK
repos.
One
of
the
repos
is
an
SDK
Colonel
repo
and
a
lot
of
the
things
that
the
use
case
are
exactly
the
same
way
as
you
would
in
the
kernel
space.
J
F
J
Can
depend
on
things
or
when
we
propose
what
we
compose
the
yes
or
the
plug
to
the
runnable
plugin,
then
we
will
be
able
to
us
to
interlace
the
two
things
together
and
not
get
duplication
of
code,
so
that
may
be
an
area
where
we
may
help
and
I
believe
there's
people
on
this
call
who
are
working
on
that.
That's
DK
kernel
and
speak
more
as
to
whether
whether
they
need
help
in
that
space
here
as
well.
I.
L
Had
chatted
with
Ed
about
this
yesterday,
I
was
actually
going
to
take
a
crack
at
that
I
don't
know
if
anyone
else
is
working
on
that
I
may
be
out
of
the
loop
there,
but
I
I
was
actually
going
to
start
looking
at
that
to
go
along
with
this.
So
if
that's,
if
that's
useful
and
sounds
like
this
kind
of
dovetails
with
sr
iove
work,
I
guess
I'll
just
focus
my
efforts
there
right
now
and
yeah
presented
goods
yeah
when
you're
ready,
reach
out.
J
So
yeah
and
and
will
will
sink
off,
will
sink
offline
on
the
STA
sdk
kernel
stuff,
and
what
we'll
do
is
well
we'll
make
sure
that
things
are
populated
in
that
project
board.
Then
we
posted
in
the
announcements
section
we'll
make
sure
that
those
things
get
populated
there
as
well
and
we'll
see
if
there
we
could
find
an
easy
way
to
label
valve
or
to
make
it
clear
that
this
is
stuff
to
me
in
the
kernel
or
or
other
projects
as
well.
There
were
other
other
sub
repos.
A
My
my
my
point
of
view
here
for
this
PR
is
that
this
is
a
very,
very,
very
experimental
for
the
time
being,
I
get
that
I
also
get
that
it's
slowly
strive
is
kind
of
taking
shape
and
getting
into
some
form
that
can
be
merged.
I
would
really
prefer
if
we
can
have
this
split
it
into
smaller,
at
least
chunks.
A
A
A
Probably
we
have
some
some
common
place
where
we
can
discuss
these
ideas,
because
I
agree
that
seeing
code
is
is
the
best,
but
maybe
if
before
we
go
and
delve
into
code,
we
need
to
discuss
the
ideas.
Otherwise
it
could
be.
We
kind
of
can
end
up
losing
time
in
doing
things
that
not
that
don't
get
upstream.
A
A
A
Can
we
can
figure
out
tissues
assigned
to
people
that
want
to
do
these
and
try
to
move
this
one?
It's
really
really
exciting.
I'm
sure
that
a
lot
of
the
people
that
are
here
on
the
call
and
probably
will
be
watching
this
I'm
going
to
be
excited
about
of
this
work,
and
everyone
is
anxious
to
get
this
sub
stream
as
soon
as
possible.
A
Saying
this,
and
also
taking
like
this
idea
for
heavy
cast
back
into
account.
Can
you
please
consider,
if
you're
not
able
to
share
this
now
to
dump
your
thoughts
on
what
is
missing
and
how
we
want
to
change,
or
you
want
to
change
like
the
upstream
necessary
will
be
device
plug-in,
because
I
know
that
there's
there
were
some
things
going
on
there.
Some
changes
that
we
wanted
to
happen,
some
things
that
you
did
in
your
private
branch,
so
I'm
not
sure.
A
K
K
H
A
A
K
So
for
now,
some
time
ago,
I
discussed
with
that
possibility
turns
out
something
like
new
mechanism,
therefore
automatically
binding
and
unbinding
devices
from
the
from
the
kernel
modules.
For
the
moment,
I
don't
think
we
need
it.
Maybe
at
some
point
the
future.
It
would
be
a
nice
addition,
but
it's
definitely
not
needed
to
progress
PR
for
anything.
A
J
J
J
So,
if
you're
willing
to
hop
on
and
write,
you
know
test
up
on
any
of
these
things.
That
would
be
hugely
hugely
helpful
and
if
you
want
any
information
or
help
getting
started
with
that,
let
us
know
help
you
out
and
with
that
I.
Don't
have
anything
else
on
the
agenda
if
any
one
last
fall
for
any
additional
items,.