►
From YouTube: 2022-02-08 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
All
right
recording
has
started,
and
this
is
the
february
8
2022
rook
community
meeting-
let's
see
here
so,
let's
catch
up
on
some
of
the
recent
milestones
and
and
upcoming
patch
releases
etc.
As
well.
Let's
see
so
I
don't
know
if
there's
too
much
going
on
for
1.7
right
now,
it
looks
like
you
know.
We
had
our
last
one,
that's
about
11
a
couple
weeks
ago,
I
guess
and
not
specifically
plans.12.
A
A
It's
looking
good
yeah
11
patches
out.
There
is
pretty
good
dedication
to
getting
getting
improvements
in
there
so
feel
good
about
that.
All
right
and
more
recently,
then
we
had
a
1.8.4
go
out
and
then
we
will
have
a
scheduled
1.8.5
for
february
17th
coming
up
here
in
about
about
one
week
or
so
end
of
next
week,
all
right
so
yeah.
Let's
talk
about
the
important
issues
here
then
for
the
next
next
1.8
release.
B
B
Oh
for
the
there's,
a
couple
issues
around
multis
that
blaine
is
working
on
trying
to
get
a
whole.
It's
a
whole
new
design,
really
on
how
we
approach
multis.
C
Yeah,
I
I
think
it's
enough
to
say
that
it's
it's
in
progress.
It's.
C
D
Yeah
so.
B
A
Where,
where
was
that
one?
Oh
this
one
here,
that's
that's
this
guy
right
here,
yeah!
What's
this
red
this
red
markings
here,
what
is
that
indicating.
A
A
B
I
was
just
looking
at
what
else
is
in
the
list:
there
there's
some
discussion
about
prometheus
rules
and
if
those
are
more
of
a
first
class
citizen
in
rook
or
if
we
remove
or
if
we
don't
install
them
with
the
operator
yeah,
so
there's
a
pr
related
to
that
where
we're
discussing
it.
But
I
don't
think
we
need
to
discuss
it
here.
A
A
All
right,
well
yeah,
so
for
that
five
it
looks
like
we'll
just
kind
of
have
a
regularly
scheduled
release,
then
for
the
next
patch
there
on
february
17th
and
with
nothing
pressing,
there's
no
urgency
to
bump
up
that
that
schedule
or
that
train
there
exactly
all
right.
So
then
1.9!
You
know
we
got
a
little
bit
under
a
couple
months
there
and
you
know
we're
waiting
until
obviously
that
would
be
well
there's
typical
release
cadence.
That
would
be
followed
here
already.
A
B
No,
that's
all
just
that
we'll
see
when
quincy
is
really,
but
I
need
it.
I
don't
think
we've
well
we've.
I
think
quincy
is
still
marked
as
experimental
or
you
have
to
put
a
flag
in
the
cr
to
allow
you
to
run
it
since
it's
still
expandable,
so
maybe
in
master.
We
could
update
it.
So
it's
and
try
and
get
that
official
support
going
with
the
ci
and
everything.
A
D
A
D
We
have
daily
jobs,
testing
against
various
branches,
so
we
we
have
been
testing
on
occupancy
for
for
a
few
months
already,
and
tests
are
passing
so
that
looks
promising
excellence.
D
We
have,
I
know
we.
I
know
there
is
a
tag
upstream
for
v
17
dot,
but
it's
not
a
stable
tag
yet,
and
I
don't
think
there
is
an
official
container
build
for
such
tag
because
we
don't
have
that
so,
but
still
we
are
running
on
quincy
already.
D
A
Cool
and
then
just
quick
note
that
blaine
thanks
for
sharing
that
updated,
networky,
multi-disc
related
pr
here,
I've
added
it
to
the
progress
column
on
the
1.8
board,
so
I'll
place,
the
other
one
yeah.
Thank
you,
sir
okay
cool.
So
let's
take
take
a
quick
look,
then
at
the
1.9
project
board
and
see,
if
see,
if
there's
much
to
not
not
much
flushed
out
there.
Yet,
though,.
B
Yeah
we
haven't
spent
much
time
putting
things
in
the
1.9
board.
I
thought
I
just
added
a
couple
of
other
issues
to
it,
so
maybe
I
added
them
to
the
milestone
instead
of
the
project,
I
guess
I'll
double
check
on
a
couple
of
perhaps
but
nothing
real
urgent.
A
C
Oh,
I
did
realize
this.
Yesterday.
I've
been
talking
to
some
of
the
likes
of
csi
developers
about
getting
a
acsi
provisioner
driver
that
will
allow
us
to
create
nfs
exports
from
like
persistent
volume
claims
for
likes,
fnfs
storage.
C
B
B
D
A
Column
automatically,
when
they're
added
to
the
project.
That
makes
sense
instead
of
a
trigger
step.
So
I
keep
that
one
there
and
then
yeah
prs.
I
wouldn't
throw
all
pr's
there,
no,
but
issues
yeah.
This
looks
good.
That's
what
I
was
looking
for.
Yep.
D
B
A
A
And
then
pr's
hold
on
progress.
C
B
C
A
This
one
doesn't
have
the
same
options.
I
guess
so.
You
have
to
first
add
that
sort
of
thing
yeah.
I
think
I
think
it
makes
probably
a
sense
to
the
typical
intent.
I
would
assume
the
majority
case
is
when
your
pr
is
open,
then
it's
it's.
It's
ready
for
review,
or
you
know
it's
it's
getting
to
that
status
and
if
we
want
to
then
moving
it
back
to
hey.
This
is
still
a
draft.
It's
still
in
progress
makes
is
probably
the
more
the
minority
case.
A
I
bet
so
move
pull
requests
here
when
they're
added
to
the
project
makes
sense
to
go
to
the
review
column,
then
cool
cool,
and
then
then
we
can
add
these
guys.
A
The
ones
that
were
in
triage
at
this
year
are
any
of
these.
Should
any
of
these
be
in
in
progress.
D
Yeah,
I
think
there
is
the
you,
remove.
Definitely
all
remaining
usage
of
contacts
to
do
this.
D
D
To
to
be
merged
did
somebody
else
move
this.
B
D
A
Distinction
all
right
cool,
so
I
think
we
mostly
covered
the
milestones
here.
We
can
move
on
down
to
the
community
topics
here
so
travis
and
blaine.
Do
you
want
to
get
us
updated
on
the
conversation
you
all
have
with
datasets.
B
Thank
you,
so
we
we
met
with
them
and
I
can't
remember
his
name
already,
but
yeah
rags
it
and
anyway
he
really.
He
was
a
developer
evangelist
and
he
was
just
reaching
out
to
us
because
he
saw
something
about
rook
and
cassandra
and
he
just
wanted
to
know
what
we're
up
to
and
we're
all.
Oh
well
we're
looking
for.
Maintainers
of
this.
Are
you
guys?
Is
your
team
interested
and
he
he
really
hadn't
realized.
It
was
something
that
big.
A
B
B
And
so
we
in
the
last
two
weeks,
we
haven't
heard
back
from
rags,
and
so
I
just-
and
I
opened
that
issue
about
two
weeks
ago,
just
so
the
community
could
be
aware
of
it,
there's
been
no
comments
on
it
or
anything.
Well,
if
you
click
on
it
like
did
anybody
at
least
I
don't
think
anybody
commented
on
it.
D
B
Yeah
just
curious:
if
anybody
acknowledged
it,
nobody
liked
it
or
anything.
Just
yeah.
D
A
B
A
Yeah,
that's
yeah,
that's
fine
and
having
it
like
stay
in
that
deprecated
state
for
probably
cycle
before
it's
you
know
like
pulled
completely,
is
makes
sense.
B
Well,
and
since
we
separated
the
repos,
there
are
no
more
releases
anyway,.
A
B
D
Just
make
the
repo
read
only
and
point
to
to
that
maintained
operator.
I
guess.
A
Then
said,
giannis
a
link
to
the
deprecation
notice
and
maybe
that'll
spark
the
passion
in
his
heart
again
right.
A
A
A
Look
at
releases
too
just
to
see
what
that's
that's
doing.
Oh
just
tags,
no
official
sentences.
B
A
B
A
D
A
A
B
I
assume
it's
the
upstream
contribution
or
creation
by
datastax.
C
A
A
C
C
A
Yeah
good
point:
blaine
yeah,
thanks
for
finding
that.
That's
that's
useful,
cool!
Okay!
Then
anything
else
on
the
agenda
here
or
this
short
agenda
is
to
its
conclusion.
A
Okay,
sweet
all
right,
well,
good,
seeing
everybody
and
and
looks
like
we'll,
be
working
towards
the
next
release
for
1.8.5
and
then
the
1.9
stuff
we
talked
about,
and
I
guess
that's
it.