►
From YouTube: Ceph Month 2021: Ceph Project Update
Description
By Sage Weil and Josh Durgin
Slides: https://www.slideshare.net/Inktank_Ceph/202106-ceph-project-update/Inktank_Ceph/202106-ceph-project-update
Ceph month schedule: https://pad.ceph.com/p/ceph-month-june-2021
A
A
These
are
all
nice
words,
but
are
a
little
bit
meaningless
and
a
little
bit
more
concrete
terms.
Seth
is
open
source
software.
That's
a
software-defined
system
doesn't
rely
on
any
particular
piece
of
hardware
because
you
can
run
it
on
any
sort
of
commodity
parts.
That
means
quantity,
servers,
ip
networks,
hard
drives,
ssds
and
vms,
and
so
on
and
it's
unified,
and
that
a
single
cluster
can
serve
object,
block
and
file
workloads.
Obviously,
so
seth
is
free
and
open
source
software.
That
means
you
have
the
freedom
to
use
the
software
freeze
and
beer.
A
A
A
We
provide
data
durability
via
replication
or
erasure
coding,
and
there
are
no
interruptions
of
service
from
rolling
upgrades
or
online
expansion
or
contraction
of
the
cluster
and
seth
is
always
designed
to
favor
consistency
and
correctness
over
performance,
although
obviously
we'll
try
to
get
those
and
also
stuff
is
designed
to
be
scalable.
So
it's
an
elastic
storage
infrastructure,
which
means
that
the
cluster
may
grow
or
shrink
over
time.
As
your
needs,
change
or
as
hardware
is
refreshed.
A
We
release
seth
every
year
in
march,
so
we
have
a
stable
named
release
every
12
months.
We
provide
back
ports
for
two
releases,
so
that
means
bug
fixes
and
security
updates.
That
means
that
a
release
will
release
really
reach
its
end
of
life
shortly
after
the
newer
release.
That's
two
years
after
that,
so,
for
example,
nautilus
is
reaching
end
of
life
right
about
now.
Now
that
pacific
is
out,
so
we
just
did
a
security
bug
fix
release
a
couple
weeks
ago.
A
We
provide
packages
debian
and
rpm
release
packages
on
the
upstream
sep
website,
as
well
as
container
container
images,
and
recently
we've
been
working
on
some
pro
process.
Improvements
in
this
area
so
we're
getting
better
at
doing
the
security
hot
fixes
quickly
and
getting
them
out
simultaneously
for
multiple
stable
branches
and
are
working
on
a
more
regular
cadence
for
those
stable
releases
so
a
little
bit
about
stuff
month,
which
is
where
you
are
right
now
june
21..
A
A
We
did
not
plan
an
in-person
event
this
year
either,
obviously
because
the
pandemic
is
still
continuing,
but
we
wanted
to
give
people
an
update
on
the
project
and
provide
venue,
but
we
didn't
want
sort
of
like
a
full-blown
virtual
conference
that
took
all
day
and
had
you
sitting
in
front
of
zoom
for
extended
periods
of
time.
So
the
idea
is
to
spread
it
out
over
several
weeks
and
have
sort
of
bite-sized
chunks.
A
A
A
So
please
open
up
the
pad
and
add
whatever
you'd
like
next
year.
We
would
like
to
do
another
cephalocon
and
assuming
we
do,
it
would
be
in
march
2022,
but
we
don't
have
any
definite
plans
yet,
but
we
don't
know
where
we
would
hold
it.
We
could
go
back
to
doing
it
in
seoul,
which
is
where
we'd
plan
to
do
it
two
years
ago
or
one
year
ago,
but
didn't
we
could
also
go
for
something
in
north
america
after
seoul
was
canceled.
A
So
if
you
guys
have
suggestions
about
which
region
and
so
on,
please
let
us
know
we
hope
to
have
an
in-person
event,
but
it's
sort
of
an
open
question
whether
we
want
to
try
to
invest
in
making
it
more
of
a
hybrid
type
of
thing
where
you
can
also
participate
remotely
or
if
we
should
just
focus
on
having
sort
of
a
more
traditional
conference,
more
interested
in
your
feedback.
So
please
let
us
know
a
bit
of
an
update
on
the
seth
foundation.
A
A
These
are
educational
institutions
and
government
institutions
and
nonprofits,
and
so
on
so
current
projects
that
the
foundation
is
focused
on
one
that
we
started
a
couple
years
ago
was
an
effort
to
improve
the
theft
documentation
and
we
have
a
full-time
technical
writer
stacked
over
who's
on
contract.
For
a
couple
of
years
now,
hopefully,
you've
noticed
some
improvements
on
the
setbox
as
a
result,
as
a
result
of
his
efforts.
A
We
also
have
a
website
update
that's
in
progress
for
the
last
several
months
or
six
months,
maybe
even
a
year
a
while
now
that
effort
has
been
spearheaded
by
soft
iron,
one
of
our
premier
members
and
we're
very
grateful
for
their
efforts.
There
we're
shifting
away
from
wordpress,
so
it's
gonna
be
a
static
site
generated
from
github.
A
A
They
can
support
both
sort
of
cell
flat
or
instructor
led
courses.
So
there's
the
potential
to
have
more
advanced
courses
later,
even
like
paid
certifications
and
so
on.
We
don't
really
have
any
specific
plans
here.
We're
focused
right
now
on
just
having
some
initial
free
material
there
to
spread
the
level
of
suffix
expertise
within
the
community,
but
we're
excited
about
pursuing
this
new
direction.
A
Sorry,
my
headset
always
turns
off
we're
drastically
reducing
the
amount
of
money
that
the
fundation
has
been
spending
with
public
cloud
providers
to
host
a
lot
of
the
infrastructure
by
buying
hardware
to
put
in
the
cpu
lab.
Instead,
it's
much
more
cost
effective,
and
so
at
this
point,
we've
basically
are
only
putting
public-facing
content
in
ovh.
So
things
like
the
tracker
and
the
stuff
website
and
download.com.
A
So
we're
pretty
happy
about
that.
We're
saving
a
bunch
of
money
there
and
buying
lab
hardware.
So
that's
hardware
for
doing
builds
for
doing
ci
tests,
all
the
github
checks
and
stuff
that
we
do
and
we're
also
expanding
the
stuff
cluster.
That's
in
the
lab
that
we
use
to
store
all
of
our
stuff
results,
and
so
on.
Windows
support
is
coming
along
we're
contracting
with
cloud
base
to
do
a
lot
of
this
initial
development
and
to
set
up
all
the
upstream
ci
and
testing
and
stuff
to
do
that.
A
So
we're
very
excited
we're
going
to
hear
more
about
that
from
alessandro
in
about
45
minutes
and
also
there's
a
new
marketing
committee
right
now,
soft
iron
canonical
and
red
hat
are
participating,
but
we're
eager
to
have
anybody
else
going
in.
Essentially
this
is
the
idea
here
is
to
coordinate
sort
of
upstream
project,
focused
marketing
activity
and
press
and
so
on
for
the
community.
A
B
B
B
So
that
should
be
able
to
help
us
use
the
lab
much
more
efficiently
and
get
a
lot
more
interesting
testing
done,
especially
at
larger
scales
within
the
lab
another
area.
We
want
to
focus
on
going
in
in
the
future
is
downgrade
testing.
This
would
mean
some
testing
downgrades
within
a
given
major
release,
so
from
one
minor
point
release
to
the
previous
one
or
perhaps
for
the
the
previous
few.
B
B
The
orange
here
is
octopus.
These
are
different
versions
and
the
little
red
there
is
pacific,
so
pacific
was
just
was
just
released
around
that
time.
We
see
that
line
starting
to
get
increased
and
octopus
is
leveled
off,
so
it's
users
are
upgrading
now
to
pacific
and
now
that
it's
so,
which
is
great
to
see.
B
B
B
There's
an
optional
identity
channel
that
lets
you
provide
some
kind
of
information
like
an
email
address
in
case
developers
would
like
to
contact
you
about
your
cluster
and
in
the
future,
we're
working
on
a
performance
channel
to
add
a
bit
more
granular
information
about
how
the
cluster
is
used.
In
terms
of
like
what
kinds
of
read
versus
write
patterns
we
see
in
the
cluster,
what
kind
of
rates
there
are
other
sorts
of
information
like
that.
B
B
Grab
the
json
report
that
includes
all
this
information
and
inspect
yourself
to
see
exact,
precisely
what
is
being
shared
and
what
isn't
safe.
So
you
think
on
the
next
slide,
we
have
a
little
bit
of
information
about
from
the
most
recent
ceph
user
survey,
asking
whether
folks
enable
telemetry,
and
we
see
about
a
quarter
of
that
response.
Finders
haven't
enabled
on
every
cluster,
another
15
or
so
have
enabled
on
some
clusters
and
60
don't
have
it
enabled
yet
there's
a
wide
range
of
reasons.
For
this.
B
The
most
common
answer
is
that
the
clusters
on
our
protected
network
that
doesn't
have
access
to
the
internet.
Unfortunately,
we
have
a
solution
for
this.
You
can
add
a
socks
proxy
to
that
selling
p
module
and
have
it
report
through
that.
That's
one
side
pretty
easy
to
solve.
Second,
most
common
is,
I
haven't
gotten
around
to
it
yet.
B
I
would
like
to
talk
a
little
bit
about
where
we
see
stuff
going
in
the
future
in
general.
I
think
there
are
kind
of
three
major
aspects
of
that
we
want
to
focus
on.
First
off
is,
of
course,
the
basic
reliability,
which
is
the
baseline
of
a
storage
system.
You
expect
it
to
be
stable
and
not
lose
your
data,
of
course,
and
then.
Secondly,
there
is
a
user
experience,
though
out
of
the
box.
B
B
Kind
of
helping
you
set
up
more
end
user
protocols
that
you
would
that
would
be
taking
more
effort
than
with
other
systems.
So
you
can
really
easily
set
up
a
small
cluster
to
as
a
kind
of
nas
replacement
and
we're
working
on
kind
of
turnkey
support
for
nfs
and
object,
storage
and
samba
coming
in
quincy.
B
So
there
are
a
number
of
new
classes
of
devices
coming
along
down
the
pipe
they're
at
varying
stages
of
development.
Some
are
already
available
for
purchase
today.
Some
are
still
in
kind
of
standardization
phases,
but
we're
looking
at
a
number
of
these,
especially
in
the
context
of
like
crimson
rework
of
the
osd,
to
take
advantage
of
these
incredibly
fast
storage
devices,
which
have
really
shifted
the
bottlenecks
over
the
last
five
to
ten
years
from
the
disc
to
the
cpu.
B
But
we'll
see
a
lot
more
discussion
about
what
exactly
that
means
in
terms
of
crimson
later
in
the
sf
month.
But
for
now
is
to
be
aware
that
this
is
kind
of
where
we're
dealing
with
all
these
kinds
of
different
new
hardware
and
new
devices
and
it's
being
designed
in
a
way.
That's
flexible
and
composable
enough
to
work
with
any
of
these.
B
There's
also
some
discussion
on
further
future
plans
for
crimson
a
kind
of
a
second
phase
of
it,
which
would
would
involve
changing
the
replication
style
of
the
osd,
to
avoid
needing
to
write,
involve
the
cpus
on
the
replicas
in
the
replication
path
at
all.
So
that
would
be
a
massive
decrease
in
the
cpu
requirements
that
if
you
have
a
three
to
a
three
times
replication
that
would
be
you
know,
cutting
out
the
cpu
from
those
two
replicas
would
be
a
two-thirds
reduction,
which
would
be
huge,
that's
a
a
very
large
project.
B
Finally,
there's
a
large
ecosystem
of
software
around
nsf
that
stuff
integrates
with
some
of
these
things
are
I'm
ensuring,
like
rook
in
the
kubernetes
space
and
there's
a
more
also
more
support
for
k
native
via
rgw,
especially
with
the
bucket
notifications,
apis
and
things
like
sp
select,
which
let
you
work
with
all
kinds
of
software,
like
spark
that
treats
the
very
large
scale
object
store
almost
like
a
database
also
a
lot
of
efforts
around
data
movement
in
general
and
multi-site,
with
interoperability
between
a
private
cloud
and
a
public
cloud.
In
particular.
B
This
will
probably
be
described
a
bit
more
in
the
rgw
talks
later
this
month,
but
some
of
it
involves
some
kind
of
replication
between
a
private
data
center
and
a
public
cloud,
as
well
as
within
a
public
cloud
and
being
able
to
choose
different
backends
for
each
of
those
there's.
Also
some
newer
emerging
de
facto
standards
in
in
the
industry
like
apache
aero
4k.
These
are
kind
of
general
data
and
formats
for
use
for
for
a
large
number
of
tools,
especially
in
the
machine
learning
and
data
science.
B
Space
which
are
giving
storing
data
in
a
very
efficient
format.
For
queries,
as
well
as
enabling
queries
to
be
saved
as
kind
of
like
a
what
you
might
call
a
materialized
view
in
the
relational
database
world,
so
you
can
have
multiple
steps
in
in
your
pipeline
that
kind
of
trade
these
these
these
use
of
the
data
and
then
expose
them
to
subsequent
steps
without
any
of
the
data
any
computation
leaving
the
cluster
you
could.