►
From YouTube: CNCF Network Service Mesh Meeting 2019-12-17
Description
CNCF Network Service Mesh Meeting 2019-12-17
A
So
welcome
everybody
I'm
going
to
go
ahead
and
put
a
link
to
the
meeting
minutes
in
the
chat,
so
you
can
see
the
agenda
and
also
so
that
folks
can
add
themselves
to
the
attendee
list.
We
usually
start
about
five
after,
but
please
do
be
aware
that
the
entire
meeting
is
being
recorded
and
it
will
be
posted
to
YouTube.
Thank
you
very
much
Ivana
for
sharing
the
the
agenda
in
the
meeting
minutes.
Welcome.
A
B
Interestingly,
some
of
our
best,
some
of
our
best
meetings,
have
started
with
no
agenda,
so
I,
don't
don't
feel
like
if
there's
an
agenda
posted
there
like
don't,
don't
feel
like
you
shouldn't
or
that
you
shouldn't
post
anything.
It's
you're
definitely
welcome
to
have
anything
that
that
you
feel
should
be
spoken
about
know.
A
Definitely
sort
of
reminds
me
of
my
background
is
in
string
theory
and
when
I
was
a
graduate
student
that
was
of
the
Rutgers,
which
at
the
time
was
the
number
two
place,
letter
string,
theory
and
the
way
they
ran.
Their
group
meetings
was
in
the
same
style
as
Quaker
spirituals,
which
is
to
say
that
everyone
met
a
given
time
in
their
common
room,
and
you
sat
there
in
silence
and
you
waited
until
someone
was
moved
to
speak.
A
A
B
B
And
let's
also
get
started
so
welcome
to
the
next
network
service
training.
We
have
a
weekly
meeting
every
Tuesday
at
8
a.m.
Pacific
time.
We
also
participate
in
the
scenes
here.
Telecom
user
group,
which
occurs
every
first
Monday
at
8
a.m.
and
I,
was
gonna,
be
a
first
Monday
at
8
a.m.
Pacific
and
third
Monday
at
3
a.m.
Pacific,
and
the
next
call
was
yesterday
at
we
also
have
sorry.
That's
probably
I
want
to
check
to
see
if
they're
doing
anything.
B
D
E
D
B
B
C
B
B
We
have
FOSDEM
2020
coming
up.
There
is
an
SDN
room
which
is
going
to
cry
Fonz
down,
which
is
in
February.
First
and
second,
there
is
a
cubic
online
cloud
native
con
Europe
at
Amsterdam,
coming
up
on
March
30th
through
April
2nd.
The
call
for
proposals
is
now
closed
and
the
notifications
will
go
out.
Approximately
January
12
there
is
a
there
is
a
msn
con
fq
con
tu
that
we're
looking
to.
They
would
look
what
you
set
up.
So
we
will
post
information
about
about
this.
As
time
goes
on.
You
know.
A
The
wheels
are
starting
to
turn
on
that,
but
we
need
to
get
up.
You
know
the
event
site,
the
CFP,
the
prospectus
for
sponsors
etc.
But
if
you
are
interested
in,
if
your
company
is
interested
in
sponsoring
an
SM
con,
it
may
be
a
good
idea
to
just
start
warming.
The
idea
part
of
the
reason,
two
perspectives
as
an
up
is
we're
still
working
through
sort
of
budget
and
therefore
sponsorship
levels,
and
that
kind
of
thing.
B
Yeah
strongly
strongly
recommend
taking
a
getting
that
set
up
with
your
with
your
budget
and
also
if
you
would
like
to
speak
to
start
thinking
about
what
you
would
like
to
speak
about.
It's
been
unfortunate,
but
the
pine
for
Keep
Calm,
it's
a
bit
sooner
than
usual
at
least
rated
for
the
mm
one.
So
you
definitely
start
thinking
about
about
potential
pockets
as
well.
B
B
E
With
holidays
and
post
cube
con
this
week
was
a
little
slow.
We
got
one
new
follower,
followed
seven
more
folks
and
posted
six
times
this
week.
We've
got
some
things
scheduled
to
go
out.
We
have
posted
the
keynote
videos
from
network
service
mask
on
and
a
high-level
session
videos,
as
well
as
a
new
stack
article
that
was
featuring
network
service.
Mesh
links
to
those
are
in
the
meeting
notes.
E
E
Well,
we've
got
about
10
things
scheduled
to
go
out
in
between
now
and
the
20th,
so
there'll
be
an
increase
in
activity
on
that
spy.
And
aside
from
that,
if
the
contributors
podcast
is
available,
we
can
post
a
link
to
that
and
once
we're
ready
to
share
the
day
zero
event
at
networks,
a
cube
con
Europe,
we
can
post
save
the
dates'
and
sponsorship
available
and
sign
up.
B
Thank
you
very
much
yeah
cheering
there.
The
videos
have
been
posted,
including
the
slides
and
the
announcement
section
of
the
agenda.
You
will
find
a
link
to
the
NSF
home
video
video
site.
I,
don't
know
if
that
the
youtube
link
so
there's
a
new
label
believe
everyone
on
YouTube
leaflets
in
the
enamels.
B
A
Yeah
there's
a
channel
for
MSM,
so
it
turns
out
on
the
NSM
Khan
page.
If
you
go
to
the
other
seven
comm
page,
all
the
videos
are
linked
from
the
individual
talks
and
each
of
the
talks
is
individually
linkable.
So,
for
example,
if
you've
got
to
talk,
you
want
to
point
someone
to.
If
you
go
to
the
NSM
comm
page
and
the
network
surface
mesh,
io
events
page
that
will
give
you
you
keep
tickling
for
the
talk
you
can
give
it
to
someone
it'll
point
them
to
the
talk
who
the
speakers
are.
A
The
slides
and
a
link
to
the
videos
and
the
links
to
the
videos
from
the
MSM
comm
page
are
all
within
the
context
of
the
playlist
for
the
entire
day.
So
it
is
really
the
one-stop
shop
for
hey
I
want
to
go
and
find
out
about
something
or
I
want
to
go
point.
Somebody
at
something.
The
other
thing
I'll
point
out
is
apparently
the
current
winner
in
the
who's.
Getting
the
most
views.
B
C
B
A
D
A
E
A
E
A
Yeah,
it's
being
a
drama
queen
about
it
basically
effectively.
What
appears
to
be
happening
is
there's
some
kind
of
a
hiccup
going
on
with
packet,
so
in
the
packet
guys
are
hugely
responsive
to
such
things.
We
did
go,
find
out
what's
happening,
but
there
was
apparently
a
change
where
it
used
to
be
that
if
every
element
of
a
particular
cluster
failed-
and
you
ended
up
skipping
all
the
tests
for
those
clusters,
because
you
had
no
place
that
it
wouldn't
report
the
skipping
justice
bailed,
it
would
just
report
that
cluster
elements
were
failed.
A
So
you
could
see
there
was
a
problem.
You
can
see
what
the
problem
was,
and
you
know
it's
the
overall
job
failed,
but
you
could
easily
tell
it
a
glance.
Oh
pocket
is
having
an
issue
and
apparently
that
behavior
chip
did
too
reporting
the
skipped
tests
has
failed.
So
now
it
looks
dramatically
bad
because
packet
went
down
and
therefore
127
tests
failed,
but
they
were
never
run.
They
didn't
really
fail.
A
They
just
got
skipped
because
we
couldn't
run
them,
and
you
know
overall
that
true
to
fail
the
job,
but
it
shouldn't
report
to
you
that
the
whole
world
is
on
fire
in
the
same
way.
So
the
CI
is
having
issues
we
are
looking
into
it
and
it
was
going
to
look
very
dramatic
until
we
figure
out
what's
going
on
with
packing.
A
A
Well,
what
a
lot
folks
know,
because,
particularly
with
the
difference
in
reporting,
people
could
get
really
freaked
out
that
they
somehow
their
PRS
had
done
terrible
things
to
the
world
and
no
I
mean.
Maybe
your
PR
has
done
terrible
things
to
the
world.
That
could
also
be
trail,
but
it's
much
more
likely
that
you're
hitting
this.
A
It
talks
about
them
and
there's
also
a
link
to
the
activity
diagram
that
sort
of
details
how
the
healing
works
for
them
and
it's
a
huge
simplification
of
the
healing
process
and
I
I'm
intending
to
be.
You
know
doing
some
of
the
work
on
getting
there
over
this
break.
But
I
wanted
to
make
sure
that
folks
took
a
look
number
one.
So
they
can
sort
of
call
out
where
this
is
going
and
number
two
you're
just
just
to
expand
awareness.
But
it
turns
out
to
be
a
massive
simplification.
A
I
I
sat
down
and
I
wrote
the
sort
of
SDK
snippet
for
the
piece
that
does
healing
and
I
can't
say
for
sure.
Cuz
I,
haven't
put
it
in
full
context.
To
grade
should
test
it,
but
it
looks
like
healing
is
now
a
single
file
of
a
hundred.
Approximately
a
hundred
lines
is
a
hundred
percent
of
the
healing
process,
which
is
an
incredible
simplification.
B
Good,
so
the
motor
line
is
pretty
it's
pretty
simple,
so
this
is
marrying
or
interested
in
I
think
the
whole
thing
comes
in
somewhere
between
700
and
the
thousand
lines
of
code,
or
so
there
was
a
lot
of
amount
that
the
groom
to
have
with
us.
So
if
you're
interested
definitely
definitely
read
through
the
code
and
ask
questions
if
you,
if
you
actually
have
any
little
pop-up
form.
D
B
D
So
sorry,
I
know
what
we
have
much
more
important
things
to
discuss.
We
have
much
more
important
things
to
discuss
so
Cates
because,
on
the
examples
repo
which
is
running
Knightley's,
it
uses
the
latest
kind
kind
already
does
117
as
a
baseline
image.
It's
ok,
it
was
there.
I
have
PR
today,
which
actually
requires
some
changes
in
some
of
the
components
that
we
do,
but
not
in
cremator.
D
It's
there
we'll
probably
try
to
operate
before
Christmas.
If
everything
goes
fine,
you'll
see
for
the
time
being,
we
cannot
verify
it
on
packets,
which
makes
it
impossible,
so
that's
it
so
we're
more
or
less
ready
for
it.
We
just
need
a
couple
of
verifications
and
we
know
that
any
semi
runs
fine.
On
top
of
it.
We
just
have
to
adapt
to
their
PR
API
if
we
want
to
go
fully
117.
Oh.
B
D
C
No,
that's
fine
I'm
not
used
to
zoom
sharing
so
I'm
taking
a
second
here,
but
so
I
think
this
is
the
right.
That's
a
different
presentation,
but
so
the
the
point
of
this
immediate
agenda
item
is
I
have
started
pushing
so
so
II
D
a
while
back
made
some
changes
to
the
API
to
allow
or
what
I
was
I
mean,
essentially
at
the
semantic
level
of
the
API
definition
kind
of
a
lot
of
what
I
was
doing
at
the
VLC.
C
A
C
You
know
in
the
works
for
a
while,
but
it
was
more
just
proof
of
concept
and
then
now
I
farted,
in
changes
to
making
fixes
based
on
rebasing
on
top
of
the
latest,
API
children
and
so
nicholai,
and
it
has
expected.
These
are
like
most
changes
in
nickel
I
had
some
very
real
concerns
on
what
was
what
I,
what
we're
doing
with
virtual
air
3.
C
So
we
wanted
to
discuss
that
in
this
meeting,
and
the
main
topic
is
that
we
are
that
the
the
difference
between
the
normal
NSC
idea
is
that
this
type
of
NSC
needs
to
have
connections
to
other
entities
of
the
same
type
so
in
the
same
network
service.
So
we're
not
we're
not
creating
like
a
new
network
service,
her
NSC
and
having
some
how
to
make
connection
requests
with
that
new
next
network
service.
What
I'm?
C
What
what
I
did
was
I
made
a
virtual
layer,
3
key
NSC,
do
a
find
a
network
service
call
to
the
to
a
network
service
registry
to
find
all
of
the
web
service
endpoints
for
that
Network
service
and
then
pick
out
the
ones
that
was
a
the
virtual
layer,
3
and
Essie's
and
and
do
connection
reflect
those
specific
NSC
so
so
it.
It
looks
essentially
looks
like
that.
C
The
network
service
endpoint
is
kind
of
doing
what
the
another
network
service
manager
would
be
doing,
selecting
NSCs
to
on
a
connection
request
in
firing
off
those
connection
requests
and
that
that
semantics
is
that
I,
you
can't
I,
don't
think
you
can
currently
express
that
in
the
ard
for
network
service,
there's
no
there's
no
way
to
indicate
that
a
specific
NSC
is
going
to
needs
to
connect
to
all
the
other
views
of
that
same
type
or
or
some
maybe
even
a
multi,
multiple
connection.
It
was
per
NSC.
D
Yeah
I
think
that
it
makes
it
slightly
more
clear
to
me
now
so
thanks
so
can
we
can
you
summarize
the
problem
like
today?
If
you
are,
if
you
want
to
consume
the
services
from
the
SDK,
you
effectively,
you're
constructing
a
client,
and
you
tell
the
client,
okay
I
would
like
to
consume
this,
and
that
service
name
like
this
and
then
I'm
sending
these
in
these
little
labels.
And
then
we
let
network
service
manager
to
find
all
the
endpoints
that
are
matching
these
labels
and
then
it
around
Rob
is
there.
A
Would
it
make
sense
in
your
mind,
Tim
to
simply
write
a
snippet
that
does
the
behavior
that
you
need
and
then
you
could
sub
that
in
in
an
appropriate
place,
I
mean
I,
guess
think
the
question
is,
you
know
effectively
or
actually,
okay,
wait,
I
see
where
the
problem
is
the
chain.
The
problem
is
the
view
about
chaining
on
the
endpoint
side,
but
we
don't
have
chaining
on
the
client
side.
Is
that?
Where
the
root
of
that
is
then.
C
Well,
no
I
I
think
it's
more
high
level.
I
think
what
we're
talking
about
is
that
the
role
of
the
NSE
and
in
this
proof
of
concept
is,
is
doing
endpoint,
selection
and
connection
requests
with
that.
You
know
two
exact
endpoints
and
that
is
not
conforming
to
everybody's
idea
of
what
an
NSE
should
do
and
and
so
we're
we
wanted
to
uplevel
the
conversation
on
you
know:
should
this
be
a
NSE
function
and
then,
if
so,
do
we
want
a
way
to
describe
that
this
is
allowed
or
that
this
is
going
to
happen.
A
That
is
the
way
you
happen
to
want
to
do
this
for
yourself
and
what
I
think
I'm
hearing
is
that
we've
got
too
much
going
on
in
one
of
the
snippets,
where
it's
both
doing
yeah
I,
wouldn't
mark
a
single
snippet
with
all
the
possible
ways
that
somebody
what
might
want
to
connect
their
NSC
to
someone
else.
That
strikes
me
as
likely
the
wrong
solution.
Does
that
make
sense.
A
A
C
What
I
mean
and
I
think
I
think
it's
the
first
I
mean?
Are
you
I
don't
want
to
bypass
the
Nikolai's
concern
on
when
a
you
know,
an
NS
manager
is
operating
on
a
G
RPC
request,
that's
a
network
service
request
and
it
has
fully
filled
wild
endpoint
information.
You
know
what
what
should
it
be
checking
author,
essentially
allowing
in
that
scenario
like
what
does
it
have
any
authors?
It
you
know
when
we
get
the
functionality
you
know.
Is
that
no.
A
You
want
to,
and
the
way
I've
been
thinking
about
that
issue.
Frankly,
is
it's
an
issue
of
policy
because
I
could
see
not
generally
on
wanting
to
allow
that
you
know
you
would
certainly
want,
as
a
matter
of
policy
to
say,
I
actually
want
things
to
go
to
where
the
a
network
service
manager
is
directing
them
right.
A
I
could
see
that
as
a
policy
issue,
but
we're
clearly
going
to
have
to
have
some
policies
if
for
no
other
case
than
the
case
of
healing
that
permit
that,
because,
if
a
client,
if
a
network
service
manager
goes
down
and
comes
back,
it
has
no
idea.
What's
going
on
and
the
client
basically
reconnects
to
it
and
says:
hey
man
I
had
this
disconnection
and
here's
the
path
and
you
can
see
there
where
there's
the
authorization
token
you're
stuck
in.
A
Obviously
in
that
case,
then
we
ought
to
respect
the
specified
network
service,
endpoint,
so
I.
Think
probably
we
want
to
factor
that
out
too,
like
OPA
policy
in
general,
and
then
you
could
say:
okay,
we're
gonna
we're
gonna
run
with
a
default
policy
that
allows
certain
things
or
not.
So
we
could
set
up
with
default
policy,
but
then
it's
up
to
the
user,
who
they
want
to
allow
to
behave
in
different
ways.
Does
that
make
sense
at
all.
D
A
bit
lost,
can
you
can
you?
Please
show
slide
17,
because
there
you
have
three
points,
yeah
so
effectively
the
way
that
I
see
it.
Is
that
the
note
a
wants
to
say
I
want
to
connect
to
all
the
other
indices
that
are
from
the
same
type
whatever
that
means
like
for
us
for
a
certain
type,
and
it
doesn't
know
how
many
are
there.
It
doesn't
know
their
labels,
it
doesn't
know
anything
about.
It
only
knows.
Okay,
there
are
certain
aliases
living
out
there.
D
I
want
connections
to
all
of
them,
and
you
take
me
what
we
can
express
in
our
SDK
in
our
API
that
we
have
there.
It's
like
I
want
to
connect
to
any
dot
matches,
and
it's
only
one.
You
don't
know
how
many
are
out
there.
That's
for
me
the
problem.
So
if
we
have
a
notion
in
the
SDK
where
we
can
tell
the
network,
so
it's
major.
Please
return
me.
Whatever
connections
are
out
there
to
all
of
these
that
are
matching
that
will
solve
the
problem.
If
this,
in
this
particular
case,
is
there.
B
The
would
something
that
would
help
me
understand
a
little
bit
more
as
well
is
to
understand
one
of
the
use
cases
behind
this
as
well.
I'm,
not
trying
to
invalidate
the
concept
that
skirts,
the
the
opposite,
like
maybe
a
little
bit
more
understandable
as
to
what
we're
trying
to
what
we're
trying
to
solve
sure.
C
I
mean
so
the
original
use
case
that
we
came
started
with.
Was
you
know
we
have?
We
have
the
idea
so
at
Cisco
we
are
interested
in.
You
know:
multi
cloud
solution,
Minoo
interconnecting
application
services
in
multiple
clouds,
so
we
we
we've
been.
We
have
some
VPN
related
type
solutions
where
we
essentially
set
up
inter
cluster
odd
networking
across
you
know
a
VPN
tunnel
or
dmvpn
using
like
the
transit,
be
PC
or
something
like
that.
C
But
that
goes
that
good,
you
know,
has
a
lot
of
security
problems
in,
and
so
we
liked
an
sm,
because
we
could
operate
on
the
workload
level
right.
So
we
can
have
network
services
that
bind
to
specific
application
pods
in
in
in
different
clusters,
and
then
we
could
create
a
a
NSE
that
would
n
SC
type.
That
would
you
know
we
could
hide
the
semantics
for
inter
cluster
communication,
or
at
least
inter
cluster
routing
behind
that,
and
then
in
NSM
also
has
the
data
plate
functionality
to
do
the
cluster,
where
we
could
add.
C
You
know,
inter
cluster
connectivity
value
as
well.
So
this
is
the
use
case
like
we
want
like
where
you
data
based
products
as
an
example,
but
we
want
to
be
able
to
have
specific
workloads
in
different
clusters
to
communicate
only
with
the
with
amongst
each
other
via
NSM.
We
don't
want
to.
We
don't
want
to
expose
the
entire
kubernetes
cluster
network
to
another
cloud,
so
does
that
make
sense,
yeah.
B
I
think
so
let
me
let
me
give
one
concrete
example
and
tell
me
if
I'm,
if
I'm
correct,
so
you
might
have
a
database
that
I
came
to
multiple
other
databases
on
multiple
clouds
and
so
in
order
for
the
database
to
work
like.
Let's
say
that,
there's
you
set
it
up
with
like
with
five
replicas
HNH
on
a
different
ya.
C
B
Or
cloud
or
so
on,
and
so
you
need
that
database
to
be
able
to
talk
to
all
other
four
instances
in
order
to
in
order
for
it
to
operate
properly.
And
what
you're
trying
to
do
is
saying.
Please
give
me
a
connection
to
all
of
them
so
that
I
may
communicate
with
them
directly
and
not
have
to
communicate,
would
just
switch
just
one
is,
is
that
is
that
correct?
Exactly.
C
You
you
know
for
whatever
geo
redundancy
or
you
know
you
haven't,
wanted
to
have
a
different
app
experience.
So
you
have
you,
but
they
all
need
to
access
some
replicas
from
this
master,
and
you
you
just
you,
wanted
to
kind
of
have
the
same,
a
private,
replicas
and
network
which,
with
this
with
this
ended
when
that
was
hope
you
were
thinking
of
for
NSM,
virtually
or
three
as
a
as
a
concrete
example.
B
Okay
and
so
a
bit
mikkel
I
correct
me
if
I'm
wrong,
so
without
the
NSM
SDK.
If
we're
doing
this
manually,
we
can
get
a
list
of
all
the
implants
that,
from
from
the
from
the
register
so
and
then
from
there,
then
so
we
do
I
believe
we
do
have
a
manual
path
to
to
make.
This
happen
functions
to
correct.
D
Yes,
what's
implemented
here,
my
objection
to
this
approach
is
that
specifically,
this
example
is
pretty
important.
Everybody
is
looking
at
this.
Whatever
we
set,
this
is
example
of
how
we
use
NSM
is
going
to
replicate
very
quickly.
That's
my
my
understanding
can
my
belief.
So
we
should
be
very
careful
with
what
message
we
send
with
this
specific.
A
B
Yeah,
that's
that
falls
along
my
thinking
as
well
to
keep
the
simple
the
simple
use
case
that
simple
as
possible,
because
that
should
cover
95
or
more
percent
of
most
people's
usage,
but
when
you
describe
is
also
important.
So,
for
example,
I'll
give
you
an
example
of
a
client
where
this
is
important
as
well.
B
So
when
you
want
to
connect
to
a
CD
I
have
a
client,
you
can
specify
multiple
servers
that
you
to
connect
to,
and
this
is
so
that
if
one
server
goes
down,
you
can
immediately
ask
another
server
to
continue
on
with
your
your
request.
You
don't
just
you,
don't
just
lose
your
connection
and
have
your
client
break
on
you,
and
so
there's
also
use
cases
from
the
client
side,
where
certain
databases
that
are
designed
for
a
che
may
also
have
some
other
silver
type
of
requests.
B
But
you
know,
generally,
you
do
not
generally
connect
to
all
of
them.
You'd
only
collect
two,
maybe
two
others
so
usually
no
more
than
three
well
in
your
face
of
FTE.
You
definitely
want
xcd
nodes
connecting
to
through
all
others,
because
when
they
do
their
votes,
they
need
to
make
sure
that
they
can.
They
can
handle
their
and
their
votes
properly,
even
with
you
and
once
they
switch
over
to
talking
back
to
their
single
AJ
master
again.
B
C
The
definition
of
the
you
know,
network
service,
in
this
proof
of
concept,
is
really
simple.
Like
it's,
it's
just
the
the
default
match
or
the
default
route
goes
to
the
individual,
the
the
single
virtual
layer,
three
NSC
type
and
then
the
you
know
and
any
other.
If
we
had
any
other
network
services,
we
would
probably
would
add
them
essentially
before
the
media.
Sorry,
if
we
had
any
other
network
service
endpoint
types,
we
would
add
them
in
the
definition
prior
to
that
and
as
the
virtual
layer-3,
NSE
and
so
the
chain.
C
A
I
mean
I
totally
get
what
you're
suggesting
there
and-
and
so
let's
I
think
like
that.
The
thing
that
occurs
to
me
is
that
we
have
this
lovely
thing
with
incredibly
powerful
set
of
matches
in
the
network
service,
but
it's
not
infinitely
powerful
right.
It's
not
going
to
always
Express
everything.
The
way
that
you
would
like
it
to
it's
just
going
to
give
you
a
really
really
good
90
percent,
and
you
can
sort
of
take
two
paths
from
there.
A
My
current
thinking
is
that
what
I
really
want
to
make
sure
we
get
right
here
with
the
BL
3,
is
not
incorporating
arbitrary
complexity
into
the
matching
structure
of
the
network
service,
but
rather
I'd
like
to
make
sure
that
we,
yes
we're
going
to
express
the
oK
you've
gotten
so
complicated
you're
going
to
do
your
own
thing
pattern
that
we
express
it
well
and
cleanly.
Does
that
sort
of
mesh
with
what
I
think
you're
saying
Andre
the
clay.
D
Yes
and
I
if
I
may
I
would
like
to
also
add
a
couple
of
thoughts.
My
cell
phone
is
ticking
easy.
You
know,
okay,
so
it
looks
to
me
that
the
vo
tree
should
be
slightly
more
than
everything
like,
even
if
you
are
able
to
enumerate
all
the
end
points
at
the
current.
You
know
at
that
particular
point
in
time.
D
These
the
number
of
end
points
are
eventually
going
to
change
like
you
should
be
able
to
add
more
like
at
another
cloud,
and
so
maybe
this
is
the
time
to
think
a
little
bit
into
direction
of
operators.
Should
we
have
an
operator
in
our
sdk
a
way
to
like
react
to
active
changes
in
the
number
of
registered
or
not
register
for
endpoints
within
the
service?
Should
we
have
something
like
this.
A
It's
certainly
a
possibility.
I
mean
another
possibility
that
we
may
want
to
consider
is.
If
you
look
at
the
structure
of
our
other
api
over
the
network
service
api.
Is
a
monitor,
connections,
call
yeah.
Okay!
Do
we
do
we
want
to
have
something
like
a
monitor
for
the
registry
so
that,
if
you're
playing
sufficiently
complicated
games
you
gonna
must
to
be
updated
when
a
network
service
changes
you.
B
You
beat
me
to
it.
I
I
was
actually
going
to
suggest
that
we
take
a
look
at
how
and
how
@cd
handles
some
of
these
things
as
well
from
the
client
side,
because
I
could
help
guide
our
our
direction
towards
this,
and
so
one
of
the
things
that
you
can
do
with
which
a
CD
is
you
have
this
concept
of
forget
the
exact
color
that
so
I'm
gonna
make
one
up
that
tries
to
approximate
it.
B
So
basically,
you
have
a
ridges,
a
service
or
a
server
registry,
and
that
registry
will
monitor
for
heartbeats
that
of
the
various
servers
when
it
doesn't
receive
a
heartbeat.
It
removes
it
from
the
list,
so
it
basically
gives
you
a
point
where,
instead
of
having
to
ask
find
a
bunch
of
servers
and
say
hey,
please
tell
me
what
you
think
that
the
state
of
the
world
is.
You
have
a
limited
number
of
systems.
B
You
could
monitor
the
CRD,
but
the
thing
I
don't
like
about
monitoring
the
CRT
directly
is
that
means
we
have
now
tied
the
endpoint
or
the
things
that
want
global
connections
to
monitoring
a
career
in
any
specific,
C
or
D.
So,
while
that
we
provide
a
gr
PC
and
playing
for
this,
that
means
that
if
you
decide
to
implement
using
MySQL
or
some
other
system,
you,
your
toe,
doesn't
break
as
long
as
the
code
was
implemented
properly
for
reporting
out
to
even
develop
changes.
B
A
A
question
so
I
would
say
the
same
way.
They
work
for
monitoring
inter-domain
right
now
across
cloud,
I'm.
Sorry,
monitoring,
connections
across
cloud,
which
is
you
you
make
a
monitor,
monitor,
connections
to
your
PC
call,
and
so
somewhere.
There
is
a
registry
that
you
were
addressing,
and
so,
if
you
pick
a
monitor
a
call
that
you
are
making
the
monitor
call
to
that
registry.
C
C
E
C
B
C
B
And
in
in
the
spirit
of
that,
on
the
familiar
that
we're
happy
with
any
contributions
are
able
to
use,
and
we
fully
understand
and
respect
when
you
don't
have
time
to
do
so
as
well.
So
don't
feel
don't
feel
compelled
to
to
push
on
this.
If,
if
you
don't
feel
like
you
have
the
time
or
or
or
so
on
like,
but
we're
always
appreciative
of
any
contributions.
B
C
D
D
C
F
B
So
the
recordings
are
are
not
posted
automatically
they're
posted
by
by
a
very
nice
person
from
the
scene
CF
who,
who
downloads
it
and
upload
to
manually.
So
my
guess
is:
maybe
she
may
have
gone
on
vacation
or
something
like
that,
but
weakened
Kingdom
and
I've
asked
to
see
like
perhaps
it
was
just
forgotten.
So
we
can
ask
about
that.
Okay,.