►
From YouTube: Layer5 Community Meeting - April 10th, 2020
Description
Welcome, @mandela900, @rav121rav!! New Scoop installer for mesheryctl released in Meshery v0.3.12.
A
A
A
A
Good
three
minutes
after
maybe
one
more
minute,
there's
a
number
of
people
who
end
up
joining
about
10-15
minutes
after
the
call
has
started
it's
unfortunate
because
some
of
those
individuals
are
the
ones
that
benefit
the
most
from
the
first
part
of
the
meeting,
which
is
the
announcements
so
we'll
see.
So
we've
got
a
quick
roll
cross.
We've
got
me
Jay,
sherick,
Lori,.
A
A
Manuel,
the
cool
cush
I'm,
missing
people,
Shiva
you're,
being
I'll,
let
you
guys
yeah
I,
guess
I'll,
let
you
guys
take
notes
but
good,
so,
alright,
alright
with
four
minutes
after
it's
what
April
tenth
hard
to
tell
when
you're
standing
up
as
late
as
as
I
did
yesterday,
but
but
welcome
to
today's
a
community
meeting,
we're
graced
with
the
presence
of
man.
Well,
I
think
this
might
be
your
first
time
on
the
community
call
as
a
rite
of
passage.
You
are
immediately
and
awkwardly
put
on
the
spot
to
say.
Welcome!
A
Thank
you
very
much
for
being
here
very
nice
to
have
you
I've
gotten
a
little
bit
acquainted
with
and
familiar
with
Manuel,
although
I
don't
know
that
everyone
else
is,
and
so
here's
the
awkward
part
and
then
well,
if
you're,
in
a
position
to
to
talk
and
and
introduce
yourself.
That
would
be
great
to
get
to
know
you
so.
B
A
And
I'm
well
very
nice
to
have
you
we're
gonna,
have
to
think
of
some
some
moniker
I'm,
not
sure
if
it's
DevOps,
DevOps
master,
DevOps,
ninja,
there's
some
there's
something
that
goes
with
that
we're
just
we're
actually
I
think
I
have
a
bit
of
a
well
good,
well,
a
bit
of
a
continuous
integration,
a
github
actions,
kind
of
workflow
discussion
today
that
might
be
of
interest,
so
okay,
yeah,
so
fantastic
to
have
you
on.
Please
do
please
do
meet
the
rest
of
the
folks
here.
Most
of
these
folks
are
regulars
all,
except
for.
C
A
C
A
C
C
Contributing
so
on,
I
don't
have
too
much
community
things
going
on
and
it
was
on
purpose
in
order
to
know
what
I
want
to
focus
on
and
so
on.
So
it
will
be
like
container
stuff,
mostly
meshes
and
kind
of
end
above
stuff.
Yes,
that's
it
they
vote,
but
not
I'm,
not
good
on.
That's
it.
I
said
it's
very.
C
Bring
it
yeah,
it's
a
thing:
it's
it's
good,
yeah
I'm
having
a
hard
time
on
being
useful
in
the
last
couple
of
four
months,
and
so
when
did
you
get
it
too
much
time
for
myself,
I
think
and
we
disbanded
me
I
realized
that
yeah
so
I'm
open,
so
don't
worry,
I
go
hit
there.
It's
too
much
I
might
complain
what
party
that's
right.
C
A
A
C
Yeah,
so
you
you
have
so
many
so
great
stuff
in
measuring
and
so
on,
and
a
lot
of
things
are
still
building
up.
So
it's
hard
to
keep
up
so
community
is
the
way
to
learn
and
so
on.
Nothing
having
the
job
is
not
good
and
so
on,
but
so
many
restrictions
and
things
like
that
that
can
you
you
grow
more
with
the
community.
I
would
say
so
yeah.
That's
my
I'm
always
having
an
interest
so.
A
C
C
A
A
Announcements,
a
few
of
them
here,
one,
is
that
there
yesterday
was
delivered
the
introduction
to
isseo
I'm,
so
live
training
I'm
assuming
that
yeah
that
this
is
being
shared.
So
so
the
reason
I'm
sharing
this
is
to
say
that
there
are
three
individuals
on
this
call
that
made
the
delivery
of
this
training
yesterday,
not
a
complete
disaster,
and
so
I
wanted
to
take
a
moment
to
thank
Shiva,
Naveen
and
Kanishka
for
having
spent
time
trying
to
make
sure
that
the
workshops
in
the
labs
that
we
were
delivering
yesterday
worked.
A
I
was
complaining
about
having
to
stay
really
late,
to
make
sure
that
things
were
working
and
and
and
then
I
realized
just
how
late
in
the
V
and
SH
if
I
were
up
as
well.
So
thank
you
guys.
It
was
very
helpful.
Actually
many
of
you
that
are
on
the
call
can
see
the
works
of
what
the
works
of
that
workshop,
just
in
in
slack
yesterday
I
think
there
were
25
new
people
that
joined
slack
and
so
that's
great.
They
joined
because
they're
their
students
studying
service
meshes
and
part
of
this
workshop.
A
There
are
a
number
of
you.
I
wasn't
kidding
earlier
when
I
said:
hey
we're
all
here.
Learning
I
certainly
include
myself
in
that
very
much
so
the
workshop
and
the
labs
here
these
are
open
to
community
members,
and
so,
if
you
consider
that
you
would
benefit
from
walking
through
the
labs
just
signal,
there
are
a
bunch
of
community
members
already
that
know
where
those
labs
are,
and
they
can
point
them
out
to
you.
A
Next
topic
was
a
minor
event.
Well,
what
is
it
not
a
you
technically,
not
a
minor
release,
but
like
a
patch
release
was
done
yesterday
somewhat
quickly
to
try
to
incorporate
support
for
scoop
and
if
you're,
not
familiar
and
and
I'm
not
scoop
is
a
scoop.
Is
a
packaging,
a
package
management
system
for
Windows
I?
Think
in
so
much
as
I
understand.
A
For
career
cgl
packages,
thank
you
very
much
push
for
leading
that
effort,
creating
documentation
at
the
same
time,
there's
just
kind
of
an
outstanding
ask
here
for
anyone.
That's
interested
in
testing
that
the
scoop
packages
if
anyone's
running
Windows
and
would
like
to
see
if
the
mesh,
the
mesh
Cherie
CLI,
I'm,
Ashley
CTL,
can
install
through
scoop
and
work.
Does.
That
is
that
of
interest
to
anyone.
A
A
So
next
was
I'm
not
sure
if
I'm
Kecia
cars
on
the
call
today
he
may
not
be
he's-
has
a
medical
issue
and
unfortunately
I'm
he
and
his
family
are
sheltering
in
place
and
not
able
to
go,
get
some
medicine,
and
so
that's
preventing
him
from
being
online
right
now,
I
think
he's:
okay,
he's
gonna,
be
okay,
but
but
but
yeah
so
point
of
talking
about
quiche
cars
because
he
and
I
had
Oh
logged
a
potential
talk
for
q4
I'm,
sorry,
dr.
Cohn
and
there's
interest
in
that
talk
and
more
than
that.
A
There's
interest
in
holding
a
panel
on
service
meshes
with
the
cube
if
anyone's
familiar
with
the
cube,
I
think
it's
the
silicon
angle,
silicon
angle:
they
have
this
cube
interview,
series
and
so
and
so
I
don't
know
with
any
luck.
We
might
be
able
to
get
teenisha
on
that
as
well.
That
would
be
really
neat.
Are
you
moving
through
the
announcements
yesterday?
A
Well,
this
is
something
of
a
personal
note,
but
but
not
entirely,
because
I
really
consider
that
all
the
things
that
I'm
doing
where
my
plate
is
spilling
over
truly
are
opportunities
for
anyone
else
to
step
in
and
participate.
So
yesterday,
my
Reilly
editor
had
asked
for
and
approved
a
book
on,
service
mesh
patterns
of
which
I'm
committed
to
the
idea
that
this
is
the
right
thing
to
do
to
put
out
another
one
and
in
general,
about
best
practices
and
patterns
of
running
surface
meshes
and
other
than
that.
A
A
So
I'm
excited
about
that
part
of
that
partnership
means
that
we'll
be
doing
some
things
publicly.
So
I've
got
a
webinar
tentatively
slated
for
the
23rd
of
April,
speaking
of
meetups
and
and
kind
of
virtual
meetups
that
there
are
to
meetups
in
Austin
that
that
I
organized
one
of
them
is
this.
C&Amp;C
f
meet
up.
So
it's
cloud
native
Austin,
the
other
one
is
dr.
Austin,
and
so
it's
sponsored
by
docker
we're
gonna
go
forth
with
our
first
virtual
meetup
this
coming
Thursday.
A
It
just
so
happens
that
measure
E,
there's
two
topics
for
that
meetup
one
of
them
is
necessary.
The
other
one
is
crudo.
If
you
haven't
heard
of
Kudo
before
it's,
both
mystery
and
Kudo
actually
are
proposed
for
entrance
into
CNCs.
Sandbox
Kudo
is
stewarded
by
d2,
IQ,
formerly
known
as
Mesa
sphere,
and
so
we
need
to
update
the
details.
A
A
So
there's
proposal
sitting
out
there
to
work
on
this
project,
and
then
there
are
three
proposals:
sitting
out
there
to
work
on
this
project,
about
service,
mashie
interface
and
measuring
being
a
conformance
tool
for
service
mesh
interface,
again,
mostly
for
the
benefit
of
those
that
either
haven't.
Seen
this
in
the
past
that
SMI
or
service
mesh
interface
is.
This
is
sort
of
a
lowest
common
denominator,
API
behind
which
different
service
meshes
can
plug
in
and
measure
E
and
layer.
5
were
launch
partners
with
this
initiative.
A
Last
cube
con
tu,
so
not
the
one
that
we
just
missed,
but
the
one
that
was
a
year
ago
in
Barcelona
and
just
two
weeks
ago
last
this
Friday
I
approved
SM
eyes
entrance
into
the
CNCs
sandbox,
and
so
it's
there
now
actually
later
today,
today's
the
10th
later
today
there's
a
CNC
have
webinar
on
kind
of
introducing
SMI,
so
actually
for
those
that
are
have
made.
Some
of
you
that
made
these
proposals
are
here
in
this
community.
Remind
me
on
this
call
to
get
you
a
link
to
that
CN
CF
webinar.
A
It
might
be
of
interest
to
you
to
just
get
you
more
introduced
to
what
SM
is
our
last
announcement
briefly.
That
is
that
when
I
say
that
I
approved
SM
eyes
entrance
into
the
scenes,
yes,
I
say
that,
with
my
CN
CF
had
on
the
that
hat
is
worn
in
context
of
sig
Network.
There's
a
kubernetes
sig
network
there's
also
a
CF
cig
network
that
CF
cig
network
is
home
base.
If
you
will
or
like
homeroom.
A
If
you
look
for
linker
de
Envoy,
G
RPC
Nats,
core
DNS,
the
the
network
and
traffic
related
projects,
then
the
scenes
yeah.
The
next
meeting
that
we
have
is
this
coming
Thursday
chaos
mesh
will
be
presented.
It's
proposed
for
us
as
a
sandbox
project.
A
number
of
you
will
remember
that
I
think
it
was
about.
Two
weeks
ago
there
were
maintained
errs
of
chaos
mesh
on
this
call,
and
they
gave
a
quick
introduction
to
what
that
project
is
about
well.
I
will
say
understanding
that
most
of
you
are
probably
not
familiar
with
the
project.
A
As
a
brief
introduction,
we've
also
had
littmus
chaos.
I
think.
Is
it
what's
called
representatives
on
this
call?
I'm
demoing
that
miss
chaos
they're
both
really
just
frameworks
for
creating
and
executing
experiments.
The
name
chaos
mesh
sounds
a
bit
more
messy
than
it
necessarily
is
it's.
It's
a
bit
more
of
a
general
framework
for
experimentation
in
a
kubernetes
centric
way,
but
because
of
the
mental
Association,
I
think
that
people
have
with
mesh
in
the
name
and
because
they
do
have
some
network
centric.
A
So
here's
another
open
opportunity
for
people
who
might
be
interested
in
this
topic.
There's
just
Kevin
and
outstanding,
there's
an
outstanding
desire
for
there
to
be
chaos,
capabilities
inside
of
nursery
or
in
a
project
adjacent
to
memory.
The
discussion
that
we
had
with
the
chaos
mesh
team
was
to
potentially
ingest
chaos
mash
in
measure
E
and
then
facilitate
the
running
of
experiments
from
from
within
mr.
e
Network
Center
ServiceMaster
centric
experiments,
so
I
know
that
that
struck
a
chord
with
a
couple
of
people
who
I
don't
think
are
on
the
call
right
now.
A
A
A
A
So
while
shibai
brings
this
up
for
context,
we've
had
a
release
of
mystery
to
make
for
a
couple
of
weeks
now
and
kinda
the
longer
that
we
wait,
the
bigger
the
release
gets,
which
which
isn't
a
bad
thing,
but
we're
just
a
little
overdue
to
make
the
release
I'm
part
of
making
that
release,
and
thankfully
Shivaya
is
focused
on
it,
and
part
of
that
means
that
hopefully,
we'll
have
some
better
release
process
in
place.
Take
all
in
all.
We've
got
like
44
releases
of
the
project
so
far,
many
of
which
are
rather
small.
A
F
F
F
So
we
can
have
a
separate
page
for
the
raise
notes
in
that
we
can
have
a
separate
column
for
all
the
previous
releases
and
the
current
release
can
be
shown
in
terms
of
the
only
website
itself,
like
it's
being
shown
on
big
github
or
release
notes.
So
the
people
don't
necessarily
need
to
go
to
the
documentation,
to
see
the
release
notes
or
to
the
github
repo
slash
releases,
slash
whatever
currently
is
that
we
have
so
it
can
be
their
only
main
memory
website
as
well.
A
G
F
G
F
Right
now,
some
people-
they
put
you
know
the
so,
for
example,
if
it's
related
to
you,
why
they're
putting
it
in
B
brackets
and
saying
you
I,
but
a
lot
of
them
are
just
having
general.
You
know,
pull
up
it,
but
they're
not
having
the
tags
of
it
attached
to
them.
At
least,
then
we
must
be
repository.
A
One
thing
that's
encouraging
about
the
consideration
of
the
use
of
something
like
release.
Drafter
is
well,
frankly,
is
behavior
that
Naveen
and
Kush
have
begun,
and
that
is
to
really
like
organize
the
open
issues
that
we
have.
Escucho
has
been
leading
in
this
way
as
well,
about
sort
of
structuring
the
labels
that
are
using
in
between
the
github
repos
a
bit
better
being
a
bit
more
consistent,
trying
to
kind
of
clean
up
the
all
the
outstanding
issues.
That
gives
some
hope
that
at
a
tool
like
like
a
release,
drafter
could
potentially
be.
A
F
G
We
will
have
just
one
problem
released
after
that.
We
need
to
label
PRS
like
if
it's
a
documentation,
Pia.
We
need
to
have
document
label
upon
it.
If
it
isn't
PR
related
to
you,
why
your
doctor,
we
need
to
have
appropriate
label
on
it.
So
for
this
we
can
either
design
a
custom
bot
or
we
can
use
a
third-party
bot,
which
is
a
community.
A
Actually
may
be
a
topic
to
add
on
for
just
a
moment
about
bots
there's
been
a
couple
that
have
been
you
know
suggested.
One
of
them
is
a
welcome
bot
and
another
one
is
a
scale
Bron
another
one
is
a
triage
bot,
another
one.
Is
it
not
actually
no
there's
one
other
one
and
actually
signed
you
said
it
as
well.
A
That
sandbox
is
the
mystery
Ken
within
there
a
couple
of
these
bots
have
been
turned
on,
so
those
that
aren't
familiar
with
the
capabilities
or
the
behavior
of
some
of
these
thoughts.
You
can
see
them
in
action
in
this
sandbox,
so
everyone
here
is
welcome
to
do
essentially
anything
they
want
to
do
in
that
in
that
repository,
and
if
you
don't
have
the
permissions
to
do
it,
we'll
make
sure
that
you
do
up
so
that
you
can
test
some
of
these
things
out
and
I.
A
A
Well,
one
he
did
if
there
was
general
opinion
or
if
anyone
had
opinion
about
the
use
of
a
walking
bomb,
my
really
negative,
or
that
I
could
think
it
was
whether
or
not
people
contributors
would
perceive
it
as
disingenuous
that
there's
a
bot
saying
thank
you
and
celebrating
it
rather
than
a
person,
but
I,
don't
know
that
that's
I
don't
know
that
people
feel
that
way.
They
might
be
happy.
A
A
H
J
But
in
the
talker
actions
that
you
have
a
flexibility,
you
incorporate
a
great
mind
wise
and
if
each
individual
things
inside
of
a
talker
image,
so
that,
but
that's
a
very
good,
very
gain
to
foot
and
people
are
also
using
that
toe
Corrections
for
release.
Doctor
I
think
some
of
them
I
actually
got
through
some
of
the
companies
that
they
are
doing
the
same
thing.
But
one
problem
is
that,
as
they
are
basically
slow
because
you
have
to
go
down
there,
pull
the
topper
images
for
that
and
then
other
things
happening.
J
So
that's
quite
all
right,
slow
and
javascript-based
are
basically
fast,
but
do
you
have
it
a
lot
of
things,
pure
self,
so
I
think
in
in
the
members
here
they
are
doing
that.
So
we
can
look
at
what
are
their
capabilities
are
if
they
are
familiar
with
the
JavaScript
base,
they
have
to
do
some
kind
of
own
work
on
their
behalf,
so
I
think
it's
kind
of
a
initial
thing.
We
call
would
recommend.
We
take
a
look,
because
this
is
a
very,
very
modernized
way
of
I.
A
A
A
Potentially,
breaking
down
work
flows
into
smaller
segments
might
be
helpful.
I
think
I've
seen
us
sort
of
take
the
initial
workflow
we
kind
of
build
on
it
and
build
on
it
and
sort
of
build
on
it
again
and
after
a
while
it
does,
you
know,
start
to
take
a
number
of
minutes
and
so
yeah
if
release
and
a
release,
drafter
or
whatever
mechanism
that
we
use
to
track
change
logs,
if
that
was
an
independent
one
that
might
be
that
might
be
nice,
because
so
we
can
invoke
these
only
as
necessary.
A
A
Another
component
and
we've
talked
about
this
in
the
past,
but
another
component
is
measure
EC
TL,
it's
a
compiles
to
a
single
static
binary.
It
could
be
its
own
repo
as
well
and
then
the
rest
is
sort
of
measuring
itself,
there's
logic
and
reasoning
behind
why
we
have
these
three
in
one
repo.
I
won't.
I
won't
regurgitate
that
now,
but
I'm
highlighting
it
in
context
of
the
discussion
around
actions
and
workflows.
J
Some
of
the
work
they're
using
in
at
your
dev
ops
in
some
of
them,
we
are
using
that
he'll
have
actions,
so
they
have
kind
of
a
shame
for
a
globe
and
they
have
doing
in
two
different
things.
So
and
people
are
then
people
are
thinking
that
the
best
practices
that
you'll
average
of
one
platform
to
enables
horsefly
enough
of
them.
J
So
if
we
are
using
either
providers
as
the
date
of
action
of
their,
so
we
can,
we
can
go
for
natively
for
that
tool
is
valid,
so
it
gives
kind
of
a
central,
replace
centrally
placed
with
every
contributor
things
that
they
are
the
interactions.
They
don't
have
gugu
and
learning
different
platform
to
understand
that
so
I
think
we
move
most
of
the
things
that
we
could
do
in
the
future
in
get
in
using
the
github
platform
itself,
like
their
gated.
F
J
J
They
have
it,
it
doesn't
find
it
in
the
marketplace.
I
think
we
could
do
have
a
lot
of
conversation
on
that
and
I
think
the
one
that's
practice
that
I
about
some
other
people
are
considering
that
if
you
are
going
natively,
if
doesn't
do
the
demo
places
in
three
different
things,
instead
of
going
to
the
one
place.
A
Your
voice
is
actually
really
low.
It's
it
makes
part
of
hearing
it
a
bit
hard,
but
it
sounds
like
at
least
for
my
part.
What
I'm
taking
away
is
that
is
that
there
are
a
couple
of
folks
names
to
associate
with
thoughts
and
and
efforts
to
improve
here.
Your
yours,
Adina's,
shibai,
I'm
gonna,
try
to
steal
you
away
from
this.
If
I
can
to
go,
do
some
things
in
that
new
UI
yeah.
A
C
C
It
would
take
I
would
make
it
an
firstly,
it
doesn't
look
so
complicated
for
me
to
take
this
only
two
things
out
from
where
amore
poetry
and
who
build
them.
Work
from
ABARES
workflow,
but
I
will
see
I,
not
sure
about
my
experience
with
github
workflows,
but
I
have
with
others
with
which
other
tools
with
other
much
worse
spoke
I.
Think
I
can,
if
not
I
will
I
will,
but
the
girls
I
would
not
call
you
and
others.
Oh
okay,
but
thanks
for
the
document
is,
would
I.
A
There's
much
more
to
come
in
terms
of
governance
and
people
and
roles
and
a
contributor
ladder
and
various
things
like
that.
But
with
respect
to
building
and
releasing
there's
just
a
single
release
channel
for
the
project
right
now
and
for
each
of
the
components
and
by
a
release,
channel
I
mean
there.
Isn't
the
people
don't-
and
this
is
very
familiar
I,
think
to
all
of
you.
A
But
there
isn't
the
ability
to
to
maybe
borrow
an
example
from
docker
to
go
download
the
edge
release
for
measuring
of
the
beta
release
if
you
will
and
or
subscribe
to
the
stable
channel.
So
there
aren't
there's
a
single
channel
and
really
right
now
the
way
that
part
of
this
works
is
when
a
P,
a
pull
request
is
merged
into
the
master
branch
in
the
Mestre
repo.
A
Build
automation,
takes
place
and
pushes
new
images
to
github.
If
an
a
user
is
actively
running
massery,
it
would
just
be
a
matter
of
time
before
measure
automatically
updates
itself.
So
there's
a
component
within
memory
that
reaches
out
and
checks
from
new
image
versions
and
downloads
them,
and
that's
not
a
bad
behavior.
But
it's
one
that
we
want
to
empower
users
to
have
control
over
and
in
order
to
do
that,
we'll
you
know
need
to
us
need
to
establish
a
couple
of
release
channels.
A
C
Yeah,
you
definitely
need
to
have
this
separately
because,
for
instance,
the
component
I'm
working
for
there
is
first,
you
know
the
securities
which
are
validating
and
so
on,
and
then
another
Department
and
so
on,
but
that
the
thing
sometimes
they
are
using
whatever
version
which
doesn't
have
whatever
security
bridge
or
what
which
one
is
covered.
So
everything
has
to
be
approved
before
automatically
update.
C
So
there
are
now
automatic,
like
automatic
updates
and
especially
with
everything
that
is
related
to
the
networking
stuff,
and
so
it's
even
worse.
It's
there
are
more
layers
of
approving
stuff.
So
if
it
says
today,
yes,
it's
going
is
gonna
take
some
times
so
yeah
the
edges
for
in
the
development,
when
what
you
have
is
nothing
is
not
enough
or
something
like
that,
but
they
are.
We
need
that
yeah
I
still
need
to
get
familiar
with
things
and
so
on,
but
you
definitely
need
that.
A
Yeah,
after
what
went
in
when
you
have
big
shoulders,
you
have
to
watch
out
because
cuz
then
asks
like
this
get
get
pushed
your
way
so
anyway,
so
we
didn't
really
have
a
ton
minutes
left
I
wish
did
have
he's
been
pretty
busy
this
week,
making
a
mess
of
issues
and
PRS
and
submitting
a
bunch
of
them
coach.
I
know:
you've
got
a
couple
of
things
that
are
maybe
in
a
demonstrable
state.
If
you
want
to
share
your
command
your
command
line,
let's
get
a
demo
man.
G
It
should
be
now
there,
it
is
so.
I
was
working
on
error,
checking
improvement
in
the
first
up
command
of
my
CDL
so
like
previously,
previously
the
earth
command
was
having
the
tests.
Name
is
a
required
field,
but
now
I
have
made
it
optional
field,
and
if
the
user
will
not
provide
a
test
name
field,
the
command
will
automatically
use
a
random
name,
which
you
can
see
over
here,
like,
as
you
can
see,
test
them
not
provided
using
random
test
name
and
before
there
were
issues
like
if
a
URL
was
unreachable.
G
The
test
was
still
showing
the
success
message
so
I
have
just
captured.
The
error
like
currently
I
have
used
an
error
127.0.0.1,
which
is
not
reachable
or
not
on
my
server.
So
if
I
will
run,
it
will
show
me
failed
to
make
requests
to
URL.
We
can
even
capture
what
was
the
URL,
which
is
which
is
the
pending
pending
work
on
it,
and
also
there
are
multiple.
There
are
multiple
scopes
of
improvement
in
this
command
like
if
I
will
change
the
load
generator
to
any
random
number
for
any
random
string
ABC.
A
The
GQ
mind
since
this
is
probably
the
last
topic
of
the
meeting,
maybe
a
couple
of
questions
for
you
about
the
current
behavior
of
measure.
Cpl
Perth,
if
you
just
to
confirm
I,
think
some
of
this
has
been
addressed.
But
if
you
were
to
run
just
measure,
EC
TL
perf
with
no
other
parts,
we
giving
the
user
an
example,
call
yeah.
You
know
in
my
mind,
and
certainly
everyone
else,
I'm
China
and
just
for
context.
A
You're
familiar
with
a
user
interface
inside
of
my
Sri
to
run
a
performance
test
to
generate
load,
hit
an
endpoint
and
then
do
statistical
analysis
on
how
responsive
that
endpoint
was
did
what
pushes
demoing
is
that
same
ability,
but
doing
it
from
the
command
line,
and
to
do
so
that
there
will
be
two
ways
in
which
we
expect
people
to
do
this.
One
is
to
specify
a
series
of
flags
which,
in
my
mind,
kinda
stinks
the
other
way
to
do.
It
will
be
so
push
the
thing
I
was
gonna
want
to
make.
A
G
A
A
So
then
just
you
know.
You
know
two
minutes
on
this.
Just
for
kind
of
context
about
Mary's
performance
testing.
Is
that
one
of
the
projects
within
the
community
is
this
service
mesh
formants
specification
so
as
cush
was
demonstrating
the
fact
that
you
can
run
a
mastery,
CTL
perf
and
specify
any
number
of
flags,
those
flags
would
specify
like
what
endpoint?
What
URL
do
you
want
to
test?
How
much
load
do
you
want
to
generate
for
how
long
a
bunch
of
just
parameters
about
how
you
want
to
run
that
performance
test?
A
Our
hope
is
that,
most
of
the
time
that
people
are
doing
that
they're
doing
something
more
like
a
mastery,
CTL
or
/
f
that
they're
just
pointing
to
a
file.
A
ya
know
file
that
captures
all
of
those
parameters.
So
it's
a
bit
easier
to
not
have
to
type
a
lot
type
it
all
in
and
that
yam
will
file.
The
format
of
that
would
be
one
in
the
same.
A
A
This
is
probably
one
of
the
deep
areas
that
people
will
know:
log
necessary
for
about
service
performance
management
and,
ultimately,
that
specification,
the
service
master
performance
specification.
I
know:
we've
talked
about
it
any
number
of
times
in
this
call,
but
there's
an
intention
to
create
a
commonly
referenced
index,
a
mesh
decks.
A
I
J
You
hear
me
right:
yep,
Hayley
I
think
we
should
goes
11
separate
meeting
for
a
release,
see
ICD
system
in
a
in
in
every
meeting.
We
can
do
that
or
separately
for
individual
individuals
who
take
parts
on
that
and
for
that
meeting
we
just
discuss
about
that
things.
I
think
that's
a
central
place
if
we
things
care
to
get
going
well
in
that
direction.
I
think
moving
forward
is
a
less
complication
weighing
forward
yep.
A
A
J
Leave
where
I
just
thinking
about
if
we
couldn't
do
in
the
Manistee
of
ID
meeting
so
I
can
separate
discuss
with
a
person
that
who
are
interested
in
that
kind
of
a
domain,
so
we
could
do
rather
than
in
that
everybody.
In
that
meeting,
we
could
do
that
person
that
I'm
very
holistic
about
this
and
passionate
about
CI
CCD
system
developed
system
infrastructure
on
it
is
cloud
native
stuff,
so
I
think
we
could
do
a
separate
meeting,
but
just
discussing
about
how
we
can
build
infrastructure
CIC,
any
system
deployments
I
think
moving
forward.
J
We
have
to
do
that
because
I
think
this
is
a
corner
store
of
our
project.
If
we've
done
something
right,
there
I
think
moving
forward.
We
have
less
and
more
less
complication,
moving
I
think
I
definitely
do
on
my
side
and
engaging
with
other
people's
and
I
think
moving
forward.
I
think
eyes,
missed,
sat
this
meeting.
A
So
I'm
I'll
work
with
you
to
try
to
to
make
sure
that
we've
got
that
we've
got
a
or
a
googol
meet,
and
then
we've
got
time
on
the
calendar
sign
if
you
would
maybe
take
the
reins
in
terms
of
soliciting
interests
within
the
community
about
those
that
we
want
to
participate
in
that
ongoing
work
stream.
That
would
be
great.
J
Okay,
Lee
I
definitely
do
that
and
also
going
forward
some
plans
there
and
moving
forward
some
capturing
some
demos
there
that
we
have
pretend,
because
if
we
show
something
at
a
more
real
life,
so
they
can
understand
the
concept
easily.
So
in
this
week,
I'm
I
try
to
run
some
that
demos
there
and
off
also
engage
some
people's
on
that
kind
of
thing.
J
A
That's
good,
oh,
you
got
sounding
off
already.
This
is
great,
perfect!
Okay,
it
I
want
to
make
always
we
have
such
a
nasty
habit
of
spilling
over
all
the
time.
I
want
to
try
to
end
now,
if
you
can
and
encourage
everyone
to
sound
off
in
terms
of
like
what
might
work,
timing
wise
and
and
day
wise
for
those
that
are
interested
in
and
let's
make
it
happen,
let's
make
it
happen
this
week.
This
coming
me
very
good.
All
right,
happy,
Friday,
everyone
spin!
This
has
been
nice
baby,
be.