►
From YouTube: 2020-02-10 :: 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
B
A
B
A
A
Well,
having
having
it
called
safe,
a
DM
blah
blah
blah
make
sense
for
force
FIDM
and
having
it
look
to
be
called
for.
Farook
would
make
sense
right
yeah,
but
they
want
to
keep
it
as
one
thing.
Well
right,
so
well,
that's
the
way
it
is
implemented
and
that's
the
way
the
CLI
is
supposed
to
be
kind
of
a
unified,
unified
thing
and
it
was
called
Orchestrator,
which
is
it's
a
name
and
I.
Think
it's
it's
a
good
name
and
every
weight
typing.
B
B
D
C
C
A
A
A
A
We
have
at
the
request
of
pain,
let
Orchestrator
blind
Pisan
thing
that's
created
in
in
the
work
since
July
and
of
July
and
I've
paid
to
get
it
merged
because
of
various
reasons.
One
was
now:
we
don't
want
generated
files
in
itself
repository
or
no.
We
we
don't
want
to
depend
on
a
on
a
repository,
that's
not
owned
by
other
look
or
safe
or
no.
We
don't
want
that
because
it
should
not
be
long
in
the
in
the
rook
source
tree
or
no.
A
We
don't
want
that
because
it
would
create
our
core
dependencies
or
I.
Don't
know,
I
really
cannot
get
this
thing
much
if
we
don't
count
200
where
he
foo
was
against
it.
So
I
need
a
resolution
wiki
frozen
board,
then
we
go
I,
need
your
approval
and
and
name
because
I'm
really
I
really
cannot
get
this
in.
Without
someone
absolute
result.
Okay,.
D
D
And
the
Python,
quiet
and
cold
in
the
in
the
targets.
Okay,
so
I
think
that
well,
the
only
way
to
have
something
clear
about
what
we
are
doing
in
this
moment.
Okay,
is
to
put
the
take
the
Python
classes
in
the
in
the
repository
okay,
because
in
this
element
there
is
no
place
for
four
forties
files.
Okay,
so
in
this
moment
what
we
need
to
have
is
to
have
clear
what
is
the
mention
of
look
that
we
are
using
and
to
fix
this
in
in
some
way.
D
Okay
and
I
think
that
the
right
way
to
do
that
is
to
have
his
Python
generated
classes
in
the
repository
just
in
this
moment.
Okay,
because
the
right
way
to
do
that
is
to
want
to
stab
this
as
a
third-party
dependency
when
we
are
going
to
start
the
manager
in
one
host.
I
think
that
this
is
the
right
approach.
But
in
this
moment
this
is
not
possible,
so
I
think
that
the
best
solution
is
just
to
put
they
have
their
files
in
in
in
the
repo
and
I
think
that
is
something
the
temp
tempora
I'm.
D
A
I'm
kidding
now,
no
it's
okay,
so
so
Kieffer
doesn't
want
the
Eastern
rated
files
in
this
F
repository
Sebastian
hunt
does
not
want
this
generated.
Files
in
the
repository
Travis
can
get
it
into
into
the
rook
self-organization
and.
C
D
D
Okay,
let
this
this,
let's
make
a
some
kind
of
agreement
between
everybody.
I,
think
that
in
this
moment,
I
think
that
the
most
simple
solution
is
just
to
put
in
the
the
files
in
the
repository,
and
yet
we
should
remove
them.
Okay,
but
if
not
in
what
is
the
solution?
Okay,
because
I
think
that
is
good
to
have
everyone
can
have
is
if
someone
preferences
but
I,
think
that
we
need
a
solution
and
even
for
example,
this
morning,
when
I
have
been
when
I
believe
in
the
pull
request.
D
Okay,
I
haven't
got
the
plain:
the
hookah
in
Python
files
available.
Okay,
so
for
me
it
could
be
more
easy
to
reveal
the
code
if
I,
if
I
had
the
files
in
some
place,
but
if
I
want
to
have
these
files.
I
need
to
generate
this.
So
in
this
moment,
I
think
that
the
resolution
is
just
to
put
the
de
files
in
the
repository
and
then
when
we
have
the
final
location,
we
can
become
move.
But
in
this
moment
we
need
some
kind
of
solution.
C
D
A
A
A
D
D
C
Alright,
one
click
one
really
actually
a
sec.
We
write
an
agenda
doc
going
for
our
yes,
we
have.
We
have
a
snooze.
C
Right
go
ahead
with
this
ela
cool.
All
right,
I
have
a
second
test
branch
building
with
right.
Now
it
already
passed
before
run
it
again.
It's
almost
done
so
I
might
as
well
just
run
it
again
fact:
it's
ready
to
go
right
now,
I'll
schedule.
C
Sorry
one
thing
before
we
talk
about
the
CLI,
the
this
one,
the
pod
man,
chillin
I,
just
got
a
plus
one.
It
looks
like
the
the
pod
man
person
chimed
in
to
explain
why
it's
needed
yeah.
C
The
only
other,
substantial
difference
is
that
our
unit
file
runs
it
in
the
foreground
and
there's
works,
but
I
don't
think.
There's
any
I,
don't
think
that
matters
okay,
I
want
it's,
certainly
not
relevant
to
the
shutdown
part
and
it
seems
clear
in
general,
I,
don't
know
why
they
chose
to
do
it
that
way,
but
they
did
so
and
we
actually
have
to
do
the
foreground
version
because
we're
running
a
bath
scripts
that
runs
pod
man
instead
of
running
pod
man
directly
in
the
unit
file,
because
it's
all
the
demons
are
a
little
different.
Oh.
C
C
A
C
C
Should
use,
but
we
should
put
that
in
monitor
config
database
so
that
it's
not
like
pass
really
orchestration
layer.
That's
my
thinking
like
what
the
rgw
it
used
to
be
that
arch
W
had
a
million
options
for,
or
an
SSL
certificate,
and
all
this
random
crap,
and
now
it
has
nothing
except
for
what
the
Romans
own
is
and
it
just
it's
going
to
pull
it
out
of
the
config
database.
Oh.
A
Yeah,
if
you
look
into
into
my
greenish
part,
then
it's
actually
not
that
complex
right,
you
have
an
FS
brothers,
gateway,
MDS,
add
or
remove,
or
you
have
premier
cells
every
team
arrow
ad
without
a
name.
So
if
you
come,
if
you
look
at
do
it,
then
the
type
the
explicitly
defined
type
is
not
much
different
than
an
enumeration,
except
that
not
actually
an
enumeration.
But
it's
part
of
the
specifications
of.
C
I'm
not
quite
following
I,
think
well,
I
haven't
I,
mean
so
I
think
for
things
like
our
M
having
a
single
command
is
simpler,
I
mean
they're.
Cool
things
here
want
to
fix.
I,
guess
one
is
that
it's
annoying
that
everywhere
it's
type
dot,
ID
and
then-
and
this
is
the
one
place
where
you
have-
you
can't
actually
do-
that
it's
type
space,
ID
or
ID
prefix
or
whatever
I'd
like
to
consistent,
make
that
consistent
and
then
the
other
thing
is
it's
just
a
cluttered
interface.
C
A
C
C
A
C
C
C
A
What
about
moving,
add
or
update
or
RM
before
so,
but
right
now.
A
C
C
A
C
C
C
C
D
C
Cuz
they're,
basically
the
same
thing,
except
that
the
ad
case
like
if
you
look
at
the
current
code,
the
ad
case
is
just
a
broken
version
of
update.
If
anything
right
I
mean
that's
that's.
This
is
just
a
bug
by
like
right
now
you
can
do
envious,
update
through
one
and
it
will
to
play
whatever
and
yes
demons
and
if
you
do
MDS
add
food
to
it.
Whatever
it
breaks,
it
complains
that
there
aren't
enough
host
names
and
blah
blah
blah.
We
really
really
really
need
to
documentation
the
photo
define.
A
C
C
D
Okay
in
this
moment,
if
you
see
what
we
have
paka
stator
MD
lesson
in
NPS
ad
hit
a
value-add
and
doing
things
okay.
This
is
what
we
have
in
this
moment
and
the
order
is
you
have
the
orchestrator
happy?
Okay,
then,
if
you
are
going
to
do
something
with,
for
example,
the
MDS
service
or
the
MDS
functionality,
then
you
should
add
MDS
okay
and
then
you
have
another
possibility
to
manage
or
together
all
the
things
that
you
are
going
to
do
with
MDS,
okay
and
I.
I.
Think
that
this.
C
D
C
Yeah,
it's
just
it's
just
tedious,
because
every
service
type
has
these
three
methods
that
you
have
to
specify.
Every
time
you
make
a
change
to
like
the
place
of
an
argument.
You
change
it
like
15
different
function,
definitions,
it's
the
same
in
both
the
ad
and
yet
I.
Could
it's
it's
really
hard
to
maintain
right
now,
I.
C
So
we
could
call
this
service
supply.
Is
that
what
you're
saying
you're
suggesting
I'm
QCD
I'd
call
that
service
supply
just
like
a
pipe
basically
head
sister
radar
update.
A
A
C
C
A
C
A
A
Without
fool,
then
I
would
make
it
like
so
yeah.
It's
different.
C
Like
I'm
trying
to
say
that
when
you're
doing
when
you're,
adding
a
you're
explicitly
adding
a
demon
they're,
not
interacting
with
a
service
but
you're
implementing,
adding
a
specific
demon
then
apply
as
a
weird
verb.
Think
that's
what
I'm
saying
I
think
it's
demon
add
think
it
should
be
demon.
Add
RM.
C
D
C
D
C
D
C
A
D
D
C
A
C
A
C
D
C
C
C
I
mean
it's
been
there
since
nimac
or
well.
No,
ok,
so
in
octopus,
they
added
so
that
you
can
have
a
big
section.
That's
doesn't
have
this
dot,
put
it
up
last
gibberish
part
and
it'll
still
pull
it
in.
So
you
get
all
the
all
the
preceding
hierarchical
dot,
delimited
things.
That's
new
an
octopus
and
that's.
C
A
C
Not
really
sure
what
those
configurations
are,
but
if
assuming
that
there's
a
name
for
the
dice
cozy
thing
like
if
it's
client
I
scuzzy
gateway
dot,
something
about
whatever
like
we
can
just
put
it
in
the
config
database
and
worst
case
stuff.
Atm
can
go
pull
it
out
of
the
config
database
right
if
it
needs
it
and
not
pass
it
on
the
command
line.
C
I
mean
just
trying
to
think
this
through
it
works
for
rgw,
like
all
that
right
now,
the
only
thing
that
stuff
ATM
does
for
rgw
is
when
you
create
this,
when
you
create,
when
you
do
this
command,
say
it
would
it
does
it
sets
that's
configs
that
client,
I
VAR
g
w
dot
realm
equals
out
of
your
realm,
equals.
C
C
C
C
C
Or
and
it
sort
of
in
first
what
it
thinks
it
should
be
like
it
it's
it
knows
that
the
realm
is
the
second
thing
in
the
zone
as
the
third,
but
it's
sort
of
like
implicit,
it's
hard
to
it's
not
well
document,
it's
not
obvious
from
the
interface
or
we
do
this
and
I
guess.
If
we
do
this,
does
that
mean
that
we
should
have
an
apply
for
every
type?
I
guess
that's
what
I'm
wondering.
C
Yeah,
just
that
is
harder
to
sort
of
I
mean
what
I
really
want
to
do
with.
This
is
established
a
new
naming
scheme
and
make
sure
that
work
is
also
using
it
so
that,
regardless
of
whether
you're
using
rook
or
Steph
atm,
if
you're,
going
to
configure
rgw,
you
put
it
in
this
part
of
the
of
the
configuration
database.
C
C
This
that's
work
apply,
and
some
of
these
won't
even
exists
like
Prometheus,
for
example,
we
don't
actually
need
to
create.
It's
really
just
gonna,
be
bad.
Just
thought
host
that,
because
we
don't
need
to
teach
rook
how
to
provision
Prometheus,
or
at
least
we
don't
plan
to
write
or
node
agent
or
whatever.
But
a
lot
of
this
stuff
is
Seth
idiom
specific
and
it's
really
just
the
demons
are
you're.
Doing
like
SF
or
CH.
Add
you
know,
crashed
on
hosts
those
post,
although
that
happens
automatically
currently.
C
C
C
Otherwise,
to
add
a
new
configuration
forever,
you
have
to
teach
argit
if
you
understand
it
the
config
option,
and
then
you
have
to
have
the
right
it
like
in
in
rook,
in
order
to
or
even
in
general
like
in
order
to
change
the
port
number
for
an
rgw
or
change.
The
configuration
parameter
like
you
shouldn't
have
to
go,
read,
deploy
the
container,
get
the
set
configuration
handles
all
that
you
should
just
update
the
configuration
and
maybe
like
reload
it
or
something.
C
C
A
C
A
C
I'm
talking
about
the
internal
interface
up
here,
but
right
now
we
have
a
service
supply.
I
could
keep
fettle.
So
would
we
have
one
method
that
has
a
spec?
You
know
Jeff
service
supply,
Oh
spec,
and
then
you,
you
know
if
back
instance
of
or
whatever
this
thing
is
the
vert.
Whatever
version
of
that
isn't
Python
just
send
it,
you
ate
all
the
different
types.
If
we
have
a
type
in
the
service,
spec.
C
C
A
Lots
of
letters
don't
have
names
yeah,
actually
only
RW,
n,
FS
and
NDS
have
names,
and
even
for
MDS,
it's
not
really
that
sure
that
name
II
actually
work,
though
what's
the
fastest,
oh
yeah,
it
doesn't
actually
work
nowadays
to
have
an
NDS
bound
to
a
file
system.
Yes,
yep
perfect,
so
in
the
SFF
have
a
name
that
the
w
have
a
name.
Nfs
has
a
name
and
that.