►
From YouTube: Meshery Development Meeting (Nov 03rd, 2021)
Description
Meshery Development Meeting - November 03rd 2021
Join the community at https://layer5.io/community
Find Layer5 on:
GitHub: https://github.com/layer5io
Twitter: https://twitter.com/layer5
LinkedIn: https://www.linkedin.com/company/layer5
Docker Hub: https://hub.docker.com/u/layer5/
A
A
All
right,
let's
get
up
and
going
as
I
peruse
the
new
zoo
maps
catalog
apparently
catalogs
are
a
little
bit
of
a
focus
for
measuring
at
the
moment.
There's
a
service
patterns
catalog
being
developed,
aditya
chatterjee
has
been
championing
that
effort,
but
he's
been
looking
for
feedback
before
we
get
officially
kicked
off.
I
just
I
I
I'm
compelled
to
go.
Look
at
what
is
currently
there
and
I
have
to
ask
aditya:
do
you
recall
the
the
link
to
or
the
url
rather.
A
A
But
since
we're
talking
about
catalogs,
so
this
is
you
can
tell
from
the
latin
that
this
is
a
draft.
You
know
an
in-progress
effort
to
publish
a
catalog
of
patterns
and-
and
it's
coming
right
along
the
nice
thing-
is
that
as
we
go
to
publish
other,
create
other
aspects
of
the
site
like
this
modal
here
that
there's
probably
some
reuse
that
can
go
on.
A
So
I
guess
something
which
is
nice,
but
for
all
of
you
that
are
on
the
call
you're
all
aware
of
what
it's
like
to
browse
a
catalog
as
a
shopper
online,
and
that's
basically
the
experience
that
we're
looking
to
present
here
instead
of
clicking.
A
You
know
people
can,
instead
of
adding
items
to
your
shopping,
cart
and
checking
out
you'll,
add
patterns
to
your
meshery
and
import,
which
just
we're
not
there
yet,
but
that
that's
kind
of
that's
the
flow
put
this
link
into
the
meeting
minutes
and
then
we'll
actually
go
back
to
the
meeting
minutes
and
kind
of
welcome
everybody
kind
of
get
get
started.
A
So
we're
five
after
about
20
folks,
on
the
call
anyone
on
the
call
today
that
hasn't
been
on
this
call
before
I've
been
so
success
you.
This
might
be
your
first
time
on
this
call.
We
always
take
a
moment
to
introduce
people
and
say
hi
and
talk
about
how
much
jekyll
on
windows
is
really
difficult.
A
And
success,
if
your
audio
isn't
working,
you
can
certainly
drop
us
a
line
in
chat
but
nice
to
have
you
you'll
have
to
let
us
know
where
you're
calling
in
from
and
put
a
guess
into
slack
or
to
the
chat,
see
if
see.
If
I
hit
it,
I'm
hopeful
that
I'm
wrong.
I'm
hopeful
that
it's
more
like
it's
more
of
a
country
to
the
left
or
to
the
right
there's
a
lot
of
nigerians
here,
which
is
fantastic,
but
we're
lacking
variety
from
representation
from
some
of
the
other
countries,
so
cool
good.
A
Well,
I
hope
I
hope
some
of
my
sarcasm
is
coming
through
success,
but
other
than
that,
I'm
saying
pranav
by
the
way,
if
you
don't
have
your
name
in
the
list,
get
your
your
five
moments
of
internet
fame
drop
your
name
in
the
list.
Also,
now
is
the
time
to
add
any
topics
that
you
might
have.
I
drop
one
down
below
here,
I'm
to
drop
another
one,
just
a
reminder
for
feedback
on
the
service
mesh
catalog.
A
One
last
item,
and
so
we're
just
about
to
get
started,
but
I
noticed
that
our
shield
has
joined
so
and
so
our
shield
sheikh
we're
just
about
to
start
before
we
get
going,
though
we
always
take
a
moment
to
introduce
people
and
say
hi,
get
to
know
them
our
shield.
Do
you
mind
just
doing
a
quick
introduction?
I
know
it's.
It's
really
weird.
You
just
joined
the
call
and
then
all
of
a
sudden
you're
supposed
to
speak,
but
do
you
wanna?
Do
you
wanna
just
introduce
yourself
real,
quick.
A
Awesome
yeah
nice
to
have
you
our
shield,
thanks
for
jumping
in
thanks
for
breaking
the
ice
by
the
way
and
introducing
that's
not
an
easy
thing
to
do
to
just
as
soon
as
you
join
start
to
speak.
That
happened
to
me,
since
I'm
telling
stories
that
happened
to
me.
Yesterday
I
was
presenting
on
the
cncf's
technical
oversight
committee
call.
I
joined
like
seven
minutes
late
because
I
was
busy
doing
measuring
things
as
soon
as
I
joined.
I
heard
them
say
and
and
now
lee
will
introduce.
A
B
A
B
Yeah,
I
hope
my
audio
is
there
because
I'm
traveling
right
now
and
I
might
not
be
able
to
share
my
screen
or
switch
on
the
webcam
so
I'll,
just
give
a
gist
of
what
I
wanted
to
talk
about
right
now,
so
yeah.
The
first
one
is
regarding
the
updates
for
the
state
management
implementation,
which
is
an
ongoing
process
right
now
and
and
some
people
are
actually
working
on
it
also.
B
So
if
you're
someone
who's
interested
in
ui
and
react-
and
you
want
to
contribute
to
this-
then
this
might
be
a
great
point
to
start
so
yeah
we
have
been
like
yeah,
we
are
actually
trying
to
switch
to.
We
are
actually
trying
to
make
a
architectural
overhaul
in
maturity
ui
by
bringing
in
tradex
it's
observable
and
yeah,
basically
to
improve
the
state
management
and
also
the
structure
of
how
the
code
looks
in
measure
ui
as
well
so
yeah.
So
if
you're
interested,
then
you
definitely
have
to
check
it
out
and
yeah.
B
You
can
actually
go
to
the
design
spec!
That's
over
there
to
see
what
are
the
problems
that
we
are
trying
to
address
and
how
we
are
trying
to.
What
is
our
approach
to
address
those,
and
also,
if
you
want
to
know,
if
you
want
to
know
how
to
get
started,
then
the
link
for
the
readme
file
is
also
there,
where
I
have
mentioned
how
like
keeping
in
mind
different
positions
and
yeah
how
to
get
started
with
for
every
one
of
you
guys.
So
that's
something
that
might
be
helpful
and
yeah.
B
So
we
need
some
yeah.
We
definitely
need
like.
It
definitely
needs
a
lot
of
help
and
work
from
you
guys.
So
it
would
be
great
if
you
could
jump
in
and
take
some
of
the
issues
or
tasks
that
are
to
be
done
right
now,
so
yeah
right
now,
we
in
the
state
there
is
a
spreadsheet
called
state
management
implementation
where
we
are
actually
tracking.
B
What
are
the
components
that
are
to
be
built
right
now,
so
the
first
phase
of
what
we're
trying
to
do
over
here
is
to
create
a
globally
reusable
components
and
from
them
we
can
build
on
top
like
with
using
those
things.
We
can
actually
build
complex
components
that
we'll
be
using
in
our
app
as
well.
So
that's
I
can
actually
what
we're
trying
to
do
now
and
there
are
people
who
have
signed
up
on
taking
some
of
the
issues
as
well.
B
So
if
you
feel
like
you
can
take
one
of
these
up,
then
just
feel
free
to
put
your
name
in
the
assign,
stop
and
then
just
yeah
create
open
up
a
pr,
and
let
us
know
in
the
slack
channel
or
even
over
here,
so
anything
would
do
yep
I've.
Also,
there
is
a
description
for
what
what
a
component
like
what
those
components
should
look
like
on
all
those
stuff.
B
But
if
you
are
still
not
convinced,
I
mean,
if
you're
still
not
sure
about
what
that
means,
then
feel
free
to
ask
in
the
mystery
ui
channel
people
will
be
there
to
answer
so
that
that
is
all
about
that
yep.
B
A
Nice,
so
let
me
add
to
what
the
dish
said
by
by
reinforcing
a
couple
of
things.
So
just
I
I
am
going
to
start
measuring
here
in
a
moment.
A
Actually,
I
can't
start
messaging
because
there's
a
bug
we'll
talk
about
that
in
a
second,
but
for
those
that
have
perused,
mescheri's,
ui
or
used
use
the
one
of
two
clients
that
mastery
has
the
the
ui
you'll
have
noticed
a
particular
experience,
we're
trying
to
overhaul
that
experience
in
order
to
do,
and
I'm
just
looking
at
some
screenshots
of
what
that
experience
is
like
you
might
recognize.
A
A
You
might
have
seen
some
cytoscape
js,
there's
a
there's,
a
lot
of
things
going
on
in
the
ui
and
and
rightfully
so
we're
trying
to
create
a
compelling
experience.
We're
trying
to
make
this
confusing
thing.
You
know
infrastructure
layers,
service,
meshes
much
more
comprehensible
to
users
and
thus
far
like
like
any
like
any
software
project
you
get
so
far
along
and
a
lot
of
times.
A
You
need
to
you,
you
have
to
you
get
so
far
along
and
you
you
immediately
start
paying
down
technical
debt
and,
if
you
don't
start
paying
it
down,
you're
gonna
be
in
a
world
of
hurt,
like
six
months
a
year
later
and
so
for
measuring
it's
well.
It's
coming
up
on
two
years
old
in
the
not
too
distant
future,
which
means
that
we've
been
fortunate.
A
I
suppose
it's
the
right
way
of
saying
we've
been
fortunate
enough
to
have
to
re-architect
certain
aspects
of
its
architecture,
certain
implement
certain
aspects
of
its
implementation
and
the
v2,
the
second
version
of
those
different
areas.
It
turns
out
to
be
a
lot
better.
A
lot
more
resilient
and
reliable,
like
well
written,
just
a
lot
more
principles
built
into
how
the
code
is
structured
and
the
project
works
so
at
bat
right
now
or
like
the
or
the
component.
A
That's
currently
under
the
knife
I'm
going
to
try
to
use
as
many
euphemisms
as
I
can
we'll
do.
The
american
at-bat
we'll
do
the
plastics.
I
don't
do
the
surgery
under
the
knife,
so
this
is
undergoing
not
just
this
is
it's
like
not
just
a
facial
reconstruction.
This
is
more.
You
know
major,
like
open
heart
surgery
for
measure
ui,
so
it's
pretty
exciting,
actually
to
be
a
part
of
it.
There
there's
a
new.
What
nation
said
was
that
react.js
is
still
the
foundation.
A
It's
still
the
library,
the
core
library
that's
been
used
for
the
ui,
we're
integrating
in
redux,
thunk
and
redux
observable,
which
will
play
into
some
of
the
statefully
use
cases
that
the
the
new
user
experience
will
call
for
so
jump
in
and
help
what
nitish
is
doing
here
is
breaking
down
the
various
components
of
the
ui.
A
I
mean
it
called
these
kind
of
globally
reusable
components
and
they're
going
through
a
transition
they're
going
through
a
rewrite
and
it's
nice,
because
we're
going
to
move
up
from
what
material
ui
for
to
material,
ui
5
from
react,
js
16
to
17,
if
I'm
getting
my
versions
right
and
so
like
we're
going
to
incorporate
the
observables
incorporate
state
management,
it's
going
to
be
good,
it
needs
needs
help.
A
Some
of
you
that
are
on
the
call
your
names
are
represented
here
and
so
for
those
that
are
on
the
call
do
we
can
we
get
a
little
bit
more
of
a
status
on
this
so
aditya,
since
your
name
is
first
like
are:
are
some
of
these
components
just
well?
Okay,
it's
right
here
done
so
this
one.
This
one
is
in
fact
done
and
is
the
red,
and
then
we've
got
and
so
aditya
you're
out
you're
out
in
the
lead.
You've
got
two
done.
A
E
So
I'm
still
working
on
the
coded
the
coordinator
part.
So
the
thing
is
the
code
editor
component
that
we
used.
I
mean
the
package
that
we
used.
We
can't
use
it
in
the
react
17
that
we're
using
in
the
new
new
structure.
So
that's
what
I'm
working
on
like!
I
am
trying
to
use
the
the
react.
70
version
in
that
so
yeah,
I'm
facing
a
few
issues,
I'm
trying
to
fix
it
so
I'll
contact
I'll
connect
with
nitish
or
anyone
in
the
slack.
If
I
need
some
help.
A
Nice,
that's
great!
Thank
you,
megan!
That's
a
good
update,
yeah!
I
guess
some
of
the
components
aren't
gonna
going
to
try
and
make
the
transition
we'll
have
to
find
some
new
implementations.
Okay,
who
else?
Who
else
has
got
an
update
on
their
effort
here?.
B
So
right
now
for
the
calendar
that
we
use
in
the
performance
profiles
page,
we
use
a
library
called
react
calendar.
So
nitish
said
that
we
might
want
to
look
into
maybe
another
library
to
use.
I
kind
of
forgot
about
looking
into
it.
So
I'll
do
some
research
and
try
to
find
find
another
library
that
we
can
use.
B
Ui
somewhere,
I
don't
actually
remember
that,
so
I
thought
that
if
we
could
use
the
ones
which
come
with
material
then
it
would
probably
be
the
best
for
us,
so
that
was
kind
of
the
reason
why
I
mentioned
that.
So,
if
you're
not
able
to
figure
it
out,
I
mean
if
you
are
not
able
to
find
the
implementation
material
ui,
then
yeah,
then
probably
this
is
the
right
thing
to
do.
C
B
Yeah
we
need
to
look
around
for
other
alternatives
as
well
before
sticking
on
with
this
yeah,
so
I
haven't
really
looked
into
it
that
much
so
I'll
look
into
it
and
let
you
know
sure,
okay.
A
Nice
all
right
anybody
else
want
to
sign
up,
do
so
to
get
to
get
an
idea
as
to
what
it
would
be
like
to
contribute
one
of
these
components.
It's
it's
a
rewrite,
so
it's
not
as
hard
as
creating
something
from
scratch.
A
B
Yep,
actually,
the
idea
is
that
after
we
I
mean
after
we
turn
on
the
switch
that
is
like
after
we
implement
like
get
this
thing
into
production,
then
this
is
supposed
to
be
the
readme
file
global
readme
file.
A
Nice
does
anyone
would
does
anyone
else
mind,
adding
the
tracking
spreadsheet
to
this?
That
would
be
nice
and
something
else.
B
So
as
of
now,
I
don't
I
mean
like
yeah.
Actually,
if
you
think
about
architecture
documentation,
then
that's
something
that
we'll
have
to
write,
but
this
is
about.
I
kept
in
mind
like
I
was
thinking
about
people
who
are
going
to
write
com,
react,
components
and
all
those
stuff
together,
because
all
the
most
of
the
things
that
we
have
to
hook
up
with
the
latex
are
already
done.
So
I
don't
think
there's
anything
that
was
worth
mentioning
over
here.
I.
C
A
Yeah
yeah
too
complex
to
you,
know,
yeah
right.
It
makes
sense.
Okay,
cool
good,
that's
good!
It's
nice
to
see
progress
we
should
start
to.
So
I
know
nitish
is
championing
this
effort
and
he's
planning
on
having
it
be
kind
of
a
consistent
update
week
to
week.
A
B
Yeah,
this
was
something
that
I
just
wanted
to
announce
that
with
next
year,
has
released
version
12
around
a
week
ago,
and
with
that
they
have
introduced
a
new
feature
called
like
they
have
basically
like,
if
you
know
like,
if
you
have,
if
you
have
been
looking
into
the
next
year's,
build
like
the
way
it
happens,
it's
actually
using.
B
So
we
have
actually
been
using
javascript
for
that,
but
right
now
they
have
come
up
with
a
more
efficient
solution.
That
is
there
right
now
using
a
a
rest
compiler
to
build
and
ship
our
next
js
code.
So
that
is
actually
it
next
is
claims
that
it's
five
times
faster
for
building
and
then
three
times
faster
for
the
for
the
development
server,
so
yeah
we
have
to
test
it
out
an
experimental
I
have
like
in
the
new
ui
architecture
implementation
I
have
switched
to.
B
I
mean
I
have
updated
the
next
years
to
version
12
and
but
one
caveat
here
is
that
right
now
they
don't
actually
have
the
support
for
so
we
are
actually
using
graphql
really
relay
as
a
graphql
client.
So
because
of
that
we'll
have
to,
there
is
some
transformation
that
has
to
be
done
in
the
code
which,
actually
babel
was
bubble,
was
doing
it
before,
but
right
now,
as
we
can
as
we
switch
to
a
rest
compiler
they
don't,
they
don't
actually
have
the
support
for
that.
B
B
B
Yeah,
so
the
dependency
updates
were
about
these.
Only
I
like
upgrading
next
years
to
next
year's
12
and
in
future
we
might
also
be
operating
to
react
latest
version
as
well
and
yeah.
Those
were
the
updates
and
like
doesn't
it's
not
worth
to
talk
about
those,
because
it's
mostly
about
the
next
year's
12,
so,
okay.
A
All
right
so
so
the
next
topic
up
was
from
utkarsh
utkarsh
is
has
a
fever,
so
he
is,
I'm
not
going
to
be
able
to
join,
but
this
is
a
good
time
to
talk
about
the
upcoming
v0.60
release,
which
some
people
are
probably
sick
of
us
talking
about.
At
this
point,
it
takes
a
lot
to
get
kind
of
a
significant
release
like
this
out
and
clean
and
working
and
functional
and
bug-free.
A
A
D
A
Installation
yeah
yep,
so
we've,
so
we
just
switched
the
way
that
we're
deploying
mastery
from
using
kubernetes
manifests
directly
to
using
helm
charts.
Helm
comes
with
some
niceties
but
also
some
challenges.
One
of
those
is
like
one
of
those
is
around
exactly
what
we're
seeing
here,
which
is
I'm
running
a
kubernetes
system.
A
A
It's
it's
trying
to
deploy
our
charts
and
then
it's
running
into
conflicts
because
there
are
existing
constructs,
existing
charts
that
were
already
there.
So
resources
like
a
service
account
called
mesri
operator,
is
still
present,
and
so
like
this
kind
of
a
thing,
this
is
one.
This
is
release
blocking,
because
people
can't
start
measuring.
A
But
two
we're
gonna
see
this
in
a
few
places
on
update
on
restart
on
when
we
remove
measuring
I'm
going
to
install
it
again,
if,
if
all
the
artifacts
aren't
removed,
we're
going
to
bump
back
into
this,
so
some
of
the
people
that
have
been
working
on
this
aren't
on
the
call
so
darren
the
vandu
rudraksha
utkar
sam
asuko.
A
F
Lee
can
you
show
the
the
mesh
config
the
version
returning
mesh
config
yeah?
Let's
see.
A
A
F
Okay,
I'll
tell
you
something
that
what
was
the
cause
of
this
thing
in
my
pc?
Okay.
Similarly
to
this,
my
version
was
pinned
to
v0.5.48
and
I
was
facing
issues
with
this
system
start
with
system
update
both,
and
I
was
previously
using
an
older
version
of
messenger
ctl.
Then
I
updated
measure
serial
first
and
removed
the
pinning
to
late
test,
and
then
I
ran
system
start
system
start
started
to
work
flawlessly
and
after
that
system,
update
also
is
working
flawlessly.
A
Okay,
a
there's
a
couple
of
things
like
we
should
clarify
like
right
here.
In
my
mind,
the
channel
is
just
supposed
to
be
edge
or
stable.
It's
not
supposed
to
be
anything
else,
because
that
is
the
channel
it's
we
have
two
channels
edge
and
stable,
and
the
version
is
well
it's
either
that
you're
subscribed
for
the
latest
version
within
that
channel,
or
you
decided.
You
know
what
I
don't
want
to
have
mesh
re
automatically
update
itself.
A
A
So
that's
not
good,
because
we
want
it
to
be
item
potent
in
this
way
and
helm
is
not,
but
we
want
it
to
be
able.
We
want
from
street
ctl
to
provide
an
item,
potent
experience.
What
we
want
yeah
the
another
kind
of
related
challenge
here
will
be
when
we
do
a
restart
so
that
won't
you
know
that'll
just
be
it'll,
be
interesting
because
within
kubernetes
it
will
basically
be
the
same
thing.
It
won't
it'll
be
a
delete
of
the
an
uninstall
of
the
deployment,
a
helm,
uninstall
and
a
helm
install.
A
Now
I've
tried
doing
this
by
wiping
my
kubernetes
cluster,
because,
right
now
it's
saying
hey,
you
know,
helm
is
saying:
there's
conflict,
you
can't
get
installed
I'll
wipe
the
cluster
go
to
install
it.
I
think
it
will
install
but
on
subsequent
restart
of
the
cluster
or
subsequent
start
through
mastery
ctl
I'll
bump
into
these
issues.
A
I
see
okay
yeah,
it's
interesting
because
we
went
over
this
specific
use
case
with
the
folks
that
were
working
on
this
and
they
seem
to
have
it
covered.
But
don't.
F
F
Part
why
it
is
there
okay.
So
what
I
did
is
like
what
I
recommend
you
to
do
is
like
remove
that
stable
dash
version
in
your
on
your
mesh
config
just
write
stable.
There
wipe
your
like,
create
an
entirely
new
cluster,
delete
this
cluster
and
then
run
with
the
latest
release
of
measuring
ctl,
and
I
think
it
will
work
flawlessly.
It
will
work
smoothly
after
that,
that's
what
I
did
for
my
pc
and
it
is
working
right
now
correctly,
like
the
suppose.
Okay.
A
But
probably
not
ongoing,
like
like
one.
This
just
shouldn't
be
happening.
I
mean
that's
good
what
you
said.
I
don't
think
that
it's
a
one-time
thing.
I
don't
think
that,
like
people
are
going
to
end
up
in
a
situation
where
they
rebooted
their
club,
they
turned
on
and
off
their
mini
cube.
They
ran
like
they
might
have
uninstalled
only
parts
of
measuring
and
these
air.
These
situations
should
be
handled
gracefully,
like.
F
G
Well,
actually,
I
tried
to
stop
and
remove
these
files
and
then
like.
We
would
write
the
default.
A
This
particular
error
is
being
generated
from
helm.
Helm
has
a
different
concept
of
releases.
Helm
has
its
own
like
its
own
concept
of
releases
inside,
so
it
the
helm.
The
command
that's
being
run
here
is
saying
that
it
can't
find
a
helm
can't
find
a
deployment
of
mesherie.
A
Okay,
all
right
so
we'll
move
on,
but
yeah
so
push
and
husseina,
we'll
keep
cracking
we'll
see,
we'll
see
what
we
can
figure
out
yeah
and
be
used
like
the
logi.
The
logic
that
you
said
made
sense
like
hey
if
you're
in
this
situation
do
that
do
this
that
should
have
been
taken
care
of
like
there
should
be
that
kind
of
consideration.
Already.
A
Go
okay,
wait.
Next
topic
was
from
rudraksha
rudraksha's.
His
dad
just
had
surgery
he's
some
rude
rocks
is
out.
This
is
a
great
topic,
though
splitting
out
nighthawk
from
mesh
the
mystery's
server
container.
B
So
I
had
demoed
on
the
website's
call,
so
the
updates
from
that
is
like
the
sidebar
was
not
working
like
it
was
not
routing
to
the
specific
version
that
was
selected
and
there
was
a
problem
with
the
footer.
So
I
have
fixed
that
the
sidebar
also
works.
Now
it
goes
to
the
version
that
is
selected
currently
and
yeah.
A
A
detailed
couple,
quick
questions
to
verify,
so
the
cookie
crumb
trail
there
if
or
the
breadcrumb
trail
at
the
top
is
home
with
the
version
number
in
it.
Okay,
that
makes
some
sense,
the
you're
bringing
forth
a
global
drop
down
or
a
global
selector
for
choosing
what
version
the
docs
you
want
to
look
at
if
you
click
the
drop
down,
I'm
assuming
you're,
oh
yeah,
great
you're,
not
like
we
have
a
hundred
plus
releases
of
mesherie,
but
we're
not
going
to
you're
not
going
to
inundate
the
user
with
all
those
little
minor.
A
Technically.
The
releases
that
we
have
here.
These
are
these
like
using
the
nomenclature
of
semantic
versioning.
Technically,
that
is
a
minor
release,
a
dot
five.
But
to
us
it's
a
major
one
right,
because
we're
sort
of
incrementally
stepping
there
so
great
so
you're
breaking
it
down.
Based
on
out
of
five.
Do
you
have
the
concept
of
latest.
A
Another
question
so
so
by
the
way
for
a
success
who
is
no
longer
with
us,
we'll
have
to
tell
success
that
we're
talking
about
jacqueline.
He
isn't
here.
Let's
do
that.
Can
you.
A
B
Yeah,
all
the
pages
are
inside
those
but
like
the
includes
and
all
those
are
all
globally.
Okay,
that's,
okay!
So.
B
Yeah,
it
shouldn't
be
too
big
like,
but
it's
going
to
increase
the
repo
size.
A
A
If
you
look
at
the
size
of
the
docks
that
we
have
there
of
a
certain
size,
we've
done
a
calculation
in
the
past
to
understand
how
many
versions
of
the
docs
we
could
have
up
until
the
point
that
github
didn't
didn't
like
that
anymore
or
we
ran
over
that
limit,
so
so
that
the
okay.
Well,
while
the
dock
size,
is
a
concern,
I'm
probably
more
concerned
with
not
replicating
everything
holistically,
because
if
you
leave
styling,
some
includes
some
other
things
as.
A
Universal
and
and
external,
to
a
specific
version
when
you
go
to
add
a
new
entry
in
the
menu
for
one
version,
because
we're
going
to
add
more
menu
items
or
change
the
menu
items,
that's
going
to
affect
the
other
versions
and
you'll
basically
end
up
introducing
broken
links
into
the
other
versions.
You
might
do
a
style
change
or
a
footer
update
or
add
a
translation
like
to
spanish
and
the
header,
and
all
of
that
will
break
across
all
the
rest
of
the.
A
So
it's
a
lot
while
it's
somewhat
wasteful
in
terms
of
the
footprint
on
disk.
Like
wait,
wasteful,
you
know
it's
the
simple
approach
of
just
copying:
zipping
and
copying
the
entire,
not
zipping
like
copying
the
entire
contents
guarantees
that
things
don't
break.
A
B
Yes,
so
all
the
versions
should
have
everything
right.
That's
what
you're
saying.
A
You
know-
probably,
I
think,
we'll
just
end
up
in
less
of
you
know
less
conundrum,
because
otherwise,
like
tech,
if
you
didn't
like
technically
technic
by
the
way,
if
you
can
go
to
the
docs
dot,
some
people
might
have.
Some
people
might
have
a
hard
time
envisioning.
What
we're
talking
about
and
that's,
but
if
all
that
we're
versioning
is
the
the
content
in
the
middle
of
that
middle
frame.
A
A
Yeah,
so
some
of
this
is
called
out
in
the
design
spec.
That's
there
or
it
discusses
this
a
little
bit.
B
Okay,
yeah,
I
could
do
that.
I
just
didn't
do
that
like
I
get
what
you're
saying,
but
I
just
didn't
do
that
because
it
would
like
the
repo
size
would
increase
by
a
lot,
because
we
have
six
versions
as
of
now,
and
I
have
all
already
changed,
almost
a
thousand
files-
and
this
is
not
even
the
entire
thing
like
it's
just
adapters
and
all
the
pages,
though
some
of
these
files.
C
G
A
B
A
And
when
we
do
cross
that
bridge
or
when
it
does
come
to
pass
that
that
we're
running
out
of
room,
we
can
do
a
few
things.
We
can
go
use
it
like
s3,
some
other
object,
storage,
potentially
to
just
host
those
static
files
elsewhere.
We
can
acknowledge
and
admit
to
ourselves
that
no
one
cares
about
meshri.1
or
measuring.
A
A
A
You
know
what
I
won't
go
into
it.
If
we
ever
talk
about
that,
there's
a
bunch
of
things
to
consider
if
you
break
it
out
cool,
okay,
dj,
that's
fantastic!
I
think
that
really
really
helps
is.
Have
you
been
working
on
workflow
as
well.
B
Not
yet
like
I
for
the
records,
we
would
have
to
change
the
workflow
to
just
work
on
the
latest
and
not
on
all
of
the
versions,
so
yeah
I'll.
Look
into
that
after
I'm
done
with
everything
in
the
versioning.
A
Okay,
yeah
and
then
the
release
notes
how
they
publish
as
well.
A
Sounds
good,
okay,
all
right,
so
the
next
topic
up
was
it's
from
barc.
H
Yeah
I'm
gonna
share
my
screen.
H
Yeah,
assuming
that
you
can
see
my
screen,
so
this
is
a
spike
that
I've
built
you
should
have
made
over
the
last
week.
So
this
is
about
a
migration
of
the
our
messaging
framework,
the
broadcast
specification,
so
here.
Basically,
what
I
need
to
do
now
is
that
we
need
to
review
this
this
specification
and
find
out
whether
there
is
there
is
something
missing
in
in
the
current
specification.
Basically
so.
C
H
When
we,
when
we
finally
try
to
implement
the
the
the
code,
we
were
already
aware
of
of
the
nuke
and
granny
of
the
of
this
implementation,
basically
so
a
little
bit
of
a
background
for
this
specification.
Basically,
so
we
have
some
some
some
like
nested
go
routines
for
our
for
our
from
our
goaling
code.
H
So
if
you
are,
if
you
guys,
are
interested
in
the
in
the
server
side
as
well,
so
we
we
kind
of
use
like
a
golang
for
our
server
and
and
here
is
that
the
main
problem
is
the
one
I
outlined
basically
so
in
the
goaling
channel.
If
the
channel
is
unbuffered
the
you
can
basically
block
the
whole
the
whole
implication
of
a
function
basically,
so
this
is
purely
in
the
in
the
golang
system.
H
So
so
here
what
we
are
trying
to
do
is
that
we
we
are
trying
to
like
make
a
way
around
this
system,
and
then
we
by
do
it
so
the
way
we
do
what
we
make
around
this
is
basically
we
try
to
create
a
broadcast
system
that
is
natively
coded
inside
the
inside
the
inside
the
golem
itself.
So
for
sorry,
for
a
reference
I
actually
haven't
sent
the
coins
on
the
chat
yeah.
So
that's
the
so
I've
sent
the
the
link
in
the
chat.
H
A
A
So
there's
this
document
and
then
oh
and
then
actually
michael,
asked
the
same
question
I
was
about
to
speak
to
so
that
first
comment.
There
is:
how
does
what
bark
is
presenting
align
with
a
messaging
framework
and
designer
so
barack?
It's
yep,
we
need
to
clarify,
and
this
this
probably
should
be
included
in
the
other
design.
Spec,
probably
that
that
is.
A
H
Yeah,
so
for
that
question
for
this
question
is
actually
I
answer
it
in
the
in
this
part,
so
I
put
it
inside
the
design
for
a
lot
and
yeah,
so
this
is
basically
outlines
how
this
correlates,
with
the
with
the
previously
made
messaging
system
and
notification
center
design
yeah.
So
actually
there
is
something
that
michael
asked
before,
which
is
kind
of
interesting,
so
yeah.
So
this
is
the
question,
so
I
think
so.
He
said
that
he
thinks
that
it
will
be
useful
to
other
sentences
why
you
would
like
to
persist.
H
The
data
like
when
are
we
interested
in
past
data?
So
this
is
actually
one
of
the
issues
that
I
think
that
we
should
address
so
inside
the
visualizer
for
the
for
the
mesh
map.
You
can
see
that
there
are
multiple
data
there
are.
There
are
actually
like
outdated
in
some
sense
or
data
in
in
in
terms
of
like
these
service
meshes
are
not
really
inside
your
cluster
anymore.
H
So
in
our
current
architecture
we
couldn't
really
like
determine
whether
a
node
is
expired
or
a
node
is
like
it's
still
there
or
not,
so
I
think
they
should
be
so.
This
is
the
reason
why,
like
michael,
is
asking
whether
we
would
like
to
really
persist
the
data
or
not
in
our
local
database,
so
yeah
so.
A
Yeah
yeah,
this
is
great.
We
michael's
question
is
good,
and,
and
we
do
we
want
to
persist
the
data
that
said,
we
want
to
have
a
mechanism,
for
we
want
to
have
an
audit
log,
and
that's
really.
We
want
to
facilitate
for
an
audit
log
mesh
reserver
itself.
A
A
We
so
we
can
use
kind
of
prior
patterns
that
are
there
for
persisting
performance
tests
and
other
other
things
like
that.
H
A
A
Venue
gave
an
update
on
things
for
tomorrow's
tag,
network
meeting,
which
includes
nighthawk
and
some
of
the
efforts
there.
Oh
so
monov,
do
you
want
to
give
your
update.
A
A
A
But
if
you,
you
know,
if
it's
okay
to
say
that
when
you
go
into
mesherie-
and
it
shows
you
some
info
barrack
had
has
like
really
helped
it
be
better
than
it
was,
which
was
in
an
even
you
know,
lesser
spot,
and
so
it's
time
to
enhance
that,
it's
time
to
get
charts
and
lines
and
graphs
and
big
numbers
and
that
type
of
thing
in
front
of
people's
faces,
and
so
that
that's
what
monavie
is
working
on
and
he's
to
to
do
that.
What
monavis
is
well
and
these
are
really
bad
mock-ups.
A
But
what
monavie
is
trying
to
do
is
he's
first,
starting
with
the
notion
that
mescheri
has
has
connections
to
prometheus
and
grafana
and
can
query
for
metrics
using
a
couple
of
different
mechanisms,
but
the
internals
of
mesheri
don't
need.
They
need
a
few
more
constructs
to
be
able
to
define
things
like
panels
which,
which
is
like
that
this
is
a
panel
like
a
chart,
a
single
chart
with
maybe
multiple
metrics
and
then
a
board,
which
is
what
this
represents.
A
Now
measuring
has
some
of
that
ability
today,
but
it
needs
to
be
enhanced
to
be
able
to
let
people
add
custom
metrics,
that
they
want
to
track
and
to
add
and
then
to
identify
where
they
would
like
to
put
what
board.
With
what
panels
like
what
metrics
and
so
that's
kind
of
what
he's
working
toward.
A
A
No,
we
missed
him:
okay,
okay,
cool!
Well,
that's
what
that's
about.
A
All
right,
I
think,
we're
at
time
so
we'll
see
you
some
of
you
for
tomorrow's
cncf
tag,
network
meeting
you're
all
welcome
to
come.
We
might
see
some
of
you
on
the
newcomers
call
tomorrow
and
then
on
friday
for
the
community
meeting
all
right
talk
to
you
all
soon,
bye
see
you
guys
see
you
guys.