►
From YouTube: 2020-01-08 :: Ceph Orchestration 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
So
it's
mainly
things
to
cover
that
sage
was
doing.
A
So
without
sage
being
here,
it
might
send
to
might
make
sense
to
just
postpone
it
next
week.
A
First,
one
is
mostly
removal
where
I
think
the
self-adm
should
do
everything
to
remove
all
of
this
to
make
it
simple
for
administrators
and
sage's
opinion
was
to
just
keep
it
keep
the
code
simple
in
in
self-adm
and
have
someone
else
like
the
dashboard
implement
that
code
to
properly
remove
ost.
A
It
doesn't
make
sense
to
have
it.
You
and
the.
B
Other
comment
on
one
comment
on
that:
I
guess
is
that
for
removing
osds.
Let's
see
I
mean
we
just
I
just
added
a
dock
for
this
in
rook.
Just
so,
people
can
do
it
manually
and
we
have
like
seven
steps
for
removing
an
osd,
so
it
is
kind
of
tedious,
but
at
the
same
time
I'm
not
sure
how
much
more
we
could
simplify
it
since
well.
B
Most
of
the
steps
are
around
checking
which
osd
to
remove
and
if
it's
healthy
and
mark
it
out
and
then
there's
really
only
one
purge
command
step,
osd
purge
to
remove
the
osd
and
yeah
yeah.
We
should
discuss
the
sage,
but
it
may
already
be
simple
enough
that
the
dashboard
or
other
clients
can
work
with
the
osd
purge
command.
A
Yeah
yeah,
oh,
we
are
doing
it
in
the
orchestrator
manager,
modules
for
sev
adm
or
for
rook
or.
A
B
A
Yeah
for
for
replacing
those
d,
I
think
the
idea
was
to
have
a
two-stage
operation.
One
is
to
remove
that
osd
by
marking
it
as
being
destroyed
within
ceph
and
then
creating
that
osd
again
with
a
defined
ost
id.
A
A
But
that's
a
very
much
imperative
operation.
B
A
A
B
Yeah
brooke,
just
to
catch
up
from
the
last
few
weeks,
1.2
was
released
just
before
the
holidays.
I
think
on
wednesday
around
what
was
that
the
20th,
no
18th
somewhere
around
there
who's
tracking
time.
We
are
planning
the
first
patch
release
today,
based
on
a
couple
of
fixes,
including
a
an
osd
picks
from
sebastian.
B
So
thanks
for
that,
I
don't
know
that
we
need
to
discuss
any
of
those
fixes
here,
but
just
so
you're
aware
the
then
I
had
a
couple
questions
around
the
python
client
code
generation,
so
we
had
that
issue
from
a
few
months
ago.
Is
that
something
oh
yeah
sebastian?
Do
you
want
to
comment
on
on
that?
I
couldn't
remember
like
all
the
the
settings.
Validation
updates,
that
you
keep
making
manual
well,
it
looks
like.
A
B
Sure
sounds
good
and
then
oh
just
another
note
about
something
upstream.
We
had
a
security
review
for
rook
before
the
break,
and
I
opened
up
a
few
github
issues
to
track
those
work
items.
Nothing
major
really
was
found.
Probably
the
most
severe
issue
was
logging
of
sensitive
information,
step
keys.
If
debug
logging
was
enabled
there's
a
pr
already
for
that,
but
I'm
still
catching
up
on
pr's.
B
Some
other
little
issues
that
yeah
there
are
a
couple
around
the
the
crd
validation
just
to
tighten
up
that
as
the
more
validation
we
can
do
in
the
in
the
yaml.
The
the
more
issues
we
prevent
in
the
code.
A
Yeah,
so
the
actually
doing
these
python
client
validation
would
make
it
much
easier
to
add
new
validations
to
the
humans.