►
From YouTube: Demo Theater: Ceph: Unified Storage for OpenStack
Description
Ceph is a massively scalable, open source, software defined storage system that runs on commodity hardware.  Integrated with OpenStack since the Folsom release, Ceph provides cost-effective block and object storage for the cloud.   This demonstration will showcase tools for enterprises who operate Ceph clusters, and will show how they can be used to detect issues, troubleshoot, and report on the health of the entire storage cluster.&nbsp. https://docs.openstack.org/openstack-ansible/latest/user/ceph/full-deploy.html
Speaker(s):
Connect with us:
OpenInfra Twitter: https://twitter.com/openinfradev
OpenInfra LinkedIn: https://www.linkedin.com/company/open-infrastructure-foundation/mycompany/
OpenInfra Facebook: https://www.facebook.com/openinfradev
OpenInfra Website: https://openinfra.dev/
#OpenStack #OpenInfra #OpenStackDemo #OpenSource
A
How
many
have
deployed
stuff
a
few,
a
handful?
Okay,
great?
Well,
we
we
don't
have
to
start
with
this,
but
I
am
anyway.
We
have
to
have
an
agreement
about
this
there's
way
too
much
data,
and
it's
not
going
anywhere
and
no
matter
who
you
ask
for
the
stats,
no
matter
who
you
ask
for
their
projection
of
how
much
data
we're
going
to
have
everybody
says
we're
going
to
have
way
more
than
we
can
handle.
A
So
this
particular
study,
which
came
from
an
IBC
report,
says
that
by
2020
over
15
seta
bytes
of
data
will
be
stored
and
1.5
restored.
Today,
I
don't
even
know.
What
is
that
abide?
Is
it's
like
too
many
pass
to
what
I
understand
and
what
I
could
remember.
There's
a
lot
of
data.
The
interesting
thing
about
this
is
that
there's
an
inflection
point
coming
at
some
point
in
the
future:
I,
don't
know
whether
you've
hit
it
already
or
whether
you're
gonna
hit
it
next
year
or
three
years
from
now.
A
So
we
have
a
problem
coming
up,
especially
as
it
relates
to
traditional
storage
solutions
that
don't
scale
as
well
as
they
need
to,
and
the
solution
is
going
from.
What
traditionally
has
been
a
scale-up
type
of
approach
to
a
scale
out
approach
and
I
like
this?
Because
if
you,
if
a
big
shark
comes
along
and
it
takes
a
big
chunk
out
of
your
whale,
you
have
a
dead
whale.
But
if
a
shark
comes
and
eats
1/3
of
your
school
of
fish,
you
still
have
a
school
of
fish
and
the
same
thing
happens
with
distributed.
A
Storage
systems.
Is
that
you've
taken
this
this
workload
that
is
traditionally
been
difficult
to
scale
up
and
you're,
making
something
that
can
scale
up
and
I
think
tank?
We
do
this
with
Steph,
which,
as
we
saw
a
lot
of
a
lot
of
us
have
heard
of
so
Seth,
is
a
unified
storage
platform
and
when
we
say
unified,
we
mean
that
it's
object,
block
and
file
system
storage
in
the
same
platform.
So,
on
the
object
side
we
have
s3
and
Swift
api
compatibility.
A
We
have
support
for
multi-tenant
environments,
integration
with
Keystone
for
those
who
are
deploying
alongside
OpenStack,
we're
slowly
working
on
a
phased
approach
to
geo
replication.
On
the
object
side,
the
community
is
slowly
building
that
and
there's
a
native
API
as
well
that's
extremely
rich
and
goes
beyond
what
you
can
normally
do
with
objects
in
an
object
store
on
the
block
side.
The
virtual
block
device
that
Saif
exposes
provides
support
for
snapshots
and
cloning.
It's
integrated
very
nicely
into
OpenStack
with
integrations
into
cinder
glance
and
Nova
through
the
hypervisor.
A
It's
got:
Stata
default,
Linux
kernel
modules,
their
main
mainline,
Linux,
kernel
modules,
and
it's
got
some
community
technology
around
it
to
allow
you
to
re,
expose
the
virtual
block
devices
as
I
scuzzy
Lunz
and
then
on
the
filesystem
side.
Although
that's
a
little
bit
further
into
the
future,
the
filesystem
is
PI
support
for
cosmic
semantics,
on
top
of
Ceph
again,
modules
are
in
the
Linux
kernel.
A
There's
community
work
to
re
export,
this
file
system
using
sips
and
NFS
through
Samba
or
Ganesha,
and
it's
got
auto
balancing
and
snapshot
capabilities,
although
the
filesystem
is
not
quite
ready
for
production
use.
Yet
looking
at
it
architectural
II
on
the
bottom.
Here,
the
storage
cluster
section,
you
end
up
having
a
collection
of
monitors
and
these
monitors
are
responsible
for
maintaining
the
cluster
map,
understanding
who's
in
and
who's
out,
which
hosts
are
up
in
which
hosts
her
down
and
generally
orchestrating
the
cluster.
And
then
these
object.
A
Storage
daemons
are
part
of
the
data
path
they
provide
access
to
the
underlying
disks.
So
this
is
the
storage
cluster.
On
top
of
the
storage
cluster
are
the
three
interfaces.
The
object,
block
and
file
system
interface
is
so
important
to
understand
that
stuff
is
fundamentally
an
object
store
that
is
built
block
and
file
system
interfaces
above
it.
In
addition
to
a
rest
interface.
On
top
of
that,
through
these
interfaces,
you
can
access
a
bunch
of
stuff
there.
It
speaks
s3
and
Swift
at
the
top.
A
It
can
integrate
with
host
and
hypervisors
through
libvirt
and
other
integration
mechanisms,
I
scuzzy
through
through
some
community
work
and
citizen,
FS,
and
also
the
native
stuff
SDK.
So
this
is
Steph,
but
everybody
raised
their
hands.
So
we
already
know
what
surface
SF's
integration
with
OpenStack
is
pretty
complete.
On
the
object
side
we
integrate
with
Keystone
for
management,
and
we
speak.
The
Swift
API
out
of
the
ArrayList
gateway
on
the
block
device
side
again
integrations
with
cinder
plants
and
Nova
through
the
hypervisor.
So
it's
a
pretty
complete
integration.
A
Stuff
has
also
got
a
really
strong
community.
That's
that's
growing.
This
is
IRC
mailing
listing
commits
commits
commits,
looks
so
meager
there,
but
it
actually
that's
it's
a
matter
of
scale,
but
we
have
a
very
strong
and
growing
community.
So
this
this
is
Seth
at
Inc
tank.
This
last
week
we
just
announced
in
kinks
F
Enterprise,
which
is
a
product
that
we
are
offering
and
I'm
gonna
demo.
A
If
the
demo
gods
are
good
to
me
to
help
enterprises
adopts
eff
and,
what's
inside,
basically
are
these
four
components,
set
object
and
set
block,
which
is
the
Seth
we're
all
used
to.
We
all
know
calamari,
which
is
a
new
visual
manager,
Enterprise
plugins,
which
we're
working
on
and
some
support
services,
which
are
the
the
help
you
get
from
experts
at
adding
tank,
but
we'll
start
with
Seth
object
and
block
the
set
that
we
ship
in
ink
tanks.
F
Enterprise
is
the
100%
open-source
version
of
Seth.
A
It's
not
a
fork,
we're
not
adding
extra
smarts
to
stuff
that
no
one
gets
it's
just
open-source
Seth,
but
we've
chosen
a
version
that
we
believe
is
the
most
stable
version.
That
ink
tank
is
willing
to
provide
long-term
support
for
and
we've
production
harder
than
that
version,
so
this
is
just
standard
everyday,
open
source
set
that
ink
tank
is
willing
to
stand
behind.
A
On
top
of,
that
is
calamari,
which
is
a
on
premise:
application,
it's
a
dashboard
that
allows
you
to
do
some
monitoring
and
diagnostics
of
your
stuff
cluster.
Today,
it's
monitoring
and
diagnostics
tomorrow
its
configuration
deployment
tuning,
but
today
monitoring
a
Diagnostics.
This
is
a
got,
the
capability
of
rolling,
continuous
upgrades
and
it's
it's
sort
of
a
single
dashboard
to
to
look
at
everything
that
Saif
is
doing.
A
We
are
beginning
to
work
on
enterprise
plug-ins
for
proprietary,
Enterprise
ecosystems.
If
you're
running
a
VMware
stack
or
if
you're
running
a
Microsoft,
virtualization
stack
we're
working
on
making
stuff
work
with
that.
That
will
be
part
of
anything
staff
enterprise.
The
this
is
external,
to
course,
F.
This
is
not
something.
A
That's
part,
of
course,
effort
that
the
community
is
interested
in
just
integrations
with
proprietary
ecosystems
and
then
on
top
of
that
in
except
Enterprise
is
the
technical
support,
bug
escalation
pop
you
know
hot
patches
and
that
sort
of
stuff
that
that
you
always
get
from
having
a
support
contractor.
Think
tank
I
have
screen
shot
so
I'm
gonna
step
skip
past,
because
I
think
I'm
gonna
try
to
do
a
live
demo.
A
Is
that
up
there
hey
cool,
so
this
is
the
login
page
for
calamari.
This
is
a
cluster,
that's
actually
running
in
California.
So
here
we
go.
There's
my
data.
So
this
what
I'm
looking
at
now
is
the
dashboard.
The
dashboard
is
a
single
view
of.
What's
going
on
inside
the
Ceph
cluster
in
the
upper
left
hand
corner
you
can
see
this
cluster
has
an
error
and
I
was
speaking
to
sage
the
creator
of
stuff
earlier,
and
he
was
saying:
oh
she's.
We
should
fix
that
problem,
I'm
like
no,
no,
no,
no
keep
it
broken.
A
It
makes
the
mix
the
dashboard
look
nice.
So
we
have
a
cluster.
That's
not
in
the
clean
state
right
now
the
status
on
the
top.
You
can
see
we
have
five
monitors
and
they're
all
doing
fine,
but
out
of
our
30,
we
have
35
OSDs
and
33
of
them
are
up
and
two
of
them
are
down.
So
we
have
a
cluster
that
is
experiencing
an
outage
of
our
6130
for
placement
groups.
Three
are
in
warn
mode
and
seven
are
in
critical.
A
We
can
sort
of
explore
a
little
bit
of
that
later
and
we're
using
33%
of
our
cluster,
and
you
can
see
underneath
all
of
our
OSDs.
Now
the
oft
s
again,
our
software
agents.
These
are
software
agents
that
give
access
to
underlying
storage
resources
of
these
OSTs,
19
and
30
are
are
not
working.
So,
let's
go
over
to
the
workbench,
see
what's
going
on
here.
A
We
have
graphs
that
show
generic
performance
information
from
the
cluster
right
now.
It's
showing
CPU
load
across
the
entire
cluster,
but
I'll
pick
one
host
and
show
that
we
can.
You
can
drill
in
a
little
bit
into
into
a
other
analytics,
and
this
is
coming
from
it's
coming
from
a
Dimond
agents
running
on
each
OSD
and
these
graphs
come
from
graphite.
So
this
is
the
Ceph
Calamari
dashboard
I'm,
going
to
continue
back
in
here.
A
A
One
thing
that's
missing
is
ink
tanks
if
Enterprise
does
not
yet
support
the
file
system,
because
we
don't
believe
that
its
production
ready,
but
we
in
addition,
we
have
the
management
GUI
and
all
the
features
you
get
from
being
an
ink
tank
customer
a
bit
about
the
roadmap
before
I
conclude
and
I'm
a
bit
early.
So
that's
good.
A
In
q1
2014,
we
are
hoping
to
deliver
object
quotas,
we're
also
hoping
to
deliver
I
scuzzy
as
part
of
a
ping
staff,
Enterprise
and
GUI
based
management,
instead
of
just
monitoring
and
diagnostics,
actual
management
to
the
South,
Coast
er,
and
support
for
SNMP
in
q2
we're
looking
at
tearing.
This
is
actually
a
set
feature,
a
set
project
feature.
A
lot
of
these
features
come
from
the
set
projects.
Our
ink
tank
most
of
the
Ceph
project,
erasure
coding,
is
also
coming
in
q2
GUI
based
deployment
is
something
else
that
will
do
in
calamari.
A
The
next
version
is
so
first
monitoring
Diagnostics,
then
management,
then
deployment
q3,
we're
looking
at
a
production,
ready,
SEF,
FS
role,
based
access
control
for
the
GUI,
so
that
you
can
have
different
members
of
your
team
do
different
things:
support
for
call
home
for
enterprise
customers
who
want
it
and
integration
with
vSphere.
So
that's
what's
on
our
roadmap
and
with
that
I'll
concluded,
do
we
have
any
questions?