►
From YouTube: 2019-03-27:: 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
A
B
A
Think
just
recently,
we've
just
fixed
the
problem
with
the
sold
version.
Rest
api.
Yes
for
the
passport,
so
we
have
some
really
tried
work
dependency.
You
know,
orchestra,
the
modules
end
and,
and
the
external
orchestra
doesn't
I'm,
really
failing
to
see
how
we
can
solve
the
problem
in
the
long
run.
C
B
C
Think
that
is
logical,
that
this
dependency,
these
chains
is
going
to
remove
things
okay,
but
in
any
case,
but
what
I
think
is
that
the
probably
we
should
fix
a
version
in
the
in
the
in
the
orchestrator
model.
I
mean
there
is
a
Ana
status
18
at
that
we
have
a
status
method
in
the
in
the
stator
model
in
order
to
see
if
it
is
possible
to
to
run
the
stator
of.
There
is
any
kind
of
problem.
I
think
that
maybe
we
should
fix
in
in
this
method
a
one
Bastion.
A
A
We
just
have
to
implemented
come
yes,
I
think
for
having
having
a
version
check,
basically
making
sure
that
the
version
of
the
sensible
of
the
interval
runner
service
is
compatible
with
our
ansible
manager
module,
and
they
were
similar
that
the
rook
version
is
compatible
to
the
rook
manager.
Module
and
the
deep
sea
version
is
compatible
to
the
Tipsy
minutes.
A
module.
B
This
will
have
to
be
done
inside
each
module
like
they
would
need
to
be
actually
don't
know.
If
I
can,
there
would
need
to
be
a
wafer,
say
the
deep
sea
module
to
the
query,
salt
and
see
what
version
is
present
or
somehow
and
then
and
then
you
know
and
I
mean.
Obviously
we
we
should
be
trying
to
make
our
our
version
compatibility
as
broad
as
possible.
B
A
B
C
B
A
B
I,
do
have
a
very
limited
I
do
have
a
limited
test
of
the
orchestrator
of
the
SEF
manager.
Orchestrator
module
now
happening,
it
says,
yeah
I
mean
it
just.
It
enables
the
orchestrator
and
then
it
makes
sure
that
it
can
call
SEF
Orchestrator
status
and,
and
that
that
includes
enabled
and
deep
sea,
and
it
makes
sure
it
can
call
surf
Orchestrator
service
list,
I
think
and
give.
B
B
B
That's
gonna
be
difficult,
I
mean
the
orchestrator
modules,
can't
stop
people
from
installing
things
or
upgrading
things
if
they,
if
somebody
goes
and
tries
to
do
that,
it
would
just
if
somebody
installed
the
wrong
an
incompatible
version
of
say,
rock
or
tipsy
or
ansible.
Then
the
orchestra,
the
module,
will
just
stop
working.
C
No,
no
I
am,
for
example,
I,
don't
know
if
for
deep
sea
is.
This
is
the
same.
That,
for
example,
in
my
case,
is
easy,
see,
for
example,
to
to
keep
the
safe
cluster
on
top
okay
without
any
change,
for
example,
update
the
external
okay
stator,
which
is
the
identical
runner
service,
and
in
this
case
this
can
cause
problems
in
the
in
the
class
step.
So
maybe
some
kind
of
off
check
when
the
orchestrator
model
is
is
running,
is
needed.
I.
B
C
C
Well,
we
are
running
the
the
stator
model
in
order
to
check
this
kind
of
things.
For
example,
for
me,
it
could
be
useful
well
to
check
in
the
moment
that
you
are
enable
enable
I
may
can
make
a
enabled
a
the
model.
I
think
that
it
could
be
good
to
check.
What
is
the
direction
of
the
standard
of
the
stator?
C
Is
the
mall
in
the
moment
that
you
are
doing
enable
the
the
model?
This
is
one
of
the
text
and
the
other
check
could
be.
Maybe
if
you
cut
one
kind
of
error
in
the
in
the
execution
of
it,
doesn't
matter
what
what
command
to
check
the
diversion
in
order
to
see
if
there
is
an
any
kind
of
problem
with
this.
B
B
B
C
He's
just
a
man
I
need
a
oh,
ok,
I
think
that
we
should
have
two
points
for
check
data
problem,
this
this
kind
of
problem.
One
one
point
is
when
you
start
a
model,
and
the
other
point
is:
if
you
have
any
kind
of
error.
Well,
you
can
check
that
the
external
of
the
stator
is
in
the
in
the
in
the
right
version.
I
think
that
there
is
one
of
the
this
could
save
a
lot
of
hours
of
investigating
what
is
happening
too.
You,
sir
yeah.
A
C
Yes,
the
problem
is
that
what
I
commented
on
Monday
I
have
been
investigating
what
is
happening?
Okay,
so
for
me,
it's
not
clear
in
this
moment
what
what
is
happening
is
it
if,
if
it
is
something
that
depends
of
my
environment,
I
am
using
a
container
or
is
if
it
is
something
that
comes
from
the
from
the
version.
I
think
that
the
new
version
of
the
danceable
Ronnie
yeah,
the.
C
That
mean
no
I
well,
I
am
using
now
the
last
version
of
the
ansible
running
project.
That
is
one
of
the
tools
that
is
using.
The
dancer
will
run
a
service
okay
and
the
problem
is
that
it
seems
that
the
ansible
running
tool
has
changed
part
of
the
fields
that
are
the
turn
it
in
in
a
synchronous
course.
C
This
is
basically
the
problem:
okay,
but
I
need
to,
but
I
am
taking,
but
I
am
problems
with
log
files.
Well,
as
always,
it's
not
easy,
but
what
I,
let's
see
if
I
today
I,
can
I
can
find
what
what
is
the
root
cause
and
depending
of
the
root
cause
I
will
raise
aback
in
the
in
the
f
track
head
in
order
to
have
cleared
this
problem?
Okay,
it's
what
we
discussed
money.
C
A
B
Yeah,
my
my
audio
has
been
a
bit
up
and
down
so
updates
for
me
that
the
deep
sea
is
deploying
the
orchestrator
module
more
or
less
depending
on
that
dashboard
thing.
So
the
next
thing
that
I
need
to
do
is
make
sure
that
the
deep-sea
Orchestrator
will
actually
print
out
the
urls
of
the
ice.
Cozy
and
Ganesha
endpoints,
but
I've
also
had
some
other
know,
an
Orchestrator
work
to
do
relating
to
upgrades
and
things
that
have
been
sort
of
switching
it
around
a
little
I
guess.