►
From YouTube: Ceph Testing Meeting 2018-10-24
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).
B
Yeah
I
sorry
I
haven't
been
able
to
make
it
lately,
but
I
wanna
show
up
today
awesome.
A
B
B
B
C
C
C
C
B
Yeah
I
think
I.
It
seems
to
me
like,
if
I
say,
good
use
of
time
to
just
do
like
a
mini
review
here
or
at
least
a
walkthrough,
because
because
there
is
a
decent
amount
here-
and
maybe
it'll
be
really
quick,
but
I
I,
don't
wanna.
What
I
want
to
do
is
is
is,
what's
the
you
know,
not
to
not
worry
too
much
about
the
changes
that
that
you
want
to
get
into
the
OpenStack
back-end,
because
I
trust
you
there
right
time.
B
B
B
C
B
B
C
B
C
B
C
B
So
I
guess
I
want
to
I
I
want
to
give
this
a
decent
review
and
we
don't
have
to
like
do
the
whole
thing
right
now
or
anything.
I
just
wanted
to
take
at
least
like
a
quick
look
at
it
now,
partly
so
that
I
don't
forget
to
do
it
later,
because
you
haven't
been
super
available
for
testing
stuff
lately.
Oh.
B
B
B
C
So
because
they
will
cover
in
all
this
functionality,
but
I
can't
say
many
can
meets
now,
but
for
sure
I
can
say
that
as
soon
as
we
have
basic
functionality,
which
allows
us
to
install
dependencies
from
custom
wrappers,
there
is
a
big
changes
related
to
support
for
different
versions
of
being
I
didn't
know
mostly
related
to
openSUSE
packages.
And
another
thing
is
a
big
task.
Is
support
for
deep
sea.
A
C
B
C
B
C
C
B
So
yeah
for
for
some
reason
before
before
anybody
that
currently
works
on
any
of
this
was
was.
What
was
part
of
this
is
back
when
we
ranked
tank
our
test
lab.
The
sepia
lab
was
set
up
with
external
DNS,
which
which,
when
you're
behind
a
VPN,
is
kind
of
kind
of
wrong,
but
we
never
changed
it
because
it
you
know
it
doesn't.
It
doesn't
really
matter
that
much
anyway.
It's
just
you
know
not
a
best
practice
at
all.
B
Well,
the
interesting
thing
is
is
well.
The
OVH
IPs
are
public
right,
they're,
not
behind
a
VPN.
So
so,
when
we
do
this
with
the
OVH
instances,
it's
not
you
know
we're
not
doing
anything
gross,
but
what
we?
What
we
do
is
I
found
this
this
web
service,
that
someone
had
written
and
kind
of
abandoned
and
I
sort
of
just
adopted
it
and
what
it
does
is
it
uses
NS
update
to
update
it
uses.
B
C
I
saw
the
information
how
you
just
I
in
the
documentation
that
it's
required
and
I
saw
the
reference
to
you.
Branch
I'll
go
to
York,
but
why
I
do
not
hurry
into
you
into
breaking
it?
It's
it's.
It's
separate
service
actually
and
the
DNS
mask
was
working
for
us.
Okay
and
we
had
never
problems
with
it.
But,
as
you
said,.
C
As
a
workaround,
I
actually
used
it,
external
DNS
mark
set
up
on
some
of
our
constant,
consistent
resource
resources
that
we
use
for
sharing
temporary
artifacts
or
detesting
like
go
service,
and
it
also
works
fine
for
us
just
pointing
we
added.
We
added
a
key
like
names
to
deployment
command
line,
two
to
toldja,
OpenStack,
actually
CLI,
and
it
will.
It
just
sets
the
name
server
to
configuration
file
and
just
just
one
line.
B
Okay,
yeah,
that's
cool
yeah
I,
don't
mean
to
try
to
try
to
try
to
push
you
to
use
the
same
method
that
we're
using
just
to
let
you
know
it
was
there.
If
you
didn't
know
already,
there
is
then
and
I'll
stop
talking
about
in
one
sec.
I
just
want
to
know.
There
is
a
there
is
a
role
or
in
steps
iam
ansible.
So
if
you
do
in
the
future,
decide
that
you'd
rather
go
this
path,
then
it
shouldn't
be
yeah.
C
B
B
Yeah,
it's
I
I'm,
not
sure
what
the
best
way
to
do
that
either
is
I.
Think
what
if,
if
I,
were
gonna
look
at
this
today,
the
first
place
I
would
probably
look
is
just
so
the
tooth
ology
role
in
subsea
amenable
does
have
some
ability.
It
has
like
at
least
the
beginnings
of
the
ability
to
manage
the
technology
configuration
files
on
like
on
the
technology
host
machine,
but
I
don't
think
it's
complete.
My
memory
is
that,
like
is
that
I
I
made
it
sort
of
useful,
but
not
nearly
as
useful
as
a
physical.
B
It
should
be
because
I
was
just
doing
what
I
needed
to
do
at
the
time,
but
I
could
imagine
that
you
know
if
that
feature
will
were
made
a
little
bit
better
than
then
you're
able
to
when
you,
when
you
execute
that
answer,
will
roll
you're
able
to
to
include,
as
part
of
you
know,
say
your
group
bars
somewhere.
These
are
the
the
fragments
that
I
would
like
to
add
to
the
technology
configuration
file,
but
maybe
there's
a
better
way
to
do
it.
I'm
not
sure
I
mean
I'd
be
open
to
to
whatever
solution.
C
C
So
there
is
another
thing
that
I
actually
remember.
We
call
recall
that
we
need
to
discuss
and
the
unit
test
it's
actually
not
unit,
but
they
are
functional.
So
I
added
a
jenkins
which
we
use
for
community
purposes
on.
C
B
C
You
run
it
talks
with
high
27
environment.
It's
even
if
you
run
it
from
virtual
environment,
where
a
newer
version
of
people
installed
it
it
squids
test,
specific
environment
and
it
doesn't
upgrade
at
peep
in
this
environment
and
it's
it's
taken
from
the
system.
One-
and
this
is
one
in
it-
can't
set
up
correct,
set
of
set
of
tools
to
install
the
rest
of
the
tendencies
from
the
requirements
that
apply
and
it's
failing
so
I
I
have
to
do
all
these
environment
manually.
It
would
just.
C
C
Just
so
I'm
doing
the
same,
that
is
done
by
in
bootstrap,
not
actually
in
bootstrap,
but
everything
that
talks
is
doing.
But
it's
not
super
much
effort,
but
the
pro
the
problem
was
like
to
figure
out
what
was
the
problem
with,
which
are
the
dependencies
and
I
spent
time
for
checking
what
is
what's
wrong
with
our
test
cases,
because
we
had
a
fair,
lass
and
I
figured
out
that
recent
version
of
Pi
tests
has
some
issues
that.
A
B
So
that
brings
up
something
that
yeah
that
I
was
I
was
thinking
about
a
couple
weeks
back
was
to
periodically
weep
in
versions
of
our
dependencies
right
so
that
we
don't
have
unexpected
breakages,
because
we
used
to
have
that
a
lot.
But
that
means
that
we
periodically
need
to
go
and
try
to
update
dependencies
and
and
run
tests
and
things,
and
it's
been
quite
a
long
time,
I.
Think
since
that's
been
done,
that's
something
that
we
should
do
before
too
long.
I
think
yeah.
C
B
B
I
don't
know
if
you've
seen
this
I
guess
I
think
this
is
a
new
github
feature,
but
it
has
a
way
to
tell
you
about
certain
dependencies
that
you
need
to
update
for
security
reasons
which
I
I
actually
just
noticed
yeah,
so
we
should
probably
at
least
try
to
get
those
three
and
Cibola
PI
open,
SSL
and
param
Eco
updated
I'm,
not
super
worried
about
about
security
here.
But
it's
always
you
know
if
we
should
keep
up
regardless.
B
C
C
C
C
So,
but
we
we
can't
use
all
of
them
and
right
now,
because
it's
the
code
is
incompatible
and
we
need
to
spend
some
time
for
dog
code
great,
but
ok.
So
this
this
stuff
is
kind
of
works
for
us
like
now.
We
can
we
run
unit
tests
for
downstream
or
functional,
but
there
are
some
issues
that
I
found
like.
Of
course,
there
are
a
lot
of
some
tests
which
are
trying
to
access
sepia
or
some
lab
resources
or
OpenStack,
and
there
are
a
lot
of
noise
with
errors.
C
B
C
B
C
C
C
B
C
God
yeah,
but
it's
probably
not
super
easy,
because
we
need
to
spend
some
time
for
investigating
right
yeah,
but
it's
not
blocking
us
right
now.
It's
just
for
future.
We
can
live
with
this,
but
another
thing
is
like
usability
of
the
tests
itself.
I
was
trying
to
run
him
the
way
we
run
unit
tests
and
I
found
that
they
are
not
thread
safe.
The
some
of
the
tests
are
sharing
the
same
test
data
in
temp
directory,
and
this
is
why
they
can
fail
so
I
get.
A
C
B
B
B
B
C
Some
cosmetic
changes
anyway,
even
not
cosmetic.
Then
we
probably
it's
it's
worth
to
submit
it
with
different
PR
so
because
to
minimize
merging
effort
of
upcoming.
So
probably
it's
better
to
add
those
cosmetics
after
the
changes
that
will
come
in
the
next
be
ours,
but
anyway
it's
it's.
It's
valuable
to
sound
preferences.
What
should
be
changed.