►
From YouTube: 2021-08-10 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
Okay,
welcome
everyone
to
the
rook
community
meeting
on
tuesday
august
10th
2021.
Well,
let
me
see
if
I
can
share
my
screen
here
and
we'll
get
started,
share
screen
all
right.
A
1.5,
oh
milestone,
checkup.
First,
I
think
overall
1.5
we're
pretty
much
saying.
No
more
releases
are
planned
and
1.6
we'll
plan
on
1.6.9
next
week.
At
least
I
don't
know
of
any
urgent
issues,
so
I'm
thinking
next
week
we'll
plan
on
the
1.6.9
it
well,
it
may
or
may
not
be.
Our
final
1.6
release
may
do
others
in
the
future,
depending
on
issues
that
come
up,
but
let
me
just
check
the
board
there's
nothing.
I
recall
that
was
in
here
that
needs
attention
yeah,
so
nothing
in
the
to
do
or
in
progress
or
review.
A
A
A
That
will
be
included
originally
at
the
last
community
meeting.
We
talked
about
getting
1.699
out
possibly
this
week.
A
A
The
reports
that
have
come
in
since
then
I
feel
like
are
are
pretty
minimal.
As
far
as
any
issues,
I
guess
the
testament
that
this
was
a
maintenance
release.
A
lot
of
internal
fixes
like
around
ci
that
that
have
been
good
and
stabilizing,
but
also
no
major
destabilizing
features
that
we
needed
to
get
patches
out
quickly.
A
A
A
A
And
on
to
community
topics,
all
right,
so,
first
of
all,
I
wanted
to
welcome
santosh
and
shabam
officially
to
the
reviewers
group
for
the
step
operator.
So
the
the
reviewers
are
are
those
who
are
actively
involved
in
the
project.
They're,
reviewing
pr's
and
contributing
many
pr's
and
santosh
and
stubborn
have
really
been
on
the
project
for
the
last
couple
of
years
or
close
to
two
years
and
you're
contributing
for
a
long
time.
A
B
A
B
A
small
note
on
that
it
looks
like
github
might
be
having
a
service
outage
right
now
of
some
kind,
I'm
not
able
to
see
the
files
changed
or
actually
add
a
like
a
review
on
it
right
now.
All
right.
B
It
looks
like
I
can
see
the
files
changed,
but
still
not
approve
the
review,
I'm
assuming
that
will
be
taken
care
of
soon,
but.
A
B
Anyway,
I
yeah
very
happily
approve
the
pr
and
we'll
do
that
once
github's
back
online.
A
I
think
the
next
step
we've
got
is
in
the
interest
of
decommissioning
jenkins
soon,
so
it'll
be
at
least
probably
a
couple
months
before
we
consider
turning
off
jenkins
completely
like
just
in
case.
A
A
Now
blaine
you'd
added
the
atari
fanta
phantom
partitions
topic.
What's
the
latest.
B
Yeah
yeah:
this
is
something
we
had
brought
up
like
for
how
long
it's
been
going
on.
I
think
it's
been
like
three
community
meetings,
so
I
think
this
is
finally
kind
of
rolling
to
a
close
here.
The
pr
that
I
made
to
stuff
volume
got
merged.
Yesterday
there
was
a
stuff
tracker
and
then
you
can
see
the
pr
if
you're
interested
in
looking
more
into
that
yourself.
B
A
A
B
B
If,
if
the
name
of
a
disk,
for
example,
like
sda
fails,
then
you
know
whenever
the
node
boots
up
again,
sdb
becomes
sda,
sdc
becomes
sdb,
etc.
Or
you
know,
the
controllers
aren't
guaranteed
to
be
deterministic
anyway,
and
so
those
ids
can
change
and
we
in
an
init
container
for
osds
when
they
start
up.
We,
if
we
don't
find
the
right
disk,
then
we
use
set
volume
to
scan
all
the
disks
to
find
the
right
one
to
attach
to,
but
with
the
phantom
atari
partition
issue.
B
The
yeah
seth
volume's
behavior
was
not
right
and
it
wasn't
finding
the
disks
that
it
just
wasn't
finding
the
dosd's,
because
there
were
child
devices
and
it
then
assumed
that
the
parents
didn't
have
proper
osds.
So
now
that's
fixed
and
now
our
osd
provisioning
doesn't
you
know,
rook
doesn't
have
to
do
anything
special
to
handle
the
case
anymore.
A
This
is
richard
elling.
We
run
pvcs
but
hold
this
pvc,
so
we
get
those
phantom
partitions
as
well.
But
since
we're
running
in
pvcs
we
we've
never
had
a
conflict.
B
A
B
A
B
That
that
is
something
I
that
is
good
to
have
confirmed.
That
is
something
I
I
had
suspected
was
was
possible
and
I
know
there's
a
there's
a
like
a
bug
report
that
mentions,
or
that
like
has
a
an
atari
partition
listed,
but
it's
like
an
unrelated
issue,
but
it's
good
to
know.
That
is
not
a
it's,
not
a
problem.