►
From YouTube: Layer5 Community Meeting (March 12th, 2021)
Description
No description was provided for this meeting.
If this is YOUR meeting, an easy way to fix this is to add a description to your video, wherever mtngs.io found it (probably YouTube).
A
Prakesh
there's
a
tradition
here:
welcome
for
anyone
who's
on
well
any
of
the
calls
for
the
first
time
you
get
to
say,
hi
and
introduce
and
never
let
everybody
get
to
know
you.
A
B
A
We'll
take
all
of
them,
there's
a
lot
to
go
around
yeah
nice
yeah.
That's
a
that's
a
list
of
technologies
that
you
prattled
off
there.
That's
good!
That's
fantastic!
I
don't
know
you
said
mumbai,
but
I
would
have
guessed
that
you're
from
you
know,
san
francisco
or
something
yeah.
B
My
fan
right
up
right
above
me
sure
nice,
oh
very
nice,
to
have
you
I'm
kind
of
unsure
about
what
clarify
really
is,
but
I'm
gonna
take
my
time
and
get
to
know
it
and
try
and
install
those
cpu
and
the
mesh
applications
and
try
to
play
play
along
with
us.
I've
seen
docker,
but
I
don't
know
about
kubernetes
and
this
mesh
concept
here.
I'm
gonna
try
and
contribute
in
the
website
first
and
I'll
I'll
try
and
over
what
I'm
doing.
A
It's
a
it's
a
fantastic
plan.
It
sounds
like
it
sounds
like
a
plan
that
will
be
successful
because
you
know,
as
you
go
to
contribute
to
well
there's
actually,
like
I
don't
know,
somebody
else
might
have
a
better
count.
A
There's
like
well,
I
think
we
just
turned
down
a
site,
so
I
think
we
were
at
six
sites,
maybe
we're
back
to
five
there's
a
site
for
the
nighthawk
project,
the
mesh
there's
two
for
the
mystery
project,
one
for
documentation,
one
for
the
project,
description
site,
there's
the
layer,
five
site
that
was
just
released
just
redone
totally
there's
the
service
mesh
performance
site.
A
I
should
have
been
counting.
Okay,
there's
a
lot
to
do
there,
the
docs
for
meshri
as
well.
Well,
actually,
navendu
who's,
the
only
other
brave
soul
who's
got
his
webcam
on
is
he's
been
recently
well
calling
for
some
reorganization
inside
of
the
meshery
docks,
and
some
of
that
reorganization
will
take
well
it'll,
take
a
little
bit
of
familiarity
with
jekyll
or
or
someone
to
get
a
little
bit
more
familiar
with
jekyll,
not
very
difficult
things,
but
but
kind
of
interesting,
especially
if
you're
not
horribly
familiar
with
jekyll.
A
Actually,
alonso
who's
on
the
call
he's
been
making
some
big
big
waves
inside
of
the
meshery
docks
along.
So
we
might
even
want
to
talk
about
some
of
those
changes
today,
because
I
thought
we
were
like
this
close
to
merging
your
changes
last
time,
and
so
so
we
might
want
to
put
that
as
a
topic,
but
very
good.
So
prakesh
thanks
for
thanks
for
jumping
in
it's
nice
to
have
you
all
right,
very
good.
A
So,
let's
jump
into
the
meeting
minutes
here
a
couple
of
items,
one
we
normally
list
out
all
of
our
the
new
members
week
to
week.
I
just
ran
out
of
time
to
list
down
everybody
else.
The
thing
is
is
prakesh
is
the
only
one
that's
on
the
call,
so
he
gets
gets
all
the
attention.
A
So
I
think
only
one
announcement
this
week,
if
I'm
getting
it
right,
some
of
you
had
so
one
of
the
projects
that
we
have
in
the
community
is
a
set
of
workshops
for
learning
service
meshes.
There
are
three
of
them.
A
The
recordings
for
our
workshop
just
were
announced
this
morning.
I'll
grab
a
link
and
put
it
in
here
to
make
sure
that
you
can
all
not
only
follow
along
with
the
work,
the
self,
the
self-paced
steps,
but
you
could
also
follow
along
with
the
recorded
workshop.
So
let's
go
to
is.
A
Is
nikhil
on
today?
No,
I
don't
think
so.
Okay,
so
we'll
talk
about
this
anyway.
So
so
I'll
talk
about
this
on
on
nikhil's
behalf.
So
there's
a
number
of
you
that
are
on
the
call
whose
names
I
won't
prattle
off,
because
it's
kind
of
a
long
list
of
names,
but
a
number
of
you
have
helped
get
create
a
new
website
for
layer,
five
dot
io
used
to
be
based
on
jekyll.
Now
it's
based
on
gatsby.
It
looks
so
much
better.
A
A
A
One
of
the
things
that
nikhil
had
created
on
the
site
was
contact
us
and
I
think
you
can
find
it
in
a
couple
of
areas,
but
this
is
sort
of
the
general
area
this
contact.
A
Last
night
there
was
a
gentleman
a
director
of
product
management
for
acronis.
I
think
who's
interested
in
the
blog
post
that
you
all
are
writing
interested
in
the
work
that
you're
doing
and
he
had
filled
in
the
form
asking
for
an
rss
feed
for
the
blog
posts.
A
So
a
couple
of
neat
things
about
that,
one
that
proves
that
nikhil's
implementation
of
this
contact
us
works
two.
It
shows
that
there
are,
even
without
us,
really
telling
people
about
it.
There's
people
that
are
interested
in
what
you're
doing
and
want
to
feed
for
it.
A
I
guess
rss
isn't
dead,
or
at
least
not
yet
that
individual
they
were
using
feedly,
which
I
found
to
be
kind
of
interesting,
because
it
had
been
it's
been
a
few
years
since
I
had
used
feedly,
oh
feedly.ly.
I
really.
A
Yeah
me,
I
use
it
almost
yeah,
I'm
not
sure
why
it
sort
of
went
dead
or
like
what
a
convenient
way
to
aggregate
info
that
you're
interested
in,
and
that's
probably
unfair
of
me
to
say
that
it
went
dead
like
I
think
it
just
maybe
went
out
of
prominent
popularity
but
most
sites.
I
think
still
like
this
blog
well.
Of
course
their
blog
would
support
rss,
but
most
you
know
wordpress
instances
and
various
blogging
platforms.
A
Just
whether
or
not
the
the
theme
makes
it
prominent
or
not.
Most
of
them
support,
rss
out
of
the
box
and
so
yeah,
so
hopefully
we'll
get
an
rss
feed
going
here
shortly
should
be
pretty
pretty
straightforward.
A
So
anyway,
that's
that's
that
note.
That's
kind
of
neat
this
next
one
is
austin
has
been
doing
some
work
on
on
trying
to
uplift
meshri.io,
so
austin,
do
you
want
to
do
wanna
show
people
some
of
those
designs.
C
A
C
Definitely:
okay,
hello,
everyone!
I'm
I'm
augustine!
I
modi
layer,
5
mystery
team
regarding
the
visual
designs
and
your
ux
user
experience
and
or
everything
design.
So
lately,
we've
been
working
on
revamping
the
current
mainstream.I
website
and
these
are
the
four
iterations
we
currently
have
been
working
on
this.
C
D
C
Yes,
so
this
is
a
current
frame
for
mercury.I
website.
We
should
be
working
on
the
most
recent
iteration
and
we
decided
to
change
the
style
up
a
little
bit
from
what
we
currently
have
and
also
we've
been
trying
to
make.
It
differ
from
layer
five.
So
when
a
user
comes,
you
know,
a
community
member
comes
in,
doesn't
immediately
say.
Oh,
this
is
layer
five,
so
after
rebuilding
of
the
layer,
five
and
next
generation
website,
we
started
this
and
so
far
this
is
what
we
need
to
come
up
with.
C
C
Adding
yourself
as
an
adapter
and
also
subscribing,
and
then
you
can
copy
several
service
mesh,
so
this
is
what
we've
been
able
to
come
up
with
so
far
and
we'll
keep
working
on
iteration
to
make
it
exceedingly
amazing,
both
the
user
experience
and
the
visuals
that
that's
that's
awful.
Thank
you
very
much.
A
Does
anyone
have
feedback
there,
just
to
recap
in
part?
What
austin
had
said
is
that
you
know
you,
you
can
go
browse
the
current
meshery.io
website
and
you
know
it's
a
small
small
site.
It
links
to
a
number
of
resources
that
are
external
to
the
actual
site.
It
also
in
one
of
those
bigger
resources
that
it
links
to
is
the
docs
mesh
redox.
A
It
had
been
a
while,
since
there
had
been
a
push
to
enhance
the
site,
and
so
austin
is
putting
together
some
designs
to
uplift,
it
a
little
bit
so
these
are
just.
These
are
the
first
drafts
if
you've
got
feedback,
a
say
it
here
be
in
the
slack
or
c
in
a
comment
or
a
set
of
comments
in
figma.
A
A
You
know
one
of
the
things
that
austin
had
mentioned
was
like
to
what
was
a
bit.
A
It
was
kind
of
a
bit
about
layer,
five
and
it
was,
I
think,
to
clarify
like
the
the
context
there
is
that,
while
measuring
is
used
by
any
number
of
organizations
and
any
number
of
people,
and
while
it
is
largely
stewarded
by
or
it
was
created
here
in
this
community
and
largely
stewarded
by
people
who
all
of
you
who
affiliate
yourselves
with
this
community
and
sort
of
and
wear
that
badge
hopefully,
hopefully
proudly
but-
and
you
put
in
your
time-
and
maybe
some
blood
and
some
sweat-
and
maybe
some
tears
even
into
the
thing
that
we
don't
necessarily
want
for
desire
for
measuring
to
be
people
should
understand
that
mesherie
was
born
of
and
is
curated
by
and
is
loved
on
by
this
community
by
layer.
A
Five.
But
shouldn't
necessarily
consider
that,
like
oh,
it's
entirely
owned
by
and
tightly
controlled
by
layer,
five
as
an
entity
explicitly
and
directly,
and
only
no
it's
not
it's.
We
try
to
be
as
welcoming
as
possible
to
well
to
the
users
and
their
feedback
to
other
other
technology
organizations.
Other
communities
and
their
feedback
meshery
itself
is
really
extensible.
Actually,
it
has
a
lot
of
extension
points
in
it.
A
We
hope
that
others
come
and
plug
in
their
extensions.
That
would
make
mesherie
even
more
interesting,
even
more
valuable.
So
so
as
such,
it
shouldn't
it
shouldn't,
look
just
like
it's
a
layer,
five
thing
it
should
look
similar.
It
should
look
like
a
child
of
or
a
first
cousin
of
layer,
five
yeah.
A
Nice,
so
so
I
guess
the
follow-up
there
is,
as
some
of
those
designs
harden,
I
would
expect,
will
probably
austin
will
you'll
probably
end
up
creating
a
github
issue
or
two
specific
to
a
couple
of
those
sections
so
that
folks
might
iterate
on
some
of
that
implementation.
A
It
probably
makes
sense
that,
as
those
designs
harden
that
in
the
the
measuring
development
call
on
wednesdays,
we
might
review
some
of
those
and
discuss
the
behavior
or
part
of
the
the
desire
behind
them.
One
one
item
that
is
a
a
little
bit
of
a
head
scratcher
for
me
is-
and
here
let
me
share
my
screen
to
call
this
out.
I
don't
have
an
answer
to
this
small
dilemma
that
I'm
about
to
bring
up,
but
it's
an
open
thought.
A
Largest
project
that
we
have
but
layer
five,
you
know
all
of
you
have
created
well.
You've
created
service
mesh
performance
as
another
project,
and
this
is
about
to
go
into
the
cncf.
Hopefully,.
A
A
Okay,
so
that
that's
one
another
project
is
nighthawk
or
get
nighthawk
rather,
and
that
site
is
very
much
so
in
in
a
work
in
progress
been
a
lot
of
really
good.
It's
actually
not
it's
not
too
far
off.
Now,
anyway,
point
is:
there's
mastery,
there's
get
nighthawk,
there's
service
mesh
performance
and
there
are
a
number
of
smaller
derivative
projects
that
there's
imagehub,
which
pranav
bot
was
showing
on
wednesday
there's
distributed
performance
analysis.
There's
a
few
different
projects
point
is
that
the
community
has
a
number
of
projects.
A
Community
members,
you
know
who
are
individuals
that
are
consistent
contributors,
that
their
efforts
and
you
know
are
reflected
here
and
we
try
to
uplift
them
in
their
works
that
we
had
started
by
doing
so
on
mastery
dot,
io
measure,
dot,
io
community.
Over
time,
some
of
you
have
worked,
have
paid
it
forward
enough
and
helped
others
in
the
community
and
have
become
a
mesh
mate.
A
Some
of
you
have
come
and
gone
and
maybe-
and
some
of
you
come
back
and
so
that's
represented
by
those
that
are
inactive-
those
that
are
active,
those
that
are
mesh
meshmates-
and
this
is
great
over
time,
though,
what
has
happened
is
we've
created
service
mesh
performance,
get
nighthawk,
imagehub
we're
creating
lots
of
projects,
we're
not
done
creating
projects.
A
A
Here's
what
a
profile
looks
like
nice,
guy,
really
helped
out
on
mesherie
operator
on
the
kubernetes
controllers,
the
custom
controllers
that
were
created,
I
would
he's
actually
inactive
at
the
moment,
so
we've
we've
stopped
kind
of
updating.
This,
like
I,
was
saying,
I'm
hopeful
he'll
come
back,
he
did
well
point.
Is
we
started
to
represent
all
of
you
here
and
actually,
at
one
point,
vinayak
uplifted
these
profiles
to
include
a
little
bit
of
a
different
look
and
feel
and
to
help
elevate.
A
A
A
Okay,
now
that
I've,
so
so
the
dilemma
is
or
was
or
as
we
think,
toward
an
uplifting
or
a
little
bit
of
an
uplifting
of
meshri.io,
not
an
overhaul.
Just
an
uplifting
is
so
some
links
point
to
external
resources,
so
we
don't
have
to
repeat
them.
I'm
here
like
branding,
for
example,
hey:
where
do
you
get
the
meshre
logos?
Well,
we
can
upload
them
to
measuring.io.
A
A
It's
not
it's
not
easy
to
always
determine
whether
or
not
someone
is
active
or
inactive,
being
active
or
inactive,
isn't
determined
by
whether
or
not
you
make
a
a
github
contribution
determined
in
a
lot
of
ways
and
none
of
which
are
all
of
which
none
of
which
are
easily
programmatically
quantifiable,
which
means
us
as
maintainers,
need
to
make
it
determination
as
to
when
someone
has
stepped
away.
Sometimes
they'll
signal
that
and
say
it.
A
A
A
That
we
do
want
to
highlight
those
that
have
contributed
to
measuring
and
show
that
here,
but
we'd
probably
end
up
linking
to
the
more
robust
set
of
profiles
on
layer,
five
io.
So.
A
A
A
Nobody
has
thoughts
anybody
wanted.
Maybe
I
should
call
for
a
vote
people
thinking
that
we
should
try
to
put
an
effort
and
time
into
both
or
focus
on
one
and
continue
to
advance
one.
A
A
A
A
F
Yeah
so
like
I
couldn't
actually
reproduce
it
and
like
it
was
working
like
fine
as
expected
on
my
system.
Like
should
I
share
my
screen
like,
but
it
would
work
even
after
deleting
my
contract
yeah,
I'm
sure.
A
Yeah,
if
you
don't
mind
and
maybe
show
people
the
issue
as
well,
so
that
they
can.
G
F
So
yeah,
so
I
think
the
issue
is
recently:
we
have
added
a
check
and
the
mystery
that
runs
at
the
startup
that
checks,
whether
you
are
running
with
the
latest
version
or
not,
and
if
you
are
not,
if
you
are
running
an
older
version,
basically,
you
get
a
prompt
here
that
you
can
update
the
mystery
cdl,
but
the
issue,
I
think,
is
that
you
know
the
version
that
is
being
picked
up
by
the
machine.
Ctl
does
not
contain
the
letter
v,
which
is
present
in
the
tag
at
github.
F
I
think
but
like
from
my
point
of
view
from
the
discussion,
so
actually
you
know
the
version
that
is
set
to
the
machine.
Ctl
is
passed
on
the
runtime
through
the
ld
flag,
so
it
uses
it
basically
uses
an
environmental
variable
of
like
gate
version
which
basically
finds
the
latest
stack
that
like
on
like
on
trying
on
my
system.
F
F
A
Concept,
there's
a
to
highlight
this
real
quick
as
you
go
through
there's
a
sneaky
issue.
That's
going
on
is
that
when
you
build
low
measuring
ctl
locally,
the
the
logic
by
which
or
the
location
by
which
the
hello.
A
Oh
yeah,
I'm
back
okay
yeah!
So
when
you,
when
you
build
messages,
detail
locally,
the
tag
is
retrieved
from
a
different
location
than
it
is
when
mastery
ctl
is
built
and
released
in
the
build
system.
And
so
you
can
see
right
here
where
it
says
client
version
it
has
a
v
0
and
which
it
doesn't
have
you
use
the
built
and
released
version.
F
Yeah
so,
while
locally,
we
have
already
set
it
up
using
make
right
and
it
actually
picks
up
the
correct
command
yeah.
If
you
can
see
my
screen
here
right,
we
pass
an
ld
flag
and
we
set
the
version
here.
The
variable
right-
and
it
is
being
picked
up
correctly
here,
as
you
can
see,
there's
a
v
here
right
so
and
so
like
locally.
While
you
were
like
you
were
getting,
you
were
not
getting
v-ray
and
you
actually
did,
I
think,
build
it
locally
or
it
was
a
release
build.
F
This
was
a
release,
build
okay,
so
if
this
was
a
release
print
right,
so
so
this
release
build
would
have
been
done
from
one
of
the
workflow,
I
think
and
internally.
I
think
the
workflow
would
also
use
the
make
command.
A
You
would
think
so,
but
it
doesn't,
it
ends
up
being
built
by
go
releaser
anyway,
there's
actually,
even
even
aside
from
it.
By
the
way.
I
think
that
this
issue
that
we're
looking
at
is
probably
transient,
given
that
we've,
I
don't
know
that
it's
just
the
v
that's
getting
in
the
way
in
part,
the
fact
that
we
had
rc3
and
then
we
had
rc
hyphen
for
like
the
logical,
the
way
in
which
alphabetically
as
those
are
sorted,
they
get
out
of
order
a
little
bit.
A
You
can
look
inside
of
so
there's
your
configuration
in
the
root
directory
of
of
meschery.
There
should
be
a
go
releaser.yaml.
A
Yeah,
so
actually,
if
you
don't
yeah,
if
you
would
don't
use
the
version
that
you
built
here,
but
the
version
that
you
would
have
downloaded
and
installed
like
a
user
would
have
okay,
I
would
love
to
actually
do
it
now.
F
F
Are
you
on
windows
or
yeah,
I'm
on
windows,
but
I
use
wsl
for.
A
F
A
H
A
There's
two
issues
that
have
kind
of
been
here
for
a
while:
they
hadn't
manifested
themselves
in
like
they're
manifesting
as
a
third
issue.
Now
that
now
that
you
have
incorporated
logic
for
confirming
whether
or
not
you're
running
the
latest
version
of
messaging,
you
know
every
time
you
run
every
time
you
run
a
command.
It
will
check
to
see
if
you're
running
the
latest
version.
A
If
you're
not
it'll,
tell
you
you
know,
I'm
telling
you,
you
wrote
that
logic
yeah,
that's
great
and
I
think
your
logic
is
fine,
but
it's
getting
impacted
by
the
fact
that
there's
inconsistency
with
the
tag
you
know
the
the
strings
that
are
inside
the
release
tags.
So
like
these
versions.
F
D
A
Potentially
so
that
there's
one
other
while
we're
in
here
and
making
it
making
a
mess,
there's
one
other
item
to
be
aware
of.
If
you
go
back
to
your
terminal
and
when
you
run
measuring
ctl
version,
you'll
also
notice
that
the
git
cha
well,
I
guess
you
won't
notice
it
here,
because
it's
not
talking.
I
A
Us,
but
when
it
is
talking
to
a
server
the
git
sha
for
the
server
version,
it
will
be
just
run
the
docker
tool.
Let's
do
it
it'll,
be
I
don't
know
like
eight
characters.
Long,
okay,
so
not
full,
stripped
right
and
either
way
will
work,
whether
it's
stripped
or
it's
full.
Just
so
long
as
it's
consistent
between
the.
A
A
F
You
mean:
do
you
let
the
platform
work,
yeah
yeah
so
like
currently,
when
we
create
the
config
file
like
measure
schedule,
assumes
that
the
platform
is
docker
so
like,
since
we
are
adding
kubernetes
support
to
measure
the
ctl,
it
should
ideally
ask
the
user
for
which
platform
like
when
the
config
file
is
created
at
first.
It
should
ask
the
user
which
platform
they
should
they
are
using
or
like.
F
We
can
also
add
a
flag
when
we
like
instagram
that
the
user
can
pass
either
docker
or
kubernetes,
which
will
like
silently
create
the
conflict
right
instead
of
asking
so
yeah.
We
we
need
to
add
the
change
not
on
the
call,
but
I
was
just
talking
to
her
about
this
yeah.
We
will
just
yeah
we'll
add.
F
A
A
Yeah
so
fair
enough,
you
know
we
we
won't.
I
don't
think
we'll
figure
out
the
fix
on
this
call,
but
but
hopefully
anish.
This
gets
you
into
the
mindset
of
and
gives
you
some
pointers
as
to
where
to
start
to
look.
There's
one
other
potential,
gotcha
or
like
caveat
here
is
when,
when
you
build
mesh
free,
ctl
locally,
yes,
you
were
showing
that
you
were
passing
in
some
ld
flags.
A
Do
you
can
you
go
back?
Can
you
go
look
at
that?
Make
file
real
quick.
We
had
changed
some
logic
around
in
there
and
I
don't
re.
I
don't
recall
where
we
landed,
where
we
ended.
So
at
one
point
what
we
were
doing
is
yeah
actually
yeah.
If
you
go
to
the
very
top,
the
very
top
we're
setting
some
environment
variables,
so
git
version
and
git
commit
shot
and
we're
running
a
shell
command
to
grab
the
okay
now.
A
So
here's
a
third
way
in
which
something
might
be
wonky
is
that
you
might,
while
you're,
building
mastery
cto
locally,
the
the
tags
are
being
retrieved
via
a
git
command.
While
when
the
mastery
ct
is
released,
you
know
it's
it's
that
workflow.
That
executes
that
retrieves,
the
tags
and
it
kind
of
there's
kind
of
two
areas
where
those
tags
bear
weight.
So
one
is
in
the
workflow
the
build
and
release
workflow
and
you
you
can
see
the
tags
in
there,
but
there's
a
subsequent
action.
A
F
A
H
A
H
F
H
Okay,
so
for
a
recap,
a
window,
I
actually
raised
an
issue
one.
Basically,
the
breed
is
yeah,
actually,
okay,
one
sec,
it's
somewhere
and
yeah.
This
is
actually
the
new
command
reference
controller
page
that
you
need
guys,
and
unfortunately
this
wasn't
updated
on
the
downloads
page.
So
the
main
task
was
to
what
you
can
say,
create
new
commands
on
the
dock
page
and
show
them.
H
So
this
is
the
local
post
page,
which
I'm
running
on,
as
you
can
see
here,
and
some
of
the
additional
commands
that
have
been
added
like
and
also
been
changed
like
a
double
dash,
instead
of
just
a
config
for
difference,
I'm
showing
here
and
for
now
I
don't
know
why
the
order
has
been
changed,
but
still
I'm
booked
still.
H
The
work
is
in
progress,
but
at
least
I
have
added
commands
in
order
to
get
an
idea,
and
if
you
can
see
here,
the
title
solves
have
also
been
changed
according
to
the
spreadsheet,
as
you
can
see
see
here,
also
the
new
commands,
like
the
context
and
context
complex
channel
where
including
news,
no
new
flags
also
been
added
and
the
better
part.
H
The
valdic
valley
is
also
been
introduced
here:
one
sec,
okay,
it's
unstable,
it
seems,
okay,
it's
been
resolved
and
the
new
part
has
been
added,
that
is,
the
service
mesh
patent
configuration
and
a
new
table
has
been
added
here
and
I'm
trying
to
figure
out
why
it's
the
order
is
printing,
like
that,
but
yeah
I
have
at
least
added
almost
all
the
commands
and
as
shared
in
the
spreadsheet
and
so
yeah
and
since
the
experimental
comments
are
not
assigned
yet
I
have
leaders
to
get
for
now
and
yeah,
that's
much
of
it.
A
Anyone
I've
got
a
quick
one.
Do
we
have
a
draft
of
what
the
individual
command
page
might
look
like?
A
Beautiful
alonso,
nothing
like
getting
put
on
the
spot,
you
don't
happen
to
have
that
handy.
Do.
A
I
G
A
G
I
Something
like
this,
we
are,
we
are
working
with
and
navendu,
so
we're
trying
to
get
the
the
common
name.
Then
a
general
usage,
then
a
brief
synopsis,
then
some
specific
usage
for
the
the
comment
and
then
maybe
some
other
special
flags
and
options
about
the
the
layout.
I
am
following
the
installation
layout
that
is
already.
A
A
A
good
maybe
like
what
happened
yeah,
it's
a
good
thing
to
reflect
on,
to
the
extent
that
we
that
we
end
up
providing
multiple
examples
of
usage,
for
example.
So
you
know
some
of
the
commands
you
can
use
them
in
different
ways
and
so,
to
the
extent
that
we
have
multiple
usage
examples,
there
might
be
some
thought
given
as
to
how
to
indicate
to
the
user.
A
That,
like
you
know
here,
here's
measure,
if
you
just
execute
mastery
ctl
by
itself,
here's
the
output,
here's
the
we
probably
don't-
or
I
wouldn't
think
that
we'd
want
to
necessarily
show
the
error
there
like
like,
and
the
usage
actually
is
technically
incorrect
usage
to
use
measuring
ctl
by
itself,
and
that's
why
they're
they're
getting
the
error.
So
it's
like
I.
I
know
that
this
is
this
is
work
in
progress.
A
So
all
of
what
I'm
saying
is
totally
discounted
with
the
fact
that
this
is
work
in
progress,
but
but
a
messy
measuring,
ctl-h
or
dash
or
or
measuring
ctl
version,
or
something
like
that
would
be
yeah.
A
A
Message,
oh
nice,
it
by
the
way
it's
nice
that
people
can
have
they
have
the
clipboard
option
for
any
of
these.
Any
of
these
that's
nice
yeah.
I
realize,
for
that
it'll
require
a
collection
of
you
to
come
through
and
give
further
behave
further
text
further
paragraphs
like
defining
the
behavior
or
like
hey.
If
you're
looking,
you
know,
are
like
usage
examples
that
say
things
like.
A
If
you
want
to
know
the
version
number
of
messaging
here's,
this
meshery
will
our
message:
ctl
will
automatically
you
know,
it'll
try
to
reach
out
to
confirm
whether
or
not
you're
running
the
latest
version
like
to
to
explain
all
that
is
is
really
healthy.
A
I
A
A
Yeah,
okay,
okay,
good
deal,
yeah
novendo!
Do
you
want
to
speak
to
that.
F
Yeah,
the
this
page
is
like
currently
being
revoked,
so
we
have
a
command
metrics
documentation
that
I.
F
So,
for
example,
if
we
have
the
global
commands
and
flags
and
measuring
ctm
commands,
so
we
will
have
an
individual
page
for
the
measure.
Recital
commands-
and
in
that
case
we
will
add
all
the
flags
available
for
measuring
commands
and
all
the
use
cases
of
the
measuring
receipt
accounts
with
the
global
command
so
yeah.
That
will
be
how
we
will
add
that
stuff.
I
A
K
I'm
wondering
if
anything
has
been
happening
on
the
configuration
wizard.
You
know
anything
that
I
can
do.
I
don't.
I
don't
know
what.
A
Bj
was
just
asking
about:
what's
the
latest
on
the
configuration
wizard
and
where
to
where
to
help
advance,
it.
C
Oh
sorry,
my
network
has
been
experiencing
so
for
the
configuration
wizard.
We
currently
have
a
prototype,
a
new
prototype
on
what
we've
been
working
on
and
then
the
major
aspect
to
help
improve
it
is
this
scroll
scroll
view
crew
view
for
the
cards,
which
is
what
we'll
be
looking
at,
because
the
the
current
user
experience
of
the
the
cards
we
want
to
try
and
improve
it
for
the
screw.
Let
me
quickly
bring
out
the
link
for
the
new.
K
Is
that
the
one
that
you
sent
me
austin.
C
C
K
This
other
aspect
right
I
mean
this
has
to
I
mean
like
work
in
in
in
a
real
sense
when,
when
you
it
has,
it
has
to
be
in
motion
right.
So
at
least
this
is
something
that.
A
No,
this
is
great
yeah.
I
think
austin
is
perhaps
slightly
behind
on
on
doing
a
little
bit
of
organization,
just
kind
of
getting
getting
the
same
folks
back
together
to
establish
a
little
bit
of
a
cadence
to
advancing
this.
So
really
not
much
had
been
done.
A
lot
had
been
done
since
last.
The
collection
of
individuals
on
the
configuration
wizard
had
met.
A
So
so
let
me
see
if
I
can
get
that
help
with
this
organization.
Very
briefly,
and
that
is
that
that
is
to
say
some
of
you
are
familiar
with
the
fact
that
there's
an
effort,
that's
been
initiated
to
create
a
configuration
wizard
so
that
when
people
come
in
to
use
meshri
that
they'll
get
this,
you
know
like
four
or
five
steps
to
configure
meshri
to
get
meshri
setup,
so
they
can
be
successful
with
connecting
to
kubernetes
deploying
service
meshes
connecting
to
grafana
and
prometheus.
A
That
kind
of
a
thing,
and
so
there's
been
a
series
of
wireframes
mock-ups
that
are
being
generated
here
in
figma
to
create
that
wizard.
The
that's
good
there's
a
lot
of
logic
that
needs
to
follow
with
these
steps
like
when
is
it
appropriate
to
go
from
one
step
to
the
next
hey?
What
does
it
mean
to
execute
on
a
step?
So
what
should
what
what's
being
executed
on
the
back
end?
What
process
and
operation
are
happening?
Is
it
okay?
A
If
someone
skips
the
step
like
you
know,
all
of
these
all
that
logic
needs
to
be
accounted
for.
Outside
of
you
know,
just
the
mock-ups
outside
of
just
the
interface
and
so
nikhil,
vijay,
austin
and
bart
are
the
handful
of
folks
that
have
been
giving
this
the
most
thought.
So
I
think
I
think,
the
you
guys
we
convened,
I
think
once
and
kind
of
went
through.
The
initial
drafts
of
what
this
looks
like
bart
has
been
putting
to
get
bart.
Kolansky
has
been
putting
together.
A
The
these
you
were
taking
so
awesome
has
been
working
on
the
mock-ups
bart's
been
trying
to
put
together
these
uis
that
don't
really
don't
really
do
anything.
They're,
just
they're
just
steps
and
then
bj's
been
giving
thought
toward.
Well,
hey
all
those
other
things.
When
should
you
go
from
one
step
to
the
next?
What
needs
to
be
what's
the
sequence
by
which
this
needs
to
happen?
A
What
happens
if
you
try
to
deploy
a
service
mesh,
but
it
fails
or
just
all
of
those
things,
so
this
particular
effort
has
worked
a
little
bit
differently
than
some
of
the
other
ones.
A
lot
of
times
we'll
end
up.
When
we
create
a
new
feature,
a
new
function
will
there'll
be
a
google
doc,
a
design
specification
that
outlines
what
the
feature
is
about
and
how
it's
going
to
work.
A
I
think
it's
kind
of
it's
probably
up
to
you
to
to
either
continue
here
in
figma
to
kind
of
lay
out
the
user
flow
and
sort
of
the
the
logic
by
which
this
occurs
or
if,
if
google
docs
is
preferable
to
go
to
go,
create
one
of
those
and
just
kind
of
kind
of
outline.
How
this
thing
will
flow.
K
I
think
you
know
maybe
there'll
be
like
a
little
companion
to
what's
going
on
in
figma,
so
that
I
can
put
put
some
of
my
thoughts
there
and
then
share
the
document
so
that
you
know
the
others
can
add
to
it
or
edit
it.
You
know
or
or
you
know,
completed
or
whatever
whatever.
But
I
I
can
I'll
I'll
start.
The
document
and
I
will
put.
K
I
mean
I'll
try
to
be
as
comprehensive
as
possible,
but
it'll
be
as
a
starter
effort.
You
know
I'll
just
put
my
start
up
with
the
thoughts
that
I
have
and
fill
in
the
details,
as
I
think
of
of
them,
or
somebody
else
can
can
fill
them
in
if
if
they
feel
that
it's
more
appropriate.
A
Nice,
it's
beautiful,
hey,
there's
this
really
old
design
speck
it.
It
barely
barely
follows
our
format,
it
kind
of
doesn't
from
a
long
time
ago
where,
when
we
were
working
on
configuration,
wizards
and
settings,
you
might
choose
to
reuse
this
dock
and
delete
or
rewrite
anything
that
doesn't
no
longer
make
sense.
It's
it's
just
out
there
in
the
community
drive
under
measuring
functional
and
then
installation
and
configuration
or
or
if
you
like,
to
create
a
new
dock.
K
A
And
then
the
last
item
there
is
my
suggestion
to
the
collection
of
the
the
four
of
you
is
and
by
the
way
it
doesn't
it's
not
this.
This
effort
isn't
constrained
to
the
four
of
these
individuals,
just
like
any
aspect
of
the
projects.
Anyone
who's
interested
is
welcome
to
join
in
and
and
that's
part
in
part.
What
vijay
was
kind
of
asking
is
like
hey.
We
had
a
great
kind
of
kickoff
to
the
effort
and
there's
a
little
bit
of
mock-up
there's
some
mock-up
going
on.
A
There's
some
prototype
going
on
bj's
gonna
put
some
time
into
a
you,
know
a
design,
spec
and
getting
some
of
this
on
paper.
But,
like
hey
where's,
the
next
point
of
discussion
like
is
there
a
cadence
to
is
there?
Are
there
separate
meetings
or
are
we
going
to
dedicate
you
know
10
15,
20
minutes
of
the
you
know
wednesday
measure
development
calls
or
like
that's
kind
of
in
part,
what
he's
looking
to
do
and
I'll
suggest
this
that
vijay
and
austin
you
can
and
nikhil
and
bart
you
get.
K
Yeah
I
I'll.
A
K
A
Alrighty
well
we're
about
eight.
After
so
I
appreciate
everyone
staying
late
and
same
time
next
week,
prakesh
nice,
to
have
you
thanks
for
coming.