►
From YouTube: Ceph Crimson/SeaStore Meeting 2023-02-22
Description
Join us weekly for the Ceph Crimson/Seastore 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
All
right,
let's
get
started,
I,
don't
have
much
report
this
week,
I'm
actually
working
a
lot
on
scrub
and
classic.
It
will
eventually
turn
into
a
crimson
work,
but
that's
where
a
lot
of
my
time
has
gone.
How's
it
going.
B
Yeah
I'm
reviewing
the
weak
transaction
issue
found
Johan
and
they
are
about
four
to
five
pending
PRS
for
c-store,
now
not
be
able
to
get
all
of
them
reviewed
this
week.
Sorry
about
that
and
for
multiple
messenger
I'm
working
on
extending
the
socket
and
the
socket
tests
to
multiple
shots
and
I'm
still
working
on
the
cleanups.
A
Okay,
harsh.
C
Yeah,
so
not
a
lot
of
update
from
the
QE
side,
we
have
continued
testing.
There
are
some
issues
with
our
physical
node
setup,
so
we
have
received
a
new
set
of
machines,
and
this
time
we
have
started
with
the
basic
random
testing,
and
these
are
tier
two,
so
not
very
extreme,
but
the
first
few
tests
that
we
ran
our
working
fine,
so
I
haven't
seen
any
major
failures
there
and
the
ones
that
I
talked
about
previously
about
the
RBT
test.
C
I
wasn't
able
to
raise
those
trackers
as
the
machines
that,
on
which
I
had
the
set
of
ports,
I
have
crashed.
So
once
I'm
done
with
the
rados
test,
I
will
reproduce
the
issues
that
I
had
mentioned
before
and
then
create
Checkers
for
it.
It
might
take
a
day
or
two,
so
apologies
for
the
delay,
but
that's
pretty
much
it
from
the
QE
site.
D
Okay,
you'll
see
the
yeah
yeah
okay.
So
currently
we
implemented
the
medical
system
as
this
architecture,
so
each
OSD
and
which
shared
service
hold
the
one
strong
instance
reference,
and
they
you
access
this
one
store
in
a
reference
instance
under
the
store
interface,
will
transform
to
the
exercise
to
the
Charlotte
Stone,
so
that
is
currently
implementation
and
the
things
suggested
we
separated
the
future
store,
filtered
store
interface
into
two
parts.
One
is
the
the
star.
D
Interface
is
used
by
the
mean
OST
and
surely
the
store
interface
and
used
by
each
other
OSD
and
expose
all
the
both
the
kind
of
interface
to
the
OSD,
so
OSD
sharded,
the
dispatcher
each
strategy,
dispatch
instance,
will
hold
one
instance
of
shortstop
and
the
the
the
main
OST
will
access
use
the
install
instance
to
access
to
the
interface
only
Pro
only
accessed
by
the
primary
stock
or
primary
OSD.
So
what's
your
openings.
D
D
So
because
there
is
a
OSD
Shard
and
the
stealth
Charter
says
we
want
to
open
the
exposed
to
each
shot
it
so
to
the
OST
Charter.
So
they
needed
to
use
the
store
interface
to
the
transform.
A
A
A
A
There
will
be
assured
State
between
shards,
because
there
needs
to
be
a
way
to
balance
space
usage.
We're
not
doing
that
right
now,
but
we
will
do
it
in
the
future.
D
A
A
D
D
A
D
B
Well,
so
let
me
add
my
comments
here:
yeah
is
that
okay?
So
what
what
I'm
observing
is
that
we
have
a
CN
store
and
a
c-store
both
are
shutting
now,
but
they
rely
on
the
same
assumption
that
some
interfaces
are
not
shared
across
the
whole
store,
so
they
are
shattered.
B
A
A
A
A
So
you'll
still
have
to
get
that
information
out
of
store
here.
The
store
blue
box
when
you
first
load
up
the
OSD
you'll
have
to
call
I,
don't
know
collection
list
or
whatever
and
you'll
still
get
those
hints
and
they're
still
going
to
have
to
be
placed
on
different
cores.
So
I
guess
I'm
not
totally
clear
what
this
helps
with
I
think
I'm
actually
missing
something
I
just
thought.
Well,
so.
D
To
go
you
you
understand,
but
on
the
on
the
shirt
OST
on
the
shadow
ISD
and
you
use
the
the
straps
doll,
you
need
this
idea
to
wear
shorts
or
shots
now
to
go.
A
D
A
A
In
that
case,
I
guess
we
you
would
have
to
specify
to
make
a
fast
time
or
something
so
it'll
be
a
little
bit
more
complicated,
ooh.
Actually.
A
Yeah
that's
a
different
problem,
but
anyway,
even
even
so,
I
don't
think
so.
A
D
B
D
A
A
What's
the
strategy
for
sharing
that
state,
yeah
I.
B
Guess:
data
structure:
okay!
Is
there
a
background,
the
worker
to
collect
free
space
from
each
shot
and
reallocate
it
in
the
background,
but
it
can
be
asynchronous
yeah
and
delayed.
B
Back
to
the
other
slide,
so
so
it,
it
also
means
that
the
collection
can
still
be
static
allocated
at
your
interface
level.
A
So
my
my
only
observation
is
that
I
don't
think
this
actually
makes
any
difference
to
the
execution
at
all,
because
you
could
Sim
like
all
of
these
chart.
Dispatchers
could
simply
call
into
the
store
and
the
store
would
just
grab
the
local
chart
right.
Yes,
it's
just
not
obvious
to
me
why
it's
beneficial
to
expose
this
to
the
future
I
store
interface,
it
seems
like
it
just
makes
the
interface
more
complicated,
no.
A
A
D
So
I
I
think
this
implantation
will
had
the.
A
A
I'm
just
trying
to
outline
the
sort
of
the
trade-offs
if
we
go
to
the
other
interface
we're
we're
baking,
this
rule
into
the
future
I
store
interface,
but
it
isn't
necessarily
a
bad
thing.
If
we
really
do
want
futurized
store
implementations
to
behave
like
this,
then
this
is
a
reasonable
way
to
structure
the
interface.
My
only
suggestion
would
be
to
make
sure
that
the
methods
in
store
or
disjoint
from
the
methods
in
Shard
store,
it
should
always
be
obvious,
which
one
you
should
be
using
store,
should
only
have
methods
like
Mount
and
unmount
I.
A
It
it
just
means
that
you
need
to
implement
and
you
need
to
create
an
interface
shim
for
alien
store
that
does
this
it'll.
A
A
B
Yeah,
the
global
they
should
only
be
make
half-ass
mounts
and
list
collections
yeah
and
to.
A
B
B
Yeah,
it's
it's
kind
of
us
interface
split,
so
that
some
can
only
be
used
in
the
global
OSD
and
or
the
make
half
as
process,
and
some
are
available
only
available
through
the
Shaded
OSD
yeah.
D
And
okay
still
need
to
support
I'll
install
to
follow
this
under
this
architecture.
A
E
C
A
F
Like
you
know,
we
we
can
only
use
crimson
and
sister
only
in
like
a
virtual
environment
like
a
pistachio
like
so
I'd
like
to
bring
Queen
San
his
sister
to
real
Christchurch
by
using
like
ATM
I'm,
not
sure
like
what
is
the
next
plan
for
Community
to
do
paste.
A
Yeah
I
can
kind
of
hear
you
I'm
just
I'm,
not
sure
what
you're
asking
now.
F
Yeah,
it's
like
like
for
for
staff
communities,
how
we
resolve
the
problem
that
we
can
bring
Crimson
seasonal
to
real
cost,
not
only
like
a
vistasia.
A
There
are
instructions
for
deploying
Crimson
with
ceph
ADM.
It's.
F
F
Actually,
I
modified
it
like
a
safe
set
volume.
Module
like
like,
like
some
surveying
modules,
to
make
it
wrong
in
a
real
culture.
Maybe
I
will
bring
a
PR
to
your
community.
A
A
I
got
let's
see
here:
actually
they're,
not
merged.
I
I
have
a
PR,
that's
going
to
add
some
better
instructions
for
this
yeah.
F
Mission
ID
hang
on:
oh
okay,
okay,.
A
So
this
PR
has
some
instructions
for
for
running
stuff
the
changes
to
Doc
Dev
Crimson
crimson.rst.
That
would
probably
be
a
good
place
to
start
that
should
merge
pretty
soon
I'm,
just
waiting
on
tests
to
run.
B
A
But
yeah
we'd
love
your
help
in
getting
it
tested
and
hardened
for.
C
Installing
and
then
getting
clustered
up
with
safe
ADM,
using
the
rooms
and
images
from
Shaman,
we
do
use
it
for
the
QV
testing,
so
I
do
have
it
in
on
red
hat
contracts,
I'm,
not
sure
if
you
have
access
to
it.
But
if
you
do
I
can
share
that
link
with
you.
It
has
the
details,
tips
on
how
you
can
set
up
a
cluster
using
safe
ADM
with
the
Crimson
images
from
Shannon.
A
All
right
froggy
does
that
answer
your
your
question.
C
A
Okay,
we
can
probably
move
on
then
how's
it
going.
E
This
week,
hi
oh
I,
first
already
the
LBA
pointer,
VR
and
I
saw
a
bit
another
BR
to
fix.
You
can
make
check
failure
in
in
oh
sorry,
I
think
my
chat
window
is
now
I'm
working,
something
to
the
pr
to
fix
and
failure
of
make
check
in
the
LBA
point
of
PR
and
I
also
tried
to
implement
a
store
company
transactions
throughout
our
that
that
that's
pretty
much
it
that's
all
in
this
week's
work.
A
E
A
E
E
Okay,
I
can
I
can
see
anything
in
the
chat
window.
Oh.
E
That's
it,
oh,
so
so
I
submitted
two
PR
one
for
the
week
transaction
issue,
the
other
for
the
transactions
throughout
our
throughout
our
feature
and
also
I.
Read
the
pr
I
read
the
LV
pointer
PR.
That's
that's
all!