►
From YouTube: Ceph Orchestrator Meeting 2023-01-10
Description
Join us weekly for the Ceph Orchestrator meeting: https://ceph.io/en/community/meetups
Ceph website: https://ceph.io
Ceph blog: https://ceph.io/en/news/blog/
Contribute to Ceph: https://ceph.io/en/developers/contrib...
What is Ceph: https://ceph.io/en/discover/
A
A
A
A
lot
of
them
got
restored
for
some
reason.
The
orchestration
weekly
one
in
particular
bill
is
back
to
October
26th.
A
But
a
lot
of
the
other
ones
are
all
back
like
if
they
I
can
look
like
today.
The
orchestration
weekly
2021.
A
Here
it
has
the
full
archive
there,
so
I
think
all
the
other
ones
are
back
I.
Don't
know
why
that
particular
pad
is
Missing
information,
but
everything
else
just
leaves
feedback.
So
I
had
to
ask
Adam
Creighton
about
it
a
bit.
He
wasn't
really
sure
what
happened
with
that
particular
pad
I,
don't
really
matter
if
I'm
gonna
live
without,
but
I
think
at
least
if
we
made
other
pads
that
we
were
looking
to
those
one
should
all
be
back
now.
A
It's
just
the
main
pad
I
guess
we'll
have
to
be
set
up
again.
I
might
just
remove
the
stuff,
that's
in
there
and
then
just
start
a
new
one
for
this
year.
Basically,
because
we
already
have
that
2021
archive,
so
we
don't
need
any
of
the
information,
that's
in
the
main
pad
right
now.
This
is
2021,
stuff
and
I.
Guess
we'll
have
to
live
without
a
2022
dove.
A
A
All
right,
so
that's
that
does
anybody
have
any
other
topics
they
wanted
to
have
in
here.
There
was
one
thing:
I
was
thinking
about
talking
about,
but
it's
not
super
important.
So
if
anyone
else
has
something
else,
they
wanted
to
do
probably
do
that.
First.
A
No
all
right
in
that
case,
there
was
the
one
thing
I
did
want
to
talk
about
was
as
part
of
the
compilation
work
we
had
talked
about,
maybe
being
able
to
include
other
packages.
There
are
dependencies
really
into
seppidium
the
binary
that
we
couldn't
do
before,
but
I
didn't
I,
don't
remember
what
we
left
off
on
that,
whether
that
was
actually
possible.
B
A
B
Should
be
possible,
it
should
be
just
a
matter
of
using
the
existing
infrastructure,
because,
even
even
before,
I
converted
it
to
python.
There
was
some.
There
was
like
hooks
for
that.
It's
just
unused
and
untested
at
this.
B
The
ability
to
automatically
add
dependency
to
the
to
the
Zip
app.
A
Yeah,
so
I
was
wondering
if
at
some
point
you
wanted
to
test
adding
like
one
thing
in
something
simple,
just
kind
of
something
we
could
use
for
somewhere.
Maybe
something
for
like
setting
up
our
IPS
or
whatever
you
do.
A
bunch
of
that.
B
A
Yeah
so
I
think
the
the
question
then,
would
be
if
we
want
to
do
that,
try
to
do
that
before
after
the
reef
release,
that's
a
decent
ways
out,
but
I
don't
know
for
like
the
first
time.
We
have
this
sort
of
package
in
here.
If
we
want
to
already
have
dependencies
in
there
or
if
we
want
to
just
let
it
you
know,
come
out
like
this,
oh
you
can
build
without
any
dependencies
for
now,
just
make
sure
people
can
do
the
build
part
of
it
and
then
go
and
do
another
again.
B
B
And
I
haven't
forgotten
about
the
fact
that
we
need
infrastructure
support
for
Reef
for
the
download
and
signing
and
all
that.
But
given
that
our
point
of
contact
for
that
stuff
is
Dan,
make
I
have
been
very
hesitant
to
bother
him
about
that.
Because
I
see
him
very
active
on
some
internal
chats.
Where
he's
like
pulling
his
hair
out
over
the
infrastructure.
A
Yeah
I
think
most
of
that's
back
up
now,
but
I
I
probably
want
to
wait
until
like
next
week
or
so.
I
know
that
this
all
the
stuff
happening
is
going
to
delay.
A
A
So
we
can
do
that
then
yeah,
it
was
just
so
I
guess.
Maybe
we
can
do
something
we
can
try
to
see
if
we
can
come
up
with
some
other
branch
and
then
mess
with
it
a
little
bit
and
see
how
it
goes
in
there
and
then
and
try
and
putting
those
things
into
actual,
like
main
branch
or
whatever
after
the
initial
Quincy
release
or
the
reef
release.
A
Just
so
when
we
know
that
it
works
with
the
packages
in
general,
and
then
we
can
add
the
extra
thing
of
oh
now.
You
need
the
some
dependencies
in
order
to
install
there
to
build
the
package.
B
A
Yeah
now
we
can
do
that
that'd
be
nice
after
the
release
beginning
well,
I
guess
we
could
start
testing
a
bit
earlier.
If
we
have
some
time
and
I
guess,
we
still
still
need
to
finish.
I
need
to
have
to
find
the
the
other
pad
that
you
had
for
with
all
those
things
we're
gonna
do
I
know
it
should
exist
now,
but
the
link
is
gone
from
this
main
pad.
So
I,
don't
remember
where.
B
B
Yeah
we
I
know
I
kind
of
got
like
I
said:
I
got
kind
of
distracted
with
the
containerized
build
stuff.
I
should
have
time
to
work
on
more
of
the
unit
test
stuff
now
so
I
will
try
to
assign
more
of
those
to
myself.
Now
that
the
pad's
back
and.
A
Yeah
I
did
just
merge
the
one
before
the
the
first
one
on
there,
the
agent
stuff
yesterday
that
one's
in
the
actual
tree
now
so
I'll
have
to
go
back
and
look
at
what
the
actual
coverage
is
at
this
point.
But
I
should
probably
do
some
of
these
other
ones
as
well,
I'm
being
more
priority
than
others.
The
command
deploy
I'd
really
like
to
do.
A
I
guess
we'll
go
back
to
doing
that
now
that
we're
sort
of
back
in
the
swing
of
things
and
I
think
that,
because
the
at
least
on
Main
Branch
Testing
is
still
blocked
by
the
build
issue
with
Java.
Maybe
this
is
a
good
time.
They
can
go
back
and
do
some
of
that.
A
So
I'll
try
to
maybe
look
at
some
of
those
later
today.
I'll
link,
I'll
link,
absolutely
add
a
link
to
my
PR
into
this
as
well,
because
then
that
first
one
is
actually
done.
A
A
Okay,
I
couldn't
quite
remember
what
we
had
done,
but
yeah.
If
we
do
that,
then
it's
again
it
keeps
the
compilation
part
as
simple
as
physically
possible
like
where
they
could
literally
rename
it
if
it
was
not
working
or
something
and
then
we'll
be
able
to
see
how
it
goes
and
go
from
there.
I
guess,
but
yeah.
B
B
I
think
the
reason,
the
main
reason
we
weren't
going
to
go
crazy
about
breaking
it
up
quite
yet,
is
to
make
back
ports
a
little
bit.
A
Yeah
yeah,
if
you
had
like
new
stuff
you'll,
probably
have
like
some
other
file
you're,
putting
it
in
on
a
reef
and
some
it
back
into
the
main
file,
Builder,
Quincy
branches,
but
I
think
at
least
most
of
the
Pacific
Back
40
is
probably
done
other
than
important
bug
fixes,
which
hopefully,
we
won't
have
after
we
have
all
this.
This
testing
in
here,
so
hopefully
it'll
just
be
Quincy,
or
mostly
nothing
to
worry
about.
A
According
to
that
point,
I
mean
even
then
it'll,
probably
now
that
we're
at
another.
Let's
write
another
major
release:
it'll,
probably
reduce
the
amount
of
back
Parts
between
there,
a
little
bit
as
well,
we'll
probably
stop
backboarding
or
already
stopped
backboarding
like
everything
there
we're
still
backboarding
a
lot
and
that'll
get
reduced
a
little
bit.
So
hopefully
it's
not
super
high
impact.
A
Maybe
maybe
at
some
point
we'll
add
like
a
phase
three
to
this
and
that'll
be
actually
adding
the
dependencies
or
testing
that
in
which
we
could
test
earlier
than
we
finished
phase
one
and
two,
but
as
far
as
actually
doing
it,
it'll,
probably
I
think
the
main
branch
it'll
probably
go
in
after
the
phase
two
stuff,
where
we're
restructuring
things.
B
A
A
All
right,
I
think
that's
all
I
kind
of
wanted
to
talk
about
at
least
I
had
because
doing
this
sort
of
dependency
stuff
will
enable
some
other
stuff
in
the
future,
but
nothing
we
need
to
talk
about
right
now
and
then
everything
else
I
think
we're
still
waiting
on
the
testing
infrared
to
be
back
up
for
some
of
the
main
testing.
A
There's
no
other
huge
topics
off
the
top
of
my
head
that
are
going
on
right
now,
I
guess
again.
The
most
interesting
is
still
just
like
the
the
build
stuff
but
I
think
you're
still
waiting
on
some
reviews
from
kefu
or
Ernesto
on
that.
So
something
really.
A
B
A
I
think
we
were
looking
at
that
yesterday.
I
wonder
if
there
was
an
update
like
they
were
looking
at
it
more,
but
I,
don't
think
it
was
resolved
yet
yeah.
That's
all
I
had
for
topic,
so
I
just
want
to
talk
a
bit
about
those
dependencies
and
the
binary.
What
we're
doing
there
I
think
that's
still
sort
of
the
main
development
Focus
we
have
other
than
like
any
random
feature
or
bug
you
want
to
fix,
but
that
doesn't
need
to
be
talked
about
going
to
be.
A
Does
anyone
have
any
other
topics
they
want
to?
You
want
to
go
over
in
here.
A
No
all
right
what
was
that.
A
All
right
yeah,
if
that's
the
case,
we
can
just
call
here,
save
everyone.
Some
time
and
I'll
see
you
guys
all
next
week.