►
From YouTube: Ceph Orchestrator Meeting 2020-08-10
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).
C
B
A
B
C
C
D
If
there's,
if
there's
nothing
but
rook
on
the
agenda,
just
the
announcement
that
the
new
version
is
done,
I
have
sort
of
a
a
general
question
about
the
ethos
of
the
seth
project.
I'm
from
zach,
I'm
the
doc's
guy.
I
was
hired
last
november.
D
D
Now
I
do
and
what
I
would
like
to
work
out
with
everybody
here
is:
there
are
a
lot
of
ill
formed
or
malformed
docs
bugs
where,
like
people
have
a
good
suggestion,
but
then
like
it,
gets
put
in
a
pr
that
is
addressed
like
one
time
and
then
some
somebody
clearly
is
like
the
cost
of
getting
this
thing
across
the
goal
line
is
too
much
and
then
they
abandon
it.
D
So
I
was
wondering
if
it
was
possible,
if
anyone
has
any
objection
to
me,
checking
out
that
particular
like
it
look
at.
Let's
say
that,
for
instance,
there
was
one
I
did
earlier
today
where
there
was
just
a
typo
where
run
had
two
ends
in
it,
and
it
had
been
sitting
for
like
two
and
a
half
weeks
where
no
one
was
doing
anything
with
it,
because
they
were
just
not
paying
attention
to
it.
D
All
I
need
is
someone
else
to
see
like
oh
yeah,
that
is
correct,
and
then
it
can
just
be
merged
and
no
problem,
and
then
we
can
close
both
of
them
and
clear
out
all
the
old
crud.
So
is
it
cool?
If
I
do
that,
I
I
want
to
preserve
everyone's
credit
for
having
brought
up
the
issues
earlier
I
mean,
like
I'll,
add
a
signed
off
by
line
as
well,
but
I
want
to
know
like
does
that
violate
any
norms
of
the
seth
project.
D
D
When
sometimes
there's
like
a
change,
that's
three
or
four
months
old
and
somebody's,
just
like
not
looking
at
the
thing
anymore,
but
it's
a
good
suggestion
and
that
doc
is
still
like
a
live
doc
and
the
issue
still
presents
but
they're
not
responding
to
it
and
like
we
have
the
tool
it's
just
like.
I
don't
know.
If
it's
I
don't
know,
if
everybody
is
cool
with
me
doing
it
this
way.
D
That's
my
that's
my
thing.
This
is
sort
of
a
formality
where
I've
I've
already
done
one
I'm
gonna
do
more,
but
if
anybody
this
is
a
speak
now
or
forever
hold
your
piece
sort
of
thing,
because
there's
maybe
like
15
of
them
that
I
could
get
done.
If
I
can
do
like
three
or
four
a
day,
it'd
be
it'd,
be
nice
just
to
do
that,
or
also
when
people
complain
in
irc
about
something
that
they
don't
want
to
go
through.
D
The
trouble
of
raising
a
doc's
bug,
I'd
like
I'd
like
for
just
do
it.
I
yeah
I'd
like
for
people
to
be
able
to
complain
and
then
like.
I
can
just
turn
that
complaint
into
something
useful
to
improve
things.
Oh,
they
just
go
for
it,
yeah
done
so
it
shall
be,
and
that's
all
that's
all.
I
wanted
to
ask
and
thank
you
for
telling
me
go
ahead.
D
A
D
I've
got
a
pr
that
I'm
waiting
on
comments
on,
but
that's
like
half
of
what
I
needed
sebastian
for
since
it's
7
a.m.
So
I
you
know,
maybe
next
week.
D
A
A
B
D
Yeah,
it's
oh
come
on.
It
is
the
crisp
getting
started
guide,
which
is
everything
that
you
need
to
do
to
install
a
three
node
basic
cluster
up
to
the
dashboard,
and
then
there
needs
to
be.
I
need
to
make
another
pull
request.
D
A
Sounds
good,
alright,
yeah,
the
only
other
thing
on
the
agenda.
I
just
wanted
to
point
out
the
I
mean
rook
1.4,
shipped
upstream,
so
we're
happy
to
have
that
out.
No,
I
think
real
issues
to
bring
up
here
today
to
follow
up
from
last
week.
I
guess
I
still
need
to
update
a
design
document
around
how
we
do
osd
removal,
so
I'll
put
another
line
item
to
follow
up
on
that.
A
Otherwise,
other
topics
to
bring
up
today
anybody.