►
From YouTube: 2022-06-28 Rook Community Meeting
Description
No description was provided for this meeting.
If this is YOUR meeting, an easy way to fix this is to add a description to your video, wherever mtngs.io found it (probably YouTube).
A
There
we
go
all
right,
the
recording
has
started-
and
this
is
the
june
28th
rook
community
meeting.
So
let's
jump
on
into
our
milestone
checkups
as
as
usual,
so
we
don't
have
a
particular
next
patch
release
for
1.8,
planned
11
would
be
the
next
one
I
believe,
but
there's
not
one
specifically
planned
for
that.
So
we
can
just
skip
ahead
of
that
one
and
we
won't
dive
into
that
one
and
then
for
one.
Is
that
right?
Travis
did
you
say
something
or.
A
Got
it
so
then?
Yes,
so
1.9.6,
we
did
do
a
patch
release
for
that,
since
the
last
community
meeting
and
the
release
notes
are
available
here.
Anything
like
important
that
we
want
to
call
out
within
this
this
this
patch
release
for
1.9,
oh
wait
hold
on
a
second,
is
that
the
1.9.6.
A
Be
updated,
let
me
let
me
just
update
this
link
here
copy
paste
issue
there.
We
go
all
right
now
here,
yeah
anything
particular
that
we
wanted
to
call
out
about
the
release
notes,
or
these
are
sufficient
on
their
own.
B
A
Sound
good,
then
the
1.9.7
will
be
upcoming
here
and
I'm
assuming
that
one's,
mostly
as
that's
a
date
driven
one
without
a
particular
feature.
That's
that's
driving
it
hard,
so
yeah.
The
next
next
recurring
patch
release
for
the
1.9
branch.
Yes,
what
do
we
want
to
call
out
as
coming
up,
particularly
or
a
big
focus
for
this
particular
batch
release?
Anything
in
particular.
B
A
Yes,
so
the
next
particular
date
we
have
down
here
is
is
july
7th,
then
so
yeah
not
this
thursday,
but
the
following
thursday
yeah
okay
and
then
we
can
bump
the
frequency
down
even
further
or
down
bump
the
frequency
down
from
there.
A
Got
it
okay?
That
seems
totally
reasonable
to
me
all
right
and
then
now.
First,
the
next
actual
minor
release
here
with
1.10
release.
We
can
bring
up
the
project
board
for
that
one.
We
have
that
tentably
scheduled
for
early
august
time
frame,
so
we
have
more
than
a
full
month
still
left
left
in
this
release,
so
kind
of
sort
of
early,
but
maybe
a
bit
halfway
through
the
release
cycle,
I
suppose
but
yeah.
Let's
talk
through
areas
of
focus
for
1.10,
then.
B
Yeah,
I
was
realizing
just
before
this
meeting
that
everything
we
have
in
the
road
map
for
1.10
doesn't
have
an
issue
tracking
it.
Yet
I
think
so
we
need
to.
I
need
to
make
sure
the
board
is
updated
and
1.10
is.
B
Like
maybe
it'll
be
a
lot
of
documentation
updates
and
may
not
be
a
lot
of
big
features,
but
maybe
some
smaller
features
definitely
coming.
That
would
be
nice
to
have.
A
B
Let's
see
the
crew
plug-in,
that's
we'd
like
to
get
some
help
health
checks
in
there.
That
would
make
it
really
nice
to
just
say:
hey,
run
this
analysis
on
my
cluster
and
do
that.
I
don't
think
that
that
work
hasn't
started
much
yet.
I
think
siobhan
was
going
to
work
on
that
anything
to
report
there.
C
C
B
A
nice
to
have
it
around
the
same
time
frame,
let's
say
check
for
existing
sub
volumes
before
allowing
a
file
system
to
be
uninstalled,
actually
blaine
just
merged
that
last
week,
and
we
did
back
port
that
to
1.9.
So
we
got
that
earlier
than
1.10.
B
C
B
C
B
A
Awesome
so
then
yeah
with
all
these
different
issues.
Here
then
it
sounds
like
maybe
we
can
follow
up
to
get
the
board
more
populated
and
reflecting
what's
going
on
there
and
and
what
were
the
themes
in
spirit
of
the
milestone.
The
ones
that
tend
to
release
are
sweet
all
right,
any
any
other
things
to
note
on
1.10
or
the
efforts
efforts
there,
alexander
anything
from
you.
There.
A
Okay,
then
that's
all
the
milestone
updates.
So
I
guess
we
can
go
ahead
along
to
the
community
topics.
Section
then
yep
so
july.
11Th
is
the
due
date
for
getting
the
maintainer
track
session
stuff
done,
but
that
is
submitted
and
completed
and
all
good
to
go.
Is
there
did
you
because
I
was
just
thinking
about
this
this
morning?
Actually
so
the
maintainer
track
thing,
that's
the
only
thing
that
I
had
seen
so
far.
Did
you
all
see
anything
about?
A
You
know
a
project
pavilion
or
you
know,
office
hours
or
anything
like
that?
It
also,
or
is
it
just
the
maintainer
track
talk
thing
I
haven't.
A
So
because
I
didn't
want
to
miss
that
so,
okay,
that's
good,
that
you
know
well,
we've
all
missed
it.
Then,
if
that's
the
case,
if
they
said
it
out,
we
all
missed
it.
Okay,
that
sounds
good.
So.
A
A
Yeah
is
that
is
that
the
plan
then
for
red,
hot
folks
for
in
north
america,
here
yeah
so
far,
awesome
good.
D
B
A
Now
it's
crazy
yeah.
He
just
jinxed
us,
okay,
sweet,
so
the
documentation
improvements.
We
can
go
ahead
and
move
on
to
that
topic.
B
D
Sure
yeah,
so
the
documentation
will
now
check
for
broken
links,
at
least
which
are
in
the
documentation,
yeah.
Well,
the
problem
I
get
with
previous
pr
that
has
been
merged.
I
think
just
now
that
helped-
or
at
least
like
that
was
exactly
one
of
the
points
where
I
was
like.
Oh
wait,
yeah
sure
there
is
something
missing
and
now
that
we
have
to
check
yeah.
B
D
Coming
along
great
so
far,
I
think
and
haven't
necessarily
heard
yeah
too
much
negative.
I
think
some
parts
of
the
documentation
might
simply
need
to
be
adjusted
as
well.
How
should
I
put
it?
The
mk
docs
markdown
renderer.
I
guess
you
can
call.
It
is
a
bit
stricter
at
some
points
like
you
can
start
lists
in
the
middle,
like
you
can
do
like
one
two
and
then
just
create
a
new
list
which
is
at
like
three
point,
four
point
and
so
on,
but
this
seems
to
be
less
of
a.
D
B
B
It
won't
work
across
like
if
we're
referring
to
github
docs
from
documentation,
or
vice
versa
right,
but
within
the
generated
documents
and
yeah
just
to
point
out
real
quick.
So
the
cluster
crd
doc
used
to
be
this
huge
long,
mono,
monolithic
thing,
and
now
I
basically
broke
out
the
four
main
scenarios
we've
got
from
that.
So
we've
got
hosed.
Pvc
base
stretch
cluster
and
external
cluster,
so
they
they're
each
of
their
examples
are
in
their
own
topic
and
the
cluster
crd
doc
is
still
pretty
long
with
all
the
individual
settings
described.
A
Or
accessible
as
well,
so
you
can
you
know
if
you
up
front,
you
know,
decide
the
type
of
scenario
you
want
to
follow.
Then
you
can
go
directly
to
that
doc
to
get
a
little
bit
of
focus
time
on
it.
I
like
that
yeah
and
then
everything
is
all
the
settings
and
stuff
are
still
here,
so
we
didn't
lose
any
any
documentation.
A
Yep
sounds
good.
Blaine
is,
I
think,
not
able
to
make
it
today,
but
did
we
have
some
some
some
progress
or
get
some
root
cause
on
the
nfs
deprecation
not
being
visible.
B
The
go
ahead
out.
B
So
we
could
either
fix
that
or
basically,
since
it's
a
deprecation
notice,
where
we're
not
planning
on
maintaining
it
anymore,
we
could
just
my
thought
was
just
to
quickly
merge
manually,
merge
the
new
dock
changes
and
then
not
worry
about
the
ci
for
it.
But
I
mean,
if
you
want
to
fix
those
that
sounds
good
too
I'm
just
assuming
we
didn't
need
to.
D
B
I'll
just
do
that.
I
just
need
to
remember
to
do
it
so
I'll
put
that
in
the
action
items
and
make
sure
that's
merging
someone
actually
posted
in
slack
today
in
the
documentation
channel,
hey
it's!
I
hear
it's
deprecated,
but
it
doesn't
show
up
in
the
docs
that
way.
Oh,
oh
yeah.
Thanks
for
the
reminder.
A
Okay
and
then
so
it
looks
like
the
final
item.
That's
on
the
agenda
here
is
around
the
inline
toolbox.
Spec.
A
B
For
the
toolbox-
and
it's
like
well,
we
had
to
build
the
rook
image
on
top
of
it,
because
we
put
our
script
in
there
that
you
know
configures
the
toolbox
and
blaine
suggested
wait.
Why
do
we
need
a
separate
script?
Let's
just
put
the
script
in
line
with
the
toolbox,
spec
and
then
the
image
for
the
toolbox
just
becomes
the
ceph
image
and
we
don't
need
a
rook
image.
B
So
it's
kind
of
a
just
a
cool
little
change.
I
thought
because
it
yeah
worked
smoothly
just
to
put
the
script
in
line
with
the
spec
and
I'm
still
trying
to
decide
if
there's
a
scenario
where
it'd
be
useful,
to
have
the
rook
binary
in
the
toolbox
because
there's,
but
we
because
there's
a
place,
we
use
it
for
running
the
toolbox
as
a
job
like
when
we
do
an
osd
removal
job.
B
With
the
inline
spec,
using
the
ceph
image
or
if
it'd
be
worth
keeping
rook
in
the
toolbox
image
by
default
and
have
it
as
a
new
new
example,
so
if
anybody
can
think
of
why
rook
should
be
in
the
toolbox
yeah,
let
me
know,
but
maybe
I'll
keep
it
as
a
separate
example.
Anyway,
still
thinking
about
it,
it's
fresh
off
interesting.
A
It
did
did
the
comments
here
on
the
on
the
pr
were
those
things
that
made
sense
to
you,
travis
and,
and
you
had
you
had
it,
you
have
answers
for.
A
That's
all
sounds
good.
Okay,
so
were
there
any
other
agenda
items
that
folks
wanted
to
bring
up
here
before
we
adjourn.
A
Okay,
well,
that's
everything
and
we
will
go
ahead
and
join
them
all
right,
well,
good
to
see
everybody
and
yep.
Thanks
for
all
the
effort.