►
From YouTube: 2019-04-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
Okay,
the
recording
has
started
this
is
the
April
23rd
2019
Brook
community
meeting
and
the
biggest
topic
for
today
will
be
the
zero
I
started,
the
1.0
release.
We
had
targeted
this
week
to
get
that
release
out.
So
we
need
to
do
a
check
and
see
where
we
are.
My
first
concern
was
around
their
release:
convergence
and
how
we
all
stay
on
the
same
page.
So
I'm
going
to
talk
about
that
before
we
get
into
the
specifics
of
the
release.
A
I've
seen,
you
know
a
number
of
side
conversations
amongst
different
audiences,
about
the
release
and
what's
left
and
all
that
sort
of
stuff,
so
being
able
to
have
a
more
cohesive
and
converged
discussion
about
the
release,
and
you
know
the
tasks,
assignments,
expectations
and
all
that
I
think
is
probably
going
to
be
very
important.
Instead
of
people,
you
know
working
more
siloed,
so
I
think
we're
kind
of
getting
to
a
point
where
you
know
we
have
enough
moving
parts
in
enough.
A
You
know
independent
storage
provider
teams
with
their
own
commits
and
stuff
that
we
kind
of
I
think
we
need
to
do
a
better
job
here
of
maybe
having
like
a
release.
You
know,
committee
or
some
sort
of
group.
That's
focused
on
the
high-level
tasks
or
responsibilities
for
the
release
and
kind
of
tracking
that
all
in
a
single
place
that
the
entire
community
can
keep
up
to
date
with
it
and
have
everything
in
one
place.
B
Definitely
agree
on
that
because
it's
like
you
know
we
in
the
silos
of
storage
providers.
It's
like,
we
know,
don't
really
have
visibility
or
we
haven't
really
communicated
besides
here
and
a
community
meeting
as
far
as
what's
going
on
across
them.
So
if
we're
getting
ready
for
a
release,
that's
yeah.
We
should
have
something.
The
tracks
that
communicates
it
richer.
A
Yeah
I'm
not
sure
you
know
one
place,
one
possibility
could
be.
You
know
a
dedicated
slack
channel
for
the
release.
That
could
be
one
thing
or
sharedoc
or
something
that
you
know.
We
were
tracking
everything
more
appropriately,
I'm
sure,
there's
better
ideas
is
well
yeah.
I
think
that
there
is
a
need
for
it,
though
I
mean.
B
We
do
have
the
release
board
the
github
board
that,
where
we're
supposed
to
track
things
as
far
as
what's
left
further
release
and
if
we
that
the
project
board
or
word
yoga
so
if
we'd
just
stayed
on
top
of
that,
it
would
be
more
clear
what
state
things
are
in,
although
it
doesn't
really
represent
how
long
it'll
take
to
get
some
done.
Yeah.
A
I
think
that
you
know
we
pretty
much
exclusively
only
track
code
changes
and
there
and
there's
a
number
of
tasks
that
you
know
do
not
result
in
a
change
to
the
rook
rook
repo.
You
know
like
the
blog
post
or
updating
the
CNC
f,
you
know
page
or
you
know,
marketing
efforts
er.
You
know
all
that
sort
of
stuff.
B
A
You
know
that
since
they
have
an
entirely
remotely
distributed
workforce
like
everything
gets
captured
in
an
issue
and
that's
kind
of
the
you
know
persisted
means
of
capturing
all
the
discussions
and
information,
so
that
has
some
merit
in
terms
of
at
least
note
having
a
single
place
to
go
to
to
get
the
latest
updates
and
not
have
to
crawl
through
slack
channels
or
other
external
sources.
Potentially
it's
not
you
know.
A
B
A
B
A
So,
let's,
let's
actually
start
looking
at
that
project
board
right
now,
alright,
so
you
know
this
won't,
have
the
items
for
you
know
the
external
stuff
like
like
non
code
changes,
but
we'll
talk,
we'll
talk
through
those
in
a
little
bit.
So
let's
talk
about
code
changes
right
now,
so
Travis
do
want
to
start
with
blocking
items
or
things
that
are
left
for
Saif
yeah.
B
B
A
A
You
know
Brook
repo
just
this
morning
and
had
you
know
dead,
all
the
114
stuff
and
you
know
doing
like
I'll,
make
a
disk
clean
to
get
rid
of
all
the
images
and
all
the
vendors
stuff
and
then
to
a
make
vendor
I
was
I,
was
finding
some
dependency
failures,
some
dependency
solving
failures
from
depth,
which
I
don't
think
we're
seeing
on
Jenkins,
so
I,
don't
know,
what's
quite
to
make.
That
and
I
was
wondering
if
anybody
else
had
seen
that.
B
A
Your
vendor
directory,
even
yeah
I,
did
yeah
I
did
make
this
clean,
cleans
up
the
entire
Pender
directory,
all
the
stale
images
and
and
even
gets
rid
of
the
DEP
tool
yeah.
That
should
be
pretty
thorough,
so
I
guess,
okay,
so
you
haven't
seen
that
they
don't
have
to
have
to
keep
looking
into
that.
I
am
my
priority.
Also.
A
B
B
B
But
it's
not
a
super
simple
issue:
either
that's
the
biggest
risk
in
my
mind.
There's
then
a
couple
of
other
issues:
I
was
working
on
the
self-signed.
Cert
hang
for
the
dashboard
are
actually
in
the
1.8
patch
release
that
column
I'll
skip
over
that
because
we
decided
that
those
could
wait
until
a
patch
release
if
we
need
to
which
I
think
I
like
that
column.
So
we
can
separate
what's
blocking
right
now
for
one
that
oversees
could
wait
to
a
patch
release.
Yeah
I
see
that
okay
yeah.
B
Yes,
so
then,
in
the
first
column,
now
I
just
added
30
29
to
the
one
auto
release
where
we're
detecting
RBD
devices
to
trigger
and
orchestration
I
think
that'll
be
a
simple
fix,
but
you
know,
and
I
are
going
to
talk
about
that
more
and
it
could
be
a
patch
release.
I
guess
what
I'm
saying
but
I'd
like
to
get
it
in
one
data
as
well.
If
it's
simple
and
then
2945.
B
May
need
to
wait
for
her
patch
release,
but
it's
kind
of
a
blocker
for
rgw.
If
you,
if
you
try
and
with
the
one
dot
operator
which
is
based
on
Nautilus,
if
you
try
and
configure
a
mimic
cluster
with
rgw,
it
basically
fails
and
sets
it
up
incorrectly
because
of
a
compatibility
issue
there
between
versions,
so
I'm
gonna
work
on
that
one
today,
that's
my
gonna,
be
my
focus,
among
other
things,
a
better
idea
if
it
needs
to
wait
for
a
patch
release
or
get
it
in
for
the
release.
B
Actually,
one
more
I'll
commented
on
3014
in
that
to
do
column,
it's
actually
there's
a
PR
in
progress
to
fix
this,
which
would
not
be
aggressive
about
setting
no
out.
When
any
note
is
in
maintenance,
it
would
require
a
specific,
specific
taint,
so
yeah
Blaine.
If
you
could
look
at
that,
one
that'd
be
great
when
you
get
caught
up
and
then.
A
C
C
A
C
A
C
C
D
A
Was
gonna
say
that
it
sounds
like
with
the
tight
timelines
in
potential
here
that
I
would
call
this.
You
know
not
critical
for
one
meadow
and
I
would
I
would
push
this
one
out.
I
think.
A
You
know
what
we
are
calling
like
what
we
wanted
to
do
for
patches
and-
and
you
know
what
what
criteria
we
use
to
you
back
for
things
and
in
sin.
Those
include
those
in
you
know
patch
releases,
but
I
think
that
parking
it
here
now
at
least
will
give
us
the
I
think
you
know
we
can
kind
of
have
this
as
a
bit
of
a
parking
lot
for
issues
that
we
we
know,
we
don't
want
to
block
the
1.0
release,
but
you
know
then
we'll
be
able
to
either
opportunistically
get
them
in.
A
C
A
Alrighty,
okay,
so
is
anyone
from
manifest
here
it
doesn't
look
like
the
edge
of
fest,
guys
excuse
me
were
able
to
join.
We
had
taken
a
look
at
their
transition
to
beta
and
I.
Think
part
of
the
initial
feedback.
There
was
some
sort
of
migration
support,
or
an
upgrade
support
for
existing
users
that
have
already
had
deployed
edge,
FS
and
I
think
that
they
I
remember
that
they
incorporated
in,
like
a
manual
upgrade
guide,
which
I
think
is
is
perfectly
fine
for
me.
Alexandra.
A
B
A
Okay,
so
we'll
follow
up
with
them
on
that
I
know.
This
I
know
that
this
was
definitely
an
important
item
on
d'etre
fesses
list
for
for
getting
into
one
dot.
Oh
so
the
transition
to
beta.
So
that's
up
that
they
would
be
able
to
follow
up
on
its
shortly.
Okay.
What
else
do
we
have
here?
These
are
all
ones
that
we
talked
through
talk
through.
A
Those
I
think
the
only
other
one
that
I
I
was
interested
in
is
that
we
have
a
this
pull
request
already
open
for
adding
dynamic
permissioning
to
NFS
and
I
would
love
to
see
that
in
the
milestone
included.
Since
it's
already,
you
know
we're
converging
towards
wrapping
up
that
pull
request.
So
I
just
added
some
more
comments
this
morning
and
and
I
would
love
if
Rohan.
If
you
could
take
another
look
at
the
functionality
here,
because
the
she
should
added
some
as
she's
shown,
the
call
I,
don't
think
so.
If.
A
A
Right,
you're
right,
cool
yeah,
that's
it
that's
I
would
love
to
get
this
in
one
dad.
Oh,
so,
let's,
let's
focus
on
driving
that
one
to
completion.
Yep
awesome
thanks,
Rohan,
okay,
so
that
looks
like
everything
on
the
board
there.
We
don't
look
to
be
in
terrible
shape.
I
think
that
you
know
we
don't
have
like
a
column
full
that
you
know
and
the
to
do
or
anything
like
that.
So
we've
got
a
couple.
Long
poles
for
Saif
upgrade.
We
don't
have
an
updated
status
on
edge
of
s.
A
A
Let's
talk
through
the
rest
of
these
first
Travis
sure
going
to
order
buddy,
see
see
this
is
come
on,
come
on
order
order.
I
will
have
order
in
my
meetings
all
right,
so
so
the
other
things
we
need
to
do
outside
of
the
code
base
are,
we
are.
We
need
a
blog
post
update
for
one
dot,
Oh
for
the
rodeo
blog
and
the
CNC.
A
We
finished
that
and
you
know,
start
integrating
and
feedback
and
all
that
stuff,
and
then
we
give
the
CN
CF
a
you,
know,
kind
of
a
smaller,
more
streamlined
version
of
that
that
then
links
over
to
our
blog,
the
CNC
F
I
think
needs
a
couple
days
of
lead
time
which
we
and
we
haven't
even
started
this
blog
post.
So
this
is
absolutely
a
risk
and
a
concern.
That's
you
know,
starting
to
hold
up
the
release.
A
A
Yeah,
exactly
so
and
I
think
that,
having
a
good
understanding
of
the
big
features
here,
I,
don't
think
we
like
we
have
you
know,
maybe
depending
release
notes,
might
be
a
good
start
of
that,
but
you
know
for
each
storage
provider
having
a
good
idea
of
what
the
the
highlights
are.
The
things
that
we
want
to
show
off
in
the
blog,
though,
is
a
focus
on
the
blog
post
is
gonna,
be
really
really
useful
there.
This
is
there
anybody
who
is
already
very
excited
about
the
opportunity
to
write
this
blog
post,
I'd.
A
Yeah
well
yeah:
let's
let's
talk
about
that
together,
then
Bassam,
maybe
you
maybe
we
can
put
our
heads
together
on
that
one.
Then,
okay,
cool.
A
All
right
and
then
the
we
need
to
update
the
CNC
F
cube
Khan's
keynote.
They
do
project
updates
for
all
the
CNCs
projects,
and
so
we
need
to
pass
that
over
to
I.
Think
Bryan
Liles
is
who
needs
that
and
that's
that'll
be
fairly
simple.
After
we've
done
the
blog
post,
I,
don't
just
get
I
can
pull
it
up
list
so
not
worrying
about
that.
One.
A
The
we're
trying
to
update
the
rook
that
I/o
website
and
Stephen
is
one
of
our
co-workers
that
upbound
has
started
working
on
this
and
I
saw
some
great
progress
last
week
about
pulling
that
all
together.
Stephen
do
you
have
an
update
on
you
know,
what's
left
for
updating
the
website
or
what
are
some
like
coordination
that
you
need
from
other
folks
in
the
community
yeah.
D
A
Do
you
do
you
want
to
go
ahead
and
open
like
a
work-in-progress
pull
request,
so
we
can
start
reviewing
the
changes
and
getting
feedback
in
because
yeah
that's
not
necessarily
dependent
on
the
final
copy
and
stuff.
So
if
you
can
get
a
pull
request
open
and
send
a
link
out
to
the
Brooke
slack,
then
that
would
be
great
to
get
some
start
getting
some
eyeballs
on
reviewing
that
yeah.
Absolutely.
D
A
Yeah,
it's
actually
pretty
pretty
slick
I
really
like
the
design
and
I
saw
I
saw
Steven,
give
a
demo
of
it
and
it
looked
it
looked
at
Lee
cool,
so
the
the
I
was
I
told
Steven.
That
I
would
get
some
recordings
of
that
terminal
output.
The
the
interesting
thing
for
that,
though,
and
I
need
to
look
into
this,
or
maybe
somebody
already
has
some
expertise
on
it.
The
the
you
know,
the
ASCII
I
have
no
idea
how
to
pronounce
that
damn
word
so
I
just
got.
D
A
Is
that
you
know
it
records
like
the
straight
output
from
your
terminal
prompt
in
you
know,
in
the
limited
space
on
the
website.
You
know
we
want
it
to
just
be,
like
you
know,
to
create
a
deployment.
You
know,
Brooke
ready,
blah
blah
what
it
like
very
simple
output,
but
the
in
reality
our
deployment
scripts.
D
Yeah
I'm
glad
brought
that
up,
so
you
can
actually
modify
when
it
doesn't
recording
a
basically
just
outputs
into
a
JSON
file,
and
you
can
modify
that
after
the
fact
and
just
remove
the
lines
that
you
don't
care
about.
So
the
one
that's
currently
on
my
staging
site
that
I
set
up
I
I
modify
already
because
it
had
some
some
output
that
wasn't
going
to
fit
in
that
area.
D
So
I
just
deleted
that
whole
section
out
of
the
JSON
file,
and
then
you
just
have
to
like
tweak
the
timing
of
the
file
itself,
because
it
has
some
variables
in
it
to
determine
how
long
it
should
actually
play
for.
But
you
can
actually
modify
those
after
the
fact.
Another
option
is.
We
could
probably
build
those
files
based
off
of
the
one
that
I
already
have,
rather
than
trying
to
record
them.
D
A
That's
good!
That's
really!
Good
information!
Steven
I
didn't
realize
that
you
could
manipulate
or
edit
the
artifacts
to
change
what
the
final
product
is,
that
that
makes
things
a
lot
easier.
So,
let's
so
I'll
work
with
you,
then
to
get
that
final
information
that
I'm
like
worrying
about
full
recordings
and
stuff.
So,
yes,
I'll
work
with
you.
Okay,
that.
C
A
I
think
we
have
all
that
in
on
unlock
down
already,
because
you
know
the
we
have
all
the
documentation
there,
like
the
main
game
like
installing
the
operator
and
then
installing
or
creating
an
instance
of
the
CR
DS
that
it
exposes
so
I
think
we're
good
there,
but
I
will
definitely
track
down
each
and
every
one
of
you
that
I
need,
if
I,
if
I
need
it
yeah
yeah.
This
sounds
great.
I
know
where
you
all
live
a.
B
A
Up
afterwards,
yeah
yeah
will
I
make
I'll,
make
sure
Travis
that
it's
the
what's
gonna
be
in
the
one
Dodds
you're
released,
and
it's
not
you
know
any
any
stale
old,
stuff,
cool
cool,
yeah,
cool,
okay,
so
great
progress,
Steven
on
getting
that
website
updated,
we'll
get
the
Steven
will
open
a
PR
with
the
changes.
Okay,
yeah
really
happy
to
see
that
and
welcome
to
the
root
community
too,
by
the
way
Steven,
okay,
so
okay,
then
the
other
thing
that
we
wanted
that
we've
been
working
on
is
some
updates
to
our
governance
of
the
project.
A
The
you
know,
one
of
the
issues
that
we
have
is
in
velocity
of
code
changes,
and
so
we've
been
working
on
some
some
updates
to
that
to
be
able
to
empower
the
individual
storage
providers
to
get
changes,
ceptin
it
approved
and
merged
into
master
easier,
without
complete
bottleneck
on
the
current
maintainer
team.
So
we
want
to
do
that
for
100,
but
that
is
not
a
strict.
A
You
know,
dependency
of
it
needs
to
go
into
the
one
dot.
Oh,
you
know
bits
or
anything
like
that.
So
that's
not
completely
tied
to
the
release,
vehicle
and
process,
but
we
are
absolutely
prioritizing.
You
know
finalizing
this
and
getting
things
updated.
So
we
can
remove
some
of
the
pain
points.
We
have
around
code
velocity
in
the
repo
right
now.
D
D
A
D
A
Don't
think
that
those
those
look
like
they're
largely
generated
codes
and
they
shouldn't
be
too
bad
I,
don't
think
yeah
yeah.
These
awesome,
alright,
thanks
to
the
update
Dimitri.
So
it
sounds
in,
like
the
you
know,
targeting
thursday/friday
end
of
week,
type
of
thing
seems
to
be
in
alignment
for
all
the
different
required.
It's
and
paths
that
we
have
yep.
B
A
Let's
and
then
in
in
the
spirit:
let's
try
this
for
this
release:
let's,
let's
go
ahead
and
open
up
issues
on
the
one
dunno
projects
board
for
the
other
outstanding
items.
We
have
here
like
how
the
blog
post
and
stuff
like
that,
so
that
we're
tracking
everything
for
the
release
in
one
place
and
see
how
that
goes
for
this
release
and
if
there,
if
the
process
is
rough
or
we
want
to
make
improvements,
then
we
can
do
a
post-mortem
and
decide
on
something
better
for
the
next
release.
But
maybe
we
can
just
do
that.
A
A
C
Have
something
to
talk
about?
It's
not
exactly
prevented,
oh,
but
it's
relevant
generally,
so
I
just
want
to
well
I
always
ruin
myself,
but
I
want
to
remind
there
is
the
zeesoc
running
and
I
got
the
proposal
settled
a
I'm,
not
sure
if
you
guys
have
time
to
eat
them,
I
think
Jared,
Travis,
Rohan
and
me
are
mentors
for
some
of
the
projects.
I
don't
know
if
I
could
remember
eating
well
as
LCS,
but
the
deadlines
I
believe
is
only
six
and
we
should
maybe
start
talking
about
proposals.
A
Yes,
the
week
before,
so
this
is
only
the
second
year
that
we've
done
this
and
last
year
it
was
just
me
in
Travis,
so
he
and
I
just
put
our
heads
together
and
you
know
kind
of
coordinated
on
what
we
thought.
The
best
proposals
were
this
year.
You
know
we
have
a
kind
of
a
broader
collection
of
potential
mentors
and
and
I.
The
tricky
part
is
that,
depending
on
what
project
gets
accepted,
or
what
do
we
want
to
accept?
A
You
know
various
people
may
or
may
not
be
mentors,
because
you
each
of
the
potential
mentors
for
a
specific
project.
Only
so
I
don't
know
from
the
CN
CF
organization
perspective,
if
they're
gonna
create
mentor
accounts
for
everybody
or
how
that
works,
but
at
the
minimum
we
should
as
a
potential
mentor
group,
we
should
meet
and
discuss
what
we
think
are
the
best
proposals
and
like
which
ones
we
know
are
our
highest
priority
for
what
we
think
should
get
the
offer.
So
I
I
have
access
to
all
that
stuff
right
now,
yeah.
A
D
A
Okay,
excellent,
so
that
it
makes
it
easy.
So,
let's
how
about?
Let's
do
this:
let's,
let's
create
a
google
Summer
of
Code
private
slack
channel
and
let's
discuss
the
proposals
they're
about
which
ones
that
we,
you
know
the
strengths
and
weaknesses
or
you
know
talk
about
that
there
in
that
discussion.
Does
that
sound
good.
A
B
A
That
way
that
to
give
an
input
to
the
CN
CF
of
the
number
of
slots
that
the
Brooke
project
can
get
I
went
ahead
and
selected.
You
know
as
potential
mentor
for
for
all
four
proposals,
since
at
that
stage,
they're
good
enough
to
continue.
You
know
to
continue
on
if
I
mean
it's
make
calls
about
which
you
know.
What's
the
top
one
that
gets
the
one
slot
or
you
know
how
many
slots
we
get,
then
that's
when
we
need
to
have
more
conversation
which
we'll
do
in
our
in
our
slack
channel
just
aren't
way.
A
C
A
A
Alrighty,
okay,
and
so
we
already
talked
about
the
NFS
timing,
provisioning
broke
and
it's
gonna
follow
up
on
looking
at
that
pull
request
again
and
and
Ashish
I
think
we'll
be
able
to
get
that
in
for
one
dot.
Oh
are
there
any
other
community
topics,
pull
requests
anything
else
for
that
people
want
to
discuss
right
now
the
floor
is
open.
D
A
A
A
I
think
the
biggest
thing
Rob
is
that
you
know,
since
we
haven't
been
doing
a
good
job
of
everybody,
the
you
know
the
entire
community
focusing
on
what's
left
in
the
release
and
what
the
tasks
are
and
kind
of
coordinating
everything
together.
What
we're
gonna
do
here
is
that
we're
going
to
start
a
track.
Everything
on
the
1
dato
project
board,
even
non-code
changes
like
blog
posts
like
that,
so
that
we
have
everything
in
one
place
with
you
know
the
entire
community
eyes
all
on
that
in
one
place.
A
So
that's
what
we're
gonna
try
for
the
rest
of
the
week
and
we're
gonna
target
in
two
week
to
get
this
release
out.
Ok,
great
alrighty
yeah!
We
can
follow
up
together,
Rob
if
there's
any
other
questions
or
discussion.
Yeah
awesome
thanks
for
joining.
Ok,
guys,
I
will
go
ahead
and
stop
the
recording
then,
and
let's
keep
working
towards
this
release
this
week.
Thanks
everybody
all.