►
From YouTube: Ceph Developer Summit Quincy: Orchestrator Follow-up
A
A
B
A
A
B
A
B
A
A
B
A
A
B
B
Yeah
at
the
end,
yeah,
that's
it
might
be
redundant.
That's
I
mean
those
yeah.
Let's
think
of
the
same
thing,
I
can
pull
that
off.
Well,
I
don't
yeah,
I
mean
that's
the.
If
we,
if
the
agent
gets
us
the
reconciliation
speed
that
we
want,
then
we
can
just
call
that
one
done
partly.
I
use
this
list
also
just
so
there's
a
when
we
finally
merge
and
we're
looking
at
the
end
of
the
release
and
we're
trying
to
build
this,
a
high
level
list
of
the
things
that
we
delivered.
A
I
mean
I
would
my
idea
would
be
really
to
focus
on
improving
the
architecture
and
making
sure
we
can
update
the
dashboard
pretty
fast,
even
on
really
large
clusters,
instead
of
maybe
sparing
one
or
two
ssh
connections
or
yeah,
make
cutting
the
the
the
time
to
carry
a
host
by
half,
because
it's
not
going
to
it.
It's
increasing
the
the
the
static
portion,
it
it's
just
a
yeah,
it's
the
constant
part,
you're,
reducing
the
constant
part,
but
you're
not
really
having
a
big
impact
on
larger
clusters.
B
A
B
B
Yeah,
I
just
that
the
thing
I
I
started
a
pull
request
for
this
and
I
just
kept
running
into
like
annoying
technical
issue.
After
annoying
technical
issue,
it's
just
really
complicated
because
the
manager
has
so
many
ports
and
they
can
come
and
they
can
go
depending
on.
If
you
like
turn
on
a
module,
then
suddenly
the
aj
proxy
configuration
has
to
change
and
port
conflicts
demons
that
weren't
conflicting
before
might
conflict
whatever
it
just
got.
Really
it
was
getting
really
complicated
and
I,
whatever.
B
B
B
B
B
B
A
A
B
B
B
B
A
B
So
we
right
now
we
do
it
through
the
config
options.
That's
it's
sort
of
independent
of
that
video,
but
there
are
certain
limitations
to
what
I
think
yeah.
My
question
would
be
what
the
what
the
requirement
there
is,
but
we
already
have.
We
already
have
it
some
degree
like
if
you
set
up
for,
if
you
set
an
option
on
a
single
osd,
you
can
tell
it
what
numa
node
to
use
okay.
B
A
B
B
B
A
B
A
A
B
A
B
B
We
want
all
of
our
stress
tests
to
be
migrated
to
use
that
video
where
possible,
and
then
I
get,
I
think,
in
a
few
cases,
they're
like
they're,
actual,
like
step
fading
stress
tests
that
we
want,
for
example
like
the
nfsha,
for
example.
We
should
probably
create
a
thrashing
truss
test.
That's
like
destroying
ganesha
nfs
servers
and
running
a
workload
and
making
sure
that
clients
are
behaving
and.
A
B
B
A
A
B
C
B
C
Yes,
because
we
talked
about
that,
this
process
is
probably
is
something
that
should
be
executed
the
interactivity
okay.
In
order
to
see
what
happened
in
the
in
the
moment
that
you
are
creating
it's
it's
part
of
the
architecture
topology,
so
maybe
a
with
art
or
something
like
that
in
the
dashboard
is
going
to
help.
A
B
B
B
But
I
would
be
inclined
to
leave
this
card
off
until
like
it
seems
like
the
set.
Fadem
part
is
actually
just
the
dashboard
needs
to
when
you.
If,
if
the
dashboard
is
going
to
do
like
realm
and
zone
management,
then
it
should
like
follow,
which
apply
and
actually
create
you
create
them
in
the
dashboard.
But
I'm
not
sure
if
it
does
that
yet.
A
A
B
Well,
it
yeah
yeah.
I
think
it.
I
think
it
could
get
away
with
doing
both,
because
it
could
show
all
of
the
realms
and
zones
based
on
the
realm
and
zone
config
and
if
you
create
one
it'll,
also
deploy
it
for
you,
but
if
it
already
exists,
then
it'll
you'll,
just
see
it.
You
won't
be
able
to
delete,
won't
work
properly.
I
guess
it
won't
shut
down
the
demons
for
you,
but
that
don't
happen
on
this
one.
B
A
B
A
B
I
mean
it
seems
like
an
easy
thing
to
do,
would
be
to
not
persist
them
and
then
have
them
disappear
if
manager
restarts,
because,
most
of
the
time
the
manager
doesn't
restart,
and
these
are
sort
of
cosmetic
anyway,
just
to
see
I'm
creating,
you
know
four
nfs
servers
or
whatever
it
is,
or
I'm
deploying
image.
Busties.
B
B
C
B
C
It's
not
possible
to
execute
the
the
fatm
rmrm
cluster
in
each
of
the
host.
In
fact,
we
are
using
a
file
was
file
that
is
doing
that.
Okay,
so
I
think
that,
for
example,
if
we
have
a
cluster
and,
for
example,
in
the
theft
cell,
we
are
moving
the
monitor
and
the
manager
to
the
to
the
host
where
we
are
running
the
theft
cell.
Okay,
and
after
that,
we
are
using
an
rmrm
cluster
in
each
of
the
host.
We
are
going
to
remove
everything.
C
Okay,
and
the
only
thing
that
we
are
going
to
need
to
to
clean
are
ost.
Okay,
I
know
is
this:
is
infrastructure?
Okay,
that
I
think
that
is
easy,
because
we
have
the
fav
theft
volume
command.
Okay,
and
after
that,
even
we
can
remove
the
files
that
we
have
in
the
backlift
theft
configuration
and
backlog
theft
configuration.
So
I
think
that
it's
perfectly
possible
to
remove
everything
to
have
only
one
host
and
in
the
moment
that
you
have
only
one
host
you.
C
A
C
A
C
You
can
do
that
because
you
have
information
in
the
organizator
about
what
is
the
composition
of
the
cluster,
but
we
can
do
also
from
the
from
the
third
cell
and
sorry
from
from
there
from
the
horse
directory
with
the
theft
in
the
embinary.
But
if
you
want
to
do
that
from
the
inside
orchestrator,
I
think
that
even
that
is
possible.
C
A
B
Yeah,
I
think
we,
I
think
it's
yeah,
I
think
we're
better
off
having
a
a
cfd
mrm
cluster
with,
like
seems
like
we
need
two
things.
We
need
stuff
adm,
like
zap
zap,
all
that
you
pass
an
fsid
and
then
have
for
arm
cluster
have
an
optional
flag.
That
includes
the
zap
all
for
that
same
fsid,
so
you
can
do
it
in
one
command
instead
of
two
and
then,
if,
when
you're
gonna,
do
that
when
you're
gonna
do
the
cluster,
you
just
do
like
a
one
line:
bash.
C
A
B
B
A
A
A
A
C
B
C
B
A
It
actually
works
already
and
I've
added
that
into
the
into
the
other
pad,
but
I
agree
that
we
need
to
have
some
kind
of
it.
It's
too
flexible
right
on
one
hand,
it's
super
flexible
to
have
those
config
options
overwritten
by
better
specifier,
and
on
the
other
hand,
we
we
have
too
many
competing
ways
to
do
that.
Right
now,.
B
B
A
B
A
Yeah,
just
that
would
be
my
preferred
option
to
have
one
way
to
just
update
all
the
different
default
container
images,
and
not
you
have
to
to
change
that
config
option
for
the
save
base
image.
You
have
to
set
this
config
option
for
the
monitoring
images
you
have
to
set
this
their
respect
property
for
the
proxy
stuff
having
having
one
workflow
that
does
update
all
the
container
images.
A
A
B
B
B
C
I
think
that
to
have
different
versions
in
for
each
diamond
to
open
the
tool
to
unexpected
behaviors
and
problems
now
well
difficult
to
to
resolve.
Okay,
I
think
that
well,
if
we
need
to
we
decide
to
to
deploy
a
service,
rafana
monitoring
monitors
manage
whatever.
Now
we
need
to
use
the
same
image
for
all
the
diamonds
of
one
service.
B
Yeah,
I
guess
I
would
be
inclined
to
wait
until
we
have
a
an
actual
use
case
for
somebody
who
needs
multiple,
different
custom
images
before
we
worry
about
it,
because
it's
it's
work
to
support
that
or
whereas
what
we
have
now,
but
it
still
lets
you
customize
it.
It
just
assumes
that
all
your
grafonites
and
some
in
the
cluster
are
the
same,
which
I
think
is.
B
B
A
B
B
If
I
think
this
might
be
a
problem
with
ingress
in
general,
if
you
like,
if
you
delete
the
backend
service
and
the
front-end
service
like
it
might
throw
an
assertion
or
in
some
cases
I
noticed
that
in
like
the
prepare,
create
and
generate
config
functions,
if
those
through
assertions
they
get
swallowed
and
aren't
shown
anywhere,
which
made
the
booking
interesting.
Those
are
all
these
are
all
sort
of
unrelated
to
nfs,
typically,
but
we
should
clean
that
up
at
some
point.
B
Yeah,
I
mean
one
of
the
things
that
I'm
wondering
about
the
well
the
biggest
thing.
Actually,
that
has
to
happen
with
the
nfs
thing
is
just
testing
like
it.
It
all
fits
together.
The
way
that
it's,
I
think
it's
supposed
to
fit
together,
but
I
don't
need
to
actually
scale
the
demons
and
make
sure
that
I'm
just
guessing
at
the
aja
proxy
configuration
and
we
need
to
actually
test
it.
B
I
think
the
thing
that
most
worries
me
is
that
by
default,
the
nfs
service
is
on
port
2049,
the
nfs
port,
but
if
you're
going
to
use,
then
that's
the
one
that
should
be
on
2049
and
the
backend
nfs
port
should
probably
be
something
different
in
case
they
get
scheduled
on
the
same
hosts,
20
40,
49
yeah,
and
so
I'm
wondering
if
the
nfs
service
should
default
to
a
different
port,
but
the
expectation
that
you'll
then
apply
h
a
or
or
not.
I
don't
really
know.
B
Oh,
I
guess
this
is
sort
of
related.
It
came
up
in
the
review.
There's
there's
still
this
osd
spec
affinity,
thing
yeah.
I
was
always
confused
by
this
before
I
never
fully
understood
it,
but
I
think
now
that
we
have
the
service
name
property
on
all.
The
demons
like
three
you
can
is
that
obsolete
now.