►
From YouTube: Ceph Orchestrator Meeting 2020-07-27
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
I
think
we
have
a
chrome
now.
Okay,
then
welcome
to
today's
orchestrator
meeting.
Let's
have
a
look
at
again
now,
which
is
quite
small,
so
there
were
a
lot
of
minor
bug,
fixes
that
went
into
the
videom
last
week.
A
A
Let's
pull
request
here,
I'm
pasting
it
into
the
other
pad
karen
kevin.
I
I
have
a
few
pull
requests
that
target
this
fadm
documentation
upstream.
Do
you
want
to
get
pinged
for
them.
B
A
C
Hello,
there
yeah,
maybe
I'll
just
mention
real
quick
for
the
rook
1.4
release,
we're
getting
ready
for
that.
We
were
waiting
on
the
csi
3.0
for
that
which
just
came
out
today,
so
we're
ready
to
at
least
create
the
branch
and
the
target
will
be
next
week
for
the
1.4
release.
C
D
Can
I
just
ask
a
quick
question
sort
of
about
design
philosophy
of
the
orchestrator
and
self
idiom
in
general,
one
of
the
reasons
I've
been
delaying
on
on
putting
back
a
fix
for
the
one
demon
failure
stops.
The
rest
of
the
demons
from
being
deployed
in
a
service
is
that
I've
been
investigating
what's
happening
on
the
long
run
cluster
and
the
the
finally
came
to
the
conclusion
that
I
don't
understand
what
orchestrator
and
cephem
in
particular,
are
supposed
to
do.
D
If
a
service,
if
a
demon
fails,
it
looks
as
though
it's
got
in
its
head
that
there
should
be
a
demon
running
on
a
host,
and
it's
not
it's
in
an
error
state.
C
D
A
So
the
state
of
the
schedule
of
chef
idm
is
on
the
edge
of
being
a
bit
too
simple,
so
pay
lovers
in
in
the
self-idm
schedule
are
not
yet
implemented,
so
we
right
now
rely
on
either
the
demon
is
fixing
itself
by
just
trusting
that
systemd
is
properly
restarting
demons
other
than
that
demons
are
not
getting
rescheduled
to
different
hosts,
so
they
just.
A
Paid
but
the
architect
is
there
to
actually
implement
proper
rescheduling
first,
we
just
hadn't
had
the
the
time
to
implement
it,
so
it
just.
D
Fails
all
right
so
so
right
now,
there's
there's
not
any
documented
compensatory
mechanism
for
dealing
with
that
manually
either.
It
looks
like
that's
what
I
wanted
to
verify:
okay,.
A
D
It
starts
to
border
on
re-reading,
kubernetes.
D
Right
but
part
of
the
problem
is
now
that
the
the
the
version
that's
running
there
also
is
is
very
close-lipped
about
status.
So
it's
it's
hard
to
even
tell
that
the
demon
failed
much
less.
Why
that
that
may
get
better
with
with
some
of
the
stuff
you
put
back,
but
I'm
I'm
still
not
100
sure
exactly
why
it's
failing.
It
looks
as
though
it's
not
configured
to
go
pull
an
image,
but
what's
demon
fade
no
exporter
in
this
case
and
the
the
host
in
question
doesn't
have
a
an
image
for
it.
D
D
A
Yeah,
I
I
wouldn't
call
it
by
design
right,
it's
just
the
state
that
is
right.
A
E
I
have
a
short
thing:
can
you
hear
me?
Yes,
please,
okay,
I
have
not
pushed
the
crisp
stefadium
octopus
install
guide
yet
because
it's
big
and
the
pr
that
I
would
push
would
just
be
way
too
much,
so
I'm
breaking
it
up
into
smaller
pr,
so
they
can
be
checked
and
then
individually
brought
in
also.
E
The
landing
page
needs
to
have
some
stuff
changed
so
that
it,
the
landing
page,
has
to
have
a
structure
change
as
well,
so
that's
got
to
go
into
a
different
pr,
which
is
a
part
of
the
chris
octopus
guide.
Also,
it's
called
chris
in
case
anyone's
wondering
why
I
keep
saying
crisp
back
in
november
when
sage
hired
me.
He
said
that
he
wanted
a
crisp,
getting
started
guide,
and
so
it
just
became
the
word
for,
like
the
simple,
a
to
b
guide.
E
So
that's
it
also.
If
anyone
knows
somebody
who
is
better
at
graphic
design
than
I
am,
which
is
I'm
not,
I
have
no
no
background
in
it
whatsoever.
E
A
E
E
A
Okay,
I'm
really
looking
forward
to
to
see
your.
A
Guide:
okay,
anything
else
for
today.