►
From YouTube: 2020-01-21 :: Ceph Testing Meeting
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
B
B
A
A
Yeah
we
see
some
I
mean
I,
I
load,
it
up
full
set
of
sweets
and
they
not
finished
yet,
but
some
of
them
actually
failing
because
of
some
packaging
issues
and
like
people
saying
that
this
probably
not
worth
even
fixing
them
right.
Now,
though,
I
suspect
that
we'll
have
some-
and
once
you
mentioned
about
some
stuff
related
to
sentence
and
other
stuff
I'm,
suspecting
that
there
might
be
some
it's
too
old.
So
that's
why
I
mean
I
think
we
need
to
finish
it
as
soon
as
possible
and
then
forget
about
us.
B
B
A
C
D
C
D
B
D
D
A
D
D
I
was
thinking
that
I
could
or
we
could
just
you
know,
drop
some
of
those.
You
know
hammer
jewel
upgrades.
You
know
we
want
to
test
the
upgrade
from
luminous
to
mimic
luminous
to
Nautilus,
but
testing
the
upgrade
from
jewel
to
seems
like
it's,
not
useful.
I
mean
it's
useful,
but
if,
if
it's
constantly
breaking
we
have
to
constantly
fix
it,
then
it's
not
worth
the
effort.
A
D
Well,
yeah
I
can
update
I.
Think
I
was
just
talking
with
Abhishek.
Today
there
are
two
CVEs
one
is
embargoed,
it's
in
our
GW
vulnerability
and
the
other
one
is
a
dashboard
vulnerability.
That's
currently
being
backboarded
to
the
Nautilus.
The
both
of
those
are
coming
out
very
soon,
and
so
we
may
need
to
do
a
hotfix.
A
B
D
A
A
D
A
Not
like
you
know,
my
advantage
is
that
you
know
I
have
no
opinion
so
I'm,
just
like
all
in
the
process,
so
I
actually
discussed
that
you
know
I
mentioned
to
Neha
and
Josh.
That
I
think
Abby
mentioned
the
same
sentiment
that
he
doesn't
like
some
things
but
and
I
think
you
wanted
to
wait
for
sage
to
come
from
his
vacation.
So
as
far
as
I'm
concerned
I,
don't
really
care.
You
guys
need
to
follow
it
like
to
sort
it
out,
whatever
you
don't
like
and
what
you
want
to
see
in
it.
D
A
D
A
D
A
A
See
what
you
mean
they
have
to
be
actually
Jenkins
to
be
able
to
release
from
any
any
branch,
not
just
by
okay,
listen
as
I
said
before.
As
far
as
I'm
concerned,
I'm,
fine,
with
whatever
you
guys,
decide,
I
think
I.
Think
what
you
saying
is:
it's
probably
more
involved
in
terms
of
fixing
and
that's
why
you
know
you
you
you
guys
like
have
some
difference
in
opinions,
but
but
until
until
it's
changed.
B
A
I'm
full
I'm
following
this
process
because
there's
nothing
else,
I
can
do
and
and
a
you
know
you
probably
you
probably
want
to
like
fit
up
the
discussion,
because
I
didn't
I
didn't
hear
any
kind
of
like
open
objections
to
the
current
process.
So
I
I
do
hear
that
you
don't
need
me
you're,
not
happy
and
Abby
is
not
happy,
but
you
know
you
guys
need
to
speak
up
about
it,
but
then
getting
back
to
that
release.
A
D
D
A
A
A
A
A
A
D
C
A
D
They'll
be
merged
into
a
branch,
and
it's
just
that
it'll
be
because
of
this
weakness
or
limitation
of
the
release,
jenkins
jobs.
The
release
builds
that
they
require
the
exact
branch
name,
nautilus,
that's
the
whole
problem
that
requires
us
to
do
this,
these
maneuvers,
with
with
copying
the
branches
and
then
and
then
resetting
nautilus,
temporarily,
etc.
We.
A
D
D
Yeah,
no
doubt
they
can
either
be.
If
the
PR
is
open,
then
we
can
reset
the
nautilus
and
then
merge
the
PR
rebase
it
and
then
merge
it
or
but
I
think
it's
more
likely
that
they
will
be
merged
first
and
then
we
will
just
construct
the
Nautilus
branch
so
that
it
looks
exactly
the
way
we
want
it
for
the
release
and
then
do
the
release
build.
D
D
D
Enabling
openSUSE
15.1
in
in
sepia
as
a
stable
release
or
supported
release
or,
however,
you
want
to
call
it
and
supported
distro
and
one
of
the
blockers
there
are
several
offers.
One
of
the
blockers
was
the
the
provisioning
that's
been
fixed
by
our
colleague
Rahman,
although
I
think
the
pr
hasn't
been
merged,
then
there's
another
after
that.
There's
a
problem
in
the
kernel
tasks
and
then
another
problem
in
the
install
task.
Even
before
we
get
to
Seth
death,
ABM
and
I
think
so.
D
D
Well,
yeah
we're
talking
about
it.
We
have
to
first
figure
out
exactly
what
has
to
be
done,
but
I
did
find
out
that
the
testing
kernels
are
built
in
Jenkins
and
distributed
via
chakra
and
Shama
and,
of
course,
there's
no
openSUSE
support
in
or
the
kernel.
Yet
that's
and
we
are
working
on
updating
the
kernel
tasks
to
support
openSUSE.
B
D
B
B
D
B
D
B
B
B
D
C
D
Not
require
any
any
right,
but
if
we
are
now
also
investigating
k
testing,
which
typically
requires
a
build
in
Xiamen,
and
but
we
are
looking
to
see
whether
it's
possible
to
use
the
muhammad's
you
used
for
sent
to
us.
Also
in
openSUSE,
it's
possible
that
we
might
be
able
to
use
the
the
RPM.
That's
built
already.
D
D
B
D
Base
system
now:
well,
it's
not
it's
a
little
bit
more
complicated,
but
basically
the
answer
is
yes.
If
you'd
provide
kernel
of
distro,
it
checks.
If
the
running
kernel
is
the
latest,
so
it
checks
the
repos.
It
looks
at
the
what's
the
latest
version
available
in
the
repos
and
then
it
looks
at
what
version
is
running
in
the
system
and
if
the
running
kernel
is
is
out
of
date,
then
it
updates
the
kernel
packages
and
reboots
the
system.
B
B
B
D
D
D
D
B
So
from
from
my
side,
I
just
started
to
you:
I
just
found
some
time
and
started
to
look
into
the
building
Santos
a
Imogen
in
our
OVH
instance
and
I
found
some
issues
like
with
playbook
and
conduct
it
with
David.
Go
away.
To
help
me
deal
was
a
what's
wrong
with
Santos
a
the
Imogen
seems
like
we
resulted
so
now.
B
B
So
the
test
deployed
is
broken
now,
I
mean
whatever
you
run,
it's
not
it's
failing
just
because
it
can't
find
any
any
sweet,
I
mean
any
test
case
and
sweet.
So
you
still,
you
still
can
schedule
tests
with
Santa
know
with
Nautilus,
but
it's
not
super
useful
for
me
just
because
it's
I
need
to,
because
there
is
nothing
back.
Ported,
didn't
notice
related
to
pricing.
B
B
B
D
B
They
finished
that
the
the
the
master
is
the
Iranian
against
master,
doesn't
break
backward
compatibility
at
the
moment.
It's
not
it's.
It's
not
the
same.
That's
the
question
is
I
didn't
know
how
much
time
it
will
take
to
fix
and
I
said,
maybe
tomorrow,
maybe
next
week,
do
you
need
to
do
some
too
much
something
early
in
any.
D
B
B
B
The
the
tests
are
not
working
yet
so,
just
just
because
of
self
because
unconscious,
and
there
is
some
something
to
fix:
it's
not
ready
to
merge
the
corresponding
to
two
or
TPR.
It's
not
ready
to
merge,
but
it's
I
hope
I
can
do
this
they're
quite
compatible,
so
it
could
be
deployed
both
so
there
there's
environment
variable
like
Python
or
for
the
bootstrap
script.
So
it
depends
if
you
provide
500
device
and
Python
3.
If
you
provide
python,
2,
deploys
python
2
and
by
phone
to
use
default
rate.
No
I.