►
From YouTube: 2021-02-09 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
the
recording
has
started-
and
this
is
the
february
9th
2021
rook
community
meeting
and
so
we'll
start
off
with
our
releases
and
milestones.
We
do
not
have
anything
planned
for
1.4,
so
we'll
go
ahead
and
jump
down
to
a
1.5
patch
release
that
we
have
planned
for
later.
On
this
week,
yep
they'll.
B
A
All
right
we
can
move
on
down
to
1.6
then,
and
the
next
you
know
minor
release
technically,
but
it's
more
of
a
major
release
right
compared
to
the
patches
at
least,
but
we'll
do
semantic
versioning
talk
here.
So
it
is
a
minor
release.
Minor,
release,
minor
release.
It
is
all
right
breaking.
A
A
B
A
B
A
Is
everything?
Is
this
board
up
to
date,
for
are
there
more
items
here
that
are,
you
know,
planned,
but
are
actually
being
worked
on
right
now,.
B
A
Blaine
or
alex,
or
anybody
there
any
any
these
issues
here
that
are
actually
in
progress.
You
know.
B
B
Right
he's
I
mean
he's
doing
a
few
things
with
stephan.
That's
marrying.
I
saw
one
of
those
issues,
I'm
not
sure
if
that
particular
one
is
in
progress,
though
yeah
I'll
put
an
action
item
to
follow
up
after
this
and
clean
up
the
board.
I
started
looking
at
the
1.5
board
this
morning,
but
then
got
distracted
before
we
got
to
1.6.
A
Sounds
good
my
eyes
have
finally
gotten
or
my
brain,
I
guess,
has
finally
gotten
adjusted
to
dark
mode
on
on
github.
I've
had
it
enabled
for
like
at
least
a
month
but
transitioning
to
like
you
know,
find
like
where
the
different
links
are
where
the
buttons
are
and
stuff
like
that.
It
just
looks
like
a
different
website
now
and
it
took
me
a
month
and
I'm
finally,
finally,
navigating
it.
Okay
again,
that's
a
different
look.
You're.
Throwing
me
off
jared:
that's
why
we
don't
teach
old
dogs
new
tricks.
You
know.
D
Well,
I
found
it
out.
I
think,
like
in
the
middle
of
the
night
to
protect
it.
A
Nice,
that's
funny.
Okay,
all
right,
so
yeah
we'll
follow
up
to
make
the
get
the
board
updated
there,
but
yeah
work
is
obviously
it's
like
it's
the
about
the
middle
of
the
release
cycle
for
the
1.6
upcoming
release,
so
things
are
in
progress
and,
and
things
are,
things
are
happening
there.
Any
other
questions
on
the
milestones
themselves
before
we
move
to
the
other
topics.
A
Okay,
all
right!
Well,
let's
hop
on
into
the
community
topics.
Then
travis.
You
have
an
update
for
us
on
some
of
the
providers.
Removal,
deprecation.
B
B
So
I
have
that
action
item
still,
maybe
maybe
by
end
of
dale,
not
if
I'm
lucky.
A
C
C
C
You
and
I
have
had
topics
about
this
before
and
if
I
may
give
kind
of
two
different
scenarios
that
can
happen
here
for
rook
the
first
one
is
we
go
about
removing
these
providers
and
we
have
these
joint
booths
that
we're
planning
with
ceph,
which
I
totally
see,
is
in
alignment
with
these
plans
here,
even
as
a
person
who
serves
as
a
community
manager
for
both
seth
and
gluster
okay,
I
have
to
be
fair
here
and
and
think
about
these
other
providers,
and
if
we
go
this
direction,
it
may
in
the
long
term,
change
rooks
image.
C
If
you
will
with
the
community,
so
we
will
not
be
accepting
yeah.
We
will
be
removing
these
providers
to
the
outside
public
and
just
supporting
stuff
and
that's
what
the
scenario
will
be
there.
The
second
scenario,
though
I
don't
know
what
your
plans
are
in
terms
of
this,
but
this
is
the
one
I
would
recommend
personally
and
it
is
remove
out
these
drive
these
providers.
C
Sorry,
I
keep
saying
drivers
they're
drivers
in
my
mind
from
a
previous
project,
so
providers
you
remove
out
these
providers
and
then
you
will
end
up
with
just
that,
and
then
I
that's
the
image
and
it
rook
I
will
predict-
will
lose
what
a
lot
of
the
attention
that
it
has,
because
people
love
to
see
that
they're
not
forced
to
one
thing:
they
like
flexibility,
it's
one
of
the
number
one
things
in
both
openstack
and
stuff
user
survey
is
flexibility
of
not
lock-in.
B
You
know
what
what
does
it
mean
for
a
provider
to
be
part
of
rook,
and
so
we
yeah
we
put
together
that
that
doc
reviewed
it
together
and
it's,
I
feel,
like
the
approach,
will
be
it's
welcoming
to
storage
providers,
who
are
I'd,
say
honestly,
who
are
more
or
vendor
neutral.
So
we've
got
the.
C
B
I
mean
ceph
has
multiple
vendors
that
support
it.
We've
got
there's
an
nfs
operator.
I
still
see
that
as
staying,
because
there
is
interest
from
that
from
multiple
parties
there's
and
then
the
third
one
is
cassandra
that
is
still
there
there's
and
there's
interest
there.
B
I
I'd
like
to
get
more
interest
from
the
owners
of
cassandra,
because
they're
really
the
ones
who
know
how
how
things
work
yeah
and
yeah
so
and
that's
where
the
challenge
has
been
really.
If
the
owner
of
the
storage
provider
that
data
layer,
if
they're
not
coming
to
the
root
community
and
participating
it's
just,
it's
special
every
provider
is
specialized
enough
that
we,
as
generalists
just
haven't,
been
able
to
support
it.
C
C
C
B
C
Yeah,
that's
fine!
I
don't
want
to
spend
time
on
that,
but
I
I
just
wanted
to
give
you
the
recommendation
there
I'll
carry
out
the
plans
on
keeping
it
rook
and
stuff
for
defconf.
C
I
totally
agree
travis
you
had
this
plan
carried
out
and
ideas.
I
have
can
come
later.
That's
fine!
I
I'm
totally
in
agreement
here.
A
Yeah,
that's
yeah.
I
definitely
appreciate
the
feedback
as
well
to
mike
and
your
opinion
with
your
expertise.
You
know
in
this
kind
of
this
area
with
these
type
of
issues
before
too.
So
that's
that
is
very,
very
welcome
to
mike.
A
Yeah
travis
and
I
met
also-
was
that
last
week
travis
we
got
to
hang
out
a
bit
steering
committee
and
yeah
yeah.
We
caught
up
for
on
some
of
these
issues
as
well,
too.
You
know
talking
about
the
future
direction
and
you
know
being
being
welcoming
to
other
storage
providers,
and
you
know,
investments
that
can
or
cannot
be
made
in
terms
of
the
rook
framework
itself
and
comparison
to
more
generalized
operator
frameworks,
you're,
like
operator
framework
itself
and
operator
sorry
operator,
sdk,
controller,
runtime
stuff,
like
that.
A
A
To
you
know
be
aware
of,
and
I
think
like
the
steps
that
travis
took
to
formalize,
some
of
the
engagement
with
providers
is
is
was
was
a
good
start
there
to
be
more
to
kind
of
address
it
more
directly.
B
Yeah,
as
far
as
adding
only
go
ahead
mike
another
potential
storage
provider
is
I've
talked
to
someone
in
our
my
greater
team
about
some
the
samba
operator.
There's
some
interest,
at
least
from
our
team
anyway,
to
have
some
people
come
work
on
on
the
summer
operator,
so
we'll
see
about
rook
integration,
at
least,
but
that's
that's
another
example.
I
guess
of
a
vendor
neutral
kind
of
multiple
people
being
interested
in
it
type
of
thing.
A
Cool
all
righty,
all
right,
so
I
thought
I
had
an
action
item
last
meeting
to
follow
up
on
our
docker
hub
should
be
inherited
status
of
our
open
source
application
with
dockerco
to
follow
up
with
them,
so
I
ping
them
and
got
a
response
back,
and
they
will
apparently
be
looking
at
our
application
this
week.
A
So
I
hope
to
by
the
end
of
the
week,
get
a
response
on
them
around
if
the
application
is
approved
or
if
there
are
other
concerns
or
what
the
status
of
that
is
there,
they
did
bring
up
something
interesting
and
they
weren't
entirely
clear
on
the
exact
requirements
here,
but
they
said
that
they
wanted
to
be
making
make
sure
that
that,
in
order
to
be
approved
there,
the
project
can't
be
sponsored
by
anybody.
That's
making
money
off
of
it,
which
was
a
very
vague
requirement
there.
A
I
wasn't
sure
so
I'm
trying
to
get
more
details
from
them
on
what
are
the
exact
conditions
that
you
know
that,
because
that's
a
pretty
bro,
that's
a
very
broad
categorization
of
like
this.
You
know
so,
if
somebody's
paying
for
like
cicd
system
or
somebody
like
spawn
you
know
like
helps
like
a
booth
at
a
conference,
is
that
being
sponsored
by
a
company?
That's
making
money
off
of
it
item.
So
it's
it's
they're
very.
A
There
was
like
a
one
sentence
thing
and
it
seemed
like
it
was
really
open-ended
that
they
could
potentially
deny
applications
with
minimal
no
jurisdiction.
I
don't
know
but
yeah.
So
it's
it's
that's.
That
is
one
open,
open
thing
here
to
be
worried
about
or
be
aware
of,
at
least
as
they're.
Looking
at
the
application.
D
Yeah
like,
for
example,
at
least
for
I
understand
it,
would
be
something
like,
oh
well.
For
example,
claudica
like
we
have
customers
using
rook
and
we
support
them
with
rook
ceph
or
like
even
read
it
or
in
similar
ways
with
the
upstream
product
like,
let's
see
what
they're
going
to
say,.
A
C
I
think
that
this
is
really
creates
a
bad
effect
in
open
source
projects
in
general.
It
might
lead
open
source
projects
to
create
a
flood
of
foundations
that
are
unbiased.
That,
then,
can
accept
the
money.
A
A
Yeah
one
second,
I
can
get
you
mike
who
responded
to
my
application
request.
Let's
see.
C
A
Yeah,
I
know
your
involvement
is
super
appreciated,
mike
no
yeah,
absolutely
man.
This
is
and
I'll
put
this
in
the
agenda
doc
here.
Contact
info
that
we're
working
with
here
is
william
quiviger.
A
The
application
request
they
had
an
official
form
that
I
filled
out
in
october
or
something
a
while
ago,
and
then
I
I
poked
them
just
it's
as
an
action
item
from
the
last
community
meeting.
So
within
the
last
two
weeks,
and
then
they
said
that
you
know
thank
you
for
following
up
we'll
look
at
it
and
we'll
be
getting
to
it
next
week,
which
was
this
week.
C
I
honestly
jared,
I
would
spend
it
to
them
exactly
the
argument
I
told
you
just
like
you're
gonna
create
a
flood
of
foundations,
because
there's
passionate
open
source
projects,
they're
gonna
figure
out
a
way
to
how
to
be
part
of
the
program.
That's
all
it's!
It's
actually
irresponsible
on
their
side
of
not
thinking
of
consequences.
Here
there
are
articles
written
about
people
against
the
idea
of
open
source
projects.
Creating
these
flood
of
foundations.
Do
you
need
a
foundation?
Probably
not
so.
B
D
It's
I
like,
I
think
I
had
mentioned
it
last
time,
like
I
don't
think
well,
people
are
going
to
be
too
affected
by
that
there's,
at
least
like
I
don't
know,
I
think,
like
every
company
I've
been
to
was
like
yeah,
we
have
a
registry
to
cash
images
or
something
from
the
outside
world
like
that,
not
just
like
docker
hub.
D
D
Yeah
like
just
to
maybe
throw
a
bit
more
of
like
maybe
not
necessarily
like
the
point
of
hey
we're
open
source
in
there,
but
you
know
having
the
repository
that
the
registry
there
for
the
image
with
like
200
million
pulse
is
like
the
hey
look.
The
image
is
being
used.
Kind
of
you
know
like
it's
yeah.
Well,
let's
see,
let's
see
what
comes
out
of
it.
A
D
D
A
Okay,
cool
travis.
Do
you
want
to
give
us
an
update
on
our
conversation
with
amy
yesterday
and
the
kubecon
maintainer
track.
B
Yep
we
met
with
amy
yesterday
and
she
pointed
out
that
we
were
overdue
for
submitting
our
maintainer
track
sessions,
like
oh,
missed
that
email
right
after
the
holidays,
so
we
are
able
still
to
get
that
in.
I
just
need
to
get
her
the
speaker
info
and
looks
like
our
four
speakers
will
be
myself:
seb,
blaine
and
satoru,
and
thanks
alex
for
giving
up
the
position.
You've.
You've
you've
had
for
so
long
on
that
that
as
well,
so.
D
B
D
B
A
B
A
A
Yeah
all
right,
stillbot.
B
And
stillbot
just
evolved
from
our
last
meeting,
it
is
enabled
and
working
again
and
it's
actually
happening
happening
at
noon.
Pacific,
I'm
sure
you're
all
noticing
the
flood
of
emails
around
that
time,
but
it
has
caught
up
and
calmed
down
anyway.
I
think
it's
all
good.
Just
let
me
know
if
you
see
any
issues
or
have
any
other
thoughts
on
parameters.
We
should
give
it.
A
A
A
Okay
and
then
just
a
final
note
on
this-
that
the
buckets
for
our
charts
and
binaries
were
migrated
over
successfully
a
while
a
little
bit
ago.
We
did
the
1.5.6
release
that
successfully
used
the
new
targets
and
buckets.
So
we
with
a
successful
release
behind
us
or
under
our
belts.
There
we
went
ahead
and
decommissioned
deleted
the
old
buckets
with
all
that
content
from
the
upbounds
aws
account,
so
that's
completely
cleaned
up
and
the
migration
is
complete.
Now
I
think,
there's
no
more
follow-ups
on
this.
A
A
All
right,
nice,
okay,
any
other
topics
for
community
topics
or
prs
to
discuss
or
anything
like
that.
A
Well,
we've
got
a
two
action
items
here
that
travis
will
be
following
up
on
and
actually
let's
go
ahead
and
make
sure
that
that
one
is
on
there
too.
A
Uh-Huh
lucky
number
track
information
all
right,
yep
and
make
a
nice
nice
even
through
here,
cool
okay.
So
that's
all
the
action
items
that
we'll
follow
up
on
and
if
there
are
no
more
items
for
discussion,
then
we
can
go
ahead
and
break
off
for
the
for
the
week.