►
From YouTube: 2019-09-11:: 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
Okay,
perfect:
are
we
going
to
have
power,
possibly
so
yeah
I?
Guess,
let's
start
with
the
other
topic
a
bit
Kiva
is
there
anything
I
can
do
for
you
for
for
the
desperate
integration.
For
always
the
creation.
A
B
Total
to
recap
this
week
we
discussed
about
traffic,
oops
and
I
I.
Think
the
conclusion
is
we
just
you
can
know
that
traffic
Oh
Cantor
in
ER
in
Orchestrator
bacon,
and
we
we
just
start
from
you
guys
us
viewpoint,
and
if
users
lacks
some
devices,
we
just
create
a
new
trial
code.
Yeah.
You
just
submit
this
joke
of
Turin
illustrator
yeah.
A
Right
now,
dibs
is
the
only
I'll
consider
that
supports
non-trivial
drive
groups.
Yes,
so
for
the
other
beckons
you
have
to
manually
specify
the
drive
path
in
the
drive
group.
A
B
B
B
B
C
Yes,
so
since,
since
since
your
your
last
email
pointing
out
there
I
now
understand
the
problem
better
than
I
knew
before
I.
C
And
look
like
I
do
I,
like
the
I,
think
what
you
I
think.
The
structure
that
you
have
is
is
quite
neat
doing.
You
know
this
one,
then
this
one.
It's
that
sort
of
makes
sense.
Something
I,
think
why
I
guess
my
when
I
was
looking
at
the
the
getting
a
list
of
all
the
hosts
in
order
to
positive
a
create
OSDs
method.
C
C
C
D
E
E
A
E
C
A
For
right,
completions,
it
returns
to
the
caller
as
soon
as
we
have
a
result,
but
in
addition,
the
completion
can
stay
alive
until
the
thing
is
actually
done.
Like,
for
example,
you
can
go
to
2q
monitors
and
say
yes,
I
want
to
make
a
new
OSD
and
then,
as
soon
as
that,
that
wish
is
submitted
to
queue
manages
the
control
flow
is
going
back
to
the
caller,
but
in
the
background
the
oldies
are
still
getting
created,
like
the
volume
is
executed
and
stuff
like
that.
A
But
as
soon
as
we
have
submitted
the
the
configuration
change,
the
completion
is
basically
has
a
result,
even
though
it's
not
yet
effective.
C
A
C
A
A
A
C
C
C
A
A
E
I
asked
because
maybe
when,
if
you
enter
the
using
dry
fruits,
probably
you
can
select
a
big
group
of
OS
this
in
order
to
do
the
operation
and
it's
a
big
cooperation
that
is
going
to
take
a
lot
of
time,
but
yeah,
maybe
that
it's
possible
that
the
user
wants
to
create
just
to
three
different
OS
T's
using
three,
the
deponents
okay.
So
if
you
get
the
return
of
the
command
immediately
and
the
operation
is
been
being
in
security
in
in
background,
this
is
possible.
E
A
A
Because
the
orchestrator
is
the
only
place
where
we
can
introduce
some
kind
of
locking
overall
orchestrators,
like,
for
example,
in
ansible
I.
Think
if
one
operation
on
one
host
is
in
flight
like,
for
example,
we
are
creating
losses
on
one
host,
then
it
does
not
make
sense
to
create
another
set
of
overseas.
E
A
D
A
D
B
A
D
D
A
A
A
A
Yeah,
let's
conclude
that
became
there
is
nothing.