►
From YouTube: Layer5 Community Meeting (July 29th, 2022)
Description
Layer5 Community Meeting - July 29th, 2022
Agenda:
[Debopriya] Community
See the Member Profile badges - collect the whole set!
ICYMI - Resources available: Learning Paths
Layer5 Writing Program
Volunteers needed: Feature blog posts for the Meshery v0.6.0 release. Some posts have already been written, but others need a write-up.
[Craig/Ruth] A presentation of GitHub Codespaces.
Volunteer Needed: [CI] Configure Meshery for Codespaces #5904
[Aditya/Lee] Now available: Meshery Docker Extension
Join the community at https://layer5.io/community
Find Layer5 on:
GitHub: https://github.com/layer5io
Twitter: https://twitter.com/layer5
LinkedIn: https://www.linkedin.com/company/layer5
Docker Hub: https://hub.docker.com/u/layer5/
A
So
hi
everyone
welcome
to
the
layer,
5
community
meeting,
it's
great
to
see
all
of
you
here.
We
always
begin
all
of
our
calls
with
the
introduction
of
our
newest
members
and
today,
let's
begin
with
craig
who's
here
with
a
presentation
we
will
be
hearing
in
a
while.
So
click,
why
don't
you
introduce
yourself
to
the
community
over
here.
B
Oh,
thank
you
really
glad
to
be
here.
I
thanks
for
the
welcome
I'm
a
product
manager
at
github.
My
interest
is
in
helping
more
and
more
people
contribute
to
open
source
communities.
I've
been
involved
in
various
open
source
communities
for
the
last
12
years
now,
starting
with
with
hadoop
and
that
ecosystem
moving
on
into
openstack
and
the
last
six
years,
or
so
in
the
kubernetes
community,
and
I
now
work
at
github
on
tools
for
developers.
C
A
D
A
C
C
A
Yep,
so
I
think
we
can
begin
with
the
agenda
items
right
now
cool.
So
the
first
topic
is
by
me,
so
I
wanted
to
talk
about
our
community
profile
badges.
So
basically,
if
you
there's
a
link
in
the
meeting
minutes
I'll
share
the
link
in
chat
for
everyone
to
access
it
on
the
left
website,
we
have
the
members
page,
which
is
the
list
of
most
of
our
community
members.
This
is
to
get
your
profile
on
the
member
page.
A
It
is
like
a
sequence
of
the
community
contribution
ladder,
and
one
very
interesting
thing
about
this
page
is
that
we
recognize
your
major
major
area
of
contribution
through
badges.
So
we
have
a
filter
here
to
basically
sort
people
on
the
basis
of
badges,
and
these
are.
This
is
a
sort
of
recognition
given
to
people
who
have
been
associated
with
a
particular
aspect
of
our
project
for
a
long
time.
A
So
here's
the
mashery
badge-
we
have
a
couple
of
badges
over
here,
so
this
is
a
very
great
way
to
showcase
your
area
of
interest
to
showcase
what
projects
you've
worked
on.
You
can
gather
as
many
badges
as
you
want
you.
You
can
actually
gather
all
of
them
if
you've
worked
on
all
of
our
projects,
so
this
is
a
great
way
to.
This
is
one
step
up
the
contribution
ladder
that
I
was
talking
about
so
start
contributing.
A
If
you
want
you
can
as
and
when
you
spend
more
time
in
the
projects
here,
you
can
get
these
badges.
We
have
community
managers,
we
have
mesh
mates
continuously,
monitoring
all
the
activity
that
happens
here
and
yeah,
so
this
is
mostly
about
badges.
Does
anyone
else
over
here
who
has
received
any
of
these
badges
want
to
talk
about
this
journey.
A
E
D
A
C
Yeah
no
yeah,
I
guess
the
point
yeah
collect
the
whole
set,
there's
a
there's,
a
few
mesh
mates
that
are
on
the
call,
and
so
there's
some
mesh
made
emerituses
or
maritime
that
are
on
the
call
as
well
anyway.
We
certainly,
I
think,
deborah
priya's
point
here-
is
that,
like
it's
not
alway,
people
aren't
people
are
super
excited
generally,
which
is
nice
to
get
a
member
profile
on
the
page.
C
It's
just
a
recognition
of
the
fact
that
you've
kind
of
found
a
home
and
you've
been
around
for
a
while
you've
been
being
impactful,
there's
a
collection
of
of
folks
here
that
can't
help
themselves
but
help
others,
and
we
acknowledge
them
as
meshmates,
and
they
enter
in
into
a
formal
program.
The
mesh
mate
program
to
like
pay
it
forward
to
help
people
kind
of
get
their
get
their
first,
we'll
get
traction
on
a
project,
and
you
know
whether
that's
through
code
or
or
like
a
litany
of
any
other
non-code
things.
C
I
think
it
takes
longer
to
describe
the
non-code
things
than
it
does
the
code
things
that
happen
around
here.
This
is
one
of
them.
These
badges
are
created
by
the
community
so
anyway,
there's
just
tons
of
stories.
Tons
of
blog
posts
that
are
out
there
for
folks
to
read
we'll
have
to
see
if
anyone's
got
the
whole
set
yet
or
not.
I
don't
know
so
other
than
that.
What's
what's
next.
A
So
talking
about
non-code
contributions,
there's
also
a
new
writing
program
that
we
have
the
lay
five
writing
program,
and
this
welcomes
all
writers.
You
don't
have
to
be
necessarily
a
member
of
the
leaf
community.
You
can
be
a
guest
writer,
so
you
can
write
anything
from
blog
posts
to
resource
articles.
We
have
a
collection
for
blog
posts.
Similarly,
we
have
a
collection
for
resources,
cloud
native
resources,
which
includes
all
these
various
types,
and
there
could
be
anything
else.
Anything
more
that
you
want
to
add
to
this
articles.
A
Workshops
recorded
webinars,
anything
the
list
is
endless,
so
if
you
have
any
sort
of
knowledge
that
you
want
to
share
or
if
you've
been
contributing
for
a
long
while
and
you've
worked
on
a
new
feature,
you
want
to
show
off
that
new
feature
of
yours
feel
free
to
write
a
blog
post.
This
is
open
to
everybody.
All
that
you
have
to
do
is
fill
out.
This
content
form
that
we
have
over
here
and
a
member
of
the
team
will
reach
out
to
you.
A
Let
you
know
of
the
next
steps,
so
this
is
a
very.
This
is
open
for
everyone
and
if
you
think
that
you
want
to
get
accustomed
to
our
projects
first,
there
are
a
couple
of
resources
available
as
well.
One
of
them
is
mentioned
here,
the
layer,
5
learning
paths.
It
has
a
couple
of
courses.
There
are
a
ton
of
coming
soon
courses.
We
have
this
active
course,
which
is
introduction
to
service
meshes
and
advanced
concepts
and
service
meshes.
So
it
takes
you
through
a
step-by-step
process.
A
Chapter-Wise
course
for
you
to
master
service
measures.
There
are
also
okay,
so
there's
an
option
to
switch
between
the
service
meshes
as
well,
so
you
can
do
linkedin.
You
can
do
istio
so
make
use
of
this
learn
about
service
meshes.
This
is
a
huge
effort.
This
is
a
huge
project
that
our
community
members
have
put
together.
So
there's
a
ton
of
other
resources
as
well.
It's
all
available
on
the
website.
We
have
books,
we
have
workshops
so
yeah.
I
just
wanted
to
point
everyone
out.
A
A
B
B
D
B
B
D
B
I
already
did
a
quick
introduction
at
the
beginning,
but
I'll
just
kind
of
tell
you
what
my
role
is:
I'm
a
product
manager
at
github,
I
focus
on
code
spaces,
which
is
a
product
we're
going
to
talk
about
now
and
how
code
spaces
works
for
open
source
communities
and
that's
a
brand
new
thing,
so
so
I'll
get
into
that
it.
It
isn't
really
here
yet
in
terms
of
being
available
to
everyone.
That's
happening
later
this
year
and
I'll
get
into
that
as
well.
B
I'm
now
in
the
layer,
5
slack,
so
I'm
intending
to
be
an
active
participant
in
the
community,
so
you
can
definitely
reach
out
to
me
there
and
I'm
also
peter's
craig
on
twitter
and
my
dms
are
open.
If
you
want
to
reach
out
there,
so
the
my
thesis
is
this:
that
the
world
has
amazing
complex,
huge
and
terrible
challenges
in
front
of
us
as
we
grow
and
get
more
complicated
and
emit
more
carbon
dioxide,
and
basically
just
do
more
stuff
without
thinking
about
it.
B
If
we
don't
do
the
right
things,
we
really
have
to
harness
the
ingenuity,
the
power,
the
backgrounds,
the
different
points
of
view
of
a
much
much
larger
swath
of
our
species
and
and
that's
a
a
very
kind
of
optimistic
view.
I'll
have
to
say
I'm
I'm
making
a
it's
kind
of
a
naive
point
of
view
also,
but
I
also
don't
do
it
from
a
place
of
kind
of
ignorance.
I
I
really
do
believe
very
strongly
that
yeah.
B
I
have
my
dark
days
too,
but
I
believe
that
we
can
solve
a
lot
of
the
problems
if
we
harness
everybody.
The
problem
is
that
today,
these
open
source
ways
of
working
aren't
accessible
to
everyone.
In
fact,
a
very
small
swath
of
us
are
working
in
these
kinds
of
communities,
and
there
are
a
lot
of
reasons
for
that.
B
You
know
I'm
bringing
a
product
from
a
company,
and
that's
feels
funny
right,
like
it's
like
we're
a
for-profit
company,
we're
a
part
of
microsoft.
I
want
to
acknowledge
that
right
up
front,
but
our
strategy,
I
believe
very
strongly,
is
you
know
it's
compatible
with
this
vision
for
getting
things
together
and
what
we
want
to
do
is
we
want
to
make
everyone
able
to
contribute
to
open
source
projects
using
tools
that
we
provide
through
github.
B
So,
let's,
let's
dig
in
a
little
bit
to
the
specific
blockers
that
I
want
to
talk
about
today.
So
one
of
the
things
when
people
come
to
open
source
projects
that
they
one
of
the
challenges
when
we're
talking
about
software
projects
that
people
have
is
a
lot
of
people.
I
talk
to
their
computers,
can't
even
install
the
dependencies
that
are
required,
and
you
know
that
that's
a
big
hurdle,
if
you
can't
buy
a
thousand
dollar
laptop
or
god
forbid,
if
you
need
to
compile
kubernetes
a
two
thousand
dollar
laptop.
B
How
are
you
gonna
work
on
it
right
like
that?
That's
just
a
fundamental
thing!
Then
the
next
thing
is
you
go
look
at
the
readme
and
you
know
many
of
us
in
the
open
source.
Try
really
really
really
hard
to
make
readme's
accessible,
but
the
reality
is
that
the
hurdle
from
where
you
know
where
people
come
from
to
actually
reading
and
understanding
a
a
readme
is
very
high.
I'm
just
seeing
the
chat
is
there
some
challenge?
Are
people
able
to
see
my
presentation.
C
C
B
B
Because
we're
you
know,
we
just
make
lots
of
assumptions
about
what
people
know
and
come
into
and
that's
natural
and
then,
as
you
get
even
deeper
into
projects
get
like
git
is
an
incredibly
complex,
distributed
content
management
system
that
assumes
a
bunch
of
understanding
and
knowledge.
You
know:
have
you
ever
tried
to
do.
B
Kubernetes
is
a
you
know,
a
classic
example
of
an
incredibly
complex
project,
and
lots
of
people
have
worked
very,
very
hard
to
make
kubernetes
as
inclusive
welcoming
and
you
know,
accessible
as
possible
right,
and
so
this
is
kind
of
how
you
get
to
contribute
to
kubernetes.
The
first
thing
you
see
is
you
know
this:
this
nice
markdown
document
that
talks
about
communication,
the
github
workflow,
opening
a
pull
request
right
away,
a
github
workflow.
I
mean
it's
interesting.
B
It's
it's
it's
nice
for
us
that
our
product
is
mentioned
right
away,
like
that's
fine,
but
a
pull
request.
A
code
review
best
practice.
These
are
these
are
kind
of
deep
concepts
for
people
who
are
just
really
getting
started.
Like
you
even
go
into
communication,
and
you
know
right
away,
it
is
your
best
contact
for
your
sig
of
issues
related
to
the
six
topic.
I
mean
what
right
like
this
is
not
really
a
thing
that
is,
is
easy
to
consume.
So
let's
talk
about
an
alternative.
B
B
B
So
a
codespace
is
a
development
environment
that
will
have
all
of
the
dependencies
that
are
required
to
do
development
work
in
a
given
project,
all
of
the
tools
that
are
required
and
all
the
configurations
and
services
and
everything
else
that
are
required
to
be
productive
right
away
in
the
environment,
and
that
means
that
the
readme,
so
all
the
steps
you
need
to
do
to
your
local
development
box,
the
you
know,
step
by
step
understanding.
What
app
is
understanding.
What
brew
is
understanding
how
to
configure
testing
tools?
B
B
So
the
on-demand
means
that
I
don't
have
to
pay
a
bunch
of
money
up
front
in
order
to
get
it.
It's
not
a
big
hurdle.
I
can
do
it
whenever
I
want
it
behaves
the
way
I
want
for
my
project
and
for
me
and
then
I
can
use
it
anywhere.
I
can
be.
You
know
we
have
members
who
have
used
it
because
they've
been
fleeing
conflict.
B
B
So
what
does
that
look
like
from
sort
of
what
are
the
pieces
and
parts
of
a
code
space?
So
it's
a
full
development
environment,
not
just
the
editor,
but
it
automatically
pulls
down
all
the
source
code.
So
new
people
coming
to
a
project
don't
have
to
understand
what
a
fork
is.
What
git
clone
means
like
right
away.
All
the
code
is
laid
out
there.
It's
got
all
the
runtimes
and
packages
you
need
to
actually
run
it.
It's
got.
You
have
the
debugger
and
all
the
tools
tightly
integrated
and
set
up
ahead
of
time.
B
It's
got
the
terminal,
any
extensions,
all
the
configuration
is
sort
of
all
pre-packaged
and
ready
for
you
turns
out
when
we
talk
to
a
lot
of
maintainers.
A
huge
amount
of
the
maintainers
job
is
helping
community
members
with
these
just
initial
setup
challenges,
and
so
this
reduces
the
amount
of
frustration
that
new
contributors
have
coming
to
a
project
and
reduces
the
frustration
and
stress
level
for
maintainers
who
are.
B
Problem
in
a
lot
of
our
open
source
communities
and
maintainers
are
constantly
trying
to
balance
like
well.
How,
when
do
I
invest
time
in
the
code?
When
do
I
invest
time
in
the
community?
When
do
I
invest
time
in
the
new
contributor
experience,
and
so
this
is
intended
to
be
like
a
quantum
leap
forward
for
the
maintainers
to
have
a
central
place
to
manage
these
configurations
and
customizations,
so
that
new
contributor
experiences
are
just
that
much
smoother
and
leap
people
further
into
the
participation
in
communities
right
away.
B
You'll
see
here,
I've
got
my
original
readme.
I've
got
the
changes
I
made
to
the
readme
here.
I've
just
added
a
new
option
and
I
say
well
if
you
just
want
to
get
going
starting
with
coding-
and
I
put
in
here
a
block
that
says
just
open
and
get
code
spaces,
and
it's
got
a
badge.
So
it'll
be
like
a
button
that
you
can
link.
B
B
This
is
just
a
whole
lot
easier
for
a
lot
of
users
when
they're
getting
going
than
learning
the
command
line.
You
can
do
all
of
this
directly
from
the
command
line
as
well,
and
you
can
see
I
did
this
in
an
environment
where
I
actually
was
just
validating
that
you
could.
Actually.
This
is
just
a
basic
four
core
machine
in
code
spaces.
I
could,
I
actually
use
the
command
line
and
did
you
know
make
kubernetes,
so
I
validated
I
could
build
everything
easily
in
kubernetes
there
and
what
does
that
look
like?
B
You
just
click
on
this
button
and
you've
got
a
full
development
environment
with
all
the
tools
all
the
dependencies
installed
right
away.
Instead
of
spending,
you
know
a
workshop
and
hours
and
hours
trying
to
understand
it.
You've
got
that
going
right
away,
so
I
I've
hit
that
up.
So
I
think
I
hit
a
lot
of
these
points
already,
but
the
idea
is
that
for
a
maintainer
you
can
create
a
smooth
contributor
experience.
You
get
fewer
issues
about
setup.
B
B
Later
this
year,
we're
making
code
spaces
available
to
every
developer
on
the
planet
and
you'll
have
a
certain
amount
of
usage
of
that
for
free,
so
we're
actually
the
amount
it's
going
to
be
quite
generous.
It's
going
to
be
more
than
100
compute
hours
per
month
for
free
and
then
there'll
be
a
nominal
fee
for
compute.
Once
you
get
beyond
that,
and
a
certain
amount
of
storage
available
for
free
to
every
developer
on
the
planet
and
that's
going
to
our
vision
is
that
that
will
make
anybody.
B
B
What
I
want
to
do
is
I'm
taking
nominations
for
open
source
projects,
and
what
I
can
do
is
I
can
sort
of
jump
into
the
future
and
make
code
spaces
free
for
now
to
everyone,
who's,
a
part
of
github
organizations,
and
we
can
then
work
together
to
add
the
development
containers.
Those
are
the
actual
configurations
that
specify
how
open
source
project
can
work
with
with
code
spaces
and
be
perfect,
and
then,
before
the
end
of
this
year,
we're
gonna
make
it
available
to
everyone
in
that
way.
B
You'll
already
be
set
right
and,
and
we'll
also
have
the
benefit
of
collaborating
with
y'all.
To
make
that
experience
great,
we
can
make
our
product
even
better
from
the
feedback
I
get
from
the
community
right
as
being
a
part
of
that
community.
So
that's
what
I'm
asking
today,
that's
my
bit.
What
I'd
love
to
hear
is
what
people
think
what
we
could
do
to
make
it
better,
and
I
actually
did
lee
happily
already
created
an
issue
where
we
can
track
this
work
in
the
measuring
project.
C
I
won't
re-articulate
the
value
proposition
that
craig
just
mentioned,
like
it's,
it's
quite
attractive
to
a
project
like
like
measuring
in
part
because
well
just
for
example,
people
will
any
number
of
folks
will
come
and
try
to
contribute
to
the
ui
and
there's
the
ui
is
currently
undergoing
a
refactoring.
Just
for
measure
is
one
one
of
a
few
different
projects
that
this
community
has,
but
it's
the
biggest
one
and
turns
out
in
the
same
repository,
if
you're
going
to
build
kind
of
all
of
meshri
and
have
the
uib
dynamic.
C
Well,
you've
got
to
compile
some
go
as
well
and
then
there's
some
particular
rigmarole
about
what
version
of
go
and
you
have
make
installed
and
etc,
and
it
just
sort
of
unravels
into
a
ball
of
frustration.
Or
maybe
it
rolls
up
into
a
ball
of
frustration,
and
so,
for
my
part,
I'm
hopeful
that
there's
an
easy
button
to
to
one
of
craig's
points,
like
unlocking
exactly
what
we've
spent
tons
of
time.
C
C
Maybe
some
aspects
of
this
that
are
tbd
but
looking
into
the
future
as
code
spaces
becomes
generally
available
and
and
and
the
thought
is
that
there
would
be
you
know,
100
hours
per
per
person
using
those
is
that
the
general
like
a
github
account
itself
is
well
typically,
unless
you're
in
a
soul-crushing
corporate
enterprise
like
the
github
account,
is
your
account
your
thing
and
you
carry
it
with
you
and
and
again,
unless
you're
in
a
really
backwards
organization.
That
doesn't
believe
in
that
philosophy
you,
the
code
spaces
hours
are.
C
B
We
have
three
organizations
and
we
have
paid
organizations,
so
we
make
money
off
of
enterprise
organizations
and
we
try
to
enable
free
organizations
and
work
with
open
source
projects
to
have
either
the
free
organization
or
whatever
level
of
organization
makes
sense
for
for
their
their
organization.
The
organization
can
choose
to
pay
for
code
spaces
in
those
organizations
or
not.
B
That's
a
configuration,
that's
possible
to
that,
and
so,
when
I
create
a
code
space
in
an
organization
by
default,
my
free
usage
will
be
the
first
thing
consumed
unless
that
organization
has
chosen
to
pay
for
court
code
spaces
made
from
that
organization,
so
enterprises
typically
pay
for
a
plan
that
will
allow
them
to
pay
for
code
spaces
for
their
employees
work.
Whether
that's
you
know,
like
you
said
you
know,
you
brought
your
own
github
account
and
identity,
and
all
that
with
you,
which
is,
I
agree,
not
the
soul-crushing
approach.
B
I
happily
worked
for
a
company
that
definitely
doesn't
do
that
approach.
I
brought
my
account
with
me
or
a
new
account,
that's
specific
to
and
managed
by
that
enterprise,
but,
for
you
know,
users
outside
of
that
enterprise
context.
They
typically
have
their
own
individual
account
and
they
can
then
either
work
in
other
organizations
in
output,
space
or
open
source
organizations,
or
you
know
in
their
own
repo,
in
which
case
they
will
consume
those
free
hours
on
those
repos.
C
B
F
I
want
to
be
brief,
bright
and
gone,
because
I
wanted
to
list
listen
first,
but
I
didn't
see
any
other
hands
up.
If
I
understand
this
right,
you
know
when,
when
you
say,
microsoft
and
or
github
is
going
to
enable
this
for
a
project
or
for
a
set
of
humans,
those
are
little
buckets
of
compute.
Basically,
that
start
with
a
container
as
their
starting
state.
So
I
guess
the
couple
of
questions
I
have
are
kind
of,
I
think,
there's
three
main
ones
and
adjusting.
F
However,
you
like
I
suppose,
but
how
ephemeral
are
these
environments
and
are
they
programmable
meaning?
Could
you
have
a
failing?
You
know
every
time
a
ci
job
runs
and
fails
say:
could
the
failing
state
be
added
as
an
additional
layer
on
top
of
whatever
base
layer?
The
dev
environment
was
so
time
to
diagnose
a
failed
ci
job,
for
whatever
reason
is
the
failed
state
is
loaded
already
like
we
did
this
way
back
when
with
hyper-v.
Second,
how
many
cores
and
or
how
much
memory
and
or
cpu
architectures
are
available.
F
You
know
with
edge
computing,
particularly
in
the
service
mesh
space.
We're
gonna
see
the
prevalence
of
arm
and
other
non
x86,
architectures
and
and
three
you
know:
can
you
dial
up
or
down
you
know?
So,
should
we
consider
this
really
just
the
development
environment
or
the
jump
box
from
which
you
would
go,
do
something?
And
then,
if
you
wanted
to
work
with
github
deployments
or
your
own
infrastructure
to
actually
have
clusters
and
meshes
deployed,
is
there
any
facilities
or
infrastructure
or
apis
to
connect
things
in
a
secure
way
using
github
secrets
so.
B
Those
are
kind
of
my
three
broad
questions.
Those
are
great
questions,
so
let
me
see
if
I
can
recall
them
and
go
through
them
one
at
a
time,
so
the
first
one
was
about
when
you
have
say,
build
or
actions
failures.
Can
you
layer
code
space
on
top
of
that
to
do
diagnosis
of
that
test?
Failure?
That
is
absolutely
our
vision
of
where
we're
going.
B
There
are
some
technical
reasons
that
actions
and
code
spaces
come
were
built
in
parallel
by
different
teams
with
different
assumptions.
I
am
actively
that's
actually
one
of
the
core
things
I'm
working
on
as
a
product
manager
at
github
is
to
solve
that
challenge.
I
want
the
you
know:
it
works
in
my
dev
environment
and
it
works
in
my
build
environment.
I
never
want
to
see
it
works
in
my
dev
environment,
but
not
my
build
environment
and
vice
versa.
I
want
the
story
that
you
just
told
to
be
absolutely
true.
F
For
this
community,
too,
like
service
meshes
and
all
of
these
things
can
be
quite,
it
can
take
quite
some
time
and
they're
complex
already,
and
so
you
have
a
failing
case
on
top
of
quite
a
few
different
layers.
So
so
I
think
the
time
to
you
know
from
a
productivity
perspective
for
particularly
for
new
contributors,
but
for
people
that
do
a
lot
of
code
reviews
as
well
or
want
to
replicate,
fulfilled
or
a
passing
test
result
because
it
works
in
the
positive
case
as
well.
F
F
B
B
The
second
question
was
about
sort
of
scale
of
the
resources,
so
we
have
a
different
machine
types
that
are
available:
everything
from
two
core
to
32,
core
machines
and
one
gpu
type
that
we're
currently
working
on
rolling
out
of
beta
for
for
different
kinds
of
use
cases,
and
so
the
100
plus
I
don't.
I
can't
specify
the
exact
number
of
hours
of
included
free
usage
are
actually
core
hours.
B
So
if
you
use
a
2
core
machine,
the
number
of
hours
that
we
get
the
included
hours
would
obviously
would
be
half
of
that,
because
there's
the
multiplier
factor
for
each
of
the
course
that
you're
consuming-
and
so
you
can
use
you
know
a
16
or
32
core
machine
for
the
period
of
time.
You
need
your.
Your
second
part
of
that
question
was
about
the
sort
of
persistence
of
those,
so
configurable.
B
B
I
suspend
that
code
space
and
I'm
no
longer
consuming
core
hours
until
I
resume
that
work
right
or
I'm
creating
a
new
contribution.
I
want
to
play
around
with
the
code.
I
don't
know,
I
don't
even
know
what
I
want
to
do,
I'm
going
to
create
a
code
space
I'll
play
around
with
it
I'll
stash
my
changes
in
my
own
fork
code
space
goes
away.
F
F
B
The
reporting
is
an
area
where
we
do
have
some
maturing
to
continue
to
do.
We
have
a
billing
user
interface,
where
you
know
you
can
get
reporting
about
how
many
which
users
of
which
repos
concern
could
consume,
how
many
core
hours
and
that
kind
of
thing,
but
it
isn't
as
capable
as
we'd
like.
Yet
that's
an
active
area
of
investment.
F
I
I
meant,
like
I'm
a
dev,
I'm
in
my
environment,
I'm
maybe
running
some
stuff
is,
is
me
observing
the
totality
of
that
code?
Space
from
the
various
things
I
might
observe
is
that
on
me
to
do
myself
from
within
the
code
space,
or
is
there
sort
of
monitoring
like
how
busy
is
it?
Did
some
script
just
do
a
while
one
loop-
and
you
know
like
how
do
I
know
what's
going
on
as
if
I
would,
by
running
a
vm
locally
or
a
container
locally,
I
can
from
the
side
or
outside
of
it
diagnose.
B
B
B
So
lee
was
asking:
is
it
multi-container
capable
and
the
answer
there
is?
Yes,
it
supports
supports
both
docker
in
docker
and
dockerfront
docker
and
docker
compose
scenarios.
So
if
you
have
you
know
multiple
services,
you
need
to
run
all
that's
supported
from
multiple
containers
and
then
are
the
100
hours
tethered
to
specific
architectures.
B
And
then
do
all
the
extensions
of
vs
code
work.
The
answer
to
that
is
that
we,
our
intent,
is
that
they
all
work.
Have
we
extensively
tested
everyone,
it's
an
open
marketplace,
and
so
it's
just
not
practical
to
test
every
single
one,
but
there
is
nothing
special.
In
fact,
one
of
the
things
I
didn't
mention
that
is
that
there
are
basically
two
ways
in
which
to
work
with
a
code
space.
B
It's
really
just
a
remote
development
container,
as
I'm
sure
matt
has
devised
defined
and
that
that
means
that
I
can
either
work
in
the
web
browser
based
ide
or
I
can
connect
remotely
to
that.
Dev
container,
that's
running
in
the
cloud,
either
from
my
vs
code,
running
locally
from
through
ssh
from
my
local
vim
or
emacs
or
whatever
my
editor
of
choice
is
that
supports
remote
connections
through
ssh
into
that
out
into
that
environment.
B
B
You
can
go
find
the
specs
and
the
reference
implementation
for
the
cli
code
spaces
actually
uses
that
reference
implementation
of
the
ci
of
the
cli
under
the
hood,
so
the
intent
is
that
way.
Anybody
who
wants
to
create
a
new
ide
that
works
with
codespaces
or
any
remote
development
container.
We
can
have
a
common
set
of
interfaces
to
work
with.
B
C
Well,
you
got
everybody
hot
and
bothered
craig.
We
got
some
excited
folks,
so,
like
craig
had
said
before,
no
doubt
a
few
of
you
have
some
questions.
Craig
is
in
the
layer,
five
slack
and
so
he's
also
in
a
bunch
of
other
slacks
and
some
discus
discords
and
some
probably
some
irc's
and
everything,
and
so
you'll
be
patient
with
him.
If
you,
if
you
pop
him,
if
you
pop
out
a
question,
if
you
do,
you
know,
please
do
so
in
a
public
forum
so
that
others
can
can
benefit
right
man.
C
This
is
good,
so
to
wrap
to
wrap
this
up.
There's,
like
craig
had
said,
there's
an
open
issue
open
for
a
volunteer
or
two
or
three,
maybe
a
good
learning
opportunity
for
a
couple
of
folks
as
we
go,
though,
to
we'll
want
to
you
know,
capture,
notes,
collectively
about
the
experience
about
you
know,
good
things,
bad
things
and
facilitate
that
you
know
get
that
feedback
to
craig,
and
so
yeah
measuring,
in
particular,
could
be
yeah.
C
Stan
stands
to
be
potentially
novel
in
some
areas
for
code
spaces,
to
the
extent
that
the
to
the
extent
that
we
go
into
kubernetes
and
go
into
service
meshes
and
go
into
webassembly
filters
and
like
or
touch
on
a
few
things
that
maybe
some
of
the
other
projects
aren't
aren't
touching
on
just
yet,
but
ultimately
will
and
so
so.
For
my
part,
I
can't
wait
to
break
code
spaces,
I'm
just
fair
enough
music
to
my
ears,
yeah,
then
what
priya
did?
What
do
we
have
next.
A
C
Yep
sounds
good.
Also,
we've
got
about
about
seven
minutes
left
jared.
Who
was
on
the
call
earlier?
Well,
he
did
a
video
recording
about
about
this,
and
so
we
might
have
to
get
his
his
recording
out
in
the
hands
of
people.
So
very
briefly,
just
I'm
gonna
do
a
quick
introduction
and
then
mesh
mate
chatterjee
is
going
to
speak
the
rest
of
it
about
us.
C
Nice
and
so
docker
desktop
docker
desktop.
I
think
it
is
here
for
windows,
linux
well
now,
linux
and
mac.
So
I'm
running
a
mac,
I'm
running
docker
desktop,
there's
a
new
marketplace
for
extensions
instead
of
docker.
Well,
there
there
used
to
be-
and
there
still
is
docker
plug-ins,
which
were
more
of
a
cli
extension.
So
you
could
do
you
could
create
a
plug-in
as
a
container
or
a
set
of
containers
and
do
a
docker,
cli
docker
plug-in
now.
C
Docker
desktop
has
extensions
kind
of
a
similar
concept,
but
a
little
more
well,
I
don't
know
arguably
more
accessible
or
there's
a
marketplace
for
these
extensions.
This
was
announced
just
this
last
dockercon
a
couple
of
months
or
so
ago,
and
of
the
first
ones
to
come
out,
player
five
and
then
the
mystery
project.
Our
docker
partners
had
released
well,
given
a
couple
of
talks
at
this
last
dockercon
about
mesherie.
C
Actually,
we
were
fortunate
to
do
one
of
the
top
well
one
of
the
talks
with
hashicorp
and
console
the
other
one
with
the
good
folks
at
hpe
on
the
spire
and
spiffy
projects.
As
a
matter
of
fact,
spire
is
like
inches
away
from,
I
think,
becoming
a
graduated
project
or
spiffy
inspire
both
and
so,
and
so,
if
we
don't
cover
all
everything
today,
there's
a
couple
of
links
that
I'm
sure
I'm
sure
we'll
be
sharing.
E
Okay,
I'll
take
over
then
awesome,
so
lee
already
has
the
extension
installed,
so
hey
guys,
so,
basically,
what
so
for
dockercon
2022
docker
came
up
with
two
of
the
two
really
great
introductions
to
docker
desktop.
One
was
a
docker
desktop
for
linux,
which
was
much
awaited
and
docker
extensions,
and
we
got
to
be
part
of
one
of
the
first
extensions
here.
So
what
happens
here
is
when
you
go
and
install
an
extension
from
the
marketplace
it
installs
a
container
and
for
measuring,
particularly
we
have.
E
We
have
a
docker
desktop
extension
container
in
which
these
adapters
get
installed
inside
those
containers
as
sub
containers,
so
the
screen
that
lee
has
up
right
now,
it's
after
you
log
into
the
docker
desktop
extension
of
machinery.
You
first
have
to
get
a
token,
and
then
you
are
redirected
to
this
ui,
so
yeah
as
he
clicked
on
the
logo.
Right
now
you
go
into
the
meshi
dashboard
and
that's
it.
This
is
the
easiest
way
to
deploy
mystery
on
your
system.
C
E
E
E
Yeah
as
lee's
demonstrating
over
here,
it's
pretty
cool
it's.
This
is
our
code
spaces.
You
guys
go
ahead
and
break
things
here
as
well
to
test
it
out
because
there
are
bugs
there
are
plenty
of
bugs
that
we
can't
see
but
yeah.
Please,
please
get
on
the
waiting
list
to
test
it
out.
We
really
need
feedback
over
here
and
yeah.
E
Like
I
said,
this
is
the
easiest
way
to
get
around
doing
things,
because
I
know
how
difficult
it
is
to
start
your
dev
environment
or
to
get
especially
for
windows
users
that
you
have
to
install
make.
That
is
a
huge
pin
so
yeah.
This
is
the
easiest
way
to
do
anything
on
measuring,
so
do
check
it
out
and
give
us
your
feedback.
There
might
be
some
bugs
in
the
extensions
as
well.
So
it's
great
it's
it's
great
to
get
as
many
eyes
as
possible
on
this.
A
C
C
C
Yeah,
nice
good,
so
hey
so
so,
just
as
we
go
to
wrap
up,
we,
it
had
been
some
time
since
we
had
a
layer,
five
community
meeting
and
it's
really
nice
to
have
craig
join
to
help.
Kick
it
back
off.
It's
certainly
brought
in
some
folks
who
are
interested
in
code
spaces.
I
suspect,
there's
already
one
two
or
three
folks
who
are
volunteered
on
the
code.
Spaces
issue
for
mesheriy,
and
so
with
any
luck
we'll
be
we'll
have
that
single
click
button.
You
know
at
some
point
soon.
C
Good
other
than
that
next
week
looks
like
the
at
least
near,
as
I
recall,
looks
like
a
regular
week.
There's
the
websites
call
on
mondays
there's
about
six.
I
think.
There's
a
seventh
one,
seventh
website
coming:
that's
that's
curated
within
the
community
that
one's
on
service
mesh
patterns
and
then
measuring
dev
meeting
that
measures
ci
meeting
and
hopefully
we'll
get
back
into
a
cadence.
Probably
a
monthly
meeting
for
the
community
meetings
is
that
is
that
about
right,
a
teacher.
A
We
are
like
on
time,
so
I
think
we
can
cover
all
these
topics
in
the
next
community
meeting,
which
we'll
have
pretty
soon
and
like
guest
speakers
are
most
welcome,
like
that
is
what
our
plan
is
for
all
the
community
meetings
that
we
have
all
this
sort
of
presentation.
It's
really
enlightening.
We
had
a
really
good
time
today,
learning
about
code,
spaces
and
mesh
map,
so
yeah
looking
forward
to
more
such
sessions
soon.