►
From YouTube: 2019-03-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
NĂ©cessaire
Travis
isn't
going
to
join
us,
don't
make
it
less
missing
anyway,
lessons
learned,
orchestrated
or
attending
PR
I
haven't
open
for
error
handling,
turned
out
that
the
release
candidate
to
or
Nautilus
was
delayed
this
for
over
a
week.
Now,
though,
if
I
had
knew
that
before
then
I
could
have
merged
that
already
last
week,
but
on
the
other
hand
it's
kind
of
a
medium
risk
PR
and
we
have
suboptimal.
A
B
C
D
So
we
we
access
safe
ice,
cozy
gateways
with
a
REST
API
through
a
rest
of
API
and
and
for
what
we
do
to
know
that
the
URL
for
that
REST
API,
is
that
we
fill
in
the
service
URL
attribute
in
the
service
descriptor
quest
of
the
orchestrator,
as
we
have
already
discussed
previously,
so
the
the
catch
today
was
that
I
enabled
HTTPS
SSL
support
in
in
surface
KZ,
API
and
and
now
I
need
to
know
if
I
need
an
option
to
basically
tell
the
dashboard
to
to
not
validate
the
the
SSL
certificate.
D
Otherwise
I
can
access
the
API
so
well.
That
is
easy.
If
I
have
a
configuration
option
in
were
just
to
tell
to
force
it
to
to
avoid
the
validation
when
I
start
thinking
that
how
I'm
going
to
get
that
information
from
the
orchestrator.
That
is
not
that
clear
and
and
then
I
start
thinking.
Oh
wait!
Actually
you
have
more
information
that
we.
Whenever
we
want
to
access
the
REST
API,
we
have
more
information
that
we
require.
A
D
A
D
Always
need
the
some
way
to
pass
the
information
that
this
kind
of
things
to
access
the
REST
API,
so
I'm,
not
sure
how
you
guys
want
to
these.
This
kind
of
information
to
be
populated
on
the
service
descriptor
class
I.
A
Don't
know
thunder
on
the
on
one
side,
we
would
have
that
thing
implemented
for
all
Orchestrator.
A
A
It's
not
something
that
information
provided
to
the
dashboard,
but
more
of
a
hint
that
this
certificate
is
invalid
or
not.
And
if
yes
should
it
ignore
the
certificate
and
I
don't
know,
and
would
it
be
a
big
deal
to
implement
that
implementation
that,
secondly,
in
the
dashboard
very
similar
to
the
graph
Anna,
no.
D
D
To
force
the
avoidance
of
the
Thistle
verification,
maybe
we
can
also
use
the
same
command
even
if
the
DI
Scaasi
gateway
urls
come
from
the
orchestrator.
D
Maybe
that's
the
the
option
but
but
but
then
we
also
need
what
about
the
credentials.
I.
A
A
On
the
other
hand,
the
credentials
are
stored
within
the
manager
module
anyway
in
the
dashboard
module.
So
as
long
as
this,
as
long
as
it
is
stored
within
the
manager,
everything
should
be
fine,
but
then
discover
the
I
think
that
among
commands
are
in
plain
text
written
down
to
the
audit
log.
So
every
man
command
that
contains
passwords
written
down
to
the
log
file.
E
I
think
that,
depending
of
the
external
case
data,
probably
the
configuration
that
we
are
going
to
need
is
going
to
be
different,
for
example,
in
the
uncivil
Orchestrator.
Now
we
are
using
one
share
one
password
and
when
we
are
using
not
we
are
doing
not
only
that
validating
the
certificates,
but
this
is
going
to
change.
We
are
going
to
use
TLS
a
la
gente,
fication,
okay,
and
this
is
something
that
is
going
to
happen.
Only
it
or
not.
E
You
will
decide
to
use
another
another
kind
of
approach,
so
maybe
we
will
need
this
kind
of
to
specify
in
the
configuration
of
the
R
cos
theta,
this
kind
of
things
I
think
dependent
independent
of
the
external
or
cos
theta
that
you
are
going
to
use.
Probably
you
will
need
different
settings
and
we
will.
We
need
a
place
where
what
to
put
these
settings,
it
could
be
they.
A
D
E
Sorry
Natalie,
it
is
these
last
week
I
has
been
working
in
in
other
things,
and
it
seems
that
that
is
a
stop.
My
plans
is
to
start
this
week
with
the
modifications
in
the
ansible
runner
service
in
order
to
room
with
TLS
and
let's
see
if
it
it
could
happen
if
I
am
a
little
bit
with
a
little
bit
of
the
leg,
because
I
wanted
to
finish
things
last
week
and
it
was
impossible
to
for
me
to
finish
so.
F
A
F
B
F
A
F
Yes,
give
it
time
yeah,
the
only
I'm,
the
only
one
I
was
worried
about
was
the
pull
request
from
Volker
that
fixes
the
localized
config
options.
I
think
that's
still
broken
in
its
current
form,
but.
F
F
Is
is
there
somebody
still
filling
with
that.
A
I
had
made
a
review
of
the
progress
and
I
think
I'm
going
to
look
at
it
and
then
it's
it's
basically
finished,
at
least
from
the
command
line,
the
facade
up.
So
then,
we
are
now
waiting
for
that
thing
in
deep
sea
and
in
the
DP
Orchestrator,
and
you
know
maybe
maybe
rook
and
the
rock
Orchestrator
yeah.
F
F
F
B
F
Next
blocker
or
whatever,
but
it's
like
it's
one
of
those
things
where
I
think
the
version
in
some
toss
is
too
old.
We
need
to
like
pull
something
out
of
that
bowl
or
something
like
that.
Can
you
help
out
with
that
I,
don't
know
if
it's
just
like
a
hack
in
that
docker
file
or
something
to
like
grab
a
random
yeah.