►
From YouTube: 2022-03-22 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
march
22nd
2022
a
lot
of
22's
going
on
there
rook
community
meeting.
So
let's
jump
on
into
milestones
and
upcoming
things
1.7,
you
know
we
haven't
had
to
do
a
patch
release
for
that
or
we're
not
planning
on
one
coming
up.
So
we'll
basically
just
completely
skip
that
one
for
the
1.8,
though
we
did
a
a
patch
release,
the
1.8.7
that
was
just
two
days
after
the
community
meeting
last
week
or
last
time.
A
So
we
did
do
that
one
and
then
we'll
have
another
scheduled
one
at
the
end
of
the
month.
Here
I
believe
that'll
be
after
travis
gets
back,
and
so
he
made
a
comment
that
there's
not
anything
super
pressing
that
we're
aware
of
so
we
will
just
do
that
that
scheduled
one
after
he
gets
back.
Let's
take
a
quick
look
at
the
board,
though,
and
see
if
there's
anything
important.
That
folks
want
to
bring
up
any
notes
on.
We
don't
have
anything
in
the
blocking
release,
column.
A
We've
got
a
couple
things
that
have
been
merged
in.
I
don't
know
if
there's
a
big
pressing
thing
or
you
know
any
risks
to
call
here
seb.
Do
you
have
any
ideas
about
the
things
that
we
need
to
get
in
or
anything
that's
important.
C
B
A
Yeah
and
that
that
makes
sense,
that's
aligned
with
you
know
we're
not
planning
on
doing
the
release
until
until
travis
is
back
anyways.
So
that
makes
sense
to
me.
A
All
right
and
then
obviously
there's
the
upcoming
1.9
released
as
well,
which
will
be
the
next
minor
release.
That's
you
know
we,
as
we've
been
discussing
over
the
last
couple
community
meetings
that
is
contingent
upon
the
quincy
release
of
ceph
being
available
and
and
official
builds
and
all
that
jazz,
so
that,
apparently
this
is
news.
I
think
that
we
didn't
know
before
the
the
release
is
for
seth.
A
Quincy
is
march
31st
now,
and
so
then
we'll
be
able
to
take
that
pick
that
release
and
then
start
doing
our
release
candidates
for
1.9,
pretty
much
directly
after
that.
So
we'll
we'll
create
the
1.9
release
branch
right
after
that,
as
well
we'll
start
using
the
official
stuff
release
and
we'll
start
getting
these
candidates
out
working
towards
the
1.9
official
release
for
rook
out
of
that
1.9
branch.
A
So
that
looks
like
it
will
be
targeted
for
about
a
week
later
on
april
7th,
so
we're
kind
of
coming
down
until
a
limited
amount
of
time
in
the
1.9.
You
know
main
branch
future
work
there.
So
I
don't
know
actually
how
well
updated
this
board
is
here.
But
let's
talk
about
some
of
the
outstanding
features
that
we
have
that
we're
trying
to
get
in
there's
a
number
of
things
in
progress.
A
Some
of
these
are
actually
merged,
though
assume
that
those
should
be
moved
to
done
then,
since
they
are
already
already
closed
down
but
yeah.
Let's
talk
about
some
of
the
the
tasks
here,
then
that
are
outstanding
or
in
review,
since
we
do
have
a
limited
amount
of
time
before
we're
trying
to
branch
and
get
1.9
going
there
so
sev
this
one
is,
it
was
opened
by
you.
I
don't
know
if
you're
working
on
it,
though,
but.
B
Yeah,
no
someone
is
yes,
someone
is
so
the
first
one.
The
person
has
rebased
the
branch,
so
I
think
it's
almost
ready
to
be
merged,
so
that's
gonna
make
it
for
one
time
it's
a
it's.
A
major
change
in
the
code
base,
so
we're
just
waiting
the
last
minute
to
emerge
it
so
that
we
can
really
avoid
like
back
ports
and
and
interpret
conflicts.
B
So
this
this
one
is
going
to
be
in
the
second
one
is
probably
going
to
miss
the
one
line,
but
might
end
up
being
a
backboard.
So
because
it's
a
bug
fix
I'm
working
on
this
one
and
the
rook
code
is
ready,
but
there
is
another
architectural
change
and
maybe
it's
the
wrong
yeah.
I
think
it's
in
the
wrong.
B
A
B
A
B
D
A
Github
today
too,
so
there
could
be
some
lingering
lingering
funny
business
going
on
yeah.
B
B
A
Here,
yeah
yeah,
so
let's
see
oh
yeah,
that
doesn't
look
good
okay,
so
we
may
not
be
able
to
accomplish
anything
with
github
right
now,
but
we
will
try
to
update
the
board
later.
So
maybe
that's
why
some
of
these
guys
are
still
stuck
in
progress
and
they
haven't
been
moved
to
done,
like
maybe
oops,
okay,
so
anyways,
but
so
you
have
so
then
this
is
that
90
925!
B
Hello,
it's
the
internet
approach
of
that
vr
based
on
the
new
design
proposed
in
9003,
which
I'm
also
trying
to
add
to
the
release
online
board.
But
the
mac.
A
Okay,
fair
enough:
okay!
So
we'll
get
that
on
the
board
and
that's
that's
in
drafted,
so
is
it
already
being
reviewed
then,
or
is
there
some
more
work
to
do
before
you
open
it
up
for
out
of
draft.
B
A
Okay,
got
it
okay,
so
then
we
can
try
to
remove
this
then
from
the
board
as
well.
Since
this
is
an
abandoned
effort
once
github
is,
is
back
and
running
and
able
to
do
right
operations
it
would.
It
would
seem
any
other
comments,
then,
on
some
of
the
other
features
that
are
in
progress
in
the
status
on
those
ones
and
the
making
it
into
1.9.
B
B
B
A
Cool
yep
so
he's
working
that
as
well.
Okay,
cool
anything
else,
then
that's
like
worth
mentioning.
That's
part
of
the
to
do
column
then,
since
all
these
are
done
and
we'll
get
those
moves
when
get
up.
B
A
Okay,
so
then
it's
about
almost
ten
nine
days,
or
so
it's
a
little
bit
more
than
a
a
week
before
we'll
go
ahead
and
create
the
1.9
release
branch.
And
then
you
know
a
week
of
big
time
in
the
lace
range
before
we'll
get
out
that
that
release
any
other
comments,
then
things
to
bring
up
in
terms
of
releases
and
milestones.
B
A
Okay,
awesome
and
then
this
is
using.
A
Have
we
in
order
to
have
been
using
quincy
already
in,
like
our
you
know,
master,
builds
etc?
Is
that
what
we've
the
way
we've
done?
That
is
with
using
this
v17
tag?
I
had
it
like
ahead
of
time
or
is
this
a
new
update,
then
that's
something
there
is
another
tag.
B
There
is
another
tag
which
essentially
follows:
whatever
current
master
is
and
we
use
it
and
we
also
have
devil
versions
which
are
at
the
tip
of
the
branch,
the
branched
version.
So
once
you
have
the
quincy
branch,
then
you
have
tags,
but
then
you
have
the
tip,
which
is
everything
between
the
tag
and
what's
coming
next,
we
also
test
that
out.
A
C
A
Pool
so
they're
yeah
we'll
have
to
make
sure
to
follow
up
on
testing
the
upgrade
guide
to
make
sure
that
smooth
updates
in
in
the
real
world
also
okay,
great
so
yeah.
So
it
looks
like
we're
making
great
progress
in
towards
1.9
and
getting
that
out.
You
know
using
the
stable
version
of
princi
converging
on.
You
know
to
make
sure
that
the
migration
and
upgrades
upgrade
story
is
good.
That's
perfect!
A
That's
wonderful
and
it's
travis
also
had
a
action
item
that
he
was
going
to
review
the
pending
release,
notes
for
quincy
to
check
on
any
new
features
and
make
sure
that
there's
nothing
else
to
worry
about
in
terms
of
things
we
need
to
integrate
or
or
deal
with
changes
et
cetera.
B
A
Thanks
for
doing
that,
then
tug
okay,
then
anything
else
than
in
terms
of
agenda
items
or
things
that
folks
wanted
to
bring
up
today
into
the
end
of
the
written
agenda
so
far
alex
anything
on
your
mind.
D
I
I
actually
had
one
something
I
wanted
to
bring
up,
so
I'm
just
pasting
a
pr
link
here,
so
I'm
kind
of
a
new
contributor
to
look
I've.
Just
I've
got
my
first
pr
merged,
I
think
last
week,
so
I
was
interested
in
working
on
this,
but
I
I'm
in
need
of
some
clarification
around
what
exactly
needs
to
happen
for
this.
So
as
I
understand
this
right
now,
we
kind
of
decipher
this
yaml
snippet
from
different,
whatever
different
expressions
that
are
supplied
to
different
fields.
D
Let's
say,
for
example,
as
you
can
see
in
the
csi
provisional
node
affinity,
it
says
not
and
then
my
key
so
then
it
translates
and
generates
the
snippet,
where
it
kind
of
just
expressed
expresses
that
into
those
terms.
D
So
if
you
scroll
at
the
bottom,
then
travis
mentions
this
idea
that
I'm
not
sure
what
he
exactly
what
functionality
does
he
mention,
but
it
would
be
a
solution
to
even
arbitrary
logic
which
I'm
not
exactly
able
to
wrap
my
head
without
so.
B
Honestly,
you
haven't
been
involved
in
that
issue,
but
I
would
really
suggest
that
if
you
have
any
questions,
then
you
put
all
of
them
into
the
issue
and
when
travis
comes
back
or
others
have
time
to
look
at
it,
then
they
will
reply
if
that
works
for
you,
I
think
it's
just
better,
because
right
now
we
don't
have
travelers.
E
Cool,
I
I
think
I
might
understand
what
travis
is
saying
here:
how
about
we'll
we'll
try
to
chat
a
bit
about
it
on
slack
and
see
if
we.
C
E
Dive
into
because
this
is
as
far
as
I
I
understand
travis
here,
sorry
for
the
mouse
in
the
background-
is
that,
instead
of
instead
of
us
doing
some
passing
logic,
we
would
basically
switch
it
to
so
well,
so
the
user
provides
it
as
yamo
and
we
use
yaml
on
marshall
or
some
other
cool
functioning
kubernetes
to
unmarshal
it
directly
into
the
anti-affinity
or
affinity
structures
which
would
make
our
lives,
I
think
much
easier
as
well
for
the
future.
D
Yeah
yeah
that
actually
makes
sense
yeah.
I
actually
thought
about
that
as
well,
but
yeah
I
it
was
kind
of
like
aren't.
We
increasing
like,
isn't
this
like
a
counterintuitive
for
the
user,
but
okay,
let's,
let's,
let's
talk
on
slack,
I'm
I
don't
want
to
take
any
more
time.
That's
fine!.
E
Yeah,
let's
talk
later
on,
just
like
yeah
yeah,
I
feel
free
to
ping.
What's
like
there
in.
A
A
Okay,
yeah
thanks
for
suggesting
that
alex
anderson
volunteer
yourself
to
help
out
with
that
issue,
and
thank
you
for
bringing
that
up
as
well.
In
the
first
place
there
so
yeah.
That's
that's
great
and
appreciate
the
contributions
you're
making
too.
A
Okay,
cool
yeah,
then
I
guess
after
that
then
we'll
follow
up
with
that
on
slack
and
we
can
go
ahead
and
adjourn
now.
Then.
A
Thanks
everybody
amounts.
C
All
right,
so
I
I'm
also
kind
of
a
new
contributor
to
rook,
so
I
sent
in
the
pr
I
think
that
was
being
discussed
for
the
context
or
to
do
so
it
was
a
beginner
pr.
So
I
wanted
to
ask
so
what
would
be
the
procedure
to
kind
of
pick
things
up
and
understand
things
as
we
go
along
so
should
I
just
kind
of
look
through
all
the
issues
there
or
something
like
that.
B
C
A
In
one
way
that
you
can
maybe
get
a
idea
of
what
issues
are
somewhat
prioritized
as
well
as
by
looking
at
the
release
boards
here
and
see
that
hey
in
1.9.
These
are
things
we'd
like
to
do,
but
like
this
one
here
doesn't
have
somebody
assigned
to
it.
This
one
here
doesn't
have
someone
assigned
to
it.
So
there
are
issues
at
least
that
we
have
identified
somewhat
recently
as
being
useful,
but
you
know
nobody's
working
on
them
there
so
like.
A
That
is
a
good
place
to
look
for
in
terms
of
issues
that
probably
have
relevant
and
recent
value
as
well.
A
A
All
right,
sweet
now,
final
call
for
for
anything
else.