►
From YouTube: 2021-06-15 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
We're
missing
a
couple
of
folks
jared
and
seb
that
are
out
traveling
or
otherwise
gone,
but
this
may
be
a
quick
meeting,
all
righty
first
to
do
a
little
milestone,
checkup
so
for
the
1.5
release,
so
we
just
did
a
1.5.12.
I
think
it
was
last
week
that
was
the
last.
That's
the
last
one
last
release
of
planning
on
for
1.5.
Other
things
could
come
up.
We
may
plan
one
in
the
future,
but
I
think
we're
at
a
good,
stable
point
for
1.5
and
focusing
on
1.6
just.
I
should
confirm
that.
A
A
A
Yeah
one
thing
just
to
mention
I
was
talking
about
santosh
about
this
morning-
is
these
hybrid
storage
pools,
which
I
think
will
be
a
nice
feature
on
the
pools
where
we'll
be
able
to
have
basically
a
two-step
crush
rule
that
lets
you
say
hey.
I
want
ss
one
replica
and
ssds
and
the
next
replica
on
hvds
give
you
some
fast
reads.
Even
if
the
writes
are
as
slow
as
the
hdds.
A
All
right
we'll
call
it
at
that,
then
for
1.6
for
1.7.
Now
our
next
minor
release
we
have.
We
talked
about
the
end
of
mid
and
july
as
being
the
target
for
releasing
1.7.
A
A
A
So
what
what
we
decided
on
after
the
last
meeting
is:
okay,
let's
still
just
build
the
chart
in
master
and
it's
only
available
through
the
master
channel,
but
we
put
something
in
the
1.6
docs
that
has
instructions
on
how
to
go,
install
it.
While
it's
like
experimenting
the
idea
being
there
that
hopefully,
we
can
get
some
feedback
on
if
we
need
to
take
a
different
approach.
A
A
B
A
Know
the
the
ceph
cluster
previously
with
that
master
channel.
Oh,
if
you've
got,
I
believe,
let's
see,
that's
a
good
question.
We
should
verify
or
test
that,
but
I
would
think
the
cluster
could
just
take
over
the
chart
if
it's
got
the
same
cr
name
and
I
would
think
it
could
take
it
over
but
yeah.
That's
a
good
question
to
follow
up
on
I'll
put
that
in
the
action
items
confirm
if
cluster
cr
can
be
taken
over
by
the
home.
A
A
So
I
think
there's
really
two
more
things
left
so
there's
this
tag
jenkins
pipeline
that
we've
been
using,
which
creates
the
release
branch
and
then
pushes
tags,
and
I
wanted
to
have
a
discussion
with
seb
when
he
gets
back
next
week
about
what's
the
right
way
to
do
that
with
github
actions,
because
I'm
not
clear
on
how
we
could
trigger
that
shabom.
Do
you
know
how
we
could
trigger
an
action
without
a
push
action
or
without
a
pr?
B
Actually,
I
have
not
started
looking
to
this,
maybe
once
I
start
like
I
might
have
something,
but
we
I
think
we
can
start
with
like
we
can
together
action
with
the
tags
also.
So,
if
not
it
is,
it
is
not
push
or
pull
then
it
is.
It
can
be
tagged
also,
but
there
are
some
other
other
things
which,
by
which
we
can
together
events.
I
will
have
to
just
see
what
are
those.
A
So
yeah
we'll
follow
up
on
that.
I
just
want
to
make
sure
it
remains
independent
from
whatever
local
development
environment
so
that
we
don't
accidentally
do
something
wrong
or
pick
up
some
local
tag.
Instead
of
doing
having
an
official
tag,
we
could
presumably
just
like
make
sure
the
tag
is
in
a
particular
format
or
on
a
branch
that
is
like
release
dash
something
right.
A
Right
so
it's
validation.
Hopefully
we
can
just
make
sure,
even
if
we
do
have
to
push
it
like,
with
the
script
running
on
your
local
branch,
it
looks
like
we
can
also
run
actions
manually
if
that's
better
yeah.
I
think
that's
what
I
was
hoping
for.
Actually,
if
we
can
just
trigger
yeah
like
a
chat
thing,
there's
like
a
dock
section
on
that.
A
A
Sounds
good,
okay
and
then
the
other
one
we've
already
talked
about
before
it's
just.
We
need
to
enable
the
action
for
releasing
and
publishing
the
build
on
the
release
branch.
It's
already
working,
fine
mastery,
but
I
think
we
just
all
we
would
have
to
do
is
backboard
that
or
have
it
in
the
release
branch
for
it
to
work
right
or
is
anything
else
needed
for
that.
A
B
B
Yeah,
I
will.
I
will
start
looking
to
that
from
like
next
week,
yeah
next
week
or
like
on
thursday
yeah
yeah.