►
From YouTube: 2019-01-29 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
Can
you
see
the
agenda
doc
on
your
screen?
Now?
Yes,
all
righty.
So
this
is
the
January
29th
2019,
look
a
community
meeting
and
we'll
go
ahead
and
start
off
by
taking
a
look
at
the
various
milestones
we
just
released
is
0.9
that
to
patch
release.
So
a
lot
of
the
issues
that
we
had
pending
that
we
wanted
to
get
out
into
the
hands
of
our
users
are
now
available
for
them
with
that
0.9.0.
A
A
B
B
A
A
Think
that
the
young
yeah,
you
did
review
it
and
you
brought
up
the
backwards.
Compatibility
issue
and
I
did
not
see
an
update
from
Yanis
on.
C
C
A
C
C
A
B
A
B
C
There's
one
main
problem
there,
especially
for
well
the
simple
case
here
that
is
I
think
sometimes,
which
is
kind
of
another
problem,
is
if
the
operators,
on
the
same
note
SD
as
the
monitor
the
monitor,
will
begin
doing
the
failover
in
some
cases
and
then
well
in
a
middle,
be
exterminated
because
of
the
one
parts
being
stopped
so,
but
this
first
understand
the
issue
there,
it's
kind
of
into
the
same
direction.
That's
there.
C
B
I
was
looking
at
is
that
the
new
month
does
come
up,
but
the
old
man
doesn't
get
taken
out
of
quorum.
The
operator
waits
forever
or
a
long
time
for
it
to
go
away.
I
I
tried
the
Mon
failover
locally,
just
in
mini
cube
at
where
I
delete
the
deployment
for
him
on
and
the
new
Mon
came
up.
But
then
the
old
one
there
is
looks
like
an
incorrect
check
for
how
many
moms
are
running
and
we
wait
and
it
times
out
and
then
at
the
next
health
check
health
check.
B
A
My
concern
at
this
point
is
that
the
complexity
of
it
might
be
a
bit
much
for
trying
to
you
know
back
port
into
a
previous
release
where
the
quality
you
know
is
pretty
well
hidden.
Things
are
stable,
so
I,
don't
have
a
you
know.
Computer
final
assessment
on
that,
but
that's
my
initial
gut
reaction
is
that
you
know
the
to
be
weary
of
the
complexity
into
a
stable
release
right
for.
B
A
A
Yeah
I
think
it
was
since
the
last
community
meeting
we,
you
know
the
road
map
was
updated,
the
milestone
was
updated,
the
project
board
was
updated.
So,
instead
of
looking
at
an
empty
miles
this
time
we
actually
have
everything
fully
captured
I
believe
in
a
plan.
41.0
has
has
issues
opened
and
put
into
the
right
milestone
a
project
and
everything.
Actually,
the
PR.
B
B
A
B
C
A
A
A
Okay,
so
I
guess
the
way,
guess
what
we
did
get
fully
updated
was
the
project
itself,
then
okay,
so
that
seems
like
a
follow
up
that
we
need
to
do.
Let
me
capture
that-
and
you
all
can't
see
this
right
now,
but
there's
a
cat
in
front
of
my
monitor
that
I
can't
see
where,
where
I'm
typing,
okay.
So
now
we
can
start
typing
again,
alright,
so
follow
up
on
including
all
1.0
issues
in
the
milestone
and
the
roadmap.
D
A
All
right,
let's,
let's
move
on
to
the
community
topics
and
questions
so
something
I
added
here
is
that
February
8th
is
the
due
date
for
submitting
proposals
for
kube
Connie
you
on
the
maintainer
track,
and
so
we,
as
always
we
get
an
intro
talk
and
a
deep
dive.
Talk
and
I
think
the
intro.
We
don't
need
to
change
anything
that
content
is
up
to
date.
We
just
delivered
it
last
month
in
Seattle,
in
as
an
introduction
to
the
project.
A
I
think
that
content
is
solid,
but
the
deep
dive
we've
consistently
kind
of
switched
around
a
bit
and
took
a
bit
of
a
different
focus
for
each
time.
We've
delivered
a
deep
dive,
and
so
I
wanted
to
solicit
feedback
from
this
forum
here.
If
anybody
had
specific
ideas
that
they
wanted
to
see
us
go
into
in
the
deep
dive,
because
I
need,
when
I
submits
the
proposals,
it
needs
to
include
a
kind
of
a
description
of
what's
going
to
be
included
in
the
deep
dive.
B
It
partially
at
least
depends
on
what
other
talks
are
accepted
as
well,
because
you
know,
if
it'd
be
nice,
to
hear
from
edge
of
what's
that
operator,
all
about
and
rook
cuz,
it's
just
been
added
recently,
but
they
I
think
they
have
a
talk
submitted
as
well
separately.
So
we
wouldn't
need
both
of
those
in
that
case,
but.
C
B
A
A
Alex
said
just
use
chat,
so
he
might
have
lost
audio
or
going
into
the
subway
or
something
yet
see.
So
it's
very
loud
on
the
subway
say
say
Alex.
Let
let
me
know
if,
if
that's
something
you
want
to
present,
because
when
I
submit
I
need
to
also
have
names
on
them,
I
am
more
than
happy
I.
Think
as
a
strategy.
We
want
to
have
the
maintainer
team,
at
least
the
names
attached
to
these.
A
So
we
can,
you
know,
be
all
be
have
representation
and
and
registration
for
the
conference
that
way,
and
so
we
can
put
names
on
them,
but
you
know
having
an
idea
of
who
actually
wants
to
present
the
content.
Is
it
good
to
know,
especially
if
it's
a
new
topic-
and
you
know
I,
am
always
more
than
happy
to
present
and
and
speak
on
rook.
You
know
the
intros,
especially
the
intro
talk
I've,
given
that
one
like
five
or
six
times
now,
I
think
so.
A
I
can
continue
doing
that
or
somebody
else
can
take
have
a
chance
at
that.
If
they
want
to,
it
should
be
pretty
easy
because
all
the
contents
is
already
created.
So
there's
not
you,
don't
have
to
even
really
make
a
presentation
or
anything
but
I'm
more
than
happy
to
do
it.
I,
like
I,
like
speaking
and
Alex,
said
sure
in
the
chat.
So
it
sounds
like
it's.
It
sounds
like
he'd
be
interested
in
doing
that
and
we'll
also
have
to
talk
to
about
it.
That's
a
full
35
minutes.
A
A
Alright
and
then
I
wanted
to
also
report
on
rook
CI
integration
with
the
CN
CF
there
I
think
was
last
week,
the
CI
working
group
for
the
CN
CF
had
a
meeting
after
not
having
one
in
December
sort
of
been
a
couple
months
and
they
presented
on
their
plans
for
the
V
to
CN.
Cf
CI
is
what
they're
calling
it,
and
so
the
integration
story
for
that
for
Brooke.
A
What
we
had
hoped
for
was
that
we
would
be
able
to
kind
of
transfer
off
the
day-to-day
hosting
and
running
of
our
CI
to
the
CN
CF
that
was
kind
of
the
original
intent,
but
that
isn't
pretty
clear.
That's
not
the
business
that
they
want
to
be
in
and
they
want
each
of
the
individual
projects
to
be
hosting
their
own
CI
and
doing
the
integration
steps
to
get
the
data
and
the
results
and
such
into
the
CN
CF
CI
dashboard.
A
So
in
the
v2
version
of
that
effort,
there
that
the
working
group
is
doing
the
March
timeframe
is
when
they
say
they'll,
be
ready
to
have
documentation
and
guidance
on
how
projects
can
perform
an
integration.
How
new
projects
can
be
added
to
their
the
CI
dashboard
in
CI
experience
there,
so
we
will
reengage
with
them
in
March
to
figure
out
what
the
steps
are
there
and
what
what
we
want
to
do
there,
but
so
the
big
takeaway
here
is
that
hosting
see
I
will
continue
to
be
the
responsibility
of
the
rook
project.
A
Now,
thankfully,
we
have
a
wonderful
new
experienced
member
of
the
team,
Chris
Chris
Meyer,
and
that
will
have
some
time
to
be
working
on
on
rook
CI
stuff
and
has
already
taken
steps
to
fix,
bugs
and
improve
the
quality
and
reliability
of
our
CI
process
and
Jenkins
and
everything
Chris.
Do
you
have
any
comments
that
you
want
to
share
about
that
effort
right
now,
yeah.
D
So
I
mean
right
now,
I'm
still
trying
to
get
the
lay
of
the
land
and
everything
but
kind
of
a
few
big
takeaways
is.
Obviously
we
had
that
bug
last
week
where
we
were
running
into
a
time
out
issue
with
the
GCE
step
of
integration,
testing,
which
unfortunately,
would
bomb
about
an
hour
plus
into
the
run
and
so
attempt
fixed,
for
that
was
to
just
up
the
time
needed
for
updates
to
run
on
there.
But
the
image
is
really
out
of
date.
D
So
one
of
the
takeaways
here
is
today
I'm,
going
to
create
a
new
image
and
then
put
that
into
production
for
us
to
use
which
will
speed
things
up.
But,
as
I
mentioned
earlier,
part
of
the
sprint
that
I'm
working
on
right
now
is
to
actually
create
an
automated
process
that
will
once
a
month
create
new
templates
not
only
for
GCE
but
also
AWS
and
Azure.
D
Should
we
want
to
add
that
in
there
so
we'll
have
no
more
than
a
month
old
image
during
these
runs,
because
it's
just
wasted
time
to
have
updates
going
on
during
that
run,
so
yeah,
that's
kind
of
where
we're
at
now
I'm
going
to
also
be
going
through.
Actually,
all
the
steps
either
things
that
we
can
kind
of
clean
up.
That
might
be
a
little
bit
brittle
or
kind
of
fragile.
So
that's
kind
of
what
I'm
doing
right
now.
B
E
E
A
A
A
E
I'd
love
to
be
able
to
do
it,
we've
been
distracted,
but
we
got
pulled
off
of
the
design
to
help
some
folks
get
Seth
integrated
with
OCP
and
just
do
some
test
runs
on
that,
so
our
focus
would
shift
a
little
bit.
We
are
moving
back
under
the
design
today
and
then
probably
the
rest
of
the
week
so
yeah
tomorrow
or
the
following
day.
Probably
a
really
good
time.
All
the
committee
will
figure
out.
I
know,
she's
got
tons
of
means,
I
have
to
sell
the.
E
A
A
A
That
similar
to
the
already
existing,
like
there's,
been
a
for
a
long
time,
there's
been
like
a
config
key
value,
store
that
you
can
use,
there's
an
API
for
it.
You
can
use
with
the
monitors.
Is
that
is
it
the
same
store?
But
now
it's
actually
it's
gonna
be
used
and
to
actually
be
more
of
a
platform
for
configuration
throughout
all
the
demons.
Or
is
it
a
totally
different
new
store
and.
B
B
It's
it's
not!
The
complete
implementation,
it'll
be
a
couple
of
different
two
or
three
different
PR.
It's
probably
like
this
first
one.
It
just
keeps
the
SEF
calm
but
gets
rid
of
the
net
container
for
the
Mon
demons
and
then-
and
it
doesn't
do
anything
special
for
mimic
yet
either
that'll
be
a
separate
PR
to
do
something
different
for
mimic.
I.
A
B
A
A
B
So
guess
I
could
have
added
it
to
this
list
as
well.
The
woman
has
to
open
up
PR
yesterday
for
the
CSI
integration
kind
of
an
initial
stab
at
that.
I
haven't
looked
at
it
yet
so
I'm
not
sure,
and
he
still
marked
if
it
is
working
progress.
Okay.
So,
but
he
asked
me
to
take
an
initial
look
at
it:
I'm
not
sure
others
need
to
yet,
but
it
feel
free
to,
of
course.
C
A
I
think
that
that's
appropriate
as
well
yeah
cool
all
right
now,
there's
something
else:
I
wanted
to
bring
up
what
was
it
shoot?
I,
don't
think
it
was
too
important,
though
okay.
So
yes,
sir,
we'll
follow
up
on
those
looking
at
those
pull
requests,
especially
some
the
older
ones,
and
we
will
also
follow
up
on
you
know
getting
all
of
the
1.0
issues
included
into
the
milestone
and
have
that
fully
fleshed
out
along
with
the
road
map
updates
that
Travis
had
gathered
together
cool.
Are
there
any
other
topics
that
anybody
wanted
to
discuss
today.
A
B
B
A
B
A
B
A
I'll
do
that
right
now:
ok,
cool!
So
that's
everything
that
for
today
then
so
I
think
we
can
adjourn
a
little
early
this
week.
Then.