►
From YouTube: 2020-11-03 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,
the
recording
has
started-
and
this
is
the
november
3rd
2020
rook
community
meeting.
We
can
skip
over
1.3
since
we
do
not
have
any
planned
patch
releases
for
that.
We
have
been
targeting
a
1.4.7
pack
from
release
for
a
little
bit
now,
so
we
can
take
a
quick
look
at
that
board
there,
because
that
is
coming
up
this
week.
B
B
I
I
I'm
not
sure
it's
a
repro
for
some.
I
need
to
figure
out
if,
if
that's
a
repro
still,
I
thought
barsha
from
red
hat
looked
into
it,
but
maybe
she
must
have
commented
on
a
different
issue,
because
I.
C
A
Is
this
the
original
poster?
Oh
no,
it's
not
the
original
opener
of
the
issue,
but
somebody
that
ran
into
it
that
had.
It
was
a
good
analysis
here
of
a
couple
of
things
that
they
did
wrong
that
got
them
to
this
issue.
A
A
On
that
thursday
yep
so
two
days
from
now,
that's
expected
to
go
out.
Okay
and
then
1.5
is
a
much
bigger
effort
here.
The
first
1.5
minor
release
we've
been
targeting
this
as
our
kind
of
quarterly
release.
Cadence
we've
been
planning
the
entire
time
to
have
this
out
before
kubecon
north
america
starts
targeting
a
week
from
today,
so
next
tuesday,
and
the
plan
here
is
to
cut
the
release
1.5
branch
two
days
from
now
on
thursday,
the
same
day
that
we'll
be
releasing
the
1.4.7
patch
here
is
the
board
here.
Travis.
A
Do
you
have
any
issues
of
importance
here
to
call
out-
or
you
know
some
of
this
view
column
here-
that
probably
won't
get
addressed.
B
B
Oh
that's,
just
a
pr
in
progress
and
I
think
we
can.
We
should
be
able
to
get
it
in,
but
it's
not
a
blocker
either
the
stretch
cluster,
the
one
that's
in
review
there
that
one
yeah.
I
want
to
try
and
get
it
in
before
we
branch,
since
it
is
more
of
a
major
feature
for
the
release.
Right,
that's
and
I'm
doing
some
final
testing
and
it
needs
just
a
final
review
cool
and
then
I
think
we're
good
there
and
just
I
guess,
comment
on
yep
so
thursday.
B
I
believe
we
should
be
ready
for
branching
and
then
from
thursday
through
the
release,
we'll
get
the
upgrade
dock
up,
updated
and
tested
for
upgrades,
and
then
I
think,
we'll
be
ready.
Tuesday
is
probably
pushing
it
if
we're
branching
it
on
thursday,
so
wednesday
or
thursday,
maybe
in
reality,
be
more
of
what
we're
we're
targeting
here.
A
That's
reasonable.
It's
still
well
ahead
of
the
that's
one
week
before
qcon
itself
starts
pretty
much.
So
that's
fine.
B
A
Maybe
seb
or
blaine
these
issues
that
are
assigned
to
you
all:
that's
not
anticipating
those
making
it
in
the
1.5
release.
I
assume.
D
D
B
A
All
right
sounds
good,
blaine,
okay,
so
yeah.
That's
the
the
plan
for
1.5
cut
to
be
cutting
the
release.
Branch
on
thursday
they'll
have
a
few
days
of
upgrade,
guide,
testing
and
bake
time,
etc,
and
maybe
some
backboarding
of
other
fixes
that
we
need
to
do,
but
then
targeting
wednesday
for
the
release.
A
Okay
alrighty,
so
that's
all
the
milestone
stuff
and
so
moving
on
to
the
community
topics
here,
kubecon
is
coming
up
in
two
weeks
from
now
I
believe,
and
so
everybody
should
have
submitted
their
recordings.
I
think
those
are
all
in
that's
great
for
the
rook
session,
that
is
on
friday.
The
last
day
of
the
conference,
blaine
and
alexander
have
graciously
accepted
to
be
present
for
the
live
q.
A
at
the
end
there.
So
thank
you,
gentlemen,
for
doing
that.
A
Appreciate
that
alexander
you've
done
one
of
those
live
q,
a
things
before
as
well
too
and
blaine,
I'm
not
sure
if
you've
gotten
a
chance
to
do
one
of
those,
but
they
it
is
a
little
confusing
when
you
first
get
thrown
into
it,
so
feel
free
to
sync
up
with
alexander.
A
If
you
haven't
already
to
kind
of
get
some
tips
on
how
to
manage
the
questions
and
how
to
use
the
software
there,
the
platform
the
little
what's
the
name
of
it
entrada
whatever
platform
to
to
manage
questions,
because
it's
a
little
confusing
at
first.
C
Well,
it
was
called
in
in
toronto
or
something
like
that.
It's
it
can
be
a
bit
confusing.
I
think
think
it
will
be
a
bit
hard
to
sync
up
on
that
earlier,
because
well,
I'm
not
remembering
too
much
how
the
structure
was.
I
think
they
might
change
something
till
then,
who
knows
I.
C
B
A
Yeah
awesome
all
right
and
then
in
the
travis
you
provided
the
updates,
including,
like
a
user
testimonial
story,
type
of
thing
too
for
the
keynote
project
update.
So
thank
you
for
doing
that.
That
is
done
and
confirmed.
B
Right,
I
wasn't
clear,
though
I
was
thinking
from
our
last
discussion
with
with
amy
and
chris,
that
there
might
be
some
other
opportunity
for
keynote
since
regret.
We've
graduated,
I
haven't
heard
anything
from
them,
though
I
think
it's
maybe
we
should.
I
guess
we
should
bring
them
and
see.
What's
up
if
there's
any
other
involvement,
that's
that
we
can.
A
Yeah
yeah,
that
is,
I
remember
that
discussion
as
well
too,
so
that
may
there
may
be
an
opportunity
there.
They
may
not.
I
remember
them
kind
of
presenting
it
to
us
as
a
potential,
and
you
know,
like
oh
we'll,
see
how
things
shake
out.
We're
still
figuring
it
out.
So
it
may
very
well
be
that
that
didn't
happen,
but
we
can
follow
up
and
ask.
B
D
D
Right
so
it's
like
it's
the
it's,
the
almost
it's
the
latest
milestone.
You
have
it's
the
highest,
almost
the
highest
grade
from
cncf.
So
if
you
don't
get
like
three
minutes
of
the
keynote,
then
who
gets
it.
A
A
Level
or
diamond
level
sponsors
all
right:
okay,
all
the
money
right,
it's
always
about
the
money,
all
right
cool,
so
that
is,
I
think,
everything
for
kubecon.
So
two
weeks
from
now.
Oh,
that
actually
reminds
me
too.
So
I
think
the
first
day
first
morning
of
kubecon
is
when
our
next
community
meeting
is
scheduled.
A
So
we
may
want
to
cancel
or
postpone
that
one
to
skip
that
one
for
kubecon
since
we'll
we'll
all
be
there.
Probably
I
don't
know
what
time
things
start
on
that
day,
but
that
is
the
first
day
of
coupon.
Is
the
17th
two
weeks
from
now.
B
A
Cool
okay,
that
sounds
good.
We'll
keep
that
on
the
calendar.
Then
travis
did
you
add
this
topic
about
the
lsd.
B
Creation
yeah,
that's
the
one
I
mentioned
a
minute
ago.
As
far
as
just
so
yesterday,
the
ci
started.
Failing
like
oh,
what's
going
on
it's
funny,
it
was
right.
The
master
build
that
first
failed
with
all
these
errors
was
from
the
nf
nfs.
No,
the
the
pr
emerged
yesterday
jared
with
the
nfs
operator
right,
yeah,
yeah
yeah.
Some
of
the
quota
changes
for
that
yeah
right
and
I
was
just
confused
because
why
is
why
are
the
self-tests
all
failing
now
after
the
the
nfs
operator
changed?
What
did
I
do
right?
B
I
almost
pinged
you
like
jared,
go
fix
it
and
then
I
realized
oh
wait.
This
is
nothing
to
do
with
nfs
operator,
the
ceph
nautilus
latest
patch
release
came
out
and
apparently
had
a
pretty
big
breaking
change
for
us,
because
the
set
volume
batch
mode
for
lbm
seems
to
not
work.
It
prints
a
message
about
it
being
deprecated,
but
then
it
just
doesn't
work
and
so
yeah.
It's.
I
think,
we've
got
a
bigger
issue
where
we
need
to
recommend
people.
B
Don't
use
that
release
of
nautilus
in
rook
if
they're,
using
osds
on
non-pvcs
at
least
the
pvc
case
still
works.
A
Travis,
do
you
so
do
you
think
that
that's
a
potentially
a
bug
there
like
where
it's
you
know
announcing
that
it's
deprecated,
but
it
actually,
the
functionality
doesn't
work
at
all
anymore
either,
and
it's
in
a
patch
release,
which
is
kind
of
unexpected,
for
something
to
be
broken
in
apache.
Is
that
a
upstream
regression
that
needs
to
be
addressed.
B
D
Well,
thank
you
without
actually
knowing
really
the
issue
jared,
you
actually
quite
summarized
it
really
well.
This
is
something
that
shouldn't
be
happening
in
a
pinpoint
release
like
it's
a
it's
a
regression.
Definitely
because
you
don't
you
don't
insert
breaking
changes
in
the
middle
of
a
release
and
that's
what
happened
even
though
one
of
our
colleagues
hardly
vote
for
not
having
that
change
merged,
but
it
looks
like
they
decided
to
go
with
it.
Anyways.
D
So
yeah,
I
guess
we'll
have
to
just
open
up.
I
think
saturday
is
going
to
open
up
an
issue
on
the
tracker
on
step
tracker
so
at
least
to
highlight
that
they,
just
like
we
said
you
will
be.
You
will
be
breaking
things
by
doing
this,
so
they
actually
did
break
things
now
and
we'll
see
how
to
take
it
from
there.
I
guess
for
now
the
like
pinning
to
14
or
2
12
is
fine.
B
A
There
there
weren't
any
other
fixes
or
improvements
that
we
were
counting
on
getting
out
of
the
dothra
team,
really.
D
There
is
one,
but
it's
it's
a
hot
fix
and
it's
not
something
we
use
in
rook,
so
I
don't
think
we're
affected
by
the
hot
the
by
the
bug
that
is
being
fixed
in
the
dot
13
release.
So
for
now
it's
otherwise.
We
would
have
seen
that
earlier
right.
D
So
I
guess
it's
fine
to
just
pin
with
the
12.12
radius
until
we
find
a
solution
for
that
regression.
Volume.
B
D
Yeah,
the
problem
is
that
there's
not
there
are
not
so
many
ways
around
it,
because
now
it's
part
of
the
stable
code,
it's
not
like.
We
can
really
easily
avoid
that.13
version
or
yeah.
Well,
we
can,
but
it's
just
like
it's
going
to
be
ugly.
If
people
do
upgrade
and
then
we
just
reject
that
version,
yeah
we'll
have
to
see
right.
E
Yeah,
but
is
that
something
that,
like
maybe,
would
be
for
the
best
in
rook
like
it
would
be
really
awkward
to
be
like?
Actually,
we
don't
support
this
version,
I'm
not
gonna
do
anything
but
like
that.
That
could
be
for
the
best
to
not
break
anything.
Just
to
say
you
know
to
update
like
a
1.4
patch
and
in
1.5
just
be
like.
We
don't
support
this
version
of
zeph.
D
I
mean
it's,
it's
really
this
one,
so
anybody
that
upgrades
2.4
2.413
won't
see
anything
until
they
expand
their
cluster,
so
we
can
still
avoid
people
like
if
they
come
with
if
they
come
up
with
another
hotfix
or
they
give
us
a
way
to
work
around
it
without
having
to
just
change
too
many
things
in
our
code,
we
could
solve
that
by
group
with
ease
or
wait
for
the
next
14.2.14.
D
B
D
D
D
Yeah
this
one
yeah,
which
obviously
won't
solve
the
case
where
you
have
an
existing
cluster
and
then
you
upgrade
to
that
newest
version
of
ceph
and
then
you
start
trying
to
expand
the
cluster
or
actually
yes,
if
you
upgrade
the
version,
then
you
will
expand
the
cluster
with
different
types
of
osd's
with
raw
mode.
So
it's
it's
a
workaround.
A
B
A
Okay,
any
other
thoughts
on
this
yep
all
right
sounds
good.
You
gotta
travis,
to
update
us
about
in
turn
to
the
outreach
program.
B
Yep,
I
just
added
that
we
do
have
an
intern
who
has
submitted
a
proposal
for
this
project.
Actually,
blaine
do
you
want
to
talk
about
it?
You've
been
tracking
it
more
closely.
E
Yeah,
oh
my
microphone
still
yeah.
We
have
one
applicant
madavi
from
I've,
the
philippines-
maybe
I
I
forget
now
exactly
singapore
yeah,
that
that
sounds
right.
I'm
just
like!
Well,
it's
that
time
zone,
but
she's
done
a
really
good
job
getting
started
with
rook.
I
think
like
getting
a
cluster
up
and
running
and
being
able
to
test
things.
I
mean
even
just
that
in
rook
is
a
pretty
big
step.
I
think,
and
has
a
fix
to
documentation.
E
We
do
want
to
make
sure
that
she's
comfortable
writing
some
go
code,
travis,
and
I
think
that
actually
having
writing
a
a
go
utility
similar
to
how
the
osd
purge
was
written,
is
the
right
way
to
go,
especially
since
we're
gonna
have
to
query
like
both
the
kubernetes
api
and
also
ceph
kind
of
makes
go
the
the
best
choice
there
since
doing
it
in
like
bash
or
python,
like
we
don't
have
as
good
integration
and
scaffolding
in
place.
E
Yeah,
I
think
I'm
I'm
inclined
to
accept
her
as
as
an
intern
as
long
as
like
she's
interested
in
doing
some
code
writing
or
as
long
as
we
can
like,
find
some
some
common
ground
on
like
skills
that
she
wants
to
learn
and
ways
that
the
rook
project
can
benefit,
even
if
that
is
just
documentation
in
in
the
end,
I
think
it's
still
a
worthwhile
endeavor.
A
Cool,
it's
always
awesome
to
get
to
get
new
contributors
involved
in
the
in
the
project
in
the
community.
So
that's
always
exciting,
awesome!
Okay,
so
that
is
the
last
agenda
item
that
we
had.
We
don't
have
any
other
specific
pr's
or
issues
to
talk
about
here,
since
we
kind
of
talked
about
this
one
up
here.
Are
there
any
other
topics
that
folks
wanted
to
add
that
were
not
in
the
agenda.
B
A
All
right:
well,
then,
yeah!
What's
that
travis
cool,
so
we
so
two
weeks
until
kubecon
we'll
see
folks
online
before
then
we
still
do
have
this
community
meeting
scheduled
for
two
weeks
from
now,
maybe
a
short
one,
but
we'll
have
that
scheduled
still
and
otherwise
we
will
see
everyone
online
and
at
kubecon.