►
From YouTube: 2020-01-28 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
January
28th
2020
rook
community
meeting
and
we'll
start
as
usual
on
our
milestone.
Checkups
I
know
I
think
was
right.
After
the
last
community
meeting,
we
did
both
a
1.1
release
and
a
1.2
patch
release
as
well.
I
think
was
1.1.2
got
two
and
one
dot
1.9,
maybe
as
yep,
so
I
don't
Travis
or
there
is
there
anymore
one
dot
ones
that
you're
aware
of,
or
is
the
ninth
packs
they're
kind
of
the
end
of
the
line
for
right
now,
all
right.
B
I
wasn't
planning
on
anymore
last
week.
I
think
I
saw
one
merged,
her
back
board
to
1.1.
I
came
over
with
that
one
said:
do
you
remember
which
one
that
was
or
am
I
thinking
of
the
wrong
thing
here,
but
I?
Don't
know
that
yeah
I
don't
know
if
we
need
to
do
a
release
for
that
or
or
what
the
need
was
for
that
one.
C
C
A
B
B
So
there's
a
PR
open.
That's
about
ready
for
merge
that
Mahdi
was
working
on
he's
not
in
this
meeting,
but
the
thought
is
in
master
will
make
CSI
I,
know
the
default
and
then,
when
we
back
port
it
to
1.2,
we'll
make
it
available
or
simple
to
enable,
but
the
default
will
still
be
the
previous
version
of
CSI
s,
FCS
I,
just
because
it's
such
a
big
update
to
do
in
a
patch
release
and
the
patch
release
also
requires
our
back
changes
so
for
patch
releases.
B
C
A
B
A
A
A
Let's
I
have
a
whole
section.
A
B
B
A
A
B
A
A
B
A
A
B
Definitely
so
the
overall.
The
thought
is
that
so
that
we
have
this
experience
committee,
where
the
steering
committee
is
the
overall
project
direction,
not
at
the
specific
storage
provider
level,
but
really
at
the
project
that
were
like
what
do
we
want
to
accomplish
long
term
with
the
project
type
of
questions
like
probably
discuss,
and
what
does
it
mean
to
add
new
storage
providers?
How
should
we
factor
things
out,
so
other
storage
providers
can
be
added
eat
more.
C
B
Or
a
separate
repos
or
whatever,
that
doesn't
the
details
of
that.
Don't
need
to
be
worked
out
by
the
steering
committee,
but
that's
just
an
example
of
something
that
steering
community
could
vote
on
potentially
as
project
direction.
The
and
then
we
would
have
project
maintainer
x',
which
basically
we'd
be
expanding.
Our
maintainer
definition
from
what
it
is
today
to
include
storage
provider,
maintainer
x'.
B
A
A
Part
of
it
yeah
yeah
and
then
another
big
change.
There,
too,
is
that
you
know
currently
with
the
conflict
resolution
and
voting
process
for
the
project,
which
I
think
we've
only
used
like
one
time
or
either
to
win
to
add
or
remove
maintainer
Zoar
people
will
push
access.
So
it's
not.
You
know
it's
not
a
heavily
contested
or
you
know,
a
lots
of
conflicts
in
the
project.
So
it's
not
a
process.
A
It
has
to
get
used
very
often,
but
a
big
change
to
it,
though,
is
that
the
that
we
had
a
concept
of
senior
maintainer,
x'
and
standard
maintainer
x'.
Then
you
know
senior
maintainers,
head
up
voting
to
votes
and
regular
standard
maintainers
had
only
one
vote,
but
we're
doing
away
with
that
and
that
the
steering
committee,
everyone
that
who
has
a
seat
on
the
steering
committee,
gets
a
single
vote.
So
it's
a
little
bit
less
complicated
and
a
little
bit
more
balanced
of
the
decision-making
process
across
all
representatives
of
the
project.
B
B
A
A
B
A
Cool
sounds
good,
great
work,
though
Travis,
okay
and
then
CI
bags.
It's
not
really
much
update
on
that
one,
but
you
know
there's
not
a
whole
lot
left
on.
It
is
well-
and
it's
mostly
around
security
stuff,
which
we
did
a
big
push
for
with
the
disclosure
process
and
the
audit
so
I
think
we'll
be
in
good
shape,
but
that
one
production
testimonials.
We
have
sent
out.
A
Know
I'm
not
sure
because
I
just
created
it
with
Survey,
Monkey
and
I,
don't
I
don't
have
an
act
like
a
paid
plane
or
anything
like
that.
So
I
don't
know
it
might
have
been
not
the
best
decision
and
I
apologize
for
that.
But
I
don't
know
if
I'd
share
access
to
it
because
it's
you
know
just
a
free
thing:
oh
yeah,
pink.
A
I
can
see
them
all
and
maybe
I
can
try
to
get
you
access
or
like
give
you
the
password
or
something
to
it.
That's
the
only
I.
Don't
you
know
it's
my
personal
account
but
I,
don't
you
know
I'm,
not
creating
a
whole
bunch
of
personal
survey,
monkey
surveys
and
sending
them
out
to
people
that
I
need
to
keep
so
that.
A
Cool
and
then
we
sponsor
so
getting
sponsorship
from
the
technical
oversight
committee
member,
you
know
we
needed
one
sponsor
jumping
to
this
rice
and
Alexis
Richardson
are
all
leaving
their
term
is
up
I
think
tomorrow
and
the
29th
there
so
we'll
be
getting
three
new
members
on
the
TOC.
There
is
a
maintainer
voting
that
is
ongoing
right
now.
So
if
you
are
a
official
maintainer
of
a
CN
CF
project,
you
are
allowed
to
vote
for
the
next
toc
member
and
I.
A
Don't
know
Alexander
in
Travis,
if
you
guys
have
already
done
this,
but
Bassam
and
I
did
it
yesterday,
but
you
can
vote
for
the
next
TOC
member
by
sending
an
email
to
this.
This
list
here,
correct
I
have
not
done
my
cool
and
then
ashamedly
is
Bassam.
He's
Alibaba
I
can't
read
director
of
camera
rig.
Actually
what
his
position
is
at
Alibaba,
but
Bassam
mentioned
him
as
a
good
potential
as
a
sponsor,
and
he
teaching
is
not
leaving
the
position
right
now
he's
and
he's
already
elected.
A
A
A
Okay,
then
we
got
to
present
all
that
stuff.
So
you
know
we've
been
ramping
up
on
this,
we're
spending
more
time
on
it
and
we
need
to
continue
continue
doing
that.
So
you
know
this
week
we'll
make
another
push
and
try
to
follow
up
on
all
these
things
here
and
keep
keep
moving
forward
and
with
the
goal
of
having
approval
before
if
right,.
B
B
B
A
A
We
I
think
some
people
are
mentioning
some
ideas,
but
I
don't
think
anyone
has
written
up
proposals
for
them
yet
so,
if,
if
anyone
has
you
know
a
project
idea
that
they
would
love
to
get
a
you
know,
google
Summer
of
Code
participant
to
university
students
to
spend
their
time.
You
know
two
to
three
months
over
the
summer,
working
on
and
gaining
invest
in
Ciroc
community.
A
You
know,
let's
follow
up
together
and
get
a
proposal
put
together
for
that.
The
last
two
years
have
been
very
successful
with
that
with
with
you
know,
creating
the
NFS
operator
and
doing
multi-home
networking.
So
it's
always
been
a
really
valuable
and
rewarding
program
to
participate
in
and
well.
If
we
want
to
do
it
again
and
we
have
good
ideas
for
it.
The
due
date
is
by
next
week
for
very
fast.
A
So
this
is
a
topic:
I
wanted
to
bring
up
because
I
a
bit
confused
about
it,
honestly,
so
rook
dot
IO.
You
know
the
main
mic
marketing
documentation
site
here
with
our
awesome,
graphics
and
everything.
It's
currently
it's
a
host
about
github
pages.
So
you
know
you
check
things
into
the
github
repo
and
then
that
you
know
hosts
a
static
site
right
there.
A
A
Myself
personally,
and
so
maybe
somebody
has
some
more
history
here-
is
why
the
where
this
issue
came
from
what
was
the
original
justification
for
moving
the
whole
rocket
that
IO
site
to
be
hosted
and
metal
if
I,
when
it
was
opened,
there
was
no
description
and
there's
no
justification
on
it,
so
I'm
not
sure,
really
why
this
needs
to
be
done,
or
if
this
is
an
investment
we
really
need
to
make
Travis.
Do
you
have
a
memory
of
why
this
is
needed?
No.
B
C
B
A
A
We
needed
yeah
yeah
because
I,
because
Luke
Luke
Perkins
has
been
talking
about
you
know.
The
site
itself
is
he's,
got
a
fork
of
rock
Donoho's
website
and
it's
running
up
on
net
Liffe.
I
itself.
So
you
know
this
is
Brooke.
I
identify
calm,
and
this
is
you
know
the
regular
roof
that
I.
Oh,
so
there's
been
an
effort
to
create
you
know,
post
the
entire
site
over
nullify
and
I.
Just
don't
understand
why?
Well,
where
that
motivation
came
from
it's.
C
C
A
Yeah
I
think
we
should
follow
our
proof.
Okay,
okay,
I,
don't
know
who
is
Luke
and
he
said
he's
with
the
CN
CF
I
think
he's
one
of
they're
either
a
developer
our
IT
guy
over
there,
but
he
sees
contributor
to
the
rift
on
our
site.
He's
contributed
some
other
fixes
with
you
know,
icons
and
links
and
stuff
like
that:
okay,
okay,
cool,
so
we'll
follow
up
and
figure
out.
A
If
that
really
is
necessary
or
not
that,
but
we
all
the
Brooks,
maintainer
team
does
have
access
to
manage
the
DNS
records
that
are
hosted
in
notify.
So
that
is
something
that
we
already
can
do
and
had
to
do
to
get
the
cert
renewed
again
and
get
into
good
standing
so
that
we
don't
expire
and
lose
our
SSL
capabilities
on
Friday
Jared.
Yes,.
C
A
B
A
The
Brit,
so
we
have
Auto
renewal,
set
up
with
Amazon
cert
manager,
so
a
pound
is
paying
for
the
certificate,
and
so
we
had
that
Amazon
cert
manager
with
our
app
found
account
doing
an
auto
renewal,
but
the
DNS
was
messed
up
so
that
it
couldn't.
You
know,
goats,
find
the
right
place
to
do
a
renewal
of
it
automatically
and
so
we're
getting
notifications.
Or
you
know
we
are
saying
they
can't
do
it
and
if
the
certificate
is
going
to
expire,
so
we
updated
the
DNS
so
that
it'll
automatically
do
it
for
next
year.
A
B
B
B
A
B
A
A
C
C
C
A
C
Basically,
we
were
removing
support
for
a
bunch
of
things.
Mainly,
oh,
is
these
running
on
directories
and
as
part
of
that,
OSD
is
also
that
are
running
file,
store,
I,
think
that's
something
that
hasn't
been
done.
Anyways,
because
volume
has
always
defaulted
to
blue
store,
so
I
don't
think
there
are
a
bunch
of
people
that
changed
that
value
to
from
blue
store
to
to
fight
storm
because
well
we
there
is
no
real
benefit
of
doing
this.
C
So
it's
not
actually
a
breaking
change
at
this
point,
meaning
that
once
you're
great
to
1/3
all
of
your
always
these
deployment
will
keep
on
running
and
simply
because
the
filtering
mechanism
now
is
based
on
block
devices
and
if,
even
if
you
pass
a
directory
this,
this
won't
be
accepted,
and
this
won't
be
interpreted.
So
once
the
preper
job
looks
at
looks,
looks
at
the
OSD
store
deployed,
then
it
will
basically
do
nothing
for
the
OS.
These
are
actually
running
at
this
point.
C
Also,
we
don't
remove
always
these
anymore,
so
no
chances
that
we
will
end
up
into
a
weird
condition
where
these
are
removable
dramatically.
So
once
we
pull
a
grid
to
1/3.
If
they
have
always
these
running
on
directories,
then
those
oysters
will
continue
to
work,
because
that
deployment
will
never
be
upgraded.
It's
now,
it's
really
outside
of
Brookes
control.
So
it's
a
I
think
it's
a
good
thing
as
a
transition
path.
Also
with
that
patch
we
introduced
white
was
introduced
before
and
backwards
1
2.
It's
already
mentioned
in
that.
C
A
C
We
could
translates
that
into
a
blog
post.
We
discussed
that
during
the
last
community
meeting.
So
if
that's
something
that
everyone
still
agrees
on
then
I
can
I
can
translate
that
into
into
a
blog
post
to
draft,
and
then
we
can
publish
it
so
that
people
are
aware
of
the
biggest
the
biggest
change
of
book
one
three.
But
if
we
believe
that's
enough,
then
we
can
keep
it.
As
is
it's
up
to
you,
I
think
and.
B
I
think
there
are
a
few
things
in
my
mind.
We
can
do
so
there's
the
upgrade
guide,
of
course,
will
include
instructions
on
how
to
deal
with
this,
because
clearly,
during
upgrade
that
1.3
they'll
be
impacted
and
then
also
after
the
the
staff
release
comes
out
with
the
partition,
support,
I
think
we
should
get
the
word
out
or
in
the
1.2
documentation
or
as
how
people
can
start
transitioning
even
before
the
1.3
upgrade,
especially
since
yeah
well
after
you
upgrade
there's
no
more
support
for
the
directories
right
del.
C
B
So
the
yeah
we
need
to
get
that
into
1.2
documentation
as
soon
as
partition
supports
available
I.
Think
that's
the
right
timeline,
otherwise,
yeah
blog
post
would
help
after
it's
possible
to
point
people
at
it
or
if
we
just
have
it
in
the
documentation,
maybe
we
don't
need
the
dog
blog
post.
I,
don't
know
yet
we
can
think
about.
A
A
And
the
PR
that
we
had
today
that
I
had
added
here
to
discuss,
we
already
addressed
in
the
graduation
section,
so
that
is
open
for
anyone's
comments
or
feedback
on
that
one,
and
so
with
that,
I
will
open
the
floor
here.
If
there's
any
other
topics
of
conversation
that
anybody
else
wanted
to
bring
up
before
we
adjourn
for
the
week
here.
B
C
B
C
A
B
C
Yeah
I
guess
we've,
but
we
can
have
if
we
have
a
mechanism
already
in
place
for
first,
then,
that's
that's
perfect.
So
if
we
can
increase
that
worker
count,
when
many
things
are
happening
in
parallel,
typically
before
releases
stuff,
like
that,
your
motherf
ers,
that
we
run
the
backports
requires
see
I
run
time.
So
now
we
have,
we
were
testings
we're
doing
backwards,
4
1,
1,
&,
4,
1
2
as
well,
and
soon
4,
1
3.