►
From YouTube: Ceph Crimson/SeaStore Meeting 2023-01-18
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,
I
think
we're
not
going
to
get
Ninja,
so
we
may
as
well
get
started.
So
the
bad
news
is
that
the
lab
is
down
again,
hopefully
for
a
shorter
time.
This
time,
it's
specific
to
the
Centos
8
build,
which
unfortunately
Crimson
needs
the
key
repo
isn't
working
they're
actively
debugging
it.
It
seems
to
be
related
to
the
rgw
instance
that
works
in
the
lab.
A
I
will
let
you
guys
know
when
it
is
unbroken
hopefully
tomorrow.
For
me,
this
week
has
been
mostly
helping
out
with
the
lab
stuff
and
the
best
of
my
ability
and
reviews.
Chennai.
A
B
And
I
have
the
multiple
okay,
the
discussion.
Let's
discuss
now
or
after
the
hand,
updated.
A
We
can
do
it
after
sweetheart.
Go
ahead.
C
C
C
A
B
Okay,
so
so
this
is
the
current
Marco
OST
and
only
one
call
zero.
There
is
a
messenger
and
OSD
PG
share
the
manager.
Other
calls
implemented
the
shared
in
the
service,
so
PG
share.
The
manager
will
dispatch
the
request
to
different
accounts
for,
according
to
the
pg,
to
call
mapping
dude
I
did.
B
And
the
target
of
Miracle
is
that
after
the
messenger
implemented,
the
medical
messenger
and
each
call
has
to
has
to
be
supported,
OSD
and
PG
share
the
manager
policy,
logical
I
mean,
and
so
that
is
the
what
I
do
to
share
the
OSD
and
each
each
course
right
in
the
OSD
will
do
the
same
work
as
the
the
culture
will
ask
you
to
do
the
to
get
the
connection,
get
the
request
and
the
do
the
pt2
called
mapping
and
share
the
send
the
request
to
different
course.
B
A
B
B
And
before
the
multiple,
multiple
call
messenger
implementation,
I
needed
to
simulate
the
multiple
call
messenger,
because
only
call
0
has
the
messenger.
No,
the
messenger
on
other
cost
is
not
implemented
enough.
So
the
the
call,
zero
or
messenger
called
the
changer
dispatcher
and
they
send
the
request
to
OSD
in
the
MS
OSD
Ms
dispatch
I
have
I
will
check
if
it
is
primary
call
or
call
zero,
and
then,
if
it
is
primary,
call
I
will
do
the
submit
to
other,
to
the
call
send
the
request
to
the
other
course.
B
The
call
is
determined
by
the
random
and
divided
by
the.
How
many,
how
many
sap
count
and
in
this
code,
0
I,
will
record
the
connection
to
call
mapping.
So
that
is
for
the
following
distribution
for
the
same
connection
request
and
the
connection
here
is
use
the
foreign
pointer
and
so
submitted
to
the
requester
to
the
other
course
to
simulate
the
medical
messenger
function.
A
A
Yeah
maybe
go
ahead
anyway,.
B
B
And
for
any
functions
need
to
trigger
the
osc
single
distance,
and
the
other
shared
osc
will
will
invoke
on
the
code
0
to
to
do
it.
Just
like
currently.
C
B
A
A
Yeah,
so
it's
going
to
be
a
cross-core
request
for
for
everyone
that
isn't
core
zero.
Just
when
they're,
creating
or
removing
a
placement
group,
so
in
other
words
osd0
might
I.
It
could
turn
out
that
this
isn't
necessary.
But
this
is
my
prediction
as
to
what's
going
to
be
simplest,
you
don't
want
multiple
cores
making
independent
updates
to
The
Shard
mapping.
You
only
want
one
core
making
updates.
B
So
that
means
the
way
if
the
not
Code
Zero
such
as
when
there
is
the
request
it
will
check
the
pg2
share
the
map.
If
it
did
not
exist,
we
will
send
it
to
the
call
zero
zero
to
to
do
the
insert
and
then
after
Caldera
injured,
it
will
modify
and
notify.
The
other
calls
right.
A
B
Yeah
so
OST
repeated
that
yeah
make
sure
I
understand
it
with
yummy,
so
the
other
calls
will
check
the
PG
to
share
the
mapping.
If
it
is
not
exist,
will
evoke
on
call
zero
to
do
the
insert
right.
B
So
this
is
the
PG
to
share
the
marketing
policy
and
for
the
other
dispatchers
request,
for
example,
The
Habit
interested
habit
is
not
shorted,
so
only
one
Happy,
the
messenger
Uncle
zero.
So
so
that
means
only
one.
Code
Zero
can
get
happy
yeah
request
and
for
the
other
dispatcher.
If
the
other
calls
get
the
other
dispatchers
request
and
in
their
own
MSS
patch,
they
will
check
if
it
is
not
called
zero,
we'll
send
to
the
code
0
to
delete
to
handle
it.
So
for
other
dispatchers.
B
Yeah,
so
that's
okay
call
zero
to
do
the
other
dispatcher.
A
B
So
it
means
okay,
it's
also
handled
on
the
call,
zero.
B
Yeah
we'll
see,
and
then
so
this
Decay
get
the
structures
in
the
Charlotte
OSD.
There
is
the
single
tense
data
reference
single
stitch
is
Australia
that
only
start
on
the
on
the
code
0
and
there
is
the
PT
Shadow
manager
get
structure
like
the
currently
OSD
or
currently
OS
has
the
pg
chart
manager.
So
each
strata
currently
will
have
one
data
structure,
PD
Shard
manager
and
for
the
PD
Shadow
manager
in
each
shot.
Osd
it
holds
the
reference
of
osc
Singleton
stage
and
holds
the
reference
for
a
short
service.
B
B
Shorty
OSD
is
the
some
sub
functions
from
the
Ming
OSD
to
handle
the
connection.
All
the
connections.
A
Oh
I
say
yeah
in
that
case,
my
instead
of
short
osds.
Let's
call
this
dispatcher
or
core
dispatcher,
or
something
like
like
that.
Its
purpose
is
to
dispatch
messages
right.
B
Yeah
handle
all
the
connection
called
from
msd's
patch
to
handle
all
the
connection
function.
A
Yeah
look
so
I'm
saying
instead
of
calling
it
Shard
osds,
let's
call
it
Shard
message:
dispatcher,
something
like
like
that.
It's.
A
A
B
B
So
the
distractor
logical
is
okay.
B
A
Yeah,
hopefully
not
the
the
idea
of
those
two.
The
idea
of
those
two
is
just
to
encapsulate
the
things
that
are
OSD
wide
versus
the
things
that
are
per
quart,
so
I'm
guessing
the
wait,
so
you
were
gonna
make
it
to
that
Shard
dispatcher.
A
B
So
this
is
the
shot
of
dispatchers
and
all
the
connections
handle
logical
in
yeah.
A
B
Status
class
in
the
in
the
OST.
A
B
Yeah,
so
all
the
connections
function
and
removed
from
the
main
OST
and
other
OST
membership.
Member
and
the
member
functions
equipped
in
the
me
or
C4
example.
The
classroom,
messenger
public
messenger
front
have
been
changing
back
and
habit
and
both
Epoch
and
the
Brandy
poke
and
the
silver
block
and
yeah.
So
all
the
others
make
effects
and,
for
example,
yeah.