►
From YouTube: 2019-09-25 :: 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
C
A
B
C
B
A
A
B
C
A
C
A
A
A
B
D
C
Yes,
I
would
be
happy
to
just
hand
this
off
to
someone
else
like
I.
Don't
I,
don't
think
I'm
gonna
be
doing
a
bunch
of
really
anything
that
this
meetings
focused
on
anymore
for
a
while.
So
like
I
started
that
email
thread
on
the
mailing
list
and
it
didn't
go
very
far
so
I
left
it.
But
if
people
have
a
better
time,
we
should
just
do
that.
C
C
D
A
One
up
so
a
doodle
yeah
you
can
basically,
as
I,
did
know
yeah
I.
A
A
D
D
D
A
D
D
D
C
D
Go
of
course
we
we
probably
need
to
to
make
some
volunteer
inroads.
Who
will
work
on
it?
I
can
I
can
I
can
participate
in
this
Airport.
D
D
C
D
D
A
D
So
did
all
she
is
using
right
now
it's
managing
infrastructure
itself,
it's
a
flop,
say
Pia,
it's,
it
can
lock
machines
bare
metal
machines
and
provision
them,
and
the
same
thing
is
for
for
OpenStack
it.
It
locks
resources
in
OpenStack
and
everything
you
just
described
in
in
yeah
specification
and
and
then
the
internally.
D
D
D
A
C
A
C
C
D
The
thing
that
I
think
it's
main
difference
between
Roxy,
I,
hypothetical,
GI
and
etiology,
is
that
the
it's
ruk
test
should
be
like
contain
agnostic.
It
means
that
several
containers
can
be
I
mean
as
I
understand
correctly.
It
should
be
using
the
each
container
payroll
right
and
it
should
be
shouldn't
be
bound
to
the
number
of
resources.
I
mean
real
host
machines,
but
anyway
you
you.
You
always
have
to
keep
in
mind
that
some
some
capacity
should
be
should
be
used
for
people
in
some
cluster.
D
D
Do
it
it's
nothing
to
do
with
Jorge,
it's
just
some
other
other
stuff,
but
anyway,
if
we
are
changing
the
existing
test
cases,
if
they
are
starting
anything,
they
are
manipulating
with
the
remotes
like
Association
modes
to
particular
nodes
and
get
it.
It
will
be
changed,
probably
just
because
it
has
another
interfaces.
And
anyway
we
will
need
to
write
a
test
for
those
interfaces.
D
And
what
is
what
is
good
for
this?
You
do
not
need
to
modify
to
touji
code
and
March,
and
until
you
finish
these
this
API,
you
can
develop
this
API
separately
on
your
local
environment,
just
keeping
in
mind
that
you
already
have
setup
good
Burnett's
cluster
and
what
we
need
to
do
is
just
to
get
photo
technology
and
a
module
like
which
will
set
up
kubernetes
cluster
or
for
it
on
the
on
the
old
roles.
D
For
example,
the
the
roles
array
can
contain
only
one
role
like
OOP,
instead
of
monitors,
etc,
can
only
just
put
required
number
of
nodes,
and
then
the
group
task
can
deploy
there
like.
We
do
for
deep
sea,
of
course,
like
it's
similar
sure,
I
believe
it's,
it
will
be
changed.
I,
don't
know
how
nuances
how
the
Red
Hat
is
deploying
the
cluster.
You
guys
are
using
ansible
right
or
preparing
machines
and
deploying
the
rpms
right.
D
D
C
C
C
Mean
there's
there's
like
there's
extra
stuff
that
happens
that
key
rope,
but
a
lot
of
it's
still
just
the
same
like
we
had
like
redhead,
has
like
a
little
has
a
little
clone
of
the
lab
that
they
use
for
downstream
and
I
know.
It
runs
some
custom
stuff
which
I
haven't
looked
at
in
a
while,
but
a
lot
of
it
is
very
much
the
same
as
the
upstream
biz.