►
From YouTube: 2021-02-23 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
Is
that
probably
typical
cadence
there,
or
are
there
some
burning
issues
on
that?
One
travis.
A
B
A
All
right
and
then
yeah
1.6,
we're
still
cruising
towards
our
next
quarterly
release
for
the
end
of
march
early
april
time
frame
see
what's
what
sort
of
happenings
there
progress
since
the
last
community
meeting,
do
we
have
to
share
there.
B
A
What
are
some
of
the
buddies?
What
are
some
of
the
biggest
feature,
improvements
and
stuff
in
pacific.
D
I
wanted
to
comment
specifically
on
with
the
improvements
inside
of
blue
store.
Specifically,
I
will
say
inside
of
red
hat.
That
is
what
we're
looking
at
and
yeah
blue
store
in
general
is
going
to
help
with
the
with
rados
in
general.
It's
not
really
a
exciting
feature
in
terms,
but
I
think
people
will
see
a
slight
improvement
in
terms
of
I
o
performance.
D
But
jared
I
will
perhaps
in
the
next
community
meeting,
which
I
think
is
you
know
in
a
couple
weeks
right.
I
will
try
to
perhaps
put
together.
You
know
from
a
stuff
ether
pad
just
a
list
of
different
features
from
the
ceph
leadership
team,
in
terms
of
features
that
they
would
like
to
see
highlighted
so
that
you
know
the
general
rook
community
could
be
more
informed
about
it
and
I'll
talk
about
it
in
a
slack
thread
or
something
like
that.
A
Yeah,
that
sounds
great
yeah,
more
awareness
as
to
like,
what's
going
into
the
underlying
storage
providers,
and
you
know
the
functionality
that
would
be
available,
you
know
for
any
consumers
of
it,
no
matter
what
the
you
know,
their
distribution
or
way
that
they
deploy
it
is,
is
certainly
helpful.
Yeah,
that's
a
great
idea.
D
Yeah,
I
I
have
more
to
talk
about
in
terms
of
some
of
the
contributors
to
rick
that
I
spoke
to
at
the
work
booth
at
def
conf.
But
we
could
talk
about
that
later
in
the
meeting.
A
Yeah,
do
you
want
to
add
a
an
item
to
the
agenda
about
that
one
there
and
we'll
we
could
dive
into
that
for
sure
later
on.
That's
a
great
topic.
A
Okay,
cool
answer
anything
else
for
1.6,
then
for
features
to
highlight,
or
you
know,
obstacles
or
anything
like
that.
B
No,
I
don't
think
so,
and
just
one
more
comment
about
pacific,
I
think
when
I
think
of
when
the
question
comes
up
what's
in
pacific,
what
comes
to
my
mind
is
just
what
we're
we
need
to
expose
from
rook
from
crs
or
whatever
so
yeah.
I
know,
there's
a
lot
more
work
under
the
covers
and
improvements,
so
it'll
be
great
to
have
that
spelled
out
for
us
thanks
mike.
A
Cool
okay,
yep,
so
we're
still
working
on
you
know
towards
the
timeline,
expect
the
timeline
that
we've
been
thinking
about
there
for
the
quarterly
release,
cadence,
there's
late
march
early
april,
so
progress
is
ongoing
on
that
looks
like
a
whole
bunch
of
activity
down
here.
This
is
exciting.
A
I
like
this,
so
we'll
we'll
start
in
the
community
topics
section
now
here,
so
the
the
old,
the
old
docker
hub,
open
source
program
there
it's
been
a
bit
of
a
roller
coaster,
but
I
have
some
good
news
for
that
part,
at
least
where
they,
so
they
reject
initially
well
after
a
while,
they
rejected
our
proposal
to
our
application
to
be
part
of
the
open
source
program,
and
they
said
that
we're
the
project
is
funded
by
by
commercial
entities.
A
So
it's
not
eligible,
and
so
I
pushed
back
on
that-
and
I
you
know,
was
asking
for
details
about
that.
What
is
the
policy
you
know
where
the
cncf
owns
the
project,
the
trademark,
the
ip
all
that
sort
of
stuff
like
what's
what's
the
deal
here?
Is
that
not
a
vendor-neutral
home
for
it?
And
then
it
turns
out
that
apparently
cncf
projects
do
have.
You
know
they're
allow
listed
for
for
being
approved
here.
A
A
So
I
have
not
seen,
though,
the
official
confirmation
or,
if
there's
any
sort
of
like
you
know
like
our
profile,
getting
a
badge
or
something
like
that
like
I
have
not
heard
that,
but
the
roller
coaster
of
emotions
that
we've
been
through
years,
apparently
that
we
are
approved
and
that
once
that's
finalized
in
some
way
that
I
would
hope-
or
I
would
expect
to
no
longer
see
rate
limit
throttling
stuff
anymore.
A
C
B
C
Yeah,
if
we
get
rid
of
the
the
limit,
it
is
probably
fine.
D
So
I
spoke
to
david
galloway,
who
manages
self-infrastructure
and,
as
I
understand
now
after
these
conversations
also
that
sub
has
been
involved
with
so
ceph
has
its
own
quay
instance
that
it
has
set
up
and
which
we
are
using
for
our
own
containers
and,
as
I
understand
right
now,
that
seems
to
be
working
out
for
the
community
as
a
workaround
to
these
limits
that
are
presented
with
docker
hub.
D
So
it
was
offered
by
david
galloway
to
do
mirroring
as
well
in
this
infrastructure
and
to
provide
that
if
that
is
something
that
the
community
would
like
to
do,
we
could
explore
that
more,
and
it
would
just
be
a
matter
of
us
blooping
in
david
galloway
into
this,
and
he
can
provide
that
as
as
a
service
to
the
rook
community,
as
we
are
already
doing
with
steph.
B
D
Okay,
yeah,
you
have
to
excuse
my
ignorance,
I
I
don't
know
exactly
everything
that's
being
mirrored.
I
am
aware
that
the
stuff
community
is
using
it
as
for
amir,
so
as
a
workaround
to
this
problem
that
the
community
has
already
hit
as
well.
So
it's
just
a
you
know:
potential
as
jared
was
saying
you
know
we
could
use
it
as
another
mirror
that's
available
and
it
would
be
available
to
take
some
of
the
workload,
and
I
think
this
might
be
a
good
option.
D
You
know
not
just
from
red,
you
know
we
don't
want
it
to
just
be
red
hat.
That's
supporting
this
infrastructure.
Of
course.
It's
a
good
option
for
anybody
who
wants
to
provide
mirroring
to
the
rook
community
in
this
regard,.
B
D
Yeah
I
I
mean
I
could
say
that
this
is
coming
from
the
standpoint
that,
of
course,
we
you
know
from
the
stuff
community.
We
have
interest
in
the
success
of
the
rook.
So
this
is
something
that
I
could
work
out
on
my
end
and
get
our
you
know
person
that's
managing
our
infrastructure
involved,
so
it
doesn't
have
to
be
a
permanent
home
by
the
way,
it's
just
an
another
mirroring
option
so
to
get
us
by.
B
C
A
Cool
that
sounds
awesome,
yeah,
so
hopefully,
and
hopefully
we'll
get
some
sort
of
official.
You
know
confirmation
for,
or
you
know,
a
badge
or
something
to
confirm
in
a
more
complete
way
that
we
are
no
longer
subjected
to
the
rate
limiting
oh
blake.
A
D
Oh
go
ahead.
Oh
I'm
sorry
jared
I
mean
interrupt.
I
was
just
gonna
say
that
if
you,
I
know
that
you're
already
speaking
to
somebody
at
the
cncf,
but
I
have
multiple
people,
colleagues
who
have
left
to
the
cncf
that
are
helping
in
community
around
these
guidelines.
D
A
Awesome
mike,
I
appreciate
that
the
offer
there
you're
always
a
quite
helpful
person
mike,
I
don't
think
anyone's
ever
ever
said
that
you're
not
helpful.
D
Yeah
I
have
a
couple
of
developer
advocates
that
I
met
back
in
barcelona
that
were
president
at
cephalicon
that
have
been
interested
in
wanting
to
help
more
with
the
chef
presence,
and
so
I'm
sure
you
know
with
rook.
That's
specifically,
why?
So,
I
think,
with
that
sort
of
help,
in
terms
of
any
other
goals
that
we
may
have
in
terms
of
blockers
like
this,
I
could
share
the
actual
names
I
just
don't
have
them
in
front
of
me.
D
I
apologize
so,
but
just
people
in
the
past,
from
barcelona,
two
developer
advocates
that
I'm
thinking
of
in
particular
that
I've
been
following
so.
D
A
Blaine,
do
you
want
to
drop
your
your
google
account
email
in
the
chat
for
like
to
me
and
then
so?
I
can
copy
that
and
put
that
into
the
sharing
to
make
you
an
editor
since
you're
adding
a
lot
of
useful
stuff
here,
and
they
can
just
give
you
direct
access.
E
Cool,
so
I
was
on
mute,
sorry
yeah,
how
it's.
A
Best
to
do
that,
that's
right!
You
just
put
in
the
zoom
chat
to
me.
You
don't
have
to
put
it
to
everyone.
You
could
just
be
just
to
me
and
then
I'll
just
put
it
into
the
the
sharing
here.
A
Awesome,
all
right!
So
travis
do
you
want
to
take
the
next
couple
agenda
items
there.
B
A
Yeah,
I
didn't,
I
didn't
see
any
any
major
concerns
there.
Travis
yeah.
All
right
did
you
were
you
able
to
run
the
site
locally
to
like
to
test
it
and
make
sure
that
it's.
C
B
B
A
B
A
C
A
There
you
go
and
blaine
you
may
have
the
editor
access
now
you
might
have
to
refresh
the
page.
So
I'm
not
sure
if
it
does
it
async
or
not.
B
And
then
next
one
I
opened
the
ticket
also
a
couple
weeks
ago
for
just
realizing
that
on
our
rook
maintainers
mailing
list
for
the
cncf
we
only
had
or
we
were
missing
some
of
our
newer
maintainers,
so
everyone
so
blaine
and
seb
and
satoru,
I
think,
should
have
all
received
an
invite
said.
Did
you
see
that
seven
blame,
I
think
plain
said.
B
Good,
so
we
should
be
up
to
date
on
that
list,
thanks
yep,
just
that's
it
for
that
one
any
unless
there's
questions
all
right
and
then
outreachy
intern
coming
up.
B
E
I
guess
yeah,
I
we
talked
a
little
bit
about
reusing
the
previous
projects,
but
there's
also
been
some
work
on
those
that
might
not
make
them
the
best
for
the
new
project.
The
thing
that's
on
my
mind
has
been
kind
of
updating
the
helm
charts.
That's
been
something
on
our
heads
for
a
little
while
I
I
guess
we're
recently
learning
that
there's
a
rancher
pattern
that,
in
in
my
opinion,
I
think
this
is
not.
I
don't
think
this
is
a
good
pattern.
E
I
think
this
is
kind
of
a
smell
about
like
how
helm
doesn't
really
have
a
good
strategy
for
managing
crds.
But
rancher's
solution
to
this
is
to
make
a
pattern
that
crds
are
one
chart
and
then
operator
and
other
stuff
is
another
chart,
and
then
those
are
versioned
together
and
then
that
way
rancher
is
able
to
update
the
crds,
whereas,
like
helm,
v3's.
Most
recent
like
put
this
in
a
crds
folder,
is
not
great
because
it
only
handles
creation
of
crds
but
not
updates.
E
So
the
current
thinking
is
that
we
may
want
a
crd
chart,
an
operator
chart
and
then
a
chart
that
has
basic
resources
like
the
step
cluster
that
will
spit
out
a
a
basic
working
version
of
of
rook
for
users.
That
kind
of
expect
that,
but
to
not
go
past,
just
a
basic
working
version
and
because
we
can
rely
on
like
a
post,
renderer
and
or
the
customized
stuff
built
into
kubepetal
to
complexify
crs
yeah.
The
the
ongoing
discussion
issue
is
linked
there.
E
A
Is
is
there
any
potential
for
helm
upstream
to
add,
you
know,
updating
upgrading
functionality
for
crds?
Is
that
off
the
table
or
is
it
possible.
E
Updating
crds
can
be
like
it
can
be
damaging,
and
so
they
have
to
assume
that,
like
users
or
like
they
have
to
assume
that
the
crds
could
like
updating,
crds
could
break
stuff
with
rook's
case.
I
I
we
just.
We
try
really
hard
not
to
break
stuff,
and
the
crds
even
include
like
bug
fixes.
Sometimes,
if
there's
like
been
a
parameter
missing
or
if
we
need
to.
C
E
Right
so
I
yeah
I
mean
I
see
that
just
managing
crds
with
the
operator
is
potentially
something
that
it
isn't
broadly
recommended,
but
I
I
think
it
is
like.
E
B
B
E
Yeah,
I
think
it's
pretty
significant
to
like
reorganize
the
helm
charts
to
get
a
crd
chart
to
get
an
operator
chart
optionally
to
create
a
chart
for
the
custom
resources
to
to
tidy
those
up
and
then
also
potentially
there
is
we
can
generate.
Some
of
the
example
manifests
from
the
helm
charts
as
a
build
step.
E
Then
we
have
a
good
like
we
have
basically
the
same
user
story
that
we
have
now,
which
I
I
think
is
good
for
users
that
are
not
on
rancher,
that
or
that
don't
like
really
want
to
follow.
The
I
have
a
separate
crd
chart
from
operator
chart.
E
So
I
think,
there's
a
lot
to
do
there.
I
guess
I
have
concerns
that
users
might
be
like
hell.
I'm
like
I
can
figure
that
out
on
myself
or
whatever
I.
It
might
be
good
to
figure
out
a
project
that
is
a
little
more
in
the
vein
of
like.
B
A
D
Yeah,
the
I
don't
have
it
in
front
of
me,
I
want
to
say
it
is,
may
it
so
it's
summertime
and
winter
time
this
next
round
is
starting
in
may.
If
you
go
to
the
website,
you
can
see
the
timeline
for
both
winter
and
summer
time.
So
we
are
in
the
of
course,
going
into
the
summer
period
and
they
basically
have
this
time
period
reoccur
every
year
and
just
have
it
separated
out
got
it.
A
Got
it
yeah
cool
yeah
like
there's
a
lot
of
options
for
getting
you
know
younger
folks
and
folks,
early
in
their
careers
they're
involved
in
community
open
source
projects
like
there's
the
outreachy
stuff
that
we're
doing
here.
There's
google
summer
of
code,
the
lfx
mentorship
program
too,
that
the
cncf
linux
foundation
does
as
well
too
there's
a
lot
of
opportunities
for
that.
It's
pretty
pretty
awesome.
D
Yeah
and
I
I
would
encourage
the
rook
community
to
consider
google
summer
code
now
it
is
a
very
vetted
process
and
it
does
involve,
like
you
know,
like
somebody
filling
out
a
form,
and
it
could
be
quite
lengthy,
I
would
say,
as
opposed
to
a
lot
of
the
other
programs.
It
could
be
very
rewarding,
though
in
terms
of
what
you
could
get
out
of
it.
D
So
if
we
have
of
interest
for
the
next
round
with
google
summer
code,
that
is
definitely
something
I
can
help
coordinate
in
terms
of
the
application,
as
well
as
having
somebody
to
you
know:
vet
the
rook
community
in
for
the
first
round,
because
you
kind
of
also
it
helps
to
know
other
organizations
that
are
involved.
So
I
could
definitely
do
that
as
well,
since
we're
already
doing
great
work
in
outreachy.
D
My
mistake,
my
mistake:
yeah.
A
D
A
No
problems
yeah.
A
D
Yeah
yeah,
it
was
just
I
spoke
to
travis
for
this
round
and
it
seemed
like
we
were
skipping
out
this
time
around,
but
I
was
working
on
the
application
for
stuff,
which
you
know
we've
had
our
application
not
accepted
because
of
like
a
missing
answer
to
a
forum.
Question.
D
Your
application,
after
that,
for
missing
that
one
field,
even
though
it
wasn't
required.
So
it's
it's
interesting.
I
will
say
so.
It's
good.
If
you
know
somebody
that
knows
the
nuances
of
getting
in
like
it
just
helps.
Yeah
like
anybody
could
fill
out
the
form
it's
just
dealing
with
the
people,
I
would
say
so.
Yeah
yeah
yeah.
A
Cool
all
right
head
on
down
to
the
removing
sport
for
self
drive
groups.
E
Yeah
I'll
start
talking
about
this
travis
and
said
feel
free
to
jump
in
yeah.
So
there's
also
the
issue
link
there.
We
can
read
we're
trying
to
reach
out
to
see
if
anyone's
using
this
feature.
But
ultimately
it
is
it's
just
something.
That's
kind
of,
I
guess
stretching
us
thin
a
little
bit,
especially
with
changes
to
osds
there's
a
lot
of
code
in
there.
E
There
are
no
known
users
of
the
feature
I've
reached
out
to
a
user
that
had
mentioned
it
on
slack,
that's
not
using
it,
and
we've
also
talked.
You
talked
about
having
a
hopeful
goal
to
have
a
more
like
kubernetes
native
pvc,
only
deployment
method
by
the
end
of
the
year,
that
is
also
still
user
friendly
for
people
who
have
raw
discs,
which
means
kind
of
having
a
like
known,
working
and
recommended
procedure
for
creating
pvcs
from
raw
discs
in
an
easy
to
consume
way.
E
The
drag
groups
feature
was
added
for
the
souza
use
case,
but
with
the
souza
dev
team
kind
of
pretty
pretty
much
abandoning
ship
it,
and
I
also
reached
out
to
the
architect.
While
I
was
there
and
he's
he's
supportive
to
of
the
broader
move,
to
move
to
a
more
like
kubernetes
native
deployment
method
and
yeah
from
from
the
issue,
you
should
also
be
able
to
link
to
the
pull
request
I
opened
yesterday.
E
We
have
instructions
for
migrating
if
users
are
using
drive
groups
that,
like
don't
get
the
messages
that
we
have
put
out
on,
like
slack
and
stuff,
they
should
like
be
like
be
aware
that
it's
happening
and
they
should
like
be
able
to
read
documentation
about
how
to
how
to
migrate.
A
All
right
cool
blaine,
thanks
for
thanks
for
sharing
that
and
writing
up
the
the
thoughts
on
it
and
everything
like
that,
and
you
know
documentation
and
everything
too,
to
smooth.
A
All
right
mike,
I
got
some
t-shirts.
D
Yeah
so
finally
got
these
shirts
they've
been
printed
since
november.
We
wanted
them
to,
for
you,
know,
kubecon
a
while
back
and
I
wanted
them
for
the
for
rook
presents,
but
that
kind
of
didn't
happen.
D
So
I
want
to
be
clear,
though,
that
these
shirts
can
only
be
acquired
by
a
promo
code,
so
we
are
not
selling
these
shirts,
it's
just
purely
to
give
them
out
to
people
we
first
debuted
them
at
def
conf,
which
was
february
18th
through
the
20th
and
yeah.
It's
just.
We
want
to
be
able
to
send
out
shirts
to
all
contributors
of
rook.
That
was
original.
You
know
goal,
and
that
is
still
the
goal.
D
So
I
have
sent
some
of
you
directly
a
link
with
promo
code
and
richard
and
dave
I'll
get
you
in
there
as
well.
After
this,
with
a
link
in
promo
code
so
and
yeah,
you
can
request
a
shirt.
Free
international
shipping
takes
care
of
the
cost
as
well
so,
and
we
just
want
to
get
shirts
out
to
all
contributors.
I
will
be
doing
my
best
to
try
to
figure
out
based
on
the
list
that
I
already
have
acquired
from
the
authors
list,
sending
out
to
people
that
want
shirts.
D
That's
pretty
much
our
main
goal,
and
there
are
a
few
places.
A
few
countries
we
can't
ship
out
to
due
to
custom
loss,
local
custom
laws,
so
can't
really
work
around
that,
but
we'll
try
to
set
up
local
vendors
and
particular
countries
that
may
be
needed
as
well
based
on
demand.
D
A
That's
awesome
mike
I
like
this
and
I
like
how
to
the
like
there's
the
cool
stuff
store.
That's.
D
Awesome,
I
got
to
be
honest
with
you.
I
I
mainly
I'm
using
a
red
hat
vendor
here
and
I'm
not
really
sold
on
anything
like
this.
This
is
just
purely
to
get
people
a
form
to
a
vendor
and
get
their
address
information
to
send
out
a
shirt.
That's
about
it
and
I'm
not
sold
on
this
solution
by
any
means.
It's
just
something
to
temper
temporarily
solve
this
solution
during
a
pandemic,
I
would
say
so.
A
A
D
Oh
yeah,
I
can
definitely
help
you
in
terms
of
that,
if
you
reach
out
to
me
privately
sure-
and
we
have
a
lot
of
other
stuff
that
even
josh
burkus
puts
in
here-
that's
cncf
related,
like
I
said,
the
rook
shirts
and
the
stuff
shirts
aren't
listed
publicly
on
the
site
for
a
reason,
because
we
don't
have
the
rights
to
rook
itself.
D
We
are
just
trying
to
print
out
shirts
for
contributors,
so
I
want
to
be
clear
on
that
and
the
stuff
shirts
aren't
listed
on
there,
because
I
am
looking
for
another
vendor
to
begin
with.
So.
D
Yeah
no
problem,
so
I
just
want
people
to
know
if
you
have
contributed
to
rook
and
you
have
filled
out
a
form
for
a
shirt.
I
do
know
about
your
order
and
I
will
make
sure
you
get
a
link
and
promo
code
and
if
I
miss
you
for
some
reason,
please
let
me
know,
and
if
you
think,
somebody
in
the
community
who
hasn't
heard
about
this
needs
a
shirt
also,
let
me
know
as
well
can
definitely
help
help
them
with
that.
C
D
Yeah,
so
we
got
about
38
shirts
passed
out
from
defconf
for
this,
and
a
lot
of
people
excited
around
rook.
I
had
a
person
specifically
reaching
out
around
engagement
and
wanting
to
be
more
engaged
with
the
seth,
rato's
gateway
and
also
wanting
more
members
of
stuff
to
be
involved
with
some
of
the
work
that
they
are
doing
in
rook.
D
I
don't
have
the
person's
name
in
front
of
me,
but
I
did
make
a
note
to
follow
up
with
them
in
terms
of
making
sure
that
they
felt
like
there
was
better
presence
of
stuff
in
different
development
engagement
meetings,
since
they
seem
to
be
focusing
on.
Oh
I'm
remembering
now
there
is
a
new,
as
I
understand
new
crd,
that's
being
defined
around
object,
storage
and
they
are
focusing
on
an
initiative
around
that,
and
I
think
that
might
be
separating
things
out
from
brook
unless
rook
is
also
utilizing.
Those
crds.
B
B
Provisioning
with
yep
there
we
go
yeah
yeah,
so
that'll
be
coming
with
the
quasi
whatever
that
stands
for.
D
Yeah,
so
I
had
some
good
conversations
and
I
will
say
for
being
a
virtual
event:
it's
not
exactly
exciting
and
it
was
taking
place
on
hop
in.
However,
they
did
make
use
of
discord
as
in
a
coordination
in
conjunction
with
the
event,
and
it
worked
out
very
well
in
terms
of
people
engaging
at
the
rook
booth
and,
like
I
said,
blaine
also
was
there
to
help
out
with
some
questions,
provided
a
really
great
answer
around
longhorn
and
otherwise
yeah.
D
C
Cool
glad
that
was
a
good
experience.
Then
we
got
to
participate
in.
A
Okay
they're,
so
I
don't
see
any
more
topics
on
the
community
section
and
no
specific
pr's
to
to
go
into
that.
We
haven't
already
gone
over
previously
and
mike
to
take
an
action
item
about
the
pacific
updates.
Any
any
other
topics
that
people
wanted
to
have
in
the
agenda.