►
From YouTube: 2019-08-26 :: 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).
B
A
Whoever
he
is
he
want
to
be
caught,
did
a
great
job
creating
and
a
p.m.
pickets
with
it,
because
there
is
some
code
application
with
the
rook
module,
but
Paul
wants
to
do
it
afterwards
and
I
think
I'm
fine
with
it.
But
the
only
thing
that
I
really
wanted
to
get
soft
or
tacit
is
that
we
are
pausing,
lock,
messages
from
self
and
it's
like
housing
messages
from
the
roadblock
and.
A
A
B
B
They're
not
really
related
to
orchestration,
but
just
I
think
we'll
talk
about
that
tomorrow
in
the
huddle,
but
feeling
like
end
of
next
week
as
the
target
release
is
going
to
be
pretty
tight,
based
on
everything
going
on,
though
the
original
release
of
the
following
week,
probably
more
realistic
but
anyway,
still
pushing
for
next
week
further
release.
That's
what
I'd
like
to
do.
B
D
D
A
A
Okay,
let's
continue
yeah
I'm
still
working
on
making
sure
that
to
use
it,
it
cannot
trigger.
A
Bad
operations
from
within
the
dashboard
like
creating
he's
on
the
same
house
or
something
like
that
so
I've
looked
into
how
these
the
orchestrators
are
queuing
operations
and
make
sense
to
queue
operations
by
CID,
for
rock
and
by
host
by
for
other
orchestrators
and
yeah
the
host.
The
toast
thing
really
is
a
bit
problematic,
because
the
operations
within
the
orchestrator
api
are
not
composable,
so
you
cannot
have
a
thing.
That's
composed
out
of
multiple
things.
A
A
A
But
in
order
to
do
that,
you
have
to
combine
multiple
operations
together
like
if
you
want
to
make
sure
that
operations
on
a
specific
host
are
not
interfering
with
each
other.
Then
you
need
to
know
which
house
are
affected
by
an
operation
and
in
order
to
do
that,
you
have
to
carry
your
hosts,
and
you
cannot
do
that
right
now,
with
the
current
orchestrated,
API.
A
A
If
the
orchestrator
supports
placements
using
host
labels,
for
example,
then
we
might
run
into
the
same
problem
for
four
loko,
also
that
we
cannot
do
change
operations
from
within
the
August
feeders.
Another
example
is
I'm,
replacing
all
these
with
consist
of
multiple
tips
within
within
the
orchestrator.
That
might
also
need
composable
operations.
B
A
So
we
could
place
a
implement,
replace
these
in
the
orchestrator
I,
don't
know
if
it
would
it's
the
best
place
to
put
that
code,
but
it
is
certainly
possible
because
it
is
yeah.
The
orchestrator
is
not
declarative
but
imperative
from
from
ground
up,
so
it
might
fit
there
a
bit
better
if,
if
it
make
sense,
yeah.
B
The
replace
OSD
scenario
is
more
of
an
imperative
thing,
like
you
said,
of
doing
it
lately
and
rook,
it's
not
clear
to
me
yet
how
we
do
that,
but
based
on
planes
so
the
command
reporter.
Maybe
we
could
execute
jobs
from
the
manager
module
to
go,
do
things
on
specific
nodes
and
make
it
more
imperative
action
they
so
asti's
we
yeah.
We
talked
about
that
briefly,
at
least
two
weeks
ago,
yeah.
A
A
A
C
And
I
had
a
conversation,
Travis
I,
don't
know.
Who
else
was
there
for
that?.