►
From YouTube: 2019-08-27 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
B
A
B
Yeah
I
spent
some
time
yesterday
trying
to
make
sure
the
boards
were
up
to
date,
I
put
a
bunch
of
notes
in
in
the
agenda
to
discuss
things
around
releases
yeah
for
one
dot
or
Alize.
There
are
three
fixes
that
have
been
back
ported,
actually
I
didn't
verify
if
their
issues
are
the
support
here,
but
now
there
are
three
around,
let's
say
around
getting
their
substances
but
SEF
dashboard
being
more
stable
and
I'm,
forgetting
the
other
two.
B
B
A
B
A
B
B
A
That's
that
sounds
reasonable
all
right.
So
let's
talk
about
1.1
min.
So
we
are
that's
yeah.
It's
use
this
here
this
agenda
here,
Thank
You
Travis,
so
we
are
in
feature
freeze.
So
let's
talk
through
what's
on
the
board
here
and
how
that
translates
to
or
feature
freeze
and
then
by
I
assume
that
there
is
some
cleanup.
That's
neat.
We
need
to
do
for
the
items
that
are
in
the
1.1
milestone
like
tag
that
way
and
github
and
in
this
to
do
column
but
are
not
going
to
be
included
in
the
release.
A
B
B
A
B
The
ones
remaining
I
think
are
around
Mon
placement
and
I
put
the
P
that
P
are
in
the
list
for
discussion
later,
but
changing
how
we
schedule
those
Mon
pods,
that's
just
going
through
final
testing
with
Noah
and
then
the
other
main
change
a
couple
more,
but
there's
one
around
handling,
kubernetes
upgrades
with
pod
disruption,
budgets
and
machine
disruption,
budgets
so
that
one
I
see
it
as
lower
risk
because
it's
independent
of
our
current
controllers.
It
is
adding
new
controllers
into
the
operator,
though,
and
then
I'll
plane.
C
I'm
sure
I
am
I,
have
a
PR
number
3573
that
is
working
on
adding
in
support
for
SEFs,
I,
think
new
with
mimic,
or
rather
like
sort
of
fully
baked
with
mimic
configuration
database
that
the
monitors
to
keep,
and
we
want
to
enable
this
that
we
can.
You
know
so
that
rook
can
set
values
for
things
like
it
currently
does,
which
it
often
does
via
config
file,
but
also
so
that
those
values
can
be
overridden
by
users,
especially
in
like
debug
situations
or
for
cluster
tuning.
B
Yeah
and
then
I
guess
thanks
playing
I
guess
to
back
up
a
second.
The
way
I'm
viewing
feature
freeze
is
that,
okay,
we
had
a
big
push
to
get
features
in.
We
knew
coming
into
the
this
week
that
we
would
have
these
other
items,
and
other
storage
providers
have
items
to
like
you
know,
edge
of
s
do
declare
v1
on
their
CRTs
right,
Dmitri
and
so
yeah.
D
B
C
A
Here
that
we
have
around
feature
freeze-
and
it
seems,
like
you
know-
the
each
storage
providers
as
assessing
and
making
the
calls
on
the
risk
associated
with
those
and
then
getting
those
in
I
think
the
changes
that
would
have
cross
storage
provider
impact.
You
know
those
ones.
We
should
keep
an
eye
out
on
and
you
know
make
some
group
calls
potentially.
But
you
know,
each
individual
storage
fighter
is
still
making
their
own
calls
for
changes
that
affect
the
quality
or
functionality
of
their
particular
storage
fire.
Only
yep.
A
B
E
B
D
My
comes
my
time,
but
yeah
yeah
no
I
mean
so
I
was
thinking.
Maybe
we
should
just
set
up
the
court
date
and
basically
say:
okay.
This
is
the
hard
stop
and
you
need
to
make
sure
your
features
either.
You
know
out
right
because,
like
yeah,
otherwise
my
worry
is
that
because
the
timelines
is
like
different
providers
like
energy
first,
we
have
completely
different
set
of
agendas
right,
so
not
necessarily
even
bound
by
that
date.
But
if
you
set
up
the
date,
they
will
be
obligated
to
each
that
date.
B
Another
thought
so
I
had
a
proposal
on
lockdown
strategy
around
this,
and
when
this
is
related
to
an
issue
a
couple
of
months
as
well,
I
realized.
It
was
anyway
similar
thought
process
that
I'd
proposed
at
the
end
of
this
week
that
we
actually
create
the
release
branch
and,
at
that
point,
that
that
really
is
our
our
lockdown.
D
C
Am
I
think
that's
a
good
idea.
I
think
we
still
have
to
be
very
judicious
about
what
we
do
put
into
master,
because
if
master
gets
too
far
ahead,
then
actually
doing
back
ports
is
gonna,
involve
a
lot
of
like
refactoring
and
then
that's
also
like
I
mean
gonna,
make
it
harder
for
us,
but
also
like
potential
like
risk
for
or
things
to
not
go
the
best
as
well
right.
B
C
C
D
B
A
Write
some
width
is
like
wind
release
branch
to
release
one
dot.
One
branch
is
created,
it's
created
with
a
tag
of
having
beta
in
the
name
right,
so
we
haven't
officially
created
a
one
dot.
One
tag
at
that
point,
because
the
intent
is
to
continue
potentially
backporting
or
taking
on
fixes
and
polish
etc
to
drive
towards
the
1.1
actual
the
base
and
then
we'll
apply
that
one,
not
one
tag
at
that
point
exactly.
B
B
A
B
B
B
A
B
E
A
E
E
B
E
E
So
I
have
one
small
item
that
I
need
to
address,
as
Alexander
pointed
out,
so
I
will
do
that
in
some
time
now,
but
the
build
just
feel
for
my
last
bush
and
I
am
not
sure
as
to
what
really
the
cause
is.
It
didn't
seem
like
it
was
some
of
my
change,
but
it
could
be
so.
I
also
spend
some
time
on
that
and
maybe
I'll
pin
you
on
the
bill
channel.
Maybe
even
you
have
a
child
one
of
those.
B
Okay,
that
thing
is
that
we
do
have
a
number
of
random
CI
failures
that
are
known
issues
not
related
to
your
PR.
So
what
if
you
have
four
out
of
five
green
as
far
as
the
trip
renée's
versions?
Probably
it's
not
your
issue.
It
looks
like
Jared's
confirming
here
D
yeah
file
tests,
Hank,
that's
one
of
the
most
common
ones,
so.
E
E
E
E
E
A
B
B
B
D
B
D
B
B
A
B
D
A
D
A
D
Yeah,
that
was
that
was
first
of
all,
it
was
a
first
time
for
me,
so
I
had
never
been
mentor
for
problem
like
that.
It
wasn't
honestly.
I
did
not
capture
a
lot
of
my
time,
so
I
did
a
lot
of
work
on
himself
and
I.
Think
I
think
it's
actually
a
good
thing
for
the
young
people
to
you
know,
get
involved,
I
really
love
the
program.
I
think
we
should
continue
this
definitely
and
next
summer
we
should
figure
out
what
else
we
can
do.
D
If
you
looked
at
the
design
proposal,
what
he
put
in
place,
it's
actually
not
just
edgy.
Faced
with
you,
have
all
the
plumbing
done,
and
what
we've
merged
also
can
be
extensible
by
other
operators
as
well.
Cf,
probably
next
target
and
I.
Think
I'm,
not
the
things
we
should
do
is
to
encourage
him
to
finish
F
implementation.
For
that.
So,
let's
see
how
that
goes
to
notice.
D
A
I
hundred
percent
agree
with
that
I
think
that's
one
of
the
really
awesome
things
about
the
google
Summer
of
Code
program
is
that
you
know
it
gives
a
great
opportunity,
for
you,
know
younger
folks,
in
early
of
their
careers,
to
join
an
open-source
project
to
become
part
of
that
community
and
make
a
me
being
full
contribution
and
hopefully
remain
encouraged
to
continue
to
contribute
to
that
projects
going
forward
as
well.
That's
where
it's
great,
with
our
first
google
Summer
of
Code
alumnus
Rohan,
he's
continued
to
contribute
to
the
projects
here.
A
So
I
think
that's
a
great
idea
to
continue
to
keep
Giovanni.
You
know,
engaged
and
encouraged
he's
more
than
welcome
to
be.
You
know
to
continue
to
be
participating
in
the
community
there.
If
we
haven't
already,
we
should
you
know
tweet
about
his
effort
there
and
thank
him
and
congratulate
him
with
that.
Does
he
want
to
write
a
blog
post
about
this
topic?
A
I
think
that
you
know
that,
like
some
of
the
concepts
about
multi-home
networking
in
the
design
that
went
into
it,
what
it
accomplishes
new
scenarios
that
it
opens
up
and
stuff
like
that,
that
would
be
an
awesome,
blog
post.
If
he's
interested
in
writing,
that
he
could
get
up
a
blog
authorship
on
I.
D
Yeah
yeah,
you
have
you
definitely
to
the
block
together
and
probably
in
September
or
something
ideally
after
one,
one
of
these
right
and
people,
don't
blue
block
right
away,
so
that
will
create
a
little
bit
more
momentum
on
on
this
work
and
one
one
at
least
I.
Think
that's
what
we're
gonna
do
that
cool.
A
B
Related
to
what
I
was
mentioning
earlier,
so
our
our
a
our
tag
pipeline
currently
only
allows
for
release
branches
without
the
beta
or
other
suffixes,
so
that
poor
request
there
does
allow
for
alpha
beta
or
RC
suffixes
on
the
version,
so
I'll
need
that
reviewed,
I,
tagged
Bassam
on
it,
but
not
sure
when
he'll
be
available,
so
yeah
Jared.
If
you
want
take
a
look
at
it
or
or
someone
else,
that'd
be
great
3684.
A
B
B
Then
the
other
PR
I
had
there
is
around
the
Mon
scheduling
change
with
Noah,
so
just
yeah
to
point
out
how
differently
this
will
be
for
scheduling
mons.
So,
in
the
past,
we've
had
based
our
own
scheduling
code
where
we
look
at
the
nodes
and
we
try
and
figure
out
if
they
have
paints
and
tarnation's
or
those
sorts
of
things,
and
then
we
scheduled
moms
on
individual
nodes
and
added
node
selectors.
B
A
A
A
Ok,
that
sounds
good,
then.
So,
let's
this
week,
we'll
file
be
following
up
on
working
towards
in
with
the
1.1
release,
and
we've
got
some
ownership
for
sign
off
on
that
and
we'll
continue
to
polish
and
get
things
into
the
1.1,
but
least
branch
after
we
cut
it
and
we're
looking
forward
to
having
a
quality
release
with
new
source
writer
and
a
lot
of
new
interesting
functionality
as
well.