►
From YouTube: Meshery Development Meeting (Nov 25th, 2020)
Description
@utkarshdev23 demonstrates the new Meshery adapter framework: meshkit. Welcome Lavinia!
A
A
It
just
means
you
get
to
eat
the
whole
thing,
all
right,
very
good,
we're
a
couple
of
minutes.
After
let's,
let's
get
going
november
25th
day
before
thanksgiving
in
the
u.s,
we've
got
a
set
of
holidays
coming
up,
so
welcome
everybody.
This
is
the
mess
redevelopment,
call
I'm
hoping
that
I've
got
audio,
because
it's
either
that
my
jokes
are
really
not
funny
today
or
or
my
audio
isn't
coming
through,
and
I
I
hope
that
it's
the
latter.
B
A
I
do
recognize
that
we're
on
the
cusp
of
vacation
season
for
many
of
us
will
have
various
holidays
and
things
we
will
be
sure
to
signal
in
advance
if
any
of
the
meetings
that
we
have
each
day,
because
we
have
a
meeting
each
day
for
the
various
projects
that
are
going
on
we'll
be
sure
to
signal
in
advance.
If
any
of
those
are
cancelled.
A
I
haven't
looked
at
the
week
of
christmas
and
kind
of
new
year's,
but
it's
it's
it's
it's
possible
that
we
might
not
actually
meet.
Then
we
certainly
wouldn't
meet
on
christmas,
if
that's
yeah.
So
but
it's
nice
to
see
everyone
here
now
and
a
couple
of
new
faces
as
well.
We've
got
some
agenda
items
everyone.
A
Well.
Actually
it
may
be
the
case
that
everyone
on
the
call
doesn't
necessarily
have
access
to
the
meeting
minutes,
which
would
be
unintentional.
Everyone
should,
if
you've
been
on
a
call
before
you
know
that
the
meeting
minutes
are
a
community
effort.
So
please
please,
if
you're
on
the
call,
please
do
jump
in
and
toss
your
name
onto
the
list.
A
A
A
D
Yeah
sure
I
call
me
sudarshan
if
my
name
is
difficult
to
pronounce
and
I'm
a
third
year,
computer
science
undergrad
on
sri
lanka
and
I've
been
trying
to
get
into
mystery
community
and
got
to
know
this
community
through
community
bridge
mentorships,
but
I'm
trying
to
get
into
this
and
I
got
time
sorry.
I
couldn't
I
joined
the
community
last
month,
but
I
couldn't
attend
any
calls
like
meetings
before
like
I'm
trying
to
get
in
and
contribute
to
the
projects
on
this
month
on.
That's
my
commit.
A
A
Sit
down,
okay,
all
right!
Well,
this
goes
for
you
and
then
maybe
for
others
who
are
new
on
the
call
as
well.
If
you,
if
you
haven't,
really
found
a
point
of
interest
or
found
a
foothold
on
the
projects
or
one
of
the
projects,
I'll
I'll
chat,
you
I'll
chat
you
up
I'll
I'll
point
you
you
know
point
you
to
some
areas
of
potential
interest,
so
good
good
to
have
you.
E
Hello,
no,
I
haven't
been
into
this
before
so
I'm
definitely
from
romania,
I'm
the
friends
of
adina.
She
told
me
a
little
bit
about
this
project
and
invited
me
to
participate
as
well.
So
here
I
am
I'm
a
software
developer
and
I
have
about
10
plus
years
of
experience
for
the
past
three
years.
I've
been
working
at
public,
but
unfortunately
I've
been
let
go
and
currently
I'm
in
between
jobs,
but
I
would
like
to
participate
in
some
other
open
projects
as
well.
A
A
E
A
G
Hi
good
afternoon,
hello,
hello,
can
you
hear
me
yep
yeah,
so
I'm
tony
and
I'm
a
fifth
year
undergraduate
student
of
computer
science
with
economics
and
yeah,
I
heard
about
merch
retro,
a
community
bridge
mentorship
program,
I'm
hoping
to
get
in
like
next
match
like
yeah.
So
I
just
said
I
should
just
join
the
community
like
now
and
just
see
how
it
goes.
A
A
A
A
A
H
B
J
J
A
K
A
I
just
just
had
this:
it's
embarrassing.
I
had
a
disagreement
with
my
wife
this
morning
and
I
suspect,
I'm
in
the
heat
of
the
discussion
I
didn't
feel
like.
I
was
wrong,
but
I
think
that
maybe
my
memory
is
fading,
and
so
this
is
more
proof
than
like
yeah.
Okay,
good
good
me.
Who
do
you?
You
don't
know
pressure.
This
is
just
a
but
to
today's
smi
call.
H
H
Yes,
so
basically
it's
it's
doing
the
same
thing
that
it
used
to
do.
That
is
installing
kuma
service
mesh,
but
just
right
now
it
is
using
the
new
library
that
is
meshgate
and
mystery
adapter
library,
so
a
lot
of
code
is
now
basically
shared
among
different
adapters,
one
of
which
is
kuma.
Tinkeri
is
also
almost
complete.
Nginx
is
also
almost
complete
right
now:
okay,
yeah,
so
installation
is
complete.
H
H
A
H
A
What
he's
showing
is
the
fact
that,
for
the
nine
different
adapters
that
the
project
has
there's
been
a
lot
of
repetition
and
redundancy
in
of
code
for
each
each
service,
mesh,
that's
supported,
has
its
own
adapter,
and
that
code
has
literally
been
repeated
and
repeated
and
repeated
and
repeated
repeatedly
repeated
nine
times
and,
and
so
michael
and
abhishek,
and
a
couple
of
others
have
worked
to
help
us
help.
The
project
start
repeating
itself
and
so
lukasz
is
showing
showing
off
basically
a
v.
A
You
know
a
second
edition,
a
re-architecture
of
the
adapters
at
least
of
a
few
of
them,
and
so
we're
gonna
be
chewing
through
the
rest
of
the
list.
Soon,
a
couple
of
benefits
outside
of
being
able
to
work
more
efficiently,
have
higher
quality
of
code.
There's
a
couple
of
feature
or
functional
benefits
that
come
out
of
this.
A
One
of
those
is
that
well
so,
each
of
the
servicemen
each
of
mesherie's
adapters
has
its
own
version
number,
which
is
both
intentional,
and
it's
also
kind
of
a
pain
in
pain
in
the
rump.
It's
intentional,
because
each
adapter,
each
individual
service,
mesh,
istio,
kuma,
linker
d-
they
all
have
their
own
life
cycle.
They
all
advance
on
their
own
cadence.
They
all
are
their
own
independent
projects,
some
update
faster
than
others.
Consequently,
some
of
mesherie's
adapters
update
faster
than
others,
and
so
it
makes
sense
that
they
have
their
own
version
number.
A
The
mesher
ui
doesn't
have
its
own
version
number,
it's
the
same
as
the
server.
So
that's
nice.
Each
adapter,
though,
has
its
own
version
number
and
the
meshery
client
mesh
free
ctl,
the
command
line,
client.
It
has
its
own
version
number.
So
it
starts
to
get
a
little
bit
arduous
to
track
down
to
like
report
a
bug
and
say
well.
This
is
the
version
that
I'm
running
you're
not
always
able
to
just
say
it's
version
4.23,
you
might
have
to
list
out
all
the
components.
A
There's
a
probably
that's
a
separate
kind
of
discussion
about
about
our
release
process
and
how
to
improve
upon
that.
But
having
these
new
adapters
br
enable
us
with
some
new
functionality,
one
of
them
is
crash.
If
you
go
to
the
dashboard,
the
home
page
of
meshri
on
the
lower
right
hand,
side
in
the
past,
you
had
worked
on
the
functionality
around
release,
channels
and
version
numbers,
so
the
lower
right
hand
corner
there's.
A
So
that's
nice,
actually
utkarsh
I'll,
try
to
take
some
meeting
minutes
as
we
go,
but
there's
an
opportunity
for
us
when
there
is
a
new
version
available
to
have
a
hyperlink
to
that,
maybe
to
show
the
release
notes
or
to
have
a
tool
tip
that
shows
people
the
mastery
ctl
command
to
update
it,
or
maybe
you
know
or
something,
but
the
other
thing
that's
missing
here
is
well.
You
know
it
looks
like
you've
got
a
few.
A
H
I,
no,
I
don't
think
right
now.
We
basically
send
back
the
version
of
adapter
that
we
are
running,
but
actually
adapter
is
like
it.
After
it
does
know
what
the
version
of
adapter
is.
Basically,
the
adapter
is
familiar
of
its
own
version,
so
it
says
that
we
have
to
send
it
back
to
the
server
and
then
to
the
ui
adapter
how's.
That
capability.
J
A
Yeah,
the
the
the
pa,
this
the
pace
by
which
each
of
the
adapters
is
being
re
is
being
rewritten
is
something
of
a
testament
to
how
much
easier
it
is
yeah.
Okay,
all
right,
fair
enough!
Anybody
else
have
feedback
for
utkarsh
on
this
bootcase.
Is
there
anything
so
the
this
will
run
the
smi
conformance
test
in
the
current
release
of
the
kuma
adapter
like
have
these
changes
been
released.
H
They
haven't
like,
I
still
have
to
push
it
to
the
repository.
I
tried
running
a
smi
conformance
test.
It
was,
it
was
running,
but,
like
my
system
has
resource
constraints,
so
actually
it
didn't
throw
any
kind
of
error,
but
it
was
taking
very
long,
so
maybe
abhishek
might
test
it
on
on
it.
On
his
system,
my
system
has
a
bit
of
resource
constraints.
It's
still
something
that
needs
to
be
tested,
but
on
a
positive
side,
then,
through
any
computer.
H
A
A
All
right,
all
right,
very
good.
Let's
go
back
to
the
meeting
minutes.
If
we
could
a
couple
of
couple
of
quick
notes.
One
is
mostly
just
for
everyone
else
that
if
you
don't
have
access
to
these
meeting
minutes
or
to
the
mastery
architecture,
please
just
say
so
in
the
chat
and
I'll
we'll
get
you
that
access
right
now,
so
that
you
can
have
a
productive
call.
A
A
A
The
the
challenge
right
now
is
that
users
don't
have
the
ability
or
the
don't
easily
and
conveniently
have
the
ability
to
switch
between
one
release
channel
versus
the
next.
So
I'm
gonna
we'll
show
you
how
that's
that
can
be
done
in
a
couple
of
ways.
Today,
people
can
switch
between
a
stable
channel
or
the
edge
channel
on
the
cli
or
I'm
sorry
by
editing
part
of
mesri's
configuration,
but
it's
a
little
bit
inconvenient
and
it
feels
like
you're,
maybe
doing
something
you
shouldn't
be
doing
as
a
user.
A
So
let
me
show
you
what
kush
is
looking
to
do
with
a
new
mastery,
ctl
command
and
maybe
we'll
get
everyone
can
weigh
in
and
get
some
feedback
on
this.
This
meshery
ctl
is
the
command
line
client
from
sri
on
my
system.
I'm
not
running
mescheri
server
at
the
moment,
so
so
it's
just
the
cli
that
I've
got
installed
right
now,
and
this
is
a
good
note
actually
drove.
Did
you
mind?
Can
you
take
this
note
if
you
would
we're
being
pretty
verbose
here
yeah?
I
wonder.
B
B
A
A
A
Kush
is
working
toward
is
to
create
a
new
meshry
ctl
system
sub
command.
Today
the
system
commands
include
the
following
list.
Mastery
ctl
system
start
stop.
These
are
things
to
control,
mesherie's
life
cycle,
the
life
cycle
of
meshri
as
a
tool
get
the
logs
from
meshri
and
its
adapters,
and
so
he's
you
know
the
design
is
to
bring
forth
a
new
sub
command
called
channel.
A
A
A
A
That
needs
to
be
done
and
hasn't
been,
and
it's
not.
It
hasn't
been
not
so
much
because
that's
difficult
to
do
like
that's,
actually
pretty
easy.
It
hasn't
been
done
because
we
need
to
agree
on
what
that
command
structure
would
be
so
something
for
us
to
talk
about
something
for
us
to
write
down.
Actually
that
that's
the
problem
is
like.
It
needs
to
be
written
down
and
well
thought
out
like
all
right.
A
Okay,
then
there's
a
couple
of
other
topics
to
to
touch
on
to
talk
about
so
there's
some
things
that
are
in
need
of
volunteers.
These
were
a
couple
of
things
off
the
top
of
my
head.
That
may
or
may
not
strike
an
area
of
interest
for
any
one
of
you
or
they
might
so
this
this
first
one
by
the
way,
the
support
for
this
command.
A
It's
if
you
look
up
these
issues
and
the
related
issues
they're
over
a
year
old,
like
we
made
them
back
in
september
2019
and
it's
kind
of
the
same
thing
for
this
first
issue.
So
if
this
strikes
an
area
of
interest
for
anyone
that
you
know,
it
would
be
great
if
you,
if
you
took
a
crack
at
it,
so
this
issue
has
to
do
with
continuous
integration.
A
It
has
to
do
with
github
actions
and
our
release
process.
So
today,
mastery
and
its
components
releases
using
or
it's
continuous
integration
is
done
through
github
actions
and
and
workflow
described
in
github
actions,
so
github
actions
work
fairly
similar
to
other
continuous
integration
systems.
There's
workflow
that
that
initiates
any
time
that
we
merge,
that
code
is
merged
in
and
different
code
is
compiled.
A
You
know,
binaries
are
built,
maybe
they're
packaged
into
a
docker
file,
and
just
you
know,
maybe
tests
are
run
things
like
that,
so
fairly
straight
fairly
standard
set
of
processes,
but
there's
there's
one
that's
missing
and
and
it's
bad
for
the
users
of
measuring.
So
one
of
them,
that's
missing
is
what's
being
highlighted
in
this
here.
So
to
say
it
briefly,
every
time
that
we
make
a
release,
a
release
comes
with
notes
about
what
changed
from
the
prior
release
to
this
one.
A
Those
notes
are
automatically
cataloged
in
a
specific
way.
So
here's
the
latest
release
of
mesherie.
This
was
released
just
a
couple
of
days
ago.
It
had
included
30
commits
from
one
two
three
four
from
five
people,
and
then
it
these
these
notes
here,
they're,
very
detailed
and
not
extraordinarily
human,
readable
and
hence
they're
called
release,
notes
and
so
they're
just
really
specific.
A
A
Some
will
really
benefit
from
detailed
release,
notes
because
they're
looking
for
a
particular
bug
to
be
fixed,
something
like
that.
Other
people
wouldn't
really
benefit
from
this
because
they're
like
I
don't
really.
I
don't
know
what
that
means.
So
that
sounds
great,
you
know,
but
how
does
that
help
me?
A
And
so
there
needs
to
be
a
write-up
about
helm,
charts
and
how
to
use
them
and
how
the
changes
were
anyway.
There's
a
lot
of
there's
any
number
of
contributors
and
a
lot
of
changes
that
go
through
and
so
part
of
the
process
is
to
have
very
specific
release.
Notes.
Well,
there's
a
github
action:
it's
called
release,
drafter
all
the
github
actions.
A
A
A
D
A
A
So
switching
topics
to
like
other
other
potential
areas
for
volunteers
is
well
there's
a
couple
of
what
yeah
I
would
more
or
less
consider
a
couple
new
projects
or
a
couple
of
new
features
to
look
at.
So
one
of
them
takes
the
form
of
a
github
app.
The
other
one
takes
the
form
of
a
slack
bot
or
a
slack
app
just
like
that.
A
L
A
F
A
Okay,
I
think
we
have
a
lazy
bot
either
that
or
a
broken
bot-
okay,
oh
okay.
So
so
there's
kind
of
a
couple
of
uses
for
a
slack
bot
like
for
interacting
with
slack
one
of
them
is
having
is
having
measured
you
that
and
more
or
less
creating
support
in
mastery
for
web
hooks
and
then
the
other
one
is
helping
automate
some
of
the
community
management
and
making
sure
that
people
have
access
to
docs
and
things
like
that.
A
A
A
So
so
that's
helpful
for
checking
the
runtime
config
of
your
mesh.
So
just
now
I'm
running
istio
on
my
machine.
I'm
running
measuring
on
my
machine
mastery
reached
out
interrogated,
istio
looked
at
some
stuff
and
said
it
told
me
lee
you're,
mostly
doing
okay
but
like
in
a
few
areas.
You're
not
right.
Well,
that's
great
and
that's
great
and
also
some
people
might
complain
that
like
well
geez,
that's
great
like
why
why?
Why
are
you
telling
me
after
the
fact
like?
Wouldn't
it
have
been
nice,
you
mess?
A
A
And
so
why
doesn't
measure
just
take
a
look
at
you
know.
I
store
that
in
github
here
here
mesri,
I
I
didn't
I
authenticate
to
mesherie
using
didn't
I
that
I
thought
I
kept
using
my
github
handle
so
like
you
have
access
to
my
github
repo
anyway.
Why
don't
you
go
ashrae?
Why
don't
you
go?
Take
a
look
you!
A
You
know.
Why?
Don't
you
do
static
analysis
on
my
configs?
Well,
I'll.
Tell
you
why
mesh3
doesn't
is
because
no
one
has
volunteered
to
write
a
github
app.
Yet
it's
not
it's.
I
think,
for
both
of
these
slackbot,
the
slackbot
and
the
github,
app
like
it's
of
the
implementation
will
probably
be
done
in
mesherie
itself.
So,
probably,
ideally
in
golang
there
is.
A
But
yeah
those
are
the
two
concepts
so
so
kind
of
to
annie
rood's
point:
those
are,
you
know
you
can
think
of
them
in
different
ways,
but
but
in
this
way
these
are
different
than
what
we
have
today
are
either
of
those
two
interesting
to
anyone
or
something
that
people
think
they
could
be
successful
with
those
that
know
golang
and
those
that
are
not
already
on
on
task
somewhere
else.
So
any
rude,
you're
right
for
you,
it
is,
you
are
disallowed
from
volunteering.
A
A
A
M
D
A
D
D
D
A
A
L
A
Community
drive:
it
is
not
it's
more
of
a
listing
of
a
lot
of
the
things
that
we'd
like
to
see
accomplished
in
the
project,
but
it's
not
a
it's,
not
a
description
of
here's.
What
would
happen
and
when,
like
like
hey
by
the
dot
five
release,
it
would
be
this.
It
would
be
that
we
can
lay
that
out
to
my
other
conversation
I
had
had
with
you
on
this.
It
is
futile.
A
If
you
don't
have
consistent
contributors,
it
really
doesn't
matter
and
so
kind
of
a
waste
of
time
to
write
it
down,
and
it's
confusing
to
people
and
most
people
that
come
don't
understand.
They
aren't
seasoned
enough
to
get
it.
We're
fortunate.
Now
that
there's
a
few
that
are
indentured
servants
that
are
like
in
an
internship
or
or
employees
to
like
be
consistent
to
have
some.
You
know
for
us
to
be
able
to
make
some
statements
and
say
by
this
time.
We
should
have
this
thing
so
that
yeah,
but
that's
that's
in
part.
Why?
A
B
A
A
But
but
it
that
doesn't
mean
that
it
there's
some
diligence
shouldn't
be
done
like
particularly
on
the
mesh
map
project.
There
are
people
dedicated
to
it,
who
are
I'm
hitting
on
it
and
I'm
having
additional
structure
there.
That'd
be.
That
would
be
helpful
like
that,
is
needed,
and
and
and
we
and
we'll
do
that.
A
This
doc,
though,
is
good
to
absorb,
and
for
anyone
who
wants
to
make
comments
or
updates,
you
know,
please
do
I'm
good
to
absorb
because
it
it
gives
a
sense
of
well
something
like
this,
like
hey,
if
you're
gonna,
if
you
have
an
existing
application,
you
want
to
bring
it
onto
the
service
mesh.
Maybe
your
application
already
has
retries
configured.
A
You
bring
it
onto
the
mesh.
You
configure
retries
on
the
mesh
you're
doing
duplicate
retries,
like
maybe
that
library
that
they
used.
We
should
facilitate
displacing
it.
That's
a
project!
That's
a
it's!
A
chunk
of
work
because
there's
a
few
popular
client
libraries,
each
language
specific
that
would
need
to
be
hooked
into
analyzed.
A
A
L
A
O
O
A
Sounds
good,
there's
a
task
section
in
this
dock
that
we
can
probably
fill
in
oops.
I
sent
that
to
the
wrong,
but
in
the
the
get
the
get
nighthawk
as
a
matter
of
fact,
there's
I'll
go
do
a
couple
things
I
want
to
introduce
you
to
auto
in
that
channel
as
well
as
jacob
and
then
we'll
put
some
tasks
in
but
yeah.
The
essence
of
it
is
to
just
be
able
to
begin
to
build
nighthawk
to
different
target
os.