►
From YouTube: 2020-06-16 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
A
Alrighty,
so
the
agenda:
well,
it's
pretty
short
so
far,
so
we'll
see
if
we
keep
it
short
or
if
we
end
up
with
lots
of
topics.
A
That
seems
to
be
what
happens
if
you
don't
start
with
a
long
agenda,
it
gets
long
anyway,
all
right
milestone,
checkup
first
on
the
1.2
project
board.
Well,
no
releases
are
planned.
I
don't
think
we
have
any
issues
worth
looking
at.
Let
me
just
click
on
this.
A
The
project
board
just
to
confirm
so
no
issues
are
showing
up
there
for
discussion,
and
I
think
that
that
sounds
good
backwards,
really
focused
on
1.3
at
this
point,
so
moving
on
to
one
that
or
anything
on
1.2
anybody
wants
to
bring
up.
I
think
that's
old
news
right
on
1.3,
then
to
open
that
board.
A
A
I
don't
really
know
of
any
big
issues
that
that
we
still
need
to
get
in.
We
do
have
a
few
issues
that
are
shown
up
in
progress.
Maybe
I'll
just
talk
through
each
of
these
real
quick,
so
this
three
it
is
under
review,
I
believe,
still
waiting
for
a
response
from
some
feedback
on
it
and
yeah.
I
think
this
one
was
just
of
interest
to
the
person
who
opened
this
pr.
I
don't
think
it's
urgent
for
others
to
get
it
in
five.
A
Two,
two,
three,
the
yeah,
the
octopus
zeph
dashboard,
is
still
not
working.
We're
waiting
for
a
fix
on
the
stuff
side,
there's
not
much.
We
can
do
on
the
brooks
side.
Still.
Unfortunately,
I
haven't
heard
surprisingly
many
reports
of
that
issue.
Maybe
people
are
just
finding
it
that
it
exists
as
a
known
issue.
I'm
just
curious.
Have
other
people
heard
of
complaints
of
the
octopus
dashboard
not
working
or
are
people
not
upgrading
it
to
octopus?
Maybe
alexander
any
sense
of
that
from
your
side.
A
Yeah
so
anyway,
I
believe
it's
still
an
issue.
I'm
just
curious.
Why
more
aren't
complaining
if
it
really
is
still
an
issue.
A
Next
to
issues
around
bucket
creation-
and
I
don't
I'm
not
aware
of
the
status
on
those
or,
if
anybody's
waiting
on
those,
maybe
we
could
even
move
those
out
to
1.4
they're,
not
urgent.
A
And
then
the
last
one
isn't
really
tied
to
the
1.3
release,
but
would
be
nice
to
get
that.
We've
got
a
pr
that
will
contribute
rook,
rex
f
operator,
at
least
as
an
open
shift
operator,
and
I
believe
the
last
blocking
issue
with
that.
One
is
that
we
have
the
sec.
The
security
context,
constraints
that
earth
needs
and
which
the
olm
doesn't
seem
to
support.
A
A
A
B
A
A
B
A
A
B
A
We've
got
about
six
weeks
until
the
proposed
release
date
around
the
end
of
july.
Now
let
me
go
back
and
show
this
so
last,
at
our
last
meeting
we
talked
about
july
17th
being
the
feature
freeze
date
and
then
the
28th
as
the
potential
release
date.
It
will
go
as
well,
so
any
other
thoughts
anybody's
head
on
on
those
dates
or,
if
we'd
like
to
consider
a
change.
A
All
right
first
topic,
then,
is
graduation.
I
I
don't
have
any
update
here
in
the
last
couple
of
weeks
and
I'm
feeling,
unfortunately
like
it's
a
bit
stalled
in
committee.
Type
of
thing:
we've
done
all
the
due
diligence
on
our
side
too
we're
just
waiting
for
the
storage
sig
to
put
together
their
final
recommendation
and
call
for
the
vote,
so
yeah
follow
up
with
jared
and
saw
it
on
on
that.
So
we
can
push
that
along
and
everything
we
know
of
we've
done
for
graduation,
it's
just
let's
get
it
done
from
committee.
A
Yep,
so
I
don't
have
much
more
detail
on
that.
Have
a
comment
on
graduation
or
question.
A
Alrighty
so
google's
summer
of
code,
I'm,
how
might
I
see
you
added
some
comments?
Let
me
accept
those
all
right.
I'm
gonna
talk
through
the
the
issues
that
are
you
been
working
on.
A
A
A
Okay
next
topic,
then,
at
the
last
meeting
jerry
brought
up
that
the
nats
team
was
interested
in
getting
started
with
rook.
I
have
not
seen
yet
a
follow-up
discuss
that
so
this
will.
There
was
an
email
on
it,
but
I
think
a
couple
people
in
this
meeting
at
least
run.
So
we
can
respond
I'll,
respond
and
see
what,
when
people
see
that.
A
A
B
B
Let
me
quickly
try
to
find
the
issue
number
like.
That's
not
what
I
wanted
to
do
here.
We
go.
I
have
assigned
myself
two
issues
which,
where
are
they
come
on,
get
out?
Oh
there
we
go
and
number
1793
and
15
for
free.
B
You
don't
necessarily
need
to
go
to
them,
they're,
basically
about
us
using
a
linter,
something
like
gomez
or
with
it
generally
just
some
linter
in
general,
for
our
code
in
the
ci
and
more
or
less
as
the
ci
would
otherwise
completely
break
us
doing
anything
more
or
less
working
on
resolving
issues
like
the
license,
header
being
well,
one
line
too
close,
basically
to
the
package
package
name
line
whatever
you
want
to
call
it
and
at
missing
comments
and
such
like
that,
that's
more
or
less
what
I'm
trying
to
look
into
right
now:
okay,
it's
1793.
A
B
It's
more
like
it's
yeah,
it's
just
formatting,
basically
like
a
basic
formatting.
So
it's
not
directly
linting,
oh
well,
it
that
that's
also
limiting
to
a
certain
extent.
But
the
go
format
command
is
just
like:
hey
I'm
gonna
format.
It
right
and
I
think
to
go.
That
was
it.
That's
then,
would
shout
about
hey.
There
has
been
changes
or
something,
but
the
lintel
part
is
more
in
regards
to
that.
B
Everything
that
is
exported
has
a
comment
that
well
the
things
that
make
sense
should
have
comments
and
such
and
that's
the
comments
are
in
the
correct
format,
format
and
there's
a
bunch
of
others
like
in
the.
I
think
it
was
the
discover
package
just
variables
with
underscores
in
the
name,
but
the
variables
in
golding
should
not
have
underscores
in
their
name.
A
B
B
At
least
from
what
I
saw
most
of
them
are
basically
around
comments.
We
have
a
lot
of
com
code
where
well
not
a
lot.
I
think
it
was
just
like
600
or
something
occurrences
where
there
wasn't
a
comment
on
something
exported.
B
It's
more
or
less
one
of
the
things
that's
well,
why
not
like?
Let's
fix
it
at
least
my
virtual
studio
code,
I'm
using
with
the
go
plugin
by
default.
I'm
not
sure
I
think
you
were
using
visual
studio
code
as
well,
travis
yeah,
at
least
for
me
when
I
basically
open
well
any
file.
I
get
hey.
This
file
has
a
missing
comment
or
something
like
that,
and
you
know
why
not
just
get
rid
of
it.
Basically,
at
least
of
the
common
part
and
the
others.
B
Well,
we
would
need
to
see,
but
at
least
as
far
as
I
have
seen,
the
the
the
messages
from
the
linter,
everything
was
in
the
part
of
being
well
perfectly
reasonable
to
fix.
A
Okay,
yeah,
if
with
since
that'll,
touch
a
lot
of
source
files,
we
might
wait
a
few
more
weeks
till
we're
a
little
closer
to
1.4
to
avoid
overage
conflicts
but
yeah.
But
it
would
be
nice
to
to
improve
that
to
go
into
your
areas
for
sure.
A
Sounds
good
one
other
thing
that
came
to
mind
is
drive.
Did
you
want
to
bring
that
up
here
and
just
delay
the
status.
A
A
I
think
I
could
bring
up.
I
am
working
with
john
feyerski
pretty
closely
to
make
the
drive
groups
feature
a
reality
for
rook.
It
does
involve
stuff
changes
as
well
as
work
changes.
A
I
I
think
that
the
drive
group
support
that
rip
will
utilize
will
be
available
after
in
in
seth's,
not
the
next
release,
but
the
next
one.
The
next
release
is
intended
to
be
a
security
release.
As
far
as
I
understand,
and
so
I
I
think
it
will
be
the
15.2.5
release
of
ceph,
where
the
drive
groups
feature
is
actually
added,
and
that
may
mean
that
rook
wonderful
is
released
before
the
stuff
feature
that
that
provides.
That
really
is
the
only
like
a
kind
of
major
note
that
I
can
add.
A
A
Yeah-
and
I
guess
I
haven't
been
following
the
octopus
releases,
but
15.2.3,
I
think-
was
a
security
release,
so
dot
four
is
also
a
security
release.
I
thought
three
was
a
standard
release.
I
I
might
have
been
a
little
bit
misinformed
or
interpreted
something
wrong.
A
A
Anything
else
to
bring
up
to
the
community
hey.
I
just
put
the
the
the
issue,
the
4051,
and
this
can
we
have
a
look
at
the
progress
of
this
ticket.
A
A
Yeah,
oh,
and
did
you
just
join?
We
were
talking
about
that
a
few
minutes
ago.
Oh
I'm,
sorry,
I
got
the
meeting
double
boost.
Yeah,
that's
fine
yeah!
We
can
cover
it
again
briefly,
so
the
yeah.
We
definitely
need
to
fix
this
and
I
think
yeah
this
the
whole
discussion
about
you
know
somebody
has
a
workaround,
but
we
yep
we're
planning
on
getting
this
fixed.
I
was
commenting
on
the
so
there's
the
csi
issue,
that's
linked
from
the
rook
issue,
so
this
csisu
1003.
A
So
there's
been
some
discussion
about
about
how
that
can
happen
and
get
that
working.
So
there's
there's
still
a
question
about
whether
quay
dot
io
supports
it
for
unpaid
accounts,
which
this
csi
is
on,
but
even
if
it's
only
a
paid
account,
I
think
yeah.
We
need
to
get
it
working
because
it's
a
real,
a
real
problem.
I.