►
From YouTube: 2022-12-13 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
A
We'll
start
off
with
a
quick
project
update
the
1.10
well,
first
of
all,
1.9,
nothing,
no
other
releases
are
planned
there,
I,
don't
think
we
have
any
urgent
fixes.
A
A
Was
it
last
week
or
last
Tuesday
and
then
I
think
we'll
plan
on
it
again,
just
before
the
break
next
week,
so
probably
Wednesday
of
next
week,
we'll
plan
on
the
dot
Age
release
to
yep
get
all
those
latest
updates.
So
in
the
1.10
board.
A
Oh,
this
is
1.11.,
so
1.10
board
nothing
in
the
blocking
release.
Column
Siobhan
is
continuing
to
investigate
this
issue
with
controller
expired
certificates
for
the
for
the
mission,
controller,
I,
don't
think
that's
blocking
people
working
on
this
until
we
restart
the
operator.
B
Well,
the
object,
storage
page
doesn't
load
in
a
soft
dashboard
by
default,
might
be
something
I
have
a
feeling
it's
from
the
fix
of
that
I
implemented
this
we
might
need
to
like
hold
the
manager
reconciliation
basically,
so
that
it's
not
in
parallel,
because
the
logic
I
implemented
is
basically
accessing
one
of
the
object,
Source
or
like
well.
C
B
B
A
A
B
A
It's
assigned
a
different,
but
I,
don't
think
he's
looked
at
it
for
a
while.
So
if,
if
you
want
to
take
a
look
at
it,
that
would
be
nice.
B
A
B
Said,
like
I,
think
I
feel
like
that.
It's
probably
like
a
race
condition
between
the
initial
password
being
created
for
the
user.
Then
the
reconciliation
of
the
dashboard
user
or
like
the
dashboard
happening
at
the
same
time
or
before
or
after,
and
it's
just
not
really
getting
picked
up
correctly.
For
some
reason.
A
A
and
I'm,
going
to
make
the
proposal
to
move
it
to
mid-February
just
because,
with
with
the
break
coming
up
and
some
time
off,
that
I
have
the
end
of
January
I
feel
like
there's.
Nothing,
no
major
features
that
we're
really
waiting
to
get
out
the
door.
So
if
we
just
wait
another
month,
I
guess
is
there
any
concern
with
waiting
on
1.11.
A
A
A
To
implement
that
with
the
Cs,
it
was
more
of
a
CSI
driver,
question
I,
think,
there's
yeah
I
think
it
just
represents
we're
in
a
stable
project
with
a
lot
of
features,
and
things
are
additive,
and
so
we've
been
really
still
adding
things
features
to
the
1.10
release
and
back
recording
them
just
because
they're,
not
big
and
breaking
at
this
point.
B
A
Okay,
then,
moving
on
to
the
community
topics,
so
the
just
a
note
on
maintainer
track
for
cook
on
Amsterdam.
The
submission
is
due
by
the
end
of
January,
so
I'm
kind
of
waiting
for
health
guidelines
and
things
to
be
published,
hopefully
it'll
be
published
by
then.
So
we
can
decide.
Are
we
going
to
be
there
in
person
or
as
far
as
are
we
doing
our
talk
in
person
or
virtual
fingers
crossed
for
in
person,
though,
for
sure.
A
A
Yeah
with
our
old
dogs
I
remember,
we
had
a
tag
in
there
that
we
only
made
the
searchable.
Let's
see
what
was
it
I
think
only
the
latest
docs
would
be
searchable
by
the
search
engines.
I
couldn't
find
what
that
label
or
tag
was.
A
It's
probably
in
the
the
repo
for
the
website,
though,
for
the
doctor
published.
C
C
A
Let's
see
just
a
note
to
follow
up
from
our
last
meeting
the
helm,
documentation,
generation
PR
was
merged.
So
thanks
for
that
effort
to
yeah
someone
on
your
team,
Alexander
I
forget
his
name.
So.
B
A
A
B
So
I've
created
a
PR
to
be
honest,
it's
not
fully
there
yet
where
I
would
like
it
to
be
because
at
least
it's
like
I've
wrote
it
now
like
they're,
for
example,
There's
a
summary
section
still
where
it's
like,
for
example,
this.
How
I'm
currently
seeing
this
feature
I
see
this
as
something
more
of
that
will
maybe
be
coming
in
the
future.
It
will
or
will
obviously
be
like
a
huge
change
and
especially
because
of
it
might
be
something
for
already
just
like
a
when
we
talk
about
like
the
future
of
Rook
I.
B
Guess
people
like
that
and
like
at
least
I
guess
regarding
the
concept,
but
for
my
side,
I
kind
of
came
to
the
understanding
of
like
that.
That
I
think
there
should
be
then
so
to
say
two
layouts
whether
one
is
like
the
management
layout
here
also-
and
a
second
is
like
the
executive
or
like
the
one
that
like
actually
creates
demons
or
work
stuff
components
in
the
cluster
that
it's
basically
to
some
degree
decoupled.
A
C
C
B
You
would
technically
have
to
lay
off
like
we're
still
with
the
saf
plus
object
in
mind
as
well.
B
We
used
to
say
a
want
buy
if
this
for
these
five
discs
and
there's
no
to
be
used
and
all
the
operator
would
do,
is
they
don't
like
even
just
cover
them
or
take
care
of
creating
the
necessary
persistent
volume
claims
or
even
just
passing
down
the
persistent
volume
claim
templates
to
the
cfosd
object
that
is
then
created
and
if
it's
like
an
abstraction
layer,
I
think
one
of
the
I
guess
more
broad
examples.
B
I
kind
of
picked
up
on
from
when,
when
staff
had
like
file
store
and
blue
store
that,
for
example,
through
this
method,
at
some
point,
you
could
really
just
change
the
OSD
object
to
have
the
setting
so
basically
from
switching
it
from
file
store
to
Blue
store,
and
there
would
be
some
mechanism
in
this
at
least
separate
Loop.
That
would
take
care
of
updating
every
OSD
one
by
one
or
at
least
a
single
OSD
accordingly,
by
well
technically
destroying
the
disk
or
at
least
wiping
it
accordingly
and
then
re-initializing
it.
B
B
Star,
what's
the
name
oh
yeah
right,
but
like
at
least
from
from
that
point
on
still
it's
it's
feeling
like
an
interesting
point
to
like
have
this
design
at
the
moment
here,
but
I
said
like
with
this
kind
of
summary,
where
I'm
seeing
it
right
now
with
that
it
wouldn't
make
sense
to
implement
that
Implement
isn't
like
a
one
point,
Rook
release,
but
morph
is
like
a
2.0
so
to
say.
B
Obviously,
with
a
migration
path,
yeah
yeah
any
any
feedback
on
it.
Just
welcome
any
questions
as
well
like
I.
Definitely,
a
bunch
of
points
need
to
formulate
it
better
as
it
is
currently,
but
it's
at
least
like
when
I
thought
about
it,
especially
today.
Writing
it
well
mostly
have
mostly
today.
B
A
B
I
can
link
to
the
pr
I
have
uploaded
it
there,
but
mainly,
as
you
know,
to
be
able
to
better
talk
about
it
here
in
the
meeting
PE
agenda.
If
anyone
wants
to
take
a
logo,
just
after
all,
the
Falls
or
anything
else.
Regarding
your
structure
after
document
feel
free
to,
let
me
know:
mindly
it
like
I'm
I
was
trying
to
dump
all
the
ideas
and
like
trying
to
like
summarize
them
summarize
them
a
bit
more
already
and
give
the
whole
thing
a
different
name
now,
which
is.
B
B
Let's
call
it
a
draft
at
the
moment
if
I
said,
if
you
have
anything,
if
you
wanna
into
your
fonts
or
anything
to
it
or
even
concerns
or
whatever
I'll
feel
free
to
do
so,
I
gladly
worked
it
into
this
design
and
see
if
we
can
find
some
common
ground
for
some
open
questions
still,
and
at
least
for
example,
if
you
go
to
the
files
and
scroll
down
to
line
65,
where
I
have
like
drawn
up
an
example
of
like
a
Surfers.
The
object
like
this,
for
example,
would
be
from
my
perspective.
B
I
would
like
a
suffer
SD
would
then
look
in
the
future
so
to
say:
well,
like
you
have
your
typical
stack,
you
have
your
status
and
you
define
the
things
and
you
have
a
way
to
override
certain
Global
options
on
so
to
say
this
granular,
this
granular
granularity
of
per
osts
as
well,
which
you
obviously
already
kind
of
have
with
the
self
cluster
spec.
When
you
go
down
to
nodes
and
devices,
but
yeah.
B
It's
kind
of
boring
from
that,
and
at
least
that
this
one
thing
I
just
need
to
still
get
written
down
in
a
better
way
or
even
in
any
way
at
the
moment
that,
for
example,
this
feature
could
be
like
exactly
one
part
to
make
this
even
more
Dynamic
on
based
on
what
the
person
that
runs
the
cluster
wants
like
if
they
specify
that
with
a
volume
volume
claim
template,
all
the
operator
would
do
is
create
the
amount
of
ceph
osds
and
add
the
volume
claim
template
into
it.
A
B
As
a
like
from
a
timeline
perspective,
this
is
definitely
not
something
that
will
just
like
happen
for
1.12
1.13
yeah,
so
really
see.
This
is
more
like
a
like.
Let's
maybe
this
might
be
even
the
point
where
we'll
we
should
sit
down
and
one
of
the
community
meetings
be
like
what
would
we
see
as
like
a
rook
2.0
kind
of
thing?
B
What
is
what
are
things
that
we
are
even
from
a
development
perspective,
a
bit
hurting
with
all
the
time
like
I,
don't
know
from
a
bit
of
my
perspective
like
it's,
it
would
be
interesting
to
have
like
simply
this
logic
to
decoupled,
so
that
in
the
end,
it
like
you,
don't
really
worry
about
one
OST
and
emergent,
but
but
you
have
this
control
over
this
one
OST
as
well.