►
From YouTube: Ceph Orchestrator Meeting 2021-07-27
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
Okay,
so
alfonso
you
are
the
the
fist
with
anything
in
the
agenda.
A
Hi
no
yeah.
I
I
pointed
this
because
I
I
don't
know
who
said
if
you
receive
my
message
on
my
erc.
B
A
B
A
B
A
And
the
only
thing
remarkable
well,
two
things
to
comment:
the
one
is
that
in
the
original
code
you
are
setting
up
a
user
called
dashboard,
but
I
realized
that
we
need
an
integration
on
it
when
there
are
more
than
one
real,
because
the
users
are
very
real.
So
right
now
what
I'm
doing
is
creating
the
same
user,
but
on
each
area
that
we
can
retrieve,
and
the
other
thing
is
that
you
erased
some
documentation,
but
I'm
conversation
with
ernesto,
because
maybe
some
some
options
that
are
already
there
like
the
scheme.
A
Nivea
are
useful
still
for
some
users,
not
sure
about
deleting
all
the
options
so
well,
if
you
want,
we
can
set
up
a
brief
meeting
on
this
week
in
order
to
to.
B
A
Okay,
so
yeah,
and
then
I
will.
I
will
push
one
or
two
comments
in
that
pr
and
let's
see
if
we
can
then
can
merge.
Of
course,
in
the
driver's
side
there
is
more
work
to
be
done,
but
at
the
very
least,
with
this
adjustment
we
can
go
for
it
and
the
credentials
are
aligned
in
both
sides.
The
video
and
therefore
okay,.
B
A
A
Steps:
okay:
yesterday,
we
commented
something
in
the
orchestrator
meeting
what
I
think
that
what
is
even
good
to
comment
and
to
and
to
and
to
see
what
are
going
to
what
are
going
to
be
the
next
steps.
Okay,
ankus
is
here
in
the
meeting:
okay,
because
what
it
seems
that
the
local
storage
operator
it
is
working
on
the
inversion
4.7
and
what
is
is,
I
think
that
is
very,
very
linked
directly
to
to
open
shift.
A
B
So
I
guess
at
a
high
level
I
think,
they're.
I
view
this
in
two
two
conversations.
The
first
is
like
what
what
what
is
the
short
term
stuff
that
we
want
to
do
to
make
osd
creation
or
removal
work,
given
the
current
date
of
brook
and
lso,
and
I
think
joseph's
pull
requests
are
in
pretty
good
shape.
B
D
D
D
B
Okay,
I
mean
maybe
this
is
maybe
we're
not
going
down
the
right
path,
because
I
was
I
was
viewing.
The
osd
creation
via
the
device
sets
as
sort
of
a
possibly
a
short
term
path
that
just
triggered
the
creation,
and
then
we
removed
them
as
soon
as
they
were
created,
but
ideally
there
would
be
just
a
more
imperative.
B
Please
go
create
this
osd
that
we
could.
We
could
call.
So
I
don't
know
if
I
don't
know
what
changes
are
necessary
to
make
the
device
that
removable
piece
work
but
or
if
they're
needed
anyway,.
A
Okay,
but
what
I
I
think
that
this
could
be
what
the
defense
plan-
okay
and
try
to
make
it
work
with.
With
this,
this
kind
of
work
with
the
local
storage
operator,
installing
manually
the
local
storage
operator
and
using
the
the
proof
request
that
joseph
has
done
in
order
to
to
you
to
use
the
information
from
this
operator
and
a
part
of
that,
we
need
to
to
do
some
modification
in
the
rook
project
in
order
to
allow
the
removal
of
osds
yeah.
D
B
D
A
Okay
travis:
well
maybe
you
can.
You
can
explain
joseph
myself,
okay
about
what
are
the
modifications
that
are
required
and
we
can
work
with
that.
Okay,.
D
Yeah,
the
in
the
rook
issue
I
opened.
I
can
find
a
link
in
a
minute
here,
but
it
won't
be
trivial,
but
because
there's
just
how
we're
dealing
with
desired
state
and
actual
state
inside
the
operator
is
a
little
confusing
around
these
osd
settings
with
device
sets.
So
it
might
probably
be
quicker
if
someone
who's
already
been
in
the
code
is
there
but
yeah.
Maybe
I
can
take
a
quick
look
at
that
today,
or
at
least
tomorrow
to
see
if
there's
something
we
can
do
with
the
shortcoming.
A
B
Okay
and
on
the
on
the
removal,
I
mean
that
the
short
term
work
around
with
that
rook
issue.
Well,
I
guess
the
short
short
term
is
that
the
the
r
back
over
quest
needs
to
be
merged
and
then
just
as
full
requests
can
be
merged,
but
then
on
the
adding
osds.
There's
the
there's
the
issue
that
you
open
travis,
but
in
the
meantime
we
can
just
the
manager
cannot
remove
from
the
device
set
just
leave
it
there.
Definitely
and
that'll,
be
okay
for
the
time
being.
B
We're
good
okay,
but
there's
also
another
full
request,
just
right
that
does
that
does
osd
removal.
E
That's
not
that's
not
done
yet.
I
I
like
yeah,
it's
still
only
on
my
local
machine.
I
think,
okay,
okay,
but
I'm
I'm
working
on
it
like
right
now,
but
that
should
be
done.
B
E
I
think
there's
some
there's
there's
more
like
role-based
access
control,
changes
that
are
needed
for
for
ost
room
info,
which
is
like
the
the
pr
that
I
opened
on
rook
this
week.
I
just
I
changed
like
the
common.aml
files,
yeah
there's
just
a
couple
more
changes
that
I
have
to
make.
If
I
want
to
get
oc
removal
working,
okay,.
E
D
B
Okay,
so
then
I
guess
the
second
part
of
the
question
is
about
lso
and
this
I
think,
a
whole
bunch
of
conversations
need
to
happen
here
with
the
lso
developers
and
I
think
polly
also.
We
should
talk
to
the
topo
lvm
fellow,
because,
basically
I'll
see
unquestioned,
I
don't
think
we've
met,
but
I
have
a
pad
that
we
started
putting
together.
B
What
does
that
work
for
requirements
basically
put
a
pad
together
of
basically
everything
that
we
would
want
a
local
storage
operator
to
do
in
order
to
like
do
all
the
things
that
we
want.
B
So
I
think
the
question
is
whether
this
is
something
that
lso
would
want
to
do
and
would
want
an
expanded
scope
to
include,
and
if
so
great
it
might
also
make
sense
to
take
total
lvm
and
add
the
sort
of
the
bare
metal
like
hardware
discovery,
part
to
that
it
might
be
an
easier
path
as
far
as
like
getting
something
that
does
all
the
right
things,
I'm
not
really
sure
not
being
familiar
with
the
code
for
either
one
but.
D
Right
and
I
have
some
update-
an
update
on
some
discussions
there
in
this
okay,
so
yeah,
so
we
met
with
lso
on
friday
and
then
a
follow-up
meeting
today.
If
I
was
thinking,
I
would
have
invited
you,
but
basically
we
brought
up
the
question
hey.
D
What
would
it
take
to
get
these
new
features
that
we've
been
talking
about
like
the
dynamic
provisioning,
the
the
discovery,
and
I
think
that
my
conclusion
is
that
it's
going
to
take
time
to
get
lso
together,
but
we're
having
that
discussion
about
the
question
is
still
whether
lso
is
the
right
place
for
all
of
that
or
if
we
do
something
with
even
they're
talking
about
well,
maybe
top
lvm
can
be
used
and
we
just
work
and
work
together
with
topple
lvm
to
collaborate
or
something
so
it
might
be
that
it
might
be
really
enhanced
lso
to
do
it
all.
D
B
Yeah
yeah
quick
yeah,
so
I
mean,
I
think
I
think
the
other
conversation
I
want
to
have
is
with
the
the
product
management
manager
on
openshift
side.
I
think
it's
duncan,
who
is
responsible
for
lso
and
also
with
I
guess,
that's
iran
is
the
docs
odf,
whatever
project
manager
and
basically
like
sell
them
on
the
idea
of
including,
like
a
robust
local
storage
operator
in
that's
part
of
either
open
shift
or
udf.
B
I
think
I've
talked
with
duncan
by
the
way,
because
I
have
not.
I
have
not
talked
to
him
yet
was
basically
my
list
of
stuff
to
do
this
week.
I
was
out
most
last
week
camping,
so
I'm
just
trying
to
figure
it
out.
D
B
All
right
yeah,
because
I
mean
if
if
that
is
the
case,
then
I
think
there's
I
mean
there's
a
question
of
like:
do.
We
evolve
lso
into
this
thing,
or
do
we
evolve
topol
vm
into
this
thing?
It's
like
question
number
one
and
then
question
number
two
was:
do
we
want
to
take
that
resulting
thing
and
put
it
under
the
rook
umbrella?
Oh,
have
you
talked
to
anybody
in
like
the
rook
on
the
rook
side
of
things
or
brought
it
up
in
like
the
work
community
meeting?
D
B
D
Exactly
yeah,
one
of
them
is
a
rook
maintainer
to
satoru,
so
yeah
we
have
a.
We
have
a
good
connection.
There.
B
D
B
There
was
like
a
little
bit
of
pink
in
this
pad
that
sam
just
added
a
couple
notes
around.
We
want
to
make
sure
that
we-
and
this
ultimately
also
includes
like
the
zns
ssds
that
are
about
to
start
shipping
and
ideally
like
things
like
persistent
memory
and
whatever
other
types
of
storage.
Hardware
ideally
want
to
capture
this
as
well.
That
was
the
device
discovery
part,
but
not
clear
whether
those
would
be
inventory.
There's
another
thought.
B
Actually
I
have
that
may
or
may
not
make
sense
here,
because
it
might
be
that,
like
once
you're
in
the
category
of
like
I
want
to
dynamically
provision
a
persistent
volume-
that's
I'm
not
reliable,
then
that
could
just
be
like
a
directory
on
a
formatted
hard
drive
like
a
local
path,
but
like
dynamically
provisioned
like
I
don't
know,
if
there's
anything
in
kubernetes,
that
does
that
right
now,
but.
D
B
D
A
No,
I
I
have
put
well
recording
of
meeting
that
we
had
and
what
we
thank
us
and
could
explain
us.
What
is
the
the
flow
of
the
operations
that
are
required
in
in
open
shift
in
order
to
use
the
local
storage
operator
to
create
ost
using
the
local
storage
operator?
So
there
is
the
the
link
if
somebody
is
interested
and
what
I
think
is
that
what
basically
we
are
going
to
to
follow
the
same
workflow,
okay,
so.
B
I
gotta
run
in
a
couple
minutes,
but
the
last
thing
I
had
was
just
on
the
manager,
nfs
and
dashboard
stuff.
The
dashboard
needs
to
be
changed
to
consume
the
nfs
api
and
I
think
the
question
is
just
for
the
the
dashboard
folks.
I
sent
a
message
to
ernesto
and
the
rc
channel
that
haven't
got
a
reply.
Yet
I'm
wondering
if
somebody
in
the
dashboard
team
is
currently
working
on
this
or
if
I
should
just
go,
give
it
a
shot.
Alfonso.
Do
you
know?