►
From YouTube: 2019-10-21 :: 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
So
might
be
able
to
join
us
later
so
in
and
in
10
to
15
minutes.
We
might
get
more
information
if
you
can
join
us
today.
A
Yeah,
in
any
case,
in
any
case,
welcome
to
today's
Orchestra
meeting.
A
And
then
I
guess
we
can
start
so
I've
just
hectic
as
a
new
pull
request
for
having
a
possibility
to
have
previews
of
a
drive
group
within
the
dashboard
and
the
orchestrators
and
everyone
else.
Basically,
in
Breakfast
31
over
21.
A
A
B
B
Like
one
one
wheel
is
not
here
today,
maybe
he's
still
traveling
I'm,
not
sure
something
anyway
yeah
and
that
there's
a
question
in
that
PR
about.
What's
that
volume
inventory
attributes,
we
really
need
to
collect
I.
Think
it's
the
question
of
what
well
will
the
Tax
Board
need?
Did
we
just
dump
all
of
the
properties
or
should
we
just
look
at
a
few
that
that
rook
thinks
it
needs
properties?
Do
we
need
that's
not
clear
yet.
B
Right
I
think
it
could,
and
that
was
that
was
the
question
I
raised
on
the
PR
as
well.
I
think
why
Miguel's
response
was
just
should
we
decouple
it
from
the
that
JSON
output
I,
don't
know
if
there's
a
need
to
as
long
as
we're
battle
between
versions
or
not?
Is
there
a
reason
not
to
tie
it
to
that
I
think
that
was
his
only
concern.
A
B
A
B
A
A
A
B
So
the
next
upcoming
release,
1.1
dive,
3
tentatively,
maybe
by
tomorrow,
I
think,
there's
a
couple
of
issues.
I
haven't
caught
up
with
over
the
weekend
that
make
sure
we
get
mixes
in
there's
an
OSD
configuration
issue
where
the
config
overrides
weren't
being
picked
up,
I'm,
not
sure
that
we
have
actually
Pro
steps
for
that.
Yet
there's
the
Russian
on
any
update
on
that
today.
C
I
checked
again
with
the
person
that
but
one
of
the
personnel
reported
an
issue
and
he
seems
to
be
confused,
but
by
what
should
be
there
or
not,
so
I
asked
him
to
check
again
because
he
was
he
kept
telling
me
that
the
IPS
were
still
generated
as
part
of
the
comp
and
I
told
him
yeah,
but
even
if
the
cuff
is
being
generated,
we
don't
care
about
that
config
because
we
don't
use
it
anymore.
So
please
check
that
it's
his
self
is
being
used
and
instead
and
like
I
guess,
that's
it.
C
B
Yep,
there's
I
think
once
we
resolve
that
there
was
there's
an
OSD
upgrade
issue,
not
sure
if
it
had
make
it
in
time
for
the
least
if
it's
tomorrow,
but
then
Tosh
he's
not
in
this
call
he's
working
on
on
that
upgrade
issues
so
with
basically
with
upgrade.
If
OS
DS
are
on
TVs
we're
skipping
reconciling
of
the
OSD
pods
and
we
need
to
make
sure
we're
always
reconciling
them.
D
B
B
B
D
A
A
Yeah
that
that's
more
something
completely
within
the
orchestrator,
because
Yogeshwara
is
the
only
component
who
really
knows
what's
going
on
right
now,
so
there
is
nothing
in
the
dashboard
where
the
desperate
can
can
fix
something
right
now,
but
yeah.
If,
if
you
want
to
help
me,
then
please
that
would
be
great.
G
F
F
Currently
this
pool
is
not
doing
peering
generation
its
well,
it
does
hearing
creation,
but
it
does
it
somehow
internally
and
for
example,
if
you
want
to
create
a
monitor,
you
would
have
to
create
a
keyring
on
an
authenticated
machine
with
an
admin
key
ring
to
deploy
a
monitor
and
a
different
machine.
You
will
have
to
copy
that
key
over,
so
it's
basically
a
two-step
process
and
which-
and
the
first
process
requires
you,
know,
running
safe
cluster
and
the
other
one.
You
can
just
use
safe
demon
with
it.
So
why
don't?
F
D
F
F
F
A
A
F
F
A
A
A
F
F
A
H
I
ask
the
question
real
quick,
and
maybe
this
is
just
a
stupid
question
and
let
me
know:
ok,
if
I'm
not
technical
enough,
but
from
what
I
understood
so
far.
One
of
the
reasons
I
joined
today
is
obviously
this
ft/min
discussion,
but
from
what
I
heard
is
part
from
Sage.
No
one
is
kind
of
willing
of
maintaining
this
whole
stuff.
They
just
kinda
came
up
with
it
and
merged
it.
Just
because
he's
safe,
just
like
yeah
well
looks
good
legend,
and
now
we
all
try
to
figure
out
hey.
This
must
be
useful.
H
D
D
What
he
meant,
no
I
mean,
of
course,
it's
useful.
It's
it's
a
tool
that
knows
the
intricacies
of
how
to
start
a
safe
demon.
I
mean
that's
complex
enough
that
we
apparently
need
such
a
tour
right,
and
we
have
code
like
we
have
code
for
that
in
deep
sea
also
apartment
related
code,
and
then
we
got
the
area
safe,
demon
PR,
which
essentially
does
this
same,
or
at
least
a
very
similar
thing.
So
the
idea
is
to
reduce
co2
application
and
use
the
same
code
for
this
right.
Yeah.
A
And
SIF
demon
was
created
in
order
to
make
it
consumable
by
everyone
else,
not
just
yes
as
a
choker
straighter,
it's
just
the
SS.
A
choker
setter
is
right
now
the
main
use
case
for
it
because
H
made
it
especially
for
the
SS,
a
choker
sweater,
but
the
the
behind
the
idea
behind
SEF
demon
was
to
make
it
generally
consumable
for
everyone
else
who
was
interested
in
that
war
topic
so
yeah.
We
are
definitely
in
scope
for
that
tour.
Right
now,
hey.
A
F
F
D
G
D
Little,
of
course,
but
yeah
I
mean
the
the
obvious
benefit
service
would
be.
You
know,
to
have
a
canonical
way
of
our
safe
demon
is
deployed,
and
you
know
that's
yeah.
How?
How
do
we
get
earrings?
Where
are
the
various
data
directory
stored
and
whatnot
I
mean
I,
don't
know,
I
think
it
makes
sense
to
have
you
know
some
some
tool
or
some
resource
that
has
like
the
way
to
do
it.
E
A
E
E
E
D
F
G
E
D
E
To
disagree
with
that,
because
that's
that's
kind
of
like
the
one
of
the
reasons
that
we
got
or
settling
and
putting
the
volume
inside
the
subtree
it's
like
well,
you're
not
I,
have
to
manage
any
separations,
but
except
we
do
because
we're
back
boarding
everything
back
to
luminous
and
things
in
luminous
are
not
exactly
the
same
II.
Not
it
is
so
now
you
have
to
inside
of
set
volume
which
is
inside
a
subtree.
You
have
to
say,
am
I
luminous
or
am
I
know
this
Oh
luminous?
Does
it
this
way?
E
None
of
this
does
this
or
way,
and
it's
not
that
complicated
and
it's
really
annoying.
But
then
again,
this
is
my.
My
experience
in
in
in
general
I
think
that
core
engineers
are
really
reluctant
to
have
anything
outside
of
the
tree
and
they
really
really
really
want
everything
inside
the
tree
and
once.
B
G
E
G
I
scuzzy
in
particular,
is
a
royal
pain
because
it's
out
of
the
surf
tree
and
we
need
to
synchronize
the
the
release
management
of
that
external
component
being
caused
depends
on
it
in
no
version
checks
things
we
wouldn't
have
to
do.
It
would
be
on
the
same
release
tree
but
I'm
I
for
one
I'm,
a
big
fan
of
keeping
all
components
that
are
related
in
depending
on
set
or
saccade.
It
should
be
in
the
same
guitry.
It
makes
things
so
much
testing.
D
But
that's
that's
exactly
the
point
and
the
question
we
have
to
ask
in
what
way
does
that
hypothetical
tool
that
doesn't
exist
yet
right
in
what
way
does
that
depend
on
SEF
itself
and
as
I
had
already
mentioned,
force
F
volume?
That
interface
is
actually
quite
quite
more
like
something
that
doesn't
really
merit
an
entry
for
3/4
such
a
tool
for
safe
demon.
I,
don't
know,
I
expect
that
the
interface
like
the
actual
dependency
on
SEF
will
be
fairly
stem
as
well.
B
As
an
example
of
I
mean
orchestration
is
a
place
where
Orchestrator
needs
to
be
an
independent
or
might
be
an
independent
version
from
the
thing
it's
pulling
so
in
the
case
of
rook
rook
is
has
its
own
tree
and
it
can
play
different
versions
of
Ceph,
because
it's
decoupled
and
and
that's
that's,
been
the
way
we've
been
able
to
really
make
this
happen.
If
we
were
in
tree,
it
would
just
be
next
to
impossible
to
play
different
versions
of
Ceph
or
support.
Different
versions
of
stuff
being
able
to
have
an
independent
element.
B
E
That
I
think
that
is
really
important,
like
finding
issues
and
being
able
to
like
get
them
out
as
soon
as
possible.
I
think
that's
great
and
being
a
new
tool
or
new
set
of
modules.
That
is
definitely
what's
going
to
happen.
This
is
going
to
go
out
and
we're
gonna
need
more
features
in
more
fixes
and
faster,
especially
because
it's
new
fixes
and
changes
are
going
to
come
out.
E
So
quick,
we're
going
to
want
to
have
fix's
right
away
and
we
were
not
gonna
be
able
to
because
wouldn't
have
to
wait
now
if
it
starts
as
an
outside
thing
and
then
eventually
moves
into
this
source
free
when,
when
it's
like
super
stable
and
things
are
not
moving
as
fast
anymore.
That
could
be
one
one
path,
but
the
our
way
around
is
just
so
tricky
even
right
now,
when,
when
I
think
sage
has
sort
of
like
I
agreed
like
oh
well,
okay,
so
volume
might
be
like
a
good
thing
to
take
it
out.
F
A
F
F
D
F
With,
of
course,
you
know
design
documents
and
and
obviously
gathering
feedback
from
various
parties.
Good
and
just
know,
cool,
that's
good,
and
for
now
we
can
start
is
well
now.
Okay,
well,
I,
don't
know
where
and
where
to
start,
but
maybe
that's
where
to
put
the
code,
then
we
can
wait
for
for
stage
and
his
opinion,
yes
and
and
hash
it
out
later.
Probably,
but
I
mean
currently,
this
is
more
or
less
just.
You
know,
rewriting
the
existing
things
and
then
later
and
we
can
decide
where,
to
put
it
yeah.
F
F
G
A
A
C
Yeah,
let's
send
yeah.