►
From YouTube: Meshery Community Meeting - April, 3rd 2020
Description
Welcome @blakecova, @iam_dAggarwal and @lucjuggery!
A
A
A
All
right
morning
dozen,
you
know:
okay,
okay,
we're
about
three
minutes
after
we've
got
a
fair
number
of
folks
here,
a
couple
of
others
that
will
likely
join
as
we
get
going.
It
is
Friday
April
3rd,
just
as
a
quick
reminder
to
everyone.
The
meetings
are
recorded
and
publicly
posted
out
on
YouTube.
There's
a
community
channel
out
there,
where
we've
got
recordings
going
back
about
us
about
as
far
as
a
year
now
little
over
a
year.
At
some
point,
we
need
to
identify
measure
his
birthday
and
do
a
little
celebration.
A
A
A
Some
of
you
are
sick
of
hearing
me
say
that
the
meeting
minutes
are
a
collaboration
just
like
the
three
projects
that
we
have
going
on
here
before
we
get
going.
I'll
say
one
more
time,
I
know.
Now
all
of
you
are
in
a
position
to
that
you're
in
a
good
position
to
have
an
audio
but
drug
if
you're,
if
you're
there.
If
you
are
in
a
position
to
have
to
speak,
it
would
be
great
to
for
you
to
introduce
yourself.
A
And
I'm
not
sure
if,
if
he's
still
with
us,
is
he
yeah?
Yes,
okay,
it
might
you
might
not
be
able
to
talk
at
the
moment.
So
that's
that's!
Okay,
okay,
good,
hey
one
thing
that
I
do
a
bad
job
of
is
encouraging.
Well,
actually,
I!
Guess
I,
probably
do
this.
Every
time
is
encouraging
everyone
to
pop
in
any
topics
that
you're
gonna
want
to
discuss
today
on
the
just
as
a
quick
reminder
for
those
that
haven't
been
on
these
calls
for
a
whole
year
that
right
now
we
have
two
calls
a
week.
A
A
So
a
lot
of
folks
invited
to
this
call
the
more
the
merrier,
the
more
varied
the
topics,
almost
the
better
there's.
A
second
call
that
happens
on
Wednesdays
a
little
our
earlier
than
than
the
current
time,
and
it's
a
development
cost.
We
generally
focus
on
design,
specs
or
doing
doing
demos
working
through
issues.
It
has
weave
in
a
very
good
way,
grown
as
a
community
to
the
extent
that
there's
a
few
things
that
that
need
to
be
changed
around
to
ensure
that
we
scale
a
little
better.
A
One
of
those
is
probably
spinning
up
a
third
meeting,
a
working
group
meeting
kind
of
a
working
stream,
if
you
will
at
work
stream
and
that
one
is
probably
to
be
focused
on
the
whole
collection
of
functionality,
around
performance
management
and
the
notion
that
there's
a
new,
a
relatively
new
slack
channel
in
the
slack
account
called
performance,
we're
going
to
try
to
give
a
fairly
hard
push
there.
That
was
certainly
one
of
the
topics
that
that
myself
and
&
pratik
another
member
of
the
community.
A
A
A
The
currently
supported
ones
are
for
Tai
O
and
W
R
KQ.
There's
reasons
why
people
might
want
to
use
one
versus
the
next,
but
neither
of
them
are
does
measure
e
run
in
a
distributed
way.
I
sure
will
run
a
single
instance
of
these
load
generators
and-
and
you
know
in
do
performance
testing.
Our
hope
is-
is
that
will
work
toward
building
out
a
framework
of
doing
distributed
performance
testing
or
distributed
load
generation
hitting
endpoints
from
various
vectors
and
coalescing
those
results
and
making
mystery
a
much
more
powerful
performance
management
tool
push?
A
It
strikes
me
that
you
might
have,
if
you
have
handy
either
the
link
to
there's
a
couple
of
issues
that
were
tracking
one
for
vegetto,
one
friend
I'm
out
there
on
the
Envoy
repo.
If
you
have
those
links
handy
pop
them
in
if
you
would
but
suffice
to
say,
this
would
be
a
point
of
a
kind
of
additional
focus
and
work
within
the
community.
There'll
be
a
few
design
specs
as
well.
I
guess
this
is
a
good
time
to
ask
push.
I
know
you
were
working
on
some
thoughts
around
you
know.
A
If
and
you
think
pushes
like
some
of
us
audio
challenged
today
but
but
cush,
if
it
is
yet,
please
do
drop
in
the
link
to
the
design
spec
that
you're
working
on.
If
it's
not
ready,
you
know
no
problem,
so
I'm
gonna
work
through
some
of
these
announcements
and
then
hopefully,
I
will
stop
doing
the
talking.
The
google
Summer
of
Code,
just
in
terms
of
the
timeframe,
has
been
the
the
timeframe.
I
think
it
was
this
last.
A
I,
don't
remember
the
days
blur
together,
but
here
recently
it
was
I
think
was
Monday
or
something
the
deadline
for
project
submission
for
applications
for
student
applications
into
G
soccer
2020
I'm,
very
pleased
that
a
number
of
you
put
forth
some
impressive
looking
submissions
and
I
was
just
two
minutes
before
this
call
got
access
to
the
G,
the
CNCs
org
inside
of
G
sock
and
was
just
looking
at
a
couple
of
statistics.
That
I
think
some
of
you
might
be.
A
I
would
just
show
a
statistic
or
two
about
the
number
of
proposals
that
came
through
in
that
time
frame
for
the
CNC
F
org,
so
67
looks
like
a
couple
of
them,
maybe
didn't
quite
make
it,
but
so
65
in
total
and
I
think
we've
got
around
36
well,
members
of
the
or
33
mentors
signed
up
for
the
CNC
f
organ.
So
there
are
there's
at
least
one
of
you,
if
not
two
of
you
on
the
call
right
now
who
might
be
mentoring
this
year.
So
that's
fantastic.
A
A
Earlier
so
Krish
was
asking
hey
how
many
slots
did
earlier
this
morning,
I
sent
an
email
saying
that
that
I
was
asking
for
at
least
four
slots
for
the
project.
Ideas
that
we
have
submitted
so
I
don't
have
a
sense.
I
only
have
a
sense
based
on
having
mentored
last
year
in
terms
of
the
likelihood
of
giving
getting
that
number
or
getting
more.
A
A
Realized
this
that's
a
a
significant
topic
to
a
number
of
you
on
the
call.
So
if
I
didn't
try
to
be
as
transparent
as
possible
as
soon
as
I
get
kind
of
info
about
it,
but
feel
free
to
ask
me
additional
questions
if
I
didn't
give
to
Tim
so
good,
so
pushes
put
up
a
number
of
different
of
the
links
that
we're
kind
of
tracking
around
the
distributed
performance
testing
effort
some
interesting
things.
There
I'll
say
that
walk
the
that
very
much
related
to
this.
A
The
in
each
car
is
well
has
a
proposal
out
for
probably
our
first
rust
rust
based
well,
our
first
of
a
couple
of
things,
I
think
one
rust
based
and
then
to
Watson
filter
for
performing
a
few
interesting
functions.
One
of
those
being
the
thing
I
just
was
mentioning
around
sort
of
real-time
calculation
of
mesh
decks
mesh,
the
X
being
the.
A
B
B
A
A
Google
search
first
to
see
if
that
term
is,
if
we
can
end
up,
as
you
know,
as
a
community
and
putting
a
little
ready,
you
know
registered
TM
yeah
thanks
for
calling
that.
How
do
you
get?
We
should
be
careful.
Okay,
almost
done
with
the
announcements.
Some
of
you
are
quite
familiar
with
Nick
Jackson
of
Hoshi,
Corp
I.
Think
I've
talked
in
this
community
about
the
partnership
that
that
we
have
a
mystery
has
with
Hoshi
Corp
I'm.
A
I
think
this
just
went
up
yesterday
or
earlier
this
week,
but
there's
a
layer.
Five
is
now
a
well
a
technology,
part
service,
networking
platform
technology
partners,
I
think
they
had
a
little
bit
of
a
hard
time
trying
to
fit
understand
where
I'm
every
Finch
we're
not
proxy.
We're
not
we're
not
doing
dns
right,
you
know,
but
when
you
go
look
at
the
description
of
our
engagement,
hopefully
each
of
you
will
take
a.
A
We'll
take
it,
take
a
big
breath
and
puff
your
chest
out
a
little
bit,
because,
because
Mary
is
now
up
on
Hoshi
Corp
site
now
there
is
one
thing
that
we
do
need
to
go.
Let
the
good
folks
at
Hoshi
Corp
know
that
that
in
general,
while
measure
II
does
part
of
its
goal
is
to
help
facilitate
learning
of
service
missions
that
the
term
playground
is
something
that
we
want
to
shake
loose
from
the
project.
A
A
The
second
announcement,
hashey
Corp
related,
is
that
again
many
of
you
have
seen
either
seeing
Nick
Jackson
on
this
call
he's
been
in
the
community
for
a
while-
or
maybe
you
know
him
from
a
couple
of
the
books
that
he's
written
or
the
the
all
things
micro
services
YouTube
channel-
that
he
does,
which
is
pretty
great,
but
Nick
is
also
creating
an
open
source
project
called
shipyard
for
the
interesting
has
the
potential
to
become
a
passion
core
product?
Actually
I,
don't
I'm
foreshadowing
our
reading.
Some
tea
leaves
to
guess
that
that
is
a
possibility.
A
A
A
A
He
knows
that
there's
probably
improvements
but
but
I'm
sure
he
would
be
encouraged
that
people
gave
him
feedback,
so
pretty
cool,
so
hopefully
we'll
be
seeing
more
of
Nick.
I'd
mentioned
him
a
week
or
two
ago,
as
as
the
hash
folks
will
trying
to
pull
him
back
in
he's
a
popular
guy.
Other
announcements
I'm
push,
given
that
your
Mike
is
in
a
troubled
spot.
A
Two
of
them
now
are
anytime.
Two
of
them
now
that
the
layer,
5io
site
or
a
nursery
I/o
site
anytime,
that
you
go
to
submit
a
pull
request
rather
than
having
to
check
out
the
branch,
the
code
and
doing
your
building
yourself.
There's
a
net
lip
I
integration
for
both
of
those
sites.
Wherein,
as
you
look
at
a
given
pull
request,
there
will
be
a
link
to
where
that
PR
has
been
built
and
deployed
as
a
preview.
So
there's
like
a
per
pull
request
preview
of
each
of
the
sites.
A
That's
one
piece
of
value
that
we
can
immediately
get
out
of
metal
5
and
their
friendliness
to
open-source
projects,
and
so
that's
why
we
got
their
logo
down
here.
It
just
helps
them
the
review
process.
So
if
you
have
questions
on
that,
please
poke
push
so
push
thanks
for
that.
I
think!
There's
coach
I
owe
you
probably
an
answer
about
the
and
about
the
robots.txt
and
you
further
use
of
that
laughs.
I
salute
chat
about
that.
A
Okay,
all
right
final
thing
for
me
to
bring
up
and
then
I'm
gonna
see
if
I
can
make
it
any
of
the
any
one
of
you
guys
bring
up
a
topic.
That
topic
is
for
a
couple
of
weeks
now
I've
been
mentioning
on
this
call
hey.
We
should
really
get
out
the
next
minor
release
and
I
guess:
I'll
use
the
word
minor
lightly,
because
there's
a
couple
of
architectural
level
because
it'll
be
a
significant
release
and
the
longer
that
we
put
it
off
the
bigger
that
that
release
gets
I
would.
A
A
4.4
and
what
has
a
release
lead?
What
are
the
responsibilities
involved?
Do
you
ask?
Well
two
things
come
to
mind:
it's
one
is
just
an
organization
of
just
collecting
a
bullet
izalith
of
features
that
will
be
accounted
for
and
I'm
I
can
help
with
that.
The
second
one
is,
ideally
writing
a
short
blog
post
that
describes
those
release,
notes
and
some
of
the
features
and
why
they're
meaningful.
B
Silly
in
the
past
we're
bad
and
shame
on
me
that
I
can't
volunteer
right
now
because
I'm
trying
to
get
back
into
things,
but
in
the
past
we're
at
extreme
success
when
we
used
to
rotate
reduce
rules
based
on
release.
That's
right
so
for
one
release
it's,
it
could
be
one
because
not
only
everyone
would
get
acquainted
to
what's
going
on
and
they'll
also
play
multiple
roles
in
T
as
to
documenting
what
those
releases
release
features
are
and
also
what
has
to
go
in
what
are
the
timelines
so.
A
It's
a
lot
of
sense
to
me.
There
is
kind
of
like
the
rotating
hat
of
a
scrum
master
in
some
respects
like
a
yes
and
then
actually
I
said
so
good
thanks
for
that
yogi
I'm
shibai
thanks
for
raising
your
hand
and
then
Blake,
seeing
that
you're
on
the
call
good
to
get
to
have
you.
We
were
just
saying:
hashey,
Corp,
every
which
way
a
few
minutes
ago.
I
don't
know
if
you
were
on
at
the
time.
I,
don't.
A
No
so
yeah
our
first
two
kind
of
you
know:
announcements
up
towards
the
top.
One
of
them
is
just
the
the
work
that
you've
been
helping
us
get
toward
and
and
begin
to
see
publicly
so
I
think
that
there's
some
some
prideful
folks
on
the
call
right
now
and
they're,
seeing
they're
seeing
mesh
hurry
up
on
Hoshi
core
comp
that
that's
fantastic,
also
I
met
with
Nick
Jackson
yesterday
and
hopefully
again
on
this
coming
Tuesday
Blake
sort
of
quickly.
A
You
know
he
was
his
he's
got
a
product
that
is
working
on
there's
a
couple
of
Blake.
We
should
catch
up.
I
just
had
this
conversation
with
Nick
yesterday,
I'm
hoping
that
we
can,
that
between
him
and
and
he's
suggesting.
Maybe
he's
got
a
couple
of
good
suggestions
that
I
want
to
run
by
you
and
see
if
they
make
sense.
One
of
those
is
whether
or
not
there's
to
try
to
get
it
one
or
more
of
the
console
engineers
potentially
involved.
So.
A
So
speaking,
speaking
of
that
I'm
not
sure
if
a
su
CRO
is
on
the
call
now,
but
there
are
just
since
we're
talking
about
this
everyone
there
are,
if
you're,
not
actually
Blake.
This
might
be
your
first
time
on
the
community
contract.
If
it
is,
it
is
yeah.
Okay,
it's
a
it's
a
mandate.
It's
an
obligatory.
E
Corp
I
worked
for
a
company
in
the
cloud
computing
space
as
a
product
manager
for
OpenStack,
and
they
did
a
little
bit
of
kubernetes
and
I
spent
12
years
prior
to
that,
as
a
network
engineer,
actually
building
out
and
deploying
wireless
networks
like
WiMAX
LTE
and
a
little
bit
of
wireline
things
as
well.
So
a
lot
of
time
in
the
field
with
networking
and
yeah.
Just
you
know
now,
I'm
working,
obviously
with
console
and
service
mesh
and
that
space
so
definitely
love
it.
But
happy
to
be
here.
I've
been
chatting
with
Lee
a
bit.
E
A
F
A
There
are
a
couple
of
issues
in
here:
I
think
that
are
with
respect
to
installation
and
just
getting
the
latest
version
of
console
out
that
I'm
hopeful.
There
are
members
of
this
community
that
can
execute
on
those
with
with
relative
haste,
because
that
that
will
be
very
meaningful
to
people's
experience
with
console
and
then
there's
a
number
of
other
enhancements
to
that
adapter.
That
I
think
that
are
gonna
be
really
interesting
to
people
as
they
go
to
interface
and
interface
with
console
and
see
the
the
power
of
its
latest
functionalities.
A
A
And
what
talked
about
this
as
an
SMI
maintainer
talked
about
this
in
that
project,
about
the
need
for
to
explicitly
an
intent
conscientiously
allow
for
room
to
differentiate.
Otherwise,
each
project
I
was
representing
a
service
master.
Then
I
might
not
be
as
inclined
to
go
help
advance
the
spec.
If
all
I'm
trying
to
do
is
sort
of
commoditize,
myself
or
just
sort
of
you
know,
that's
that's
one
way
of
looking
at
it.
Anyway.
A
That's
not
measure
reason,
tension
measure,
and
so
you
that
you
can
see
that
already
when
you
go
to
run
the
SDO
adapter,
it's
a
little
more
advanced
than
any
of
the
other
adapters
at
the
moment.
For
a
couple
of
reasons,
one
of
those
reasons
is
because
there
are
a
few
service
message.
Well,
I
shouldn't
say
a
few:
if
we
go
look
at
the
service
mesh,
a
good
service
meshes
that
Adam
actually
has
adapters
for
I.
A
A
G
A
G
Okay,
so
like
I
was
just
having
talked
with
Lee
and
regarding
the
mystery
client
and
also
like
feared
spring
in
general,
about
the
design
scheme
throughout.
You
know
where
they
were
talking
about
the
websites.
Are
this
the
mesh
red
line,
so
I
was
thinking
that
we
can
probably
incorporate
some
of
the
modern
design
schemes,
for
example
having
contours
and
having
you
know
like
a
circular.
So
basically,
if
you
have
also
had
to
look
at
the
Facebook
site,
the
new
link,
everything
is
somewhat,
you
know,
contoured
and
there's
a
gradient
involved.
G
G
So
this
one
we'll
discuss
with,
if
with
the
others,
that
if
we
can
possibly
include
some
of
the
features
such
that
the
entire
functionality
of
the
application
doesn't
change,
and
it
doesn't,
it
doesn't
look
too
or
you
know
like
or
too
flashy.
So
that
was
this,
my
solution
that
we
can
probably
have
a
look
at
that
and
for
that
I
wasn't
applying
that
we
can
also
like
implement
future
designs
on
figma.
So
for
the
free
version
of
Sigma.
G
It
allows
like
two
editors
at
one
point
of
time
who
are
working
on
the
wireframes
under
designs,
but
others
can
be
or
the
viewers,
and
we
can
dynamically
change
between
the
editors
and
the
viewers,
so
it's
not
feasible.
If
someone
is
working
on
one
particular
screen
design,
then
we
can
this
ship
we
can
just
give
the
access
or
to
others
or
editing
some
other
designs.
So
that
is
like
the
entire
idea
behind
this-
that
we
can
probably
get
started
with
this
kind
of
a
design
scheme
and
implement
I
don't
live
in
that.
A
To
help
characterize
that
a
little
bit
the
second,
the
latter
bit
of
what
Shiva
was
talking
about,
was
more
with
respect
to
user
experience
and
that
being
that
that
actually
the
capabilities
of
the
project,
the
way
that
the
community
runs,
the
way
that
the
project
looks.
You
know
basically,
all
of
the
things
that
they're
continually
in
process
of
transforming.
A
Earlier
on
the
call
we
were
saying
it's
time
to
spin
up
a
working
group
around
performance
management
and
that's
a
beautiful
thing,
because
the
community
is
finally
big
enough
that
we
can
let
that
make
sense.
It's
also
a
beautiful
thing
that
there's
enough
functionality
now
and
enough
capable
people
in
the
community
that
can
come
and
take
on
to
come
and
take
on
actually
bringing
in
interface
here
that
isn't
confusing
and
is
a
bit
more
intuitive,
because
this
one
as
an
example
was
you
know,
was
us
doing
doing
what
we
could.
A
F
A
You
know
what
so
and
funny
that
you
mention
that
I
want
to
talk
about
that,
for
a
minute
am
I
still,
okay,
it's
funny
I
can't
keep
track
of
whether
or
not
I'm
sharing
my
screen
around,
but
I
guess:
I!
Guess:
I'm,
not
here's
yeah!
Let
me
ask
what
what
you
guys
think
about
something
like
this,
so
I
think
Blake
and
I
maybe
talked
about
this
I
think.
Maybe
a
number
of
us
have
talked
about
this
that
well
hey.
A
It's
my
wild
perspective,
that
service
messages
are
quite
a
powerful
component
in
your
infrastructure
and
that
of
what
we've
seen
today
from
service
meshes.
We
see
kind
of
three
feature
pillars,
worn
around
security,
a
one
around
observability
income
monitoring
and
one
around
traffic
control
or
manipulation
or
traffic
redirection
or-
and
you
know
from
there
you
could
do
some
chaos
engineering
from
there.
You
could
do
some
or
given,
where
the
layer
mat
the
cheese,
give
them
a
layer
at
which
the
service
master
sits,
I,
think
FA!
It's
like!
A
A
Some
of
these
get
really
interesting
and
and
but
but
they're
gonna
they're
gonna
cost
something
to
do
if
you're
gonna.
Some
of
these
look
interesting
because
they're
going
to
again
be
real-time
network
based
new
network
services.
If
you
will
and
if
you
bring
them
forth
and
they're
interesting
and
people
use
them,
they
need
to
understand
that
they
need
to
be
done
in
a
performant
way
and
people
need
to
understand
if
the
how
much
overhead
they
would
be
paying
for
them.
I
realized
I'm
speaking
in
the
abstract.
A
A
Dark
mode,
light
mode,
hey
dark
mode
like
it
said,
is
pretty
hip
if
you
as,
if
you
have
a
an
application
and
it's
a
collection
of
services
that
application
is
running
on
a
service
mesh.
Well,
maybe
you
know
maybe
you'd
go
to
your
development
team
and
you'd
say
hey,
you
guys,
take
a
sprint
and
let's
do
let's
implement
dark
mode,
and
maybe
that's
worth
it
to
you
or
maybe.
If
you've
got
a
mesh
present
you'd
say
you
know
what
you
know
forget
about
that:
let's
not
go.
A
If
it
was
running
on
a
mesh
visitors
of
the
site,
could
you
know
change
to
dark
mode
like
they
can
any
other
app?
But
in
this
case
that
change
is
actually
can
be
implemented
without
code
change
of
the
website.
It
could
be
implemented
as
code
change
in
the
service
mesh.
I
think
that
that
would
be
a
bit
thought
leading
and
I
think
that
that
would
be
interesting
to
explore
the
performance
overhead
of
doing
such
a
thing
interesting
to
explore
how
to
empower
the
product
owner.
F
So
it's
definitely
possible,
but
if
I
understand
what
you're
talking
about
is
basically
we're
saying
we
have
two
different
instances
of
the
front-end.
One
of
them
is
built
with
dark
mode
design.
The
other
one
is
a
usual
design
and
we
do
traffic
redirection
based
on
whatever
cookie
the
user
has
stored.
A
C
Guess
we
can
do
something
like
that
there
is
an
extension
called
dark
mode
reader
which
actually
inverts
the
color
of
the
page,
so
that
can
be
like
triggered
by
the
cookie
of
like
whenever
the
user
is,
whenever
some,
what
some
developer
is
deploying
there.
So
we
can
inject
some
JavaScript
code
along
with
it
or
something
of
that
sort
and
give
an
option
to
the
user
to
just
switch
to
the
dark
mode
or
light
mode.
Is
that
what
you
are
saying
or
did
I
also
interpret
it
on.
A
A
Implement
dark
mode
for
you,
I'm
gonna,
I'm
gonna
leave
the
thought
there
as
a
tantalizing,
hopefully
a
tantalizing
thing
and
also
I
recognize
kind
of
a
silly,
a
simple
kind
of
a
silly
example:
I'm
intentionally
leaving
it
as
such,
but
just
so
anyway,
+1
to
dark
mode.
I
like
the
idea
and
I
think
yeah
I
think
that
there
are
opportunities
around
how
that's
brought
forth.
F
Like
I,
like
the
idea
of
you,
know
showing
off
the
power
of
the
mesh
on
on
the
community
side
itself,
so
that
would
be
great,
like
maybe
not
not
the
dark
mode
per
se,
but
what
we
could
probably
have
like
maybe
have
a
better
version
of
the
site
next
to
the
main
version,
and
then
for
not
saying,
if
you're
the
adventurous
type,
you
can
try
this
the
better
version.
This
is
the
mesh
redirecting
you
to
there
to
the
better
version
in
the
background
sounds
like
that.
A
A
You
jump
to
chapter
5
over
there
and
and
you
kind
of
jump
around
through
the
book,
depending
upon
how
you
as
a
reader,
wanted
to
choose
your
anyway
bad
analogy,
but
that's
what
kid
you
might
and
now
I'm
kind
of
wasting
time
toward
the
end
of
all
our
call
I
for
my
part
and
that
yeah
that
that
resonates
very
well
with
me.
That
I
was
just
talking
about
distancing
the
term
playground
from
mystery
and
in
some
respects
we're
talking
about
bringing
forth
a
little
bit
of
a
playground.
A
I
think
that
there's
a
lot
about
you
than
that
and
in
just
sort
of
a
publicly
hosting
an
instance
of
nursery,
we
thought
we
talked
about
that
a
lot
before,
as
a
matter
of
fact,
there's
some
of
you.
So
this
is
actually
a
really
good
minder
that
on
this
next
coming,
Thursday
April
9th
there
is
a
introduction
to
yeah
I.
Think
the
other
two
through
O'reilly.
It's
a
live
training
that
some
of
you
will
be
helping
with.
A
We
I
would
expect
that
we'll
have
a
small
influx
of
I,
keep
forgetting
that
I'm,
not
sharing
my
screen.
Let
me
share
real
quick,
a
small
influx
of
a
couple
of
hundred
or
more
registrants
for
this
training
on
Thursday.
This
would
be
a
three-hour
training
part
of
the
training.
We
end
up,
asking
all
the
students
to
come,
join
the
slack
channel,
and
then
we
end
up
asking
them
to.
A
Where
is
it
misty
I
thought
I
thought
my
Cherie
was
this
and
we
end
up
yeah.
We
asked
them
to
use
measuring.
We
basically
walked
them
through
service
mission
concepts
and
how
this
deal
works,
using
a
steel
sample
app
through
the
auspices
of
memory,
and
so
just
that,
and
so
this
is
actually
one
of
those
examples.
A
My
point
to
say
that
is
linked
release.
If
you
need,
you
have
to
be
around
I'm
in
the
slack
channel
on
this
next
Thursday
around
this
time.
When
you
see
people
asking
a
bunch
of
questions
and
things
and
that's
a
great
opportunity
for
you
to
step
in
and
either
learn
some
stuff
as
they
are
or
maybe
answer
some
questions
about
service
meshes,
so
that
should
be
happening
inside
the
workshop
to.