►
From YouTube: Network Service Mesh PR Review Weekly Meeting 2020-05-19
Description
Network Service Mesh PR Review Weekly Meeting 2020-05-19
A
B
A
A
Sound
like
my
relationship
with
certain
other
web
conferencing
products
that
will
remain
nameless,
there's
one
in
particular.
That's
infamous
I
literally
can't
use
it
because
every
time
I
try
and
use
it.
It
says
you
have
to
update
your
client
click
here
to
download
so
I
click
there
I
download
the
client
and
then
I
go
back
to
login.
With
that
cloud
it
says
you
have
to
update
your
client
and
so
effectively.
A
B
A
You
well,
and
the
versioning
stuff
is
hard
like
I
know
you,
having
talked
to
some
of
the
various
guys
in
WebEx
like
they
they've
got
all
kinds
of
things,
depending
on
where
various
clients
are
around
versioning.
It's
not
an
easy
thing
and
I
involved
with
other
software
projects
that
are
not
even
even
nod.
Sas
software
projects
and
once
was
involved
with
one
that
had
an
entire
director
level
organization,
did
nothing
to
keep
track
of
the
versions
which
is
just
madness,
but
you
know
madness
happens.
B
This
doesn't
surprise
me:
I
used
to
take
I
used
to
do
Windows
updates,
might
do
it
by
starting
a
baseline
of
the
entire
file
system.
Installing
a
software
take
a
second
baseline
dip
them
deliver
that
of
the
package.
It
was.
They
got
all
the
registry
units
and
everything
else
you
could
possibly
think.
Oh,
then
they
could
surely
do
the
system.
Nothing
was
left
untouched,
yeah.
E
A
Cool
so
we'll
work
really
quickly
left
or
right
to
left,
so
the
reviews
in
progress,
I
think
I'll.
Let
me
get
back
to
those
two
on
the
in
progress
column.
Most
off
we've
got
a
few
things
that
have
come
up.
It's
bugs
actually
in
the
model,
repo
and
and
thank
you
all
for
being
so
responsive
to
people
who
raise
those
issues.
A
One
of
the
things
things
that
from
a
community
perspective,
gives
us
the
space
to
do
the
fun
refactoring
work
is
the
fact
that
we
have
working
code
that
people
can
kick
the
tires
on
and
that
we're
responsive
as
they
kick
those
tires.
So
it's
super
important
to
continue
to
you
know,
fix
bugs
over
there
and
respond
to
issues,
and
you
guys
have
been
great
about
it.
So
we've
got
well
this
one
here,
which
I
think
you've
picked
up.
Denise
on
the
bulk
registry
and
I,
see
in
the
model
Reba
Oh.
C
A
Responsiveness
has
been
fantastic,
it's
excellently
done,
I
mean
it's.
It's
really
interesting.
I
had
a
team
once
and
and
I
remember
pointing
them
to
a
particular
set
of
research,
because
the
team
was
really
struggling.
They
were
much
worse
shape
than
any
other
team
of
dog
worth
I
mean
we're
in
pretty
good
shape.
They
were,
they
were
really
struggling,
and
one
of
the
points
that
I
made
to
them
was
that
there's
actually
really
good
research
that
people
care
more
about
being
heard.
A
C
A
F
A
It
was
probably
it
simple
requests:
okay,
it's
the
pull,
request,
referencing
the
issue,
so
we
can
find
it.
No
we'll
have
to
go
look
for
the
pull
request,
but
there
we'll
get
there
I'm
sure
we
got
a
long
list
still
to
go,
but
there's
been
some
good
movement
forward
on
the
OPA
policy.
Stuff.
I'm
actually
super
pleased
by
that
so
Denise
on
the
industrial-grade,
bl3
I
know:
we've
been
talking
a
lot
in
the
last
week
and
you've
been
progressively
refining.
C
C
A
C
C
A
I
appreciate
the
link
to
draw
that
IO
because,
quite
frankly,
like
I
have
my
places.
I
could
use
this
in
talking
to
people.
It's
actually
nice
that
you
shown
three
domains,
because
it
turns
out
that
the
two
domains
is
easier
to
represent,
but
it
actually
really
doesn't
convey
the
fullness
of
what's
going
on.
So
yes,.
C
A
Yeah
and
illogically
right
here,
like
this,
looks
really
complicated,
but
launching
it
is
absolutely
correct.
The
trick
is
a
whole
lot
of
things
in
here.
I
think
when
we
get
to
the
point-
and
we
don't
have
to
do
this
out
of
the
gate
where
we
introduce
a
caching
chain
element
for
the
registry
lookups,
a
lot
of
these
new
calls
will
fall
off
because
they'll
hit
the
cache.
A
C
A
Ready
done
printer,
it's
been
doing.
Some
preliminary
work
on
some
of
that
and
IPM
is
is
super
interesting
because
normally
in
our
domain,
IPM
is
really
really
hard,
but
I
think
because
of
the
way
that
network
service
mesh
is
doing
this,
we're
going
to
get
a
situation,
that's
substantially
easier
than
it
usually
is,
and
the
reason
is
because
normally
when
you're
doing
it
or
domain
ipam,
what
you
have
is
you
have
n
domains
you're
trying
to
reconcile
n
different
IP
domains
with
each
other.
A
So
you
basically
you've
got
to
reconcile
the
power
set
of
all
the
all
BN
domains
and
that's
a
nasty
factorial
problem.
In
that
we
service
mesh.
You
only
have
to
reconcile
through
the
IPAM
pairwise,
between
the
floating
VL
3
domain
and
on
each
of
the
N
domains.
So,
instead
of
having
an
N
factorial
problem,
what
you
have
is
a
problem
that
is
much
much
much
smaller
and
your
propensity
to
get
lucky
is
going
to
be
much
much
much
greater.
B
Yeah,
that's
already
implemented
it's.
It's
called
the
the
point-to-point
item
and
another
thing
that
we
did
as
well
as
we
separated
out
the
the
journaling
of
of
what
IP
addresses
are
used
in
two
separate
space,
and
so
of
course
the
iPad
needs
to
manage
its
own
set
of
its
own
list.
But
you
can
use
the
journal
to
replay
and
work
out
what
IP
addresses
are
assigned.
Yeah.
A
And
the
point,
the
point,
depending
upon
the
journal
is
going
to
be
super
super
useful
for
the
individual
VL
3
is
managing
the
blocks
that
they're
issued
for
the
field.
3
domain
I
think
the
thing
that
we,
unless
I'm
misremembering
I,
think
the
thing
we
still
need
to
do
on
IPM
is
the
fact
that
a
given
DL
3
domain
is
going
to
have.
You
know
you
really
have
to
have
something
somehow
that
is
issuing
blocks
to
the
bl3
and
Assis.
B
A
B
Not
implemented
that
and
I
have
not
implemented
a
recover
on
on
the
from
the
journal,
yet
so
the
journal
is
created
and
it's
actually
storing
that's
and
they.
Yes,
it
is
so
we
need
to
have
something
that
can
also
recover
and
replay
the
journal
as
well.
So
those
are
they.
Those
are
the
two
gaps
are
yep.
A
And
I
think
the
thing
is
we
basically
also
need
to.
For
the
most
part,
we
need
trying
to
keep
things.
You
know
moving
forward
and
simple
steps
right.
So,
for
example,
the
journaling
in
that
stuff,
that's
gonna,
be
super
crucial
for
forgetting
to
real
industrial-grade.
It's
probably
not
the
very
first
step
right.
The
very
first
step
is
probably
the
point
deployed
IPAM
with
something
simple
to
issue
a
IP
addresses
out
to
it
right
and
then
you
start
bringing
in
the
layers
of
additional
stability
into
the
system,
make
sense.
C
A
Cool
all
right,
excellent,
and
we
should
probably
also
then
once
we
started
interesting
things
like
mats.
We
may
end
up
having
a
conversation
with
Andre,
basically
about
whether
or
not
bl3
needs
an
operator
which
it
may
write,
not
directly.
A
network
service
meshes
issue,
but
it
may
so.
This
is.
This
is
excellent.
Work
I
appreciate
this
cool.
The
wire
guard,
EPP,
plug-in
or
anything
else
and
it'll
strip
reveal
three
abilities
before
we
move
on.
E
E
A
E
E
E
E
A
C
A
You
see
what
the
software
is
doing,
but
at
the
end
of
the
day,
if
you
don't
see
it
on
the
wire,
it's
not
true
and
that's
why
I'm
so
pleased
that
you
were
using
wire
guard
a
Wireshark
to
make
sure
that
you
weren't,
seeing
the
packet
sent
back
from
the
wire
guard
go
server
because
that
tells
you
really
really
it
didn't,
send
it
right.
All
kinds
of
things
can
be
squirrely
about
the
debug
messages
that
might
deceive
you.
A
But
if
it's
really
not
on
the
line
that
on
the
wire
that
it's
really
not
on
the
wire,
because
when
you
look
at
the
places
that
this
can
break
down
right,
you've
sort
of
gone
through
and
done
a
great
job
of
debugging
it
right,
you
sent
the
handshake
packet.
You
used
Wireshark
to
see
that
it
arrived.
You
use.
The
debug
logs
in
wire
guard
go
to
see
that
it
arrived.
A
You
use
the
bug
logs
to
see
that
you
didn't
send
a
response
used
wire
guard
to
CPU
didn't
send
response,
so
you
know
that
your
problem
is
somewhere
in
that
packet,
as
opposed
to,
if
you
would
not
been
so
diligent
in
your
debugging,
it's
possible
that
the
packet
was
being
sent
and
you
were
losing
it
somewhere
in
BGP.
So
so
far,
you've
done
a
good
job
of
sort
of
drilling
into
the
debugging,
but
you
may
want
to
sort
of
compare
the
the
packets.
E
E
D
A
F
F
A
I'm
also
been
poking
pretty
hard
at
the
actually
super
funny
experience
yesterday,
because
the
as
I
was
debugging
and
getting
things
going
again
with
the
border,
bpp
agent,
I
sort
of
got
to
a
place
where
it
looked
like
the
problem
was
in
the
spire
stuff
that
you
had
updated
turns
out.
No,
the
problem
is
not
in
the
code
that
you
updated
when
I
finally
tracked
it
down.
Your
code
was
doing
the
right
thing.
In
all
cases,
it's
someplace
else
in
my
code
cool,
so
the
metric
stuff
I
think
for
the
moment
is
a
little
bit.
A
F
A
Yes,
yes,
absolutely
so
I'm,
actually
coming
around
a
little
bit
on
that
I
I'm,
coming
around
a
little
bit
on
that
I've
been
poking
at
making
the
whole
docker
things
simpler,
and
so
in
the
course
of
making
that
simpler,
I'm
I'm
warming
to
the
idea
of
potentially
doing
that
there
so
but
yeah
I
definitely
need
to
come
back
to
that.
But
we
can
do
that
a
little
bit.
Yeah
I'm
the
migrating,
the
kernel
for
door
to
new
style
cross
connects
that
were
service.
A
F
A
A
F
F
A
Feel
the
result,
it
definitely
gonna
need
a
little
bit
of
rebasing,
yeah,
so
cool,
and
then
the
we
had
this
one
that
you'd
open
the
noose
on
a
bug
about,
and
this
one
I
think
is
just
you're
doing
an
excellent
job
of
documenting
that
we
have
a
sort
of
a
intermittent
leak
of
goroutines
here
that
we
should
probably
eventually
track
down.
I,
don't
think
this
one's
super
urgent,
but
I
think
it's
important
to
keep
track
of
it,
because
it
will
be
something
we've
been
willing
to
be
fixed,
but
I,
don't
think
it's
blocking
anything.
A
A
A
What
are
you
suggesting
here
and
to
see
what
kubernetes
may
have
done
around
it,
but
we
definitely
want
to
encourage
our
friends
who
are
playing
with
sky
dive.
They've
been
really
good
to
us,
and
it
would
be
good
to
encourage
them
and
to
help
solve
their
problems.
We
also
have
this
thing
that
was
opened
with
the
wrong
test
in
secured
intranet.
I
don't
know,
is
there
any,
you
know?
Is
there
anyone
who
can
take
a
look
at
this.
A
Okay,
he
looks
like
he
wants
to
submit
the
PR
himself,
so
let's
leave
into
that
and
then
there's
this
that
I
think
it's
legitimately
a
bug.
That's
been
raised
by
Albrecht
I
can't
pronounce
this
name
there
or
is
it
you
get
have
idea
effectively
he's
got
a
problem,
and
this
one
we
really
probably
should
get
someone
on
the
mono
repo
effectively.
His
problem
is
that
he's
connecting
to
two
network
services
and
it
looks
like
he's
getting
two
connections
to
the
same
network
service
instead
of
to
the
two
distinct
network
services.
A
A
Cool.
Thank
you
very
much
appreciate
it,
because
that
you
see
from
the
comments
I've
managed
to
confuse
myself
very
badly
about
this
one
and
I
think
the
rest
of
it.
We
should
probably
go
jump
on
the
other
call
because
he
can't
start
without
us
yeah,
but
I
think
we've
gone
through
enough
for
today.
Well
we'll
go
done
with
the
community
call
start
see
there.