►
From YouTube: 2020-07-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
july
28
2020
rook
community
meeting-
let's
go
ahead
and
start
on
our
milestone,
checkup
session
or
section
as
usual.
So
let's
take
a
look
at
the
1.3
project
board
where
we
will
be
talking
about
potential
1.3.9
release.
B
Yeah,
I
don't
think,
there's
anything
in
the
board.
Oh,
I
forgot
to
review
the
board,
but
that
first
one
there
is
an
ongoing
thing
that
it's
really
just.
We
pick
up
the
base
seth
image
and
we
get
what
we
get
and
we've
got
the
latest
one.
So
I
don't
know
that
we
need
that
issue
open
anymore,
honestly.
So
I'll
comment
on
that
at
least
then
the
second
one
is
already
resolved,
so
it
just
needs
to
be
closed
or
moved
to
done.
A
And
it's
is
it
like
backboard
as
well.
A
B
A
B
A
All
right,
1.4,
though,
which
we
are
targeting
having
out
well
before
kubecon
today,
is
the
planned
feature
freeze
date.
B
All
right
yeah,
so
that
we,
I
don't
think
I've
cleaned
the
board
up
since
last
meeting.
B
B
But
yeah,
my
summary
of
1.4
really
is
that
I
think
all
the
critical
things
are
merged.
Yesterday
the
ceph
csi
3.0
release
came
out,
and
that
was
the
main
blocker,
where
we
really
needed
that
out
before
we
released
1.4.
A
Travis
is
that
a
very
simple
update,
as
in
like
we
update
the
the
version
of
the
csi
that
we're
pointing
at
and
or
is
there
additional
logic,
changes
that
were
needed
to
consume?
It.
B
Yeah,
it
was
basically
that
to
update
the
default
version
we
deployed
with,
we
still
allow
for
the
older
step
csi,
but
in
a
previous
commit
in
master.
We
made
the
change
that
to
use
the
alpha,
not
alpha
beta
snapshots
from
csi,
so
we
so
if
you
want
to
use
snapshots
now,
you
really
need
to
use
csi
3.0
to
to
have
that
latest
and
greatest.
A
Got
it
and
are
there
any
issues
here
that
are
on
the
board?
That,
since
today
is
future
freeze
or
code
freeze
that
we
are
concerned
about,
or
that
you
know
are
still
considered
someone
blocking?
We
need
to
expedite.
B
No,
I
don't
believe
so.
Quota
management,
I'm
just
reading
through
them
again.
A
Sebastian
or
alexander
any
any
issues
that
you're
still
concerned
about
for
our
1.4
feature
for
you
today,.
C
Well,
I
think
it
would
be
nice
to
make
a
little
bit
more
progress
on
the
multi-csi
work
as
well
as
the
encryption,
but
this
is
still
something
we
because,
for
example,
encryption
is
really
self-contained,
so
we
can
easily
backport
it
so
yeah.
I
don't
have
major
issues
right
now.
It's
just
that.
I
think
the
list
of
to
do
is
was
a
little
bit
optimistic.
Maybe
some
of
the
items
might
have
to
move
later
or
yeah.
B
Yeah
one
thought
about
multiples
too,
is
so
in
1.3.
We
declared
it
as
experimental
just
because
we
didn't
have
community
testing
and
I
think
we've
done
more
testing.
At
least
rohan
group
has
been
doing
it
and
he's
got
a
pr,
but
that
pr
is
still
open.
So,
as
far
as
declaring
malta
says
stable,
I
think
we
need
that
pr
in
at
least
right
seb,
yeah.
C
Well,
what's
left
is
a
little
bit
more
testing
and
still
needs
to
to
debug
his
environment.
C
C
B
A
C
A
All
right
anything
else
on
1.4
or
we'll
accept
the
code
freeze
today
and
was
there
an
affirmative
decision
on
merging
this
and
then
stabilizing
and
further
testing
after
the
merge.
B
A
A
All
righty
sounds
good,
sounds
good
all
right.
So
then
we'll
proceed
forward
with
1.4,
we'll
branch
today
and
shoot
towards
the
release
date
of
one
week
from
tomorrow
on
august
5th
and
which
is
gives
us
plenty
of
room
for
kubecon
eu
which
in
which
we
have
slides
that
are
that
are
saying
1.4
is
has
been
released
by
then.
So
that's
on
track
and
appreciated.
A
We
already
mentioned
the
sub
csi
3.0
update.
Is
there
more
to
talk
about
for
that
travis
or
is
it?
Was
it
good
enough
at
the
original
mention.
B
A
Cool
sounds
good
and
was
there
a
documentation
added
as
well,
for
when
you
mentioned,
you
know
not
being
able
to
use
alpha
snapshots
with
with
3.0
version.
A
Today,
I'm
not
sure
why
I
keep
doing
that
section
and
so
quick
update
on
graduation
that
you
know
the
vote
has
been
open.
There
are
two
binding
votes
from
technical
oversight
committee
members,
so
the
voting
is
still
not
it's
not
completed.
It
is
outstanding
and
there
is
no
explicit
time
period
that
a
vote
needs
to
be
finished
by
so
it
will,
I
suppose,
remain
open
until
enough
binding
votes
from
coc
members
are
in.
A
We
had
some
outstanding
comments
from
the
due
diligence
doc.
Last
week,
our
last
community
meeting
and
travis.
I
know
you
responded
to
some
of
the
ones
from
justin
cormack
about
the
security
audit
findings,
and
I
responded
to
the
ones
about
from
karen
rova
about,
like
our
competitive
landscape
analysis
there,
and
I
incorporated
his
suggestions
into
the
documents
as
well.
So
I
think
we're
up
to
date
on
all
comments
for
on
the
due
diligence
stock.
Were
there
were
there
any
more
follow-ups
here,
travis
that
needs
to
be
done.
B
Right
so,
first
of
all,
yeah
sabah
has
been
doing
some
great
work
he's
on
the
call
here
with
fixing
these
security
reviews,
and
we've
been
doing
quite
a
bit
of
that
in
the
last
week
or
two.
B
So
gosek
is
almost
ready
to
be
enabled,
there's
just
one
last
pr,
that's
about
ready
for
merge
and
then
we'll
be
down
to
zero
gosek
issues
and
some
of
them
issues
suppressed
where
we
know
that
we
don't
need
to
fix
them
or
there's
no
real
security
concern
and
then
yep.
This
ci
is
the
one
that
will
enable
it.
This
pr
is
the
one
that
will
enable
it
in
the
ci
with
the
build
rule
and
that
rule
is
working
already
and
it
was
showing
a
bunch
of
errors
since
all
the
fixes
hadn't
merged
yet
yep.
A
Nice
yeah,
I
haven't
seen
this
output,
yet
I'm
about
to
scroll
through
all
of
it,
but
that's
pretty.
That
is
awesome
to
be
able
to
have
that
incorporated
into
directly
into
prs
and
have
enough
of
the
flag
issues
fixed
so
that
we
can
start
from
a
clean
slate
and
be
able
to
run
this
on
ci
and
if
there's
any
positives
that
come
up
then
there's
things
that
should
be
addressed.
So
that's
really
good
position
to
get
to.
C
Yeah,
it's
really
great
and
I
think
we
can
actually
expand
some
of
that
trying
to
maybe
lower
what
the
ci
does,
because
sometimes
it
takes
time
to
kick
it
off.
So
we
might
be
offloading
some
of
the
work
we
do
in
our
jenkins
via
get
a
workflows,
that's
also
an
option.
I.
A
B
B
Oh
yeah,
yeah
yeah
this
one
too
yeah,
but
I
guess
back
to
this.
The
security
review
so
of
the
three
ish
there's
three
issues
remaining
that
were
opened
from
that
december
security
review.
B
B
B
B
B
A
Yeah
that
yeah
I
mean
that
would
be
very
good,
because
this
is
a
line
of
communication.
We
have
open
with
a
you
know,
binding
voting
toc
member.
A
So
when
we
make
progress
on
it,
responding
to
that-
and
you
know
with
the
progress
that
we've
made-
you
know
so
I
mean
if,
if
there's
a
tactful
or
appropriate
way
to
ask,
if
there's
you
know
more,
that
he'd
like
to
see
or
any
outstanding,
you
know
questions
your
doubts
that
he
has
on
this
due
diligence
document
if
we
could
still
address
them-
and
you
know,
since
we
have
this
communication
open
with
them
or
an
opportunity
to
see
into
the
mind
of
a
toc
member
exactly
that
would
be
great
to
do
that
when
we
make
progress
on
that.
A
Okay,
so
that's
the
security
section,
then
more
any
more.
To
add
on
that
topic.
A
Okay,
all
righty
and
then
virtual
cube
con
august
17th
through
20th
yep.
So
this
week
we
have
friday
the
of
this
week.
The
31st
is
the
due
date
for
recorded
and
uploaded
presentations
for
the
intro
in
the
deep
dive
alexander
and
I
have
mostly
pretty
much
finished
the
slide.
Deck
alex
has
some
great
ideas
for
updating
the
slide
deck
flow
for
the
intro
session,
making
a
little
bit
more
visual
and
less
text
heavy.
A
So
we've
got
that
deck.
Pretty
much
done.
We
met
today
and
recorded
the
intro
and
outro
session
section.
Did
it
again
sections
together
and
so
we're
going
to
independently
now
record
each
one
of
I
got
first
half
of
the
deck
and
he's
got
second
half
basically,
and
so
we'll
record
those
and
I'll
send
that
over
to
alex
for
publishing
or
sorry
for
final
cut
and
processing
and
editing
and
doing
doing
video
magic.
That
alex
does.
A
I
have
that
in
and
published
and
done
before
friday
how's
the
deep
dive
going.
B
Yep
so
sev
and
I
have
slides
pretty
much
there
and
I
don't
think
I
sent
you
guys
a
link
if
you're
interested,
so
I
will
share
them
with
you.
If
you
want.
B
Broadcast
okay,
so
we
should
figure
out
how
that
works.
C
Jared
do
you
still
have.
I
think
I
sent
you
the
screenshots
of
our
settings
we
used.
I
think
they
were
well
good
enough,
where's,
the
video,
no,
where
yeah,
that
was
good
enough
for
the
presentation
it
was
as
the
webcam
is
going
to
be
scaled
down
pretty
much
so
we
I
can
look
into
sending
you
the
pictures
of
the
settings
we
used.
C
You
need
to
set
it
up
as
you
need
it.
We
have
decided
to
not
have
webcam
after
the
intro
and
outro
for
the
intro
and
outro,
as
it's
just
well
too
hard
to
really
find
a
spot
for
the
webcams
without
blocking
like
well
some
text,
so
we
just
have
it
for
the
intro
slide
for
the
first
slide.
Even
then,
we'll
then
I'll
fade
it
out
on
in
sony,
vegas
and
yeah
and
for
the
outro
I
think
I'll
get
it
up
again.
Their
webcam
sir
okay
cool.
B
A
Yeah,
it
was
pretty
easy
to
get
it
set
up.
Travis,
you
know
alex
expedited
some
of
my
fumblings
with
like
the
specific
settings
and
a
few
key,
like
you
know,
processes
I
guess
to
use
like
more
clothes
to
use
with
it.
So
he's
definitely
pretty
good
at
that.
We
could
talk
about.
You
know
any
questions
or
difficulties.
We
have
on
slack
to
get
each
other
set
up
and
effective
with
the
tools,
but.
A
A
Yeah
exactly
yeah
like
like
the
final
product
or
when
you're
done
recording
with
it
is
like
a
mkb
or
mp4.
You
know:
output,
video,
completely
finished
viewable
watchable
video
file,
and
then
you
can
stitch.
You
can
stitch
the
two
of
them
together
as
needed.
Okay,.
C
A
All
right
and
then
so,
project
project
pavilion,
something
I
noticed
with
that
is
that,
but
you
know
with
especially
with
the
other
cncf
project
that
I'm
a
part
of
too
is
that
they
didn't
ask
what
time
you
want
to
stack.
The
booth
they've
done
that
traditionally,
in
the
past
of
you,
know,
signing
up
for
hours
or
kind
of
giving
like
a
you
know,
part-time
half-time,
full-time
sort
of
decision
on
staffing,
the
booth,
but
then
this
week
they
sent
us
the
okay,
the
booth's
open.
Here.
This
is
the
recommended
hours.
A
You
should
have
it
staffed
and
it's
the
entire
day
for
four
days,
which
is
a
little
surprising
right.
B
B
A
It
starts
at
like
seven,
I'm
sorry
like
three
a.m,
pacific
time.
So
that's.
A
Yeah,
I
don't
I
don't.
I
don't
really
see
that
as
quite
feasible.
Honestly,
so
I
don't
know
what
the
consequences
are,
but
I
I
just
yeah,
I
don't
think
it's
going
to
get
100
coverage.
I
don't
think
it's
going
to
happen
right.
A
A
B
A
So
yeah,
so
we
should
try
to
try
to
get
coverage
for
that
and
like
and
communicate
on
that,
and
they
also
have
to
another.
Weird
thing
is
that
they
have
a
structure
or
strict.
They
have
a
requirement
that
you
have
to
be
a
project
maintainer.
We
do
have
a
handful
of
maintainers,
but
it's
not
like.
We
can
draw
from
the
entire
community
to
staff
it
which
is
even
more
constraining.
You
know,
projects
that
only
have
a
two
or
three
maintainers
period.
C
C
B
A
C
A
Yeah
yeah
exactly
travis.
Have
you
been
able
to
log
into
the
platform
thing
yet.
A
Oh,
I
tried
yesterday
and
today
for
the
cross
plane
submission
we
have
there
and
it's
the
login
still
isn't
working.
It
says
it
might
take
up
to
two
business
days.
So
definitely
some
rough
patches
in
this
first
virtual
event
that
they've
done
right:
okay,
okay,
because
once
we
can
log
into
the
platform,
then
we
might
have
a
better
idea
of
the
capabilities
it
has
or
mitigation,
for
you
know
not
being
able
to
staff
it
the
full
time
so.
A
Right,
no,
that
wasn't
in
the
email,
at
least
alexander
okay
and
then
project
updates
as
well.
Travis.
A
A
B
A
I
would
recommend,
is
the
graduation
proposal
has
like
a
bunch
of
this
information
and
major
milestones,
etc.
That
we've
done
because
I
think
it's
said
since
december
or
whatever
so
we
definitely
have
some
content
that
was
put
into
their
graduation
proposal
and
it
kept
up
the
date
at
least
until
april
or
may
or
so
so
there
should
be
some
good
content
that
you
may
pluck
right
out
of
there.
It
might
be
very
easy.
A
All
right
and
then
for
google
summer
of
code.
I
think
ahmad
is
he's
not
feeling
well
today,
so
he
wasn't
able
to
make
it
the
meeting
today
and
I
hope
that
he
gets
better.
It
feels
better
soon,
but
he
is
still
ahead
of
schedule,
which
has
been
great
this
summer.
He's
consistently
stayed
ahead
of
the
previously
planned
work,
milestones
and
pace.
That's
been
awesome.
The
second
evaluation
of
the
summer
is
this
week
opened
up
this
morning
and
it'll
be
done
before
end
of
week.
A
So
the
first
evaluation
went
great
and
I
don't
expect
any
major
hiccups
or
anything
in
the
second
evaluation
ahmad's
doing
a
great
job
and
he
has
a
couple
of
nfs
provisional
related
prs.
Those
are
the
ones
he
has
open
right
now.
These
I
didn't
know
about
these
urls.
Until
just
recently,
you
can
do
a
slash,
pull
slash
a
username,
so
it's
part
of
the
restful
route
and
it
gives
you
it
essentially
turns
it
into
a
query
for
open
prs
for
that
particular
username.
A
B
A
The
implementation
as
well
for
that
design,
doc
update
so
we're.
C
A
On
those
and
iterating
through
those,
but
people
are
more
than
welcome
to
add
comments
as
well,
but
we've
got
at
least
three
pairs
of
eyes
on
this
already
with
the
mentors
for
ahmad
this
summer.
A
Okay,
any
other
community
topics
or
prs
or
issues
to
discuss.
A
Yeah-
and
we
already
discussed
the
action
item
here-
to
have
your
kubecon
presentation
recorded
before
the
end
of
the
week-
anybody
has
any
problems
with
the
software
or
getting
the
recording
done.
Let's
just
talk
about
it
in
a
group
on
slack,
since
we've
alexander
is
an
expert
at
it
and
he's
helped
me
work
through
some
of
the
things
already
that
we're,
both
probably
in
a
good
position
to
help
you
anybody
else.
So
just
ping
us
on
slack,
and
we
can
talk
about
that.