►
From YouTube: Crimson/Seastar OSD Meeting 2018-11-07
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
C
A
C
A
A
A
A
B
B
A
D
B
D
D
D
A
A
Require
that
we
we
we
have,
we
have
a
protein
protein
core.
We
can
always
pass
the
reread
published
or
the
raw
message
to
to
to
to
Charles
area
and
allow
it
to
decipher
the
article
record,
decode
the
message
or
think
of
the
father
list
and
let
the
Austin
map
as
essential,
essential
referral.
Registery
of
the
OT
map.
C
D
D
D
A
A
A
D
Yes
and
the
the
whole
idea
the
why
wise
think
it
is
only
a
POC
because
it
it
actually
needs
some
interface
changes
in
in
the
first
in
the
abstract
level,
like
the
connection
and
the
messenger
and
the
dispatcher
yeah,
because
then
now
that
messenger
is
not,
the
data
structure
of
messenger
is
not
shared
by
all
course.
It
is
a
nothing
data
structures
and
also
the
connection
and
the
dispatchers.
A
D
The
the
behaviors
of
the
data
structure
is
different
because
of
all
the
data
structures
shattered
by
the
peer
address.
So
when
we
use
connections,
we
assume
that
they
are
at
the
original.
They
are
working
on
the
original
core
of
its
its
peer
address,
so
we
we
should
be
aware
of
that
in
our
implementations.
That
depends
on
it,
but,
for
example,
if
we
implement
some
sending
messages
logics,
we
need
to
double
submit
them.
First
to
the
core,
where
the
connection
lives.
D
A
A
A
D
D
D
A
D
D
A
A
D
It
seems
you
need
some
extension.
I
can
I
can't
start
it
next
time,
I
think,
but
this
is
an
example
of
my
my
code.
So
if
a
client
that
is
guaranteed
to
use
connection,
is
you
guaranteed
to
use
one
connection
in
its
logic
right?
This
is
an
example
here.
It
just
use
one
connection
to
send
ping
pong
and
we
can.
D
D
A
A
D
Another
consideration
here
is
that
there
are
true
run
to
completion
faces
in
the
knew
the
English
sISTAR
asti
right.
The
first
one
to
completion
is
to
is
from
when
the
message
is
received
by
messenger
and
just
and
and
here
it
is
sent
to
a
PG
right.
It's
the
the
whole
logic
should
be
around
to
completion
in
one
hall
right,
ideally,
and
another
face
is
when
it
is
Doublemint
to
a
PG
and
inside
that
PG.
The
major
aisle
has
should
be
around
to
completion
until.
A
C
D
C
D
C
C
Ip
address
and
protocol
and
the
port
number
they
will
assign
the
connection
to
to
finance
on
the
cards.
I.
Think,
though
each
each
car
will
get
it
get.
Some
connection
by
the
disconnection
will
will
process
multiple
pcs
request,
but
these
multiple
pieces
request
will
cross
the
curls
all
the
curls,
maybe
yeah.
C
To
the
connection
and
the
message
will
handle
the
message
until
a
to
get
the
PT
number,
then
we
will
send
it
to
the
PT
Sharda
to
stand
are
the
cross
the
other
cross
handle
the
PT
layer
policy,
the
they
will
send
it,
the
the
for
example.
If
we
use
the
booster,
they
will
send
the
traditionals
ride
and
to
do
the
postal
operations
after
the
traditionals
rider
finished
the
proof.
Now
they
will
return
to
that
now.
C
B
A
Yes,
I
think
I
think
it's
a
it's
a
wait.
It's
a
way
to
go
and
okay,
honest
erudite.
The
worst
thing
is
nothing
but
some
course
called
communication,
because
some
crank
cannot
send
the
right,
then
the
right
request
from
the
right
port,
but
we
always
aware
of
it,
because
a
request
has
the
pigeon
number
in
the
embedded
in
it.
So
it's
a
it's
a
not
the
end
of
the
world
and
we
all
we
can
can
correctly.
Pi
PI
forwarded
request
it
to
the
right
core.
D
B
Very
good
performance,
even
if
all
client
connects
to
a
cluster
I
guess
it
can
be
handled
in
a
bit
less
performant
way,
and
it
still
would
be
fine,
but
clients
that
are
aware
about
PG,
sharding
and
tarts.
Talking
using
the
dedicated
the
PG
dedicated
parts
which
are
dedicated
parts
will
get
much
benefit
of
that
all
we
will
need
to
handle
the
backward
compatibility
will
be
just
some
extra
logic
in
oh.
Is
this
messenger
just
to
tend
the
message
to
appropriate
to
appropriate
a
messenger
to
appropriate
part
yeah.
B
A
A
A
A
D
A
A
A
For
for
better
performance,
if,
if
if
we
can
live
with
the,
though,
if
we
want
to
be
that
were
compatible,
the
console
can
still
talk
to
the
server
right
using
a
given
a
single
port,
but
on
the
server
side
we
need
to
to
dispatch
the
request
by
fight
fight
PG.
It
is
targeting
to
the
right
messenger
where
we
listen
to.
We
are
were
fighting
to
the
fighting
Pied
Piper
PG
PG
number.
A
D
Still
responsible
responsible
to
dispatch
messages
according
to
Gigi's
right,
pull
backward,
compatible,
yeah,
so
I
think
there
are
two
stages
there.
The
first
is
to
implemented
the
dispatching
logic
to
support
the
the
current
clients,
and
then
we
can
proceed
to
implement
the
sharded
port
solution
and
modify
the
client
modify
the
clients
write.
A
D
A
D
A
B
A
A
A
B
A
D
D
A
Yes,
because,
for
example,
in
OST,
if
if,
if
were
PG,
want
to
send
a
message
to
to
appear
to
appear
ot,
it
had
no
way
but
to
but
just
need
to.
Oh,
you
always
need
to
contact
the
sharded
messenger
for
for
the
connection,
but
put
it
another
way.
They
always
need
to
to
to
share
the
connections
to
to
its
peers.
A
D
C
A
A
C
So
the
process
for
one
client
requested
to
be
like
this.
The
client
do
the
connection
connected
with,
for
example,
called
zero
Nicole
dealer
accepted
and
connected
right
and
and
a
client
standard
requested
to
call
zero,
o
messenger
process
it
and
get
the
PP
number
example.
The
Pete
nombre
belong
to
the
call
one
so
the
cost
and
the
request
to
call
one.
Oh
wow,
we
all
do
the
PT
layer,
logical
understanding,
the
requester
to
the
traditionals,
ready
to
do
the
pasta
or
other
objects.
The
operation
from
the
traditional
try
to
return
to
the
call
one.
C
C
A
A
A
C
A
We
we
definitely
needed
to
redesign
our
messenger,
so
it
will
be
a
shorted
service
and
probably
we
need
to
refine
refine
the
interface
to
hide
the
defect,
to
hide
the
effects
that
the
connection
could
be
living
on
on
a
different
core.
Even
even
the
standard
want
to
send
a
message
to
to
to
use
a
connection
disturb
down
deeper
in
the
core.
C
A
B
A
D
B
B
A
B
And
also
I
want
start
poking
with
extensions
to
the
read
part
of
the
of
the
object
store
interface.
This
would
allow
me
to
to
grab
mem
stir,
and
maybe
the
the
a
bit
reworked
messenger,
to
have
some
numbers
quite
soon.
Just
to
verify
our
concept
before
before
making
the
official
architecture,
I
would
say.
B
B
Should
we
did
the
question
about
about
order
of
work?
Should
we
go
as
far
as
possible
with
with
object,
store
modification
I
mean
testing
of
a
crime
zone
plus
read
shortcut
plus
mem
star
or
maybe
before
going
to
such
testing?
Maybe
we
should
prepare
a
shortcut
or
refer
rights
as
well.
What
do
you
think
guys.
A
We
pretended
that
memories
to
have
the
share
the
same
interface
as
a
guarantor.
We
assume
that
the
protein
cost
are
still
protein
using
the
the
future
future
promise
in
the
base.
I
think
we're
meeting
the
memory
store
as
a
premise
or
assessment,
because
total
read
is
a
boost.
All
we
need
to
do
to
set
up
the
mini
VM
for
for
for
full
store
and
the
memories
to
have
a
much
less
dependency
on
assumingly
memories,
to
hazard,
much
less
dependency
than
that
Bristow
I'm.
C
B
A
B
B
B
We
are
well
very
frequently
used
operations
like
puri
puri
rights
are
paying
huge
tax
only
for
the
sake
of
supporting
less
much
less
frequented
operations,
like
least
they
like
snapshot
listing
or
something
like
that.
I
guess.
We
also
need
to
dissect
preparer
shortcut
or
right,
but
it
will
I
guess
it
will
be
more
complicated
than
the
one
we
are
working
for
on
for
its.
A
But
the
question
is
what
so,
what's
the
next
step?
If,
yes,
if
part
of
my
past,
how
will
it
help
us
to
shape
the
sister
port
I
think
that
the
the
idea
of
having
shortcut
in
in
existing
ulti
code
is
to
to
to
help
us
to
understand
which
part
we
need
to
port
or
which,
how
how
we
can
execute
the
other?
It.
B
The
rich
shortcut,
it
seems
the
real
necessary
step,
the
most
complicated
step.
There
is
finding
object,
context
and
going
to
to
object
start
just
for
doing
great
I
mean
it's
pretty
straightforward,
and
maybe
we
won't
we
mean.
Maybe
we
want
me
to
even
detected
to
some
kind
of
H
stage
execution
units.
A
Just
if
I,
if
I
fight
by
putting
the
read
pass
to
sister,
we
can
have,
you
can
read
it
all
the
dependency
and
have
better
out.
Turning
of
the
what
this
is
crimson
ulti
would
look
like.
We
probably
can
dispense
with
the
with
the
work
to
to
port
the
Kolkata,
all
the
right
path
to
stories
to
to
to
come
up
with
them,
to
look,
how
all
right
path
and.
A
A
How
is
ship
ship,
the
repast
and
the
beauty,
the
the
the
right
pass,
also
if
it
means
changer,
if,
if
the,
if,
if
we,
we
have,
let
put
it
this
way.
If
we
we
we
have,
if
we,
it
changed
a
lot,
how
we'd
shape
crimson
T
by
PI
by
looking
at
by
looking
at
the
right
path,
shorter
cause,
we
definitely
need
to
to
stop
ASAP,
but
it
does
not
not
hurt
or
it's
not.
It
cannot
change
how
we
shape
the
Crimson
OST
or
each
other
have
a
minor
impact
on
the
Hollywood
design,
our
mobility.
A
B
A
A
A
B
B
A
A
A
A
Try
to
catch
up
with
you
guys,
I
said
after
after
the
conference
and
try
to
understand
the
present
and
the
the
easy
easy
read
pass:
an
easy
bill
passed
and
we'll
try
to
reply.
Chamberlain's
query
regarding
to
share
their
shared
alive.
She'll
share
a
cache,
but
I,
don't
I.
Don't
really
think
we
need
to
worry
about
it
because
it's
a
it's
a
single
thing
and.
A
They're
regarding
to
redock,
they
will
be
working
on.
We
will
continue
looking
at
the
right
path
to
say
how
how
we
impact
our
short-term
direction
and
anything
we'll
we'll
try
to
to
make
make
a
messenger.
A
shared
service
I
know
hi-de-hi
the
only
nice
on
in
the
unit
in,
for
example,
the
look
blue
heart
connection
right
and
how
the
users,
how
do
you
may
do
you
have
any
I
mean
concrete
or
show
time
ago.