►
From YouTube: 2020-12-01 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
All
right
not
a
lot
to
talk
about
on
the
agenda
today.
It
looks
like,
but
let's
start
off
with
the
project
review.
This
bar
is
in
the
way:
okay,
okay,
all
right,
looking
at
1.4
release.
First
of
all,
so
we
do
have
a
request
for
an
updated
release
due
to
the
cbe
or
the
image
base.
Chef
image
basically
has
some
security
fixes
in
the
latest
octopus
release,
so
the
one
that
are
not
one.
The
15.2.7
release
was
yesterday
from
zeph,
and
so
I'd
like
to
get
that
release
out.
A
C
I
would
have
one
I
don't
think
I've
labeled
it
yet
and
edited
there.
I
have
one
as
well
regarding
the
labels,
okay,
yeah,
I
I
wasn't
sure
what
labels
to
add
in
regards
to
like
what
which
section
it
applies,
but
I
would
well
let
me
shortly
describe
it
the
logic
that
merges
the
labels
from
the
ceph
cluster
is
well
to
put
like
that
can
be
broken
in
regards
to
how
should
I
put
it?
C
Let
me
just
put
it
as
in
my
comment:
if
the
manager
in
the
manager,
spec
generation,
the
labels
are
get
generated
or
like
merged
in
the
code,
in
the
background,
it's
it
has
like
the
labels
that
the
user
has
said
in
it
and
when
the
next
code,
in
this
case,
at
least
for
the
preparers
d1,
is
saying,
hey,
please
give
me
the
labels.
C
It
would
see
that
the
component
label
is
already
set
because
the
manager
label
is
still
set,
so
there
was
basically
kind
of
like
a.
A
C
A
A
I
just
moved
you
all
right
so
we'll
move
on
to
the
1.5
project,
then
we're
coming
up
on
1.5.2
potentially
for
this
thursday.
A
A
Well,
I
don't
know
that
we
need
to
discuss
in
detail
here.
I
don't
know
anything
you
want
to
bring
up
about
that.
Nothing's.
A
B
Yeah,
just
maybe
I
can
summarize
it
really
quickly.
This
one
is
about
allowing
to
lock
demons
having
demons
logging
to
files
instead,
instead
of
just
looking
to
st
out
std
air.
B
So
then
people
from
support
or
people
coming
from
a
non-containerized
world
can
actually
find
logs
into
a
more
common
location,
and
we
also
implemented
log
rotation
as
part
of
that.
So
once
the
log
log
collector
is
enabled
you
set
it
to
true,
and
if
you
don't
set
any
frequency
for
the
log
rotation,
it
will
be
every
day
every
24
hours
and
that's
it.
So
we
will
be
enabling
log
two
files,
as
well
as
to
log
into
a
cdr
sdvr
of
the
container.
A
B
If
it's
using
journal
d,
then
we
always
have
the
limit.
If
it's
always
cryo,
I
think
it's
up
to
50
megs
per
container.
As
far
as
the
look
retention
goes,
or
at
least
just
the
length
of
the
log,
there
is
not
even
a
retention
thing
from
that
control,
runtime,
so
yeah,
it's
just
like
too
ephemeral
for
demons
like
zeph.
That
would
just
stay
for
a
while.
I
guess
not
so
ephemeral
containers.
A
B
A
B
It
is
we're
just
reusing
what
the
log
rotate
configuration
is
from
the
cef
packages,
so
we
don't
actually
deviate
from
any
standard
behavior.
We
just
rely
solely
rely
on
that
particular
file,
so
whatever,
if,
if,
if
tomorrow,
something
changes
inside
the
save
packages
that
they
want
to
have
a
higher
retention,
they
will
also
get
it.
We
don't
we
don't
do
anything
special
for
work.
We
just
reuse
whatever
standards
configuration
is.
A
So
the
yep
for
1.5.
We
also
need
to
update
the
base
image
to
pick
up
those
security
fixes,
and
I
know,
there's
a
couple
other
issues
or
little
features
we'd
like
to
get
in
to
the
dot
2
release,
so
please
make
sure
they're
in
in
either
the
blocking
in
progress
or
in
review
column,
and
I
see
that
alexander
just
added
the
label
on
here.
Thanks.
A
A
And
then
moving
on
to
1.6,
we
do
have
a
1.6
project
board.
Now
it
hasn't
really
had
any
activity,
yet
it
just
has
a
few
issues
on
it
to
start
tracking,
since
1.5
has
been
out
a
few
weeks
now,
it's
start
time
to
start
planning,
for
whatever
release.
I'm
thinking
march
will
be
the
right
time
frame
for
this
release
at
the
same
time
as
pacific
is
released,
so
we
can
get
that
official
support
for
pacific
in
1.6,
so
it's
yeah
any
other
thoughts
on
the
timeline
for
1.6.
A
All
right
I'll
take
that.
As
for
that
plan,
I
don't
have
any
more
specific
dates
yet,
but
we'll
finalize
that
more,
I
think
after
we
see
how
it's
going
to
pacific
in
january
february,
all
right
on
the
community
topics,
so
jared
added
this
topic.
He
wasn't
able
to
make
it
today,
but
he
discussion
last
week
about
the
docker
hub.
A
A
A
C
I
well
I,
I
think,
crayo
added
like
a
message
to
the
top
of
the
website
with
like
hey.
If
you
have
build
setting
or
something
but
like
even
me
personally
with
the
customers,
we
have
nothing,
nothing
really
yet.
A
Okay,
moving
on
to
kubecon
retrospective,
we
can
be
quick
here,
so
we
had
a
mention
of
rook
or
they
spent
two
or
three
minutes
talking
about
rookie
like
one
of
the
keynotes
on
the
open
opening
day
with
project
reviews,
so
that
was
nice
to
be
mentioned
there
and
a
good
user
story
that
we
had
from
one
of
our
users
from
dimitri
mission
from
california
tech
anyway.
So
that
was
nice.
A
A
The
next
kubecon,
I
believe,
will
be
may
for
a
virtual
europe
event
again
and
yep.
Hopefully
they
can
improve
on
that
any
other
comments
from
kubecon.
Well,
actually,
one
more
I've
got
for
the
rook
session,
so
blaine
alexander
and
I
attended,
and
for
the
last
five
minutes
when
our
audio
was
supposed
to
be
enabled.
So
we
could
talk
to
the
live
questions.
C
A
Right,
I'm
all.
I
can't
talk
yeah
so
anyway,
it
was
good
to
see
some
questions
about
what
questions.
Nothing
too
surprising.
A
Yeah,
no
okay!
Moving
on
to
outreachy,
alright,
just
a
quick
update,
blaine
how's
how's
it
going.
D
It's
going
well,
I
think
the
official
start
date
is
tomorrow,
although
that's
made
slightly
complicated
by
modavi
being
in
singapore.
So
tomorrow
for
for
her
comes
before
tomorrow
for
most
of
us
but
yeah,
I
think
we
can
figure
something
out
I'll
she's
reached
out
to
ask
for
like
how
to
get
started.
A
A
I
just
consider
what
we
need
to
work
on.
I
think,
in
the
step
operator
we
have
a
number
of
features
already
under
consideration
and
then
the
other
thought
I
had
is
like
I'd
like
to
consider
kind
of
what
what
our
progression
plan
is,
or
you
know,
or
it
should
be
for
our
alpha
operators,
since
we
have
five
operators
still
in
alpha
state.
A
So
if
we
need
to
think
about
you
know,
if
some
of
them
don't
have
community
interest,
is
it
time
to
to
drop
them?
Officially,
we've
got
the
idfs
operator,
that's
officially
deprecated,
you
know,
can
we
just
remove
it
from
the
builds
or
or
whatnot?
So
I
think
I'd
like
to
formulate
some
thoughts
around
this
the
next
couple
of
weeks
and
have
a
more
formal
discussion
about
that
next
time.