►
From YouTube: Ceph Orchestrator Meeting 2022-01-11
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
Hi
and
welcome
to
today's
orchestrator
meeting,
so
the
only
topic
I
have
on
the
again
for
today
is
that
we're
going
to
have
a
feature
freeze
for
quincy,
probably
in
january,
was
supposed
to
be
end
of
this
week.
Is
it
going
to
be
end
of
this
week?
I
don't
know
depends
a
bit
on
of
the
other
components
like
at
the
w
rbg.
A
What
do
we
have
from
from
our
side
for
quincy?
That's
still
ongoing,
so
one
thing
that
I
have
in
mind
is
that
we
still
need
to
refactor
the
self-adm
binary.
A
One
thing
we
should
care
about
because
it
it
would
be
a
shame.
It
would
be
a
bummer
if
we
are
not
able
to
get
this
done
into
quincy,
though
I
think
the
only
real
requirement
is
that
yeah
that
we
have
is
that
we
are
going
to
get
the
davidian
binary
refactorization
done
till
the
release
of
quincy.
So
I
I
don't
think
we
need
to
meet
the
feature
freeze,
for
that
particular
refactorization.
A
What
else
what
else
is
open?
We
have
the
agent
adam
there,
any
particular
pull
request
that
needs
to
be
merged,
for
the
feature
freeze
note
that
it's
still
not
yet
better
right.
It's
it's
a
it's
a
point
where
we
can
still
change
data
structures.
B
I
think
what
the
most
important
issues,
maybe
the
file
permissions
stuff
we
want
to
get
in
and
then
just
think
about
the
the
host
cache
size
going
too
big,
be
pretty
bad.
If
it
happens,
those
are
like
the
only
two.
The
other
issue
is
just
something
that
causes
totality
tests.
You
know,
I
don't
think
it's
a
big
deal,
but
those
two
okay.
A
Okay,
speaking
of
the
feature
freeze,
so
we
made
a
big
progress
in
the
manager
module
for
quincy
or
in
the
rook
manager.
Module
for
quincy.
A
This
is
tested
in
tautology
and
it
is
supposed
to
work.
I
don't
have.
We
don't
have
joseph
here
in
this
call,
but
nevertheless
plain
old
me:
did
you
had
a
look
at
the
at
the
rook
manager,
module
frequency
up
to
this
point,
or
is
it
only
tested
in
the
in
the
ci?
At
this
point,.
C
Well,
I
think
that
is
something
that
is
not
used.
B
A
Okay,
so
that
sounds
a
bit
confident,
okay,
but
let's
do
we
need
to
do
in
order
to
wrap
up
quincy
keezy,
the
lcw
manager
module
is
it?
Is
it
ready
for
primetime
frequency.
E
Hey
guys,
that
might
be
a
better
question
for
yehuda
it.
It
merged
right,
not
sure
exactly
what
it
does
or
who's
using
it,
though,.
A
A
A
But
at
this
point
this
is
not
going
to
end
up
in
the
initial
quincy
release
for
sure,
so
I
don't
think
anyone
is
going
to
make
use
of
the
htw
manager
module
in
the
early
quincy
versions.
A
A
Yeah,
the
idea
is
rook
has
a
way
to
set
up
lgw
multi-site
using
custom
resources,
and
the
idea
is
to
copy
the
same
custom
resources
put
them
into
a
self-adm
yammer
file
that
you
can
apply
to
self-adm
and
then
leverage
the
new
ntw
manager
module
to
call
lgw
item
admin,
rather
scary,
admin,
in
the
background
so
having
the
lgw
manager
module
as
a
neat
interface
for
surfading
to
just
convert
those
yamaha
specifications
into
multi-site
configurations.
E
Cool
so
ali
and
our
team
ali
moredia
did
a
lot
of
work
on
the
rook
pieces
of
that,
so
he'd
be
a
good
resource.
If
you
guys
have
questions.
F
D
A
I
mean
from
a
suffering
point
of
view.
My
assessment
is
that
every
feature
we
are
doing
can
be
easily
back
ported
in
in
the
future
versions,
because
everything
is
backward
compatible.
A
That
should
not
be
a
big
of
a
of
a
problem.
Do
we
have
different
rook
versions
that
we
need
to
consider
when
releasing
quincy.
F
Yeah,
I
I
don't
it's
possible,
but
I
don't
think
so.
Rick
tries
to
do
a
good
job
of
having
its
interfaces,
be
backwards,
compatible.
B
Other
than
this
on
the
list
already,
I
don't
think
so.
My
focus
obviously
has
been
like
the
agent
stuff
recently,
so
you've
already
covered
it.
A
D
D
F
D
Yeah
yeah
a
bit
a
good
thing
is
reduce
the
amount
of
duplication
of
code
and
you
know
reduce
the
number
of
bugs
strange
edge
cases.
We
have
as
we
do
this.
Hopefully.
A
A
One
one
thing
we
could
talk
about
as
or
what,
but
I'm
still
curious
as
e,
even
though
we
are
not
going
to
have
ilia
in
this
call,
there
seems
to
be
a
regression
for
iscsi
elia
mentioned
that
in
one
of
the
github
requests.
A
To
properly
replicate
the
the
failure
he
saw.
A
A
A
A
bunch
of
pull
requests
that
we
need
to
record
and
and
and
we
have
to
painfully
export
each
pull
request
individually.
I
just
pasted
them
into.
A
Into
the
other
pad,
let
me
let
me
quickly
share
my
screen
chromium
tab.
This
one
here.
A
A
I
guess
also
managed
to
get
back
quartered
here,
avoid
repeated
calls
to
get
modulus,
and
this
is
a
performance
improvement
that
was
created
by
sage
a
while
ago.
A
Anyone
feels
the
need
to
backport
it
to
pacific,
because
it
is
a
really
important
form
for
larger
clusters.
A
Adam
client,
adding
the
the
client
that
admin
curing
when
upgrading.
I
think
that's
that's!
That's!
On
my
plate,
let's
knock
lawyers
when
conflict
texts
fail.
I
think
that
was
mainly
due
to
the
agent
so.
B
You
already
have
a
yard
for
that.
One.
A
This
one
is
done,
oh
perfect,
I
think
we
have
for
this
one
as
well.
A
This
one
as
well,
our
container
registry
credentials
can't
backpot
it
this
one
before
it
depends
on
the
client.admin.
A
I'm
not
sure
I
pasted
the
correct
list
of
pull
requests.
I'm
sorry.
A
So,
let's
try
if
this,
I
think
this
list
makes
more
sense
here.
A
Fix
osd
activate,
I
think
I
I
can
also
have
a
look
next
week.
That's
also
doable
the
virtual
ip
should
be
used
by
the
ingress
team,
and
that
was
a
fix.
We
got
from
the
from
the
osp
fox,
but
we
still
need
to
backport
it
and
it
also
conflicted
and
done
fixed
control.
Is
these
with
osd
specs
john?
Do
you
want
to
create
a
backpack
for
this
particular
pr.
G
A
Yeah
so
typically,
we
are
doing
batch
back
parts
because
we
have
so
many
pull
requests
and
and
back
porting
into
an
individual
pull
request.
Is
such
a
big
amount
of
work,
so
we
are
really
trying
to
create
patchback
ports.
A
G
A
Checked
so
yeah,
but
but
you
could
do
this
one
here,
four
four,
three,
seven
four!
Maybe.
A
It
was
created
by,
I
think
it
was
francesco
from
the
osp
from
from
openstack.
G
I
I
could
give
you
a
hand
yeah.
Maybe
we
could
do
like
a
one-on-one.
You
can
kind
of
walk
me
through
the
process.
Perfect.
Okay,.
A
A
Nothing:
okay!
Thank
you,
everyone
and
look
up
next
week,
bye,
bye,.