►
From YouTube: Rook: Intro and Ceph Deep Dive - Travis Nielsen, Red Hat & Satoru Takeuchi, Cybozu, Inc.
Description
Don’t miss out! Join us at our next event: KubeCon + CloudNativeCon Europe 2022 in Valencia, Spain from May 17-20. Learn more at https://kubecon.io The conference features presentations from developers and end users of Kubernetes, Prometheus, Envoy, and all of the other CNCF-hosted projects.
Rook：介绍和 Ceph 平台深探 | Rook: Intro and Ceph Deep Dive - Travis Nielsen, Red Hat & Satoru Takeuchi, Cybozu, Inc.
Rook 项目将被介绍给所有层次和经验的参与者。Rook 是 Kubernetes 的开源云原生存储运营商，为不同的存储解决方案提供平台、框架和支持，以与 Kubernetes 进行原生整合。Rook 将存储软件转变为自我管理和自我修复的存储服务。将对 Ceph 存储提供商进行深入研究，展示 Rook 如何为您的生产数据提供稳定的存储块、共享文件系统和对象存储。我们将介绍 V1.8 版本发布的最新功能，进一步说明 Rook 是如何为生产环境使自身持续增强的。Rook 于 2020 年 10 月被云原生计算基金会接纳为毕业项目。
The Rook project will be introduced to attendees of all levels and experience. Rook is an open source cloud-native storage operator for Kubernetes, providing the platform, framework, and support for a diverse set of storage solutions to natively integrate with Kubernetes. Rook turns storage software into self-managing and self-healing storage services. A deep-dive will be presented for the Ceph storage provider to show how Rook provides stable block, shared file system, and object storage for your production data. The recent features in the v1.8 release will be covered to further illustrate how Rook continues to be enhanced for production environments. Rook was accepted as a graduated project by the Cloud Native Computing Foundation in October 2020.
A
A
First
of
all,
what
are
kubernetes
storage
challenges
that
everyone
has
then,
let's
get
into
what
is
rook,
what
is
ceph,
how
they
work
together
and
then
we'll
get
into
some
features
and
what
features
are
have
all
his
work
always
had
and
what
features
are
in
our
latest
release.
1.8
zotero
will
then
show
a
demo
of
what
it's
like
to
use
rook
and,
at
the
end,
we'll
be
happy
to
take
your
questions.
A
A
A
So
here's
where
rook
came
in,
we
were
looking
at
kubernetes
and
we
thought
hey.
How
do
we
bring
storage
to
kubernetes
in
a
way
that's
natively,
built
in
to
kubernetes
and
works
well
with
kubernetes,
so
rook?
It
creates
and
provides
a
data
platform
inside
your
same
kubernetes
cluster
where
you're
running
other
applications.
A
A
The
way
rook
is
implemented
is
with
an
operator
kubernetes
operator
and
custom
resource
definitions.
So
using
the
custom
resource
definitions,
you
can
tell
rook
how
you
want
the
storage
configured,
but
at
the
end
of
the
day,
the
power
that
rook
provides
is
automating
the
storage
platform
deploying
it
for
you,
configuring
it
for
you
managing
upgrades
for
you.
So
you
don't
have
to
know
all
the
details
of
how
the
storage
platform
works.
A
A
So,
let's
get
into
what
is
ceph
so
ceph
is
a
storage.
Is
the
storage
platform
that
rook
deploys.
Sephi
is
also
open
source
and
it
provides
three
types
of
storage.
It
provides
block,
storage,
shared
file
system
and
object,
which
is
fs3
compliant
ceph
favors
data
consistency.
So
you
never
have
to
worry
about.
If
your
data
is
safe
and
seth
has
been
around
for
almost
10
years
now
in
production
environments,
it
was
first
released
in
july
of
2012.
A
A
A
A
A
The
green
pods,
then,
are
the
csi
driver.
The
csi
driver,
the
csi
provisioner,
the
rbd
plug-in,
which
is
for
block
storage
and
this
ffs
plugin,
which
is
for
the
shared
file
system,
storage
and
then
each
of
the
red
pods
is
a
seth
daemon.
So
the
ceph
pods
are
the
ones
that
actually
provide
that
data
layer
and
there
are
a
number
of
different
daemons
that
ceph
provides
in
that
in
that
data,
layer,
the
mons
and
osds
the
manager
and
so
on.
A
Csi
driver
will
provision
the
storage
either
for
that
block
or
that
file
system
storage.
Now,
on
the
right
hand,
side
with
these
purple
boxes.
We
see
this
is
with
an
object
storage.
So
an
s3
interface
provides
access
to
object,
storage
and
we
provision
that,
in
a
similar
pattern
to
pvcs
with
what
we
call
a
bucket
claim.
A
A
A
If
you
have
a
shared
file
system,
the
set
ffs
kernel
driver
will
write
to
the
ceph
cluster
and
it
will
manage
the
communication
between
all
of
those
different
ceph
pods
or
if
you
have
an
s3
client.
The
s3
client
will
connect
to
the
ceph
rdw
daemon
to
read
and
write
that
object.
Storage
right
to
the
buckets
so
you'll
see
that
in
this
diagram,
when
your
applications
are
reading
and
writing,
data
rook
is
not
directly
in
this
path.
A
Rook
is
only
in
the
management
layer
when
you
set
up
or
provision
the
storage,
let's
get
into
some
of
the
key
features
that
rook
has
always
had
or
had
for
a
long
time
from
the
start.
So
first
of
all,
seth
deploying
seth
is
simple.
With
we've
tried
to
make
it
as
easy
as
we
can,
that
was
one
of
the
goals
of
the
brook
project.
A
From
the
start,
we
provide
several
manifests
for
installing
seth
in
a
default
configuration,
and
you
can
change
those
settings
for
more
complex
configurations,
but
at
the
end
of
the
day
we've
made
ceph
simple
to
install
here.
We
show
several
cube
cuddle
commands
of
what
you
need
to
create
if
you're
creating
these
manifests
directly,
and
we
also
have
two
helm
charts
that
will
help
you
install
the
operator
and
create
the
ceph
cluster
as
well.
A
We
have
a
csi
driver,
the
csi
driver,
as
has
already
been
mentioned,
it
dynamically
provisions,
the
file
in
block
storage.
It
allows
you
to
expand
volumes,
it
will.
It
also
implements
snapshots
and
cloning,
so
you
can
have
some
of
the
backup
functionality
all
right.
So
what
environments
can
you
run?
Rook
in
the
rook
primarily
is
run
in
production
environments.
In
two
types
you
have
bare
metal
environments
where
you
have
your
own
hardware,
your
or
your
own
virtual
environments,
and
you
get
to
install
rook.
A
This
is
the
this
is
the
main
scenario
where
we
expected
rook
to
be
used
where
there
is
no
cloud
provider,
storage
that
you
can
back
your
storage
with
and
back
your
applications
with.
So
the
second
environment,
though
that
is
commonly
run,
is
in
cloud
providers
where,
even
though
cloud
providers
have
storage
that
you
can
build
on,
rook
has
several
benefits
with
ceph
that
overcome
some
limitations
that
cloud
providers
have
so
in
that
cloud
environment.
What
rook
does
is
it
allows
you
to
have
storage
that
spans
availability
zones.
A
You
can
have
faster
failover
times
where
it's
seconds,
instead
of
minutes
for
your
pods
to
to
fail
over,
you
can
have
a
greater
number
of
pvs
per
node
as
many
as
30..
You
can
use
storage
with
better
performance
to
cost
ratio,
and
also
rook
really
gives
you
a
consistent
platform,
no
matter
where
you're
installing
whether
you're
deploying
an
aws
or
azure
or
google
cloud
or
or
any
environment.
A
This
is
it's
a
consistent
storage
platform
everywhere
when
you're
running
in
these
cloud
environments,
seth
will
use
pvcs
as
the
underlying
storage.
So
you
can
connect
seth
to
the
underlying
storage
platform
in
a
consistent
way
with
your
other
kubernetes
applications
as
well.
No
there's
no
need
for
direct
access
to
local
devices
when
you're
running
in
the
cloud
or
mount
them
in
advance.
It's
all
dynamically
provisioned.
A
Domains
right
now,
when
it's
time
to
update
rook
or
ceph
there's
a
way
where
rook
handles
everything
you
tell
rook
what
version
you
want
to
run
and
rook
will
upgrade
all
of
the
rook,
the
airbrush
operator
and
the
rook
demons.
Rick
will
also
update
the
ceph
demons,
all
of
the
mons
and
osd's
in
a
rolling
fashion,
so
that
your
storage
will
remain
active
and
available
and
online
during
the
upgrades
as
well.
A
Another
feature
rick
has
is:
let's
say
you
already
have
a
ceph
cluster
running
outside
of
kubernetes,
so
using
the
csi
driver
and
the
brook
operator
rook
makes
it
simple
to
connect
your
csi
driver
to
that
external
ceph.
Cluster
no
need
to
run
sap
cluster
inside
kubernetes,
if
you,
if
you
want
to
run
and
connect
to
your
existing
set
cluster.
A
Now,
if
you
want
to
have
access
to
object,
storage
with
an
s3
endpoint,
you
can
provision
object
buckets,
so
this
is
done
with
an
object
bucket
claim.
This
is
a
very
similar
pattern
to
using
a
pvc
where
rick
will
create
a
bucket
when
requested,
give
that
application
access
to
the
bucket
with
a
secret,
and
then
you
can
have
your
provision,
your
buckets
dynamically.
A
A
Another
feature
disaster
recovery
for
applications.
The
dr
is
very
important
where
applications
need
to
span
across
clusters
across
kubernetes
clusters.
Let's
say
you
have
a
whole
site
go
down.
Your
application
needs
to
continue
running
in
the
other
site,
so
the
csi
driver
supports
mirroring
the
data
with
ceph
across
the
clusters,
and
we
provide
tools
and
documentation
to
support
your
applications
in
that
failover.
A
A
A
multis.
Networking
the
multis
is
a
network
plug-in
that
provides
more
flexibility
for
different
connections,
so
work
will
fully
support.
Multis
and
1.8.
The
csi
driver
primarily
needed
an
update
to
require
that
multi-support
little
tool
that
we've
released
is
the
crew,
a
group
plugin,
so
perhaps
you've
seen
other
crew
plug-ins.
Really
it's
for
making
tube
cuddle
commands
extend
extendable.
A
So,
for
example,
you
can
say
cube
cuddle,
rook,
stuff,
sap
status
and
you'll
see
the
stuff
status
as
if
you're
running
in
the
rook
toolbox.
But
it's
it's
much
simpler
and
shorter
to
type
out.
That's
just
a
convenience
tool,
but
we
are
really
excited
about
it
in
1.8,
a
few
important
notes,
if
you're
already
a
rook
user
and
and
are
considering
upgrading
to
1.8,
we
do
require
kubernetes,
1.16
or
newer.
Older
versions
are
not
supported
due
to
old
crd
versions.
A
The
ceph
versions
supported
are
octopus
and
pacific,
with
quincy
as
experimental
coming
out
early
next
year,
but
the
support
for
ceph
nautilus
was
removed
and,
finally,
if
you've
been
using
work
for
a
really
long
time
before
the
csi
driver,
the
flex
driver
support
is
was
removed
in
1.8
and
we'll
we
have
a
tool
that
will
help.
You
convert
your
volumes
to
csi
and
now
we
turn
the
time
over
to
zotero
for
a
demo.
B
As
for
pvc-based
cluster,
you
are
free
from
describing
hardware
configurations
like
this,
and
then
you
should.
You
should
specify
only
to
field
the
count
field
and
the
volume
claim
templates,
feed
count,
field
means
number
of
ost
and
volume
claim
templates
field
is
used
for
template,
or
pvc
used
for
osds
pbc-based
cluster
is
very
easy
to
expand.
B
B
B
B
B
B
There,
no,
no
okay!
So,
let's
see
the
progress
of
creating
this
creating
root,
safe
cluster
get
code,
so
rook
safe
operator
is
already
exist
and
the
g
supports
this
port
for
safe
gsi
drivers
and
now
safe,
monitor
port
is
learning
and
the
second
and
the
next
step
is
create
a
manager
port
and
the
third
step
is
looks.
Creating
root,
safe
opera
looks
ost,
look
safe,
osd,
prepare
port,
it's
to
initialize,
initialize
data
structure,
on
top
of
our
local
block
device
and
the
last
rook
safe,
osd
port
is
created.
B
B
B
B
A
All
right,
thank
you
so
teru
for
that
demo
and
thank
you
for
joining
us
today
to
learn
about
rook.
Here's
our
here
are
a
few
links
to
our
website.
Our
documentation
come
join.
Our
slack
ask
questions
we
like
to
build
the
community
in
an
open
way.
We
do
take
contributions.
We're
excited
to
to
have
you
join
the
community,
now
we'd
like
to
take
your
questions.