►
From YouTube: Ceph Orchestrator Meeting 2020-09-28
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
A
A
B
I
I
have
put
that
okay,
more
or
less,
because
what
I
was
thinking
not
in
all
the
the
the
book
requests.
Okay,
but
sometimes
there
are
things
that
what
probably
I
think
that
they
are
going
to
to
help
the
project.
Okay,
we
are
a
good
example
with
two
of
the
paul
kastner
pull
request:
okay,
the
last
two
about
the
improvements
in
ls
and
the
about
the
50m
diamond,
but
the
seat
of
the
3dm
diamond.
That's
it
that
in
both
cases,
are
are
important.
Okay
and
well.
B
B
Well,
if
there
is
modifications-
and
we
need
to
to
do
modifications-
because
people
is
suggesting
things-
it's
okay,
okay,
and
if
we
need
to
add
more
unit
tests
or
any
kind
of
thing
to
improve.
The
call
is
perfectly
possible
that
a
pull
request
can
can
take
one
month
even
one
month,
okay,
but
the
the
thing
is
that,
well
probably
we
are
spending.
B
I
think
that
is
big,
okay,
even
but
if,
if
we
upload
the
same
level
of
quality
to
the
rest
of
the
code,
probably
fav,
I
think
that
this
moment
it
couldn't
be
what
we
have
in
this
moment.
Okay,
so
I
think
that
in
in
we
should
see
a
balance
between
quality,
the
things
that
we
want
to
have
and
what
is
the
current
state
and
what
is
the
benefit
of
the
book
request?
B
Okay,
so
I
think
that
this
is
important,
and
probably
in
this
case
and
with
this
full
two-part
request,
I
think
that
we
are
expecting
too
much
things
from
from
the
gold
and
the
benefit
that
we
have
with
the
code
in
this
state
is
is
enough
peak
for
for
taking
this
match.
Okay,
this
is
one
of
the
things
that
I
wanted
to
comment:
okay,
that
what
is
just
my
opinion,
but
I
think
that
in
any
case,
maybe
something
like
a
lab.
A
label
like
origin
or
something
like
that
would
reflect
that.
B
We
want
to
to
have
something
be
with
and
merge
it
as
soon
as
possible.
C
Well,
one
me,
I
think,
one
of
the
conversations
we
had
internal-
and
I
don't
think
you
represented
it
potentially-
is
the
fact
that
there
has
been
some
downstream
needs.
There
have
been
some
issues
with
our
downstream
where
we
needed
a
fix,
and
you
know
we
needed
to
you
know
get
a
you
know
and
again
one
of
those
went
for
a
month.
You
know,
I
don't
even
know
if
we
still
have
it
in.
I
don't
even
know
the
number.
C
I
don't
know
the
pr,
but
overall
I
think
that's
the
type
of
thing
that
you
know
we
had
to
go
out
with
a
you
know
downstream
product
with
something
that
we
knew
was
broken.
We
never
got
the
fix.
You
know.
As
a
result,
I
mean
that
I
think
is
even
more
important.
I
think
than
some
of
the
things
that
you
know
juan
me
is,
you
know,
maybe
you're
talking
about
now,
but
again
just
my
opinion.
C
I
think
those
are
the
ones
that
are
really
urgent
to
me,
and
sometimes
you
know
if
we
might
there's
no,
how
do
you
tell
if
you're
looking
and
reviewing
which
one
you
want
to
look
at
first?
I
mean
if
it
were,
you
know
something
we
marked
as
urgent.
Then,
basically,
you
know
there's
probably
a
good
reason
for
it
and
you
know-
and
I
think
that's
I
think,
that's
what
part
of
the
conversation
I
took
away,
but.
A
Right
right
so
I
mean
for
the
tuple
requested
that
you
just
mentioned
when
we
that's.
Basically,
I
think
that's
that's
just
my
fault.
I
was
out
for
a
week
and
before
that
I
was
actively
looking
into
it,
and
so
they
just
became
a
bit
stale,
but
for
for
bug
fixes-
and
in
general
I
mean
judging
on
when
to
review
something.
There
is
basically
just
a
golden
rule,
just
review
everything
at
once
right,
so
as
as
soon
as
you
can
and
usually
bug
fixes
are
they're
not
pending
for
a
long
time.
A
So
I
think
we
have
that
under
control,
pretty
good
yeah
I
mean
for
for
features
and
and
bigger
improvements,
though
those
pull
requests
they
they
tend
to
be
they
they
tend
to
be.
They
need
more
time.
You
know-
and
I
think
this
has
been
in
that
has
been
the
case
over
the
ceph
project.
A
That
is
yeah.
I
mean
we
certainly
need
need
way
to
speed
things
up,
but
I
mean,
if
you,
if
you
add,
a
label
that
says
urgent,
then
you
know
everybody
will
use
that
label.
Saying
urgent,
I
mean
right,
so
it
will
become
used
in
a
kind
of
inflating
way.
C
C
B
We
should
discuss
well
in
the
scanners,
okay,
to
see
that
this.
B
A
They
listen
with
daily
standups
and
if
something
is
really
really
urgent,
then
we
can
bring
it
up,
and
also
I
mean
especially
with
the
case
with
with
paul.
We
need
to
make
some
kind
of
asynchronous
conversation
happening
because
you
know
he's
in
new
zealand
time
zone
and
that
makes
it
really
hard
to
like
to
speak.
C
B
B
B
Yeah
competitory,
okay,
but
in
this
the
two
pull
requests.
I
think
that
we
are
trying
to
well
to
go
to
to
go
too
much
in
detail
and
to
have
a
quality
that
probably
we
don't
have
the
rest
of
the
project.
Okay,
and
for
in
this
case,
with
this
pull
to
pull
request,
I
think
that
the
benefit
that
we
are
going
to
have
is
higher
than
trying
to
have
everything
correct,
with
a
lot
of
unit
tests
a
lot
of
deutology
tests.
B
Okay,
I
think
that
probably
we
are
going
to
to
win
more
things
that
than
to
lose
in
we
if
we
go
ahead
with,
which
is
to
put
to
pull
request
even
taking
it
into
account
that
probably
we
will
need
a
big
refactor
of
the
things
okay,
but
this
is
another
another
history.
Okay,
so
just
commenting
this
this
thing-
and
the
second
point
that
I
wanted
to
comment
is
well.
This
is
just
to
well.
B
I
think
that,
probably
from
our
part,
I
I'm
talking
from
probably
from
red
hat
people
in
this
moment:
okay,
adam
daniel
and
myself,
okay,
we
need
to
to
to
do
more
reviews.
Okay.
B
B
Okay,
so
the
first
thing
to
say
is
that
we
need
to
in
to
improve,
doing,
put
requests
and
usually
take
a
look
every
day
to
this
kind
of
things:
okay
and
a
part
of
that
just
to
to
offer
help
okay,
because
well,
what
I
have
seen
until
this
moment
is
that
sebastian
was
doing
launching
the
authority
test
analyzing
what
is
happening
in
each
of
the
people
requests
and
what
I
think
that
is
going
to
happen
is
that
you
are
the
one
that
are
going
to
to
have
this
role
in
this
moment,
so
you
are
going
to
to
do
this
kind
of
thing.
B
So
the
first
thing
is
anything
that
we
can
help
in
order
to
to
to
make
a
lighter
on
to
to
make
his
cities
his
task.
We
we
will
be
happy
to
to
contribute
okay.
Another
thing
is
another
thing:
is
that
well
what
happened
in
this
last
week?
Okay-
fortunately
you
you
are,
you
are
here
now:
okay
and
nothing
ever
has
happened,
okay,
but
I
think
that
then
well,
I
don't
know,
but
I
think
that
is
only
sebastian
and
you
and
sage
the
only
person
that
can
merge
code,
okay,
so
well.
B
In
any
case,
I
think
that
at
least
two
persons
should
be
able
to
to
where
to
do
all
the
review
process,
to
launch
tautology
test,
to
ask
for
more
religions
and
to
match
the
code
every
moment.
Okay,
to
avoid,
for
example,
is
just
one
week
on
and
the
that
is.
I
think
that
is
not
not
it's
not
important.
Okay,
but
maybe
we
should
try
to
to
reach
this
level
of
possibilities.
Okay,
to
avoid
block
the
the
work,
okay
and
block
the
the
merge
of
the
of
punk
requests.
B
A
So
that
should
be.
That
should
be
the
first
step
and
then
the
second
step
would
be
learning
how
to
analyze
those
tests,
and
definitely
every
of
us
is
capable
of.
D
B
A
Probably
give
you
a
link,
or
at
least
forward
your
mail
that
I
got
when
I
got
my
my
access
to
the
c
pillar.
If
you
don't
have
it
already,
no.
B
I
I
I
don't
have
that
okay,
so
it
would
be
interesting,
but
not
only
for
me.
Okay,
I
think
that
even
is
is
something
that
I
think
that
we
can
improve
heavily
okay,
because
it's
something
that
well.
I
think
that
is
just
the
thing
that
is
completely
perfect
for
doing
something
like
a
workshop.
Okay
upstream
workshop.
So
let's
go
to
see
how.
B
We
are
executing
the
test
in
the
sepia
lab
or
we
are
using
dermatology
how
we
can
deal
with
the
logs,
how
we
can
improve
the
process
to
to,
for
example,
to
raise
attractive,
okay,
this
kind
of
things,
but
not
only
for
me-
for
everybody,
okay
and
obviously
not
everybody-
should
have
this
access.
Okay,
we
can
restrict
the
access
to
the
to
the
sepia
lab
to
certain
persons
or
third
time,
people,
okay,
but
should
be
something
that
it
could
be
open
to
to
everybody.
B
Okay,
I
think
that
probably
the
information
is
only
upstream
okay,
completely
open
it,
okay,
so,
but
but
the
problem
is
that
what
it
seems.
That
is
something
that
is
not
related
directly
with
you
so
well
for
me,
it's
more
comfortable
to
forget
about
the
autology
test,
but
that
is
not
correct.
A
B
A
Okay,
well,
it's
I
don't
think
I
mean
it's
open
if
it
would
be
there
right.
It's
it's
not
really
well
documented
and
most
of
the
time
you
just
get
a
mail
saying
you
know,
run
this
run.
This
run
this.
A
B
Okay,
okay,
you
know,
oh,
who,
how
he's
done
all
the
all
the
process?
Yes,
okay,
perfect,
so
maybe
I
can
help
you.
Okay,
if
you
want,
if
you
send
me
links,
we
can
prepare
something
and
trying
to
do.
A
upstream
workshop
is
what
I
am
proposing
in
order
to
to
show
everybody
all
this
work
is
done.
What
are
the
steps,
what
are
the
process
and
and
how
we
can
easily
understand
everything
in
this
process.
For
me,
it's
it's
something
that
is
weird
okay.
Is
it
like
a
little
bit
hidden?
B
B
A
A
All
right
so
then
I
will.
I
will
follow
up
on
the
document,
how
to
do
the
testing
and
how
the
ci
works.
A
D
Josh
was
that
the
sepia
document
you're
talking
about
yeah,
it's
the
sepia
lab
where
you
wrote
pathology
tests
yeah
there
might
actually
already
be
documentation
in
the
developer
guide
that
pretty
much
works.
I
followed
something
about
a
month
ago
when
josh
jurgen
set
up
access
to
the
cpu
lab
for
me.
So
if
you
look
in
the
developer
guide,
it
might
already
be
there.
D
Yeah
in
in
that
case,
would
you
include
me
in
that,
because
that
is
something
that
I
have
on
the
list
of
stuff
to
do?
I'm
sorry
just
holding
into
it,
but
like
it
dovetails
exactly
with
the
rewrite
of
the
developer
guide,
which
I'm
planning
on
doing
in
october,
perfect
yeah.
I
can
do
that
all
right
thanks.
A
Right
then,
then,
thanks
for
your
time
and
talk
to
you
soon.