►
Description
Speakers: Neil Levine (Inktank), Kamesh Pemmaraju (Dell)
Inktank Ceph is a transformational open source storage solution fully integrated into OpenStack providing scalable object and block storage (via Cinder) using commodity servers. The Ceph solution is resilient to failures, uses storage efficiently, and performs well under a variety of VM Workloads. Dell Crowbar is an open source software framework that can automatically deploy Ceph and OpenStack on bare metal servers in a matter of hours. The Ceph team worked with Dell to create a Ceph barclamp (a crowbar extention) that integrates Glance, Cinder, and Nova-Volume. As a result, it is lot faster and easier to install, configure, and manage a sizable OpenStack and Ceph cluster that is tightly integrated and cost- optimized.
Hear how OpenStack users can address their storage deployment challenges:
- Overview of the Ceph architecture with unique features and benefits
- Overview of Dell Crowbar and how it can automate and simplify Ceph/OpenStack deployments
- Best practices in deploying cloud storage with Ceph and OpenStack.
For more summit videos, visit: http://www.openstack.org/summit/portland-2013/session-videos/
A
Hello
hi
everyone.
My
name
is
commish
Pam
Raju
I'm,
a
Senior
Product
Manager
with
the
dell
openstack
cloud
solution
group.
Today
we
are
going
to
be
talking
about
how
we
get
easy,
this
to
use,
SEF
and
OpenStack
and
install
them
use
a
crowbar
so
quick
check
our
hands
here.
How
many
a
few
guys
actually
use
crowbar
of
her
crowbar?
A
Okay?
Well,
how
about
Seth
excellent?
So
that's
that's
fantastic!
So
today,
you're
going
to
talk
about
a
few
things.
You
know
for
those
of
you
who
don't
know
what
dell
has
been
doing
in
the
OpenStack
community,
give
a
very
quick
introduction
to
that.
An
introduction
to
what
Seph
is
all
about
and
an
introduction
to
crowbar.
So,
let's
start
off
with
that
and
then
we'll
go
into
why
crowbar
and
Seth
what
problems
are
we
trying
to
solve?
A
There
is
a
OpenStack
storage
gap,
specifically
in
the
block
storage
area
and
we'll
talk
about
how
the
solution
addresses
that
gap.
You
know
it's,
it's
mainly
around
automation
and
scale,
we'll
talk
about
that
and
then
what
we
have
been
doing
with
ink
tank
and
Dell
we've
been
working
together
for
several
months
in
the
community,
and
now
we
have
a
partnership
with
them.
So
what
have
you
done
to
enable
things
for
our
customers
and
then
in
the
end?
I
have
a
specific
example
of
a
customer
installation.
A
That's
actually
going
on
as
we
speak,
so
I've,
given
very
quick
overview
of
what's
going
on
there
and
very
quickly
on
what's
coming
next,
so
that's
kind
of
the
agenda.
So
let
me
quickly
jump
into
a
little
bit
of
a
background
on
dell's
point
of
view
around
OpenStack
clouds
and
what
we've
been
doing.
So
if
you
look
at
any
cloud
installation,
you
know
right,
it
requires
hardware,
it
requires
software,
but
the
majority
of
it
is
really
all
about
operations
right.
So
where
do
you
spend
most
of
your
money
on
time?
A
It's
in
operations,
so
things
like
you
know
when,
when
you
run
out
of
capacity,
you
have
to
add
more
more
servers
and
when
those
servers
are
added,
how
do
you
make
sure
that
those
servers
become
part
of
your
OpenStack
Club
automatically?
What
happens
if
a
server
goes
down?
What
happens
if
you
have
to
patch
an
operating
system?
What
happens
if
you
have
to
update
all
your
changes
in
in
production?
A
So
all
of
that
is
operations,
and
it
requires
significant
focus
on
those
operational
controls
in
products
and
those
decisions
around
what
you
do
in
operations
drive
your
hardware
and
software
decisions.
So
we
have
done
a
lot
of
work
at
Dell
and
we'll
talk
about
that
because
crowbar
and
calculate
some
of
those
best
practices.
So
this
is
how
the
current
solution
looks
like.
So,
on
the
software
side,
we
have
OpenStack,
we
use
OpenStack
for
our
cloud
solution.
Seph
is
the
openstack
cloud
storage
solution.
A
A
Where
crowbar
comes
in
and
their
services
and
consulting
so
I'm
not
going
to
go
into
the
details
of
this,
but
you'll
you'll
see
the
club
the
deck
later
on,
but
effectively
we
have
hardware
that
is
a
power
at
sea
and
power,
HR
series
that
are
part
of
the
solution:
storage
in
computer
part
of
that
we
use
our
own
portfolio,
Forston
switches
and
power
connect.
The
software
is
OpenStack
software.
The
installer
is
crow
bar,
which
we'll
talk
about
as
we
go
forward
here
we
use
set
for
distributed
storage.
A
The
operating
system
we
use
today
is
the
bond
to
12.
Out
of
four.
We
support
both
Windows
and
Linux
guests.
Kvm
is,
as
you
know,
very
a
popular
hypervisor
in
the
OpenStack
world.
So
that's
what
we
use
for
our
solution
as
well,
there's
deployment
and
consulting
their
support.
So
it's
the
when
customers
want
to
stand
up
an
openstack
cloud.
It's
not
just
a
software
piece,
it's
the
end,
our
end-to-end
solution
and
that's
what
dell
has
been
doing.
A
We've
been
working
with
the
community
since
day,
one
for
those
of
you
who
may
not
know
we
have
been
very
active
in
the
community.
We
run
the
OpenStack
meetups
in
Boston
and
Austin.
We
have
been
sponsoring
the
summits
for
a
long
time,
so
we're
excited
to
be
part
of
the
community.
We
are
doing
a
lot
of
work,
Iran
grizzly.
So
with
that
I'm
going
to
hand
it
over
to
kneel
to
give
an
introduction
on
safe
and
I'll
come
back
and
talk
about
crowbar
after
that.
Here.
B
We
go
thanks:
Ganesh
thumbnail,
devine
vp
of
product
at
ink
tank
already,
a
commercial
sponsor
of
the
surf
project,
so
step
is
an
open-source
massively
scalable
distributed
software-defined
storage
system
and
it
combines
three
storage
flavors
in
it.
We've
got
the
object
storage.
So,
if
you're
looking
to
do
an
s3
type
service
or
use
an
alternative
implementation
of
Swift
we're
completely
Swift
and
s3
API
compatible,
we
also
do
the
block
storage
and
are
currently
two
more
of
that
later
on.
B
So
this
is
a
way
of
abstracting
out
your
your
block
volumes
from
your
vm
into
a
separate,
dedicated
storage
system.
Finally,
we
have
our
POSIX
compatible
distributed
file
system,
which
is
ideal
for
legacy
workloads,
but
objective
block
is
really
where
most
of
the
OpenStack
effort
and
integration
work
has
been
done
in
surf,
so
the
key
sort
of
values
or
differentiators
that
we
have
around
Seth
other
than
a
unified
aspect,
which,
in
and
of
itself,
is
a
huge
boon
to
those
of
you
using
OpenStack.
B
Only
after
deploy
one
system
is,
we
have
a
very
clever
way
of
distributing
data
amongst
the
storage
system
using
algorithm
called
crush.
So
when
the
clients
are
writing
data
to
the
storage
nodes
they're
using
an
algorithm
to
calculate
where
the
data
should
be
put
and
where
it
should
be
read
from
this
is
very
very
efficient.
It
really
gives
Seth
a
huge
part
of
its
scale
story.
This
spans
many
many
when
you've
got
thousands
of
no's
having
a
fast
wave
to
work
out
where
data
should
be
without
having
it
go
through
an
index
table
there.
B
B
We
work
very
hard
to
get
the
intelligence
down
into
the
software,
so
you
don't
have
to
do
much
as
an
admin,
one
of
the
sort
of
lesser-known
features,
but
probably
most
powerful
ones
within
SEPTA's
the
ability
to
actually
take
a
object
class
if
you're
writing
your
application
and
attach
a
piece
of
your
application
logic
directly
into
the
storage
system
itself.
This
is
a
way
of
doing
true
distributed.
Compute,
so
example
is
that
you
could
write
a
piece
of
software
which
is
transforming
a
piece
of
data,
whether
it's
an
image
or
a
video.
B
You
maybe
want
to
create
a
thumbnail
or
encode
it.
You
can
create
the
software
that
does
that
the
application
code
and
embed
it
into
the
storage
system
itself,
such
as
the
application,
where
storage
development.
So
this
means
you
don't
have
to
take-
have
an
application.
Take
it
data
out
to
transform
it
right
to
back,
write
it
back
again,
it
all
happens
directly
on
the
nodes
themselves
and
finally,
is
we'll
go
into
in
more
detail
in
the
second
we're
integrated
and
OpenStack
quite
heavily,
also
integrated
into
the
Linux
kernel.
So
on
a
block
side
of
things.
B
If
you
just
want
to
mount
a
block
in
which
you
can
just
do
that,
using
any
failing
local
kernel
so
from
an
architecture
point
of
view,
whether
you're
accessing
the
system
for
object
or
block
or
the
file
system,
it's
all
built
on
our
object.
Storage
system
itself
called
ray
dose,
which
has
an
acronym
which
I
won't
go
into
raid
us,
is
really
the
sort
of
their
heart
and
soul
of
the
system.
That's
where
this
true
scale
out
happens.
B
It's
where
the
intelligent
notes
it
it's,
where
you
put
the
object
classes
if
you're
writing
code
and
it's
a
thing
which
is
you're
going
to
be
scaling
out
here:
the
clients
on
top
whether
it's
object
to
block
a
very
thin
pieces
of
code
generally,
which
is
sitting
on
your
VMS
in
the
case
of
the
block
device
and
needs.
You
also
scale.
B
These
out
as
well
but
you'll,
be
handling
that
in
a
different
capacity
planning
a
decision
through
the
block,
as
you
will
from
the
underlying
radar
system
itself,
so
rados
consists
effectively
of
two
components:
we
have
monitor
nodes
which
are
watches
of
the
system.
These
are
the
nodes
which
are
deciding
which
object,
storage,
nodes
or
earthy.
Nodes
are
up
in
serving
data
which
ones
are
not
serving
data,
so
the
monitor
nodes
themselves,
don't
actually
they're,
not
crafted
a
transaction
between
the
client
and
the
server.
B
B
Will
air
a
standard
file
system?
On
top,
you
typically
recommend
XFS
we're
looking
at
butter,
and
we
do
have
people
using
butter
who
are
adventurous
and
ZFS
is
also
beginning
to
look
attractive
now
these
are
standard
Linux
file
systems
of
any
OSD
process.
On
top.
So
from
a
provisioning
point
of
view,
these
are
fairly
standard
components.
Just
basic
dis
presented,
colonel
folks
down
a
filesystem
and
just
a
part
of
our
packages
included
an
adult
OpenStack
solution,
all
layered
on
top
of
each
other,
and
it's
just
layering.
B
A
Neil
so
we'll
come
back
to
SEF
about
how
stuff
works
with
OpenStack
in
the
next
session.
So
let's
do
a
quick
introduction
to
crowbar
for
those
of
you
who
have
not
heard
of
crowbar
I
just
got
off
of
a
session
this
morning
with
best
buy
and
probar
is
open
source
by
the
way,
and
it
turned
out
that
actually
best
buy
is
using
crowbar
and
we
didn't
know
about
it.
This
is
how
open
source
works,
I
guess,
but.
A
Is
the
way
we
we
define
it
is
is
basically,
if
you
have
think
of
it,
think
of
a
scenario
where
you
get
a
whole
bunch
of
Ross
overs
just
show
up
at
your
doorstep
and
from
that
point
on,
you
want
to
get
your
OpenStack
cluster
up
and
running.
What
does
it
take
for
you
to
do
that
today?
Right
think
about
that
there's
a
ton
of
stuff.
You
need
to
do
at
the
networking
layer,
a
ton
of
stuff
you
need
to
do
for
setting
up
your
DNS,
your
DHCP
or
ipmi.
A
It
is
a
whole
series
of
things
you
have
to
do
before
your
infrastructure
is
ready,
let
alone
the
OpenStack
stuff
right.
There
was
a
user
survey
that
came
back
this
morning.
I
don't
know
if
you
have
seen
it
it's
out
there.
The
user
committee
has
actually
done
a
survey
in
the
last
two
weeks
and
they
serve
at
about
four
hundred
and
fifteen
people
in
the
community,
various
people,
users,
operators.
What
was
the
number
one
challenge?
Any
guesses?
A
It
was
installing
configuring
and
managing
OpenStack
right
and
I'm
talking
about
one
layer
of
more
difficulty
down
below
that
at
the
infrastructure
layer,
and
this
is
what
crowbar
this
is
the
problem
that
crowbar
solves
for
you:
it
automates
the
entire
process
of
Bay
metal,
provisioning
and
getting
OpenStack
and
the
operating
system
everything
up
and
running
for
you
in
an
automated
fashion.
So,
from
a
marketing
point
of
view,
we
say,
get
your
servers
in
boxes
to
a
full
functioning
openstack
cloud
under
two
hours.
So
that's
that's
sort
of
the
mission
statement
for
us.
A
It's
fast
and
flexible.
It's
bare
metal
install
using
so
even
if
you
have
servers,
show
up
there's
all
kinds
of
stuff
inside
that
server.
There's
BIOS,
there's
raid
there's
a
ipmi
settings.
The
servers
have
different
ways
of
handling
your
your
your
actual
hardware.
So
you
somebody
has
to
go
in
there
and
do
stuff
I
mean
they
have
to
go
update
the
firmware.
They
have
to
go.
Configure
the
BIOS.
If
you're
doing
that
manually,
that's
not
cloud,
it
needs
to
be
automated.
It
needs
to
be
done
at
scale
right
and
that's
what
crowbar
does
for
you?
A
It's
all
DevOps
I
mean
the
whole.
The
whole
idea
is
DevOps,
so
it's
an
ongoing
operational
model.
So
as
you
learn
how
to
do
these
things
that
you
do
manually
today
and
take
those
best
practices
and
programming
it
program
it
back
into
your
system
and
our
automated
system,
that's
what
that's!
What
crowbar
does
for
you?
It's
it's
open.
So,
by
the
way,
the
for
those
of
you
who
followed
the
best
buy
story
this
morning,
crowbar
they're,
not
using
dell
servers.
A
That
was
the
entire
HP
stack
that
they
showed
that
picture,
so
probar
actually
works
on
other
servers
to
it's
not
dealt
specific,
it's
not
specific.
Even
to
OpenStack.
You
know
we
don't.
We've
actually
used
probar
to
deploy
Hadoop
clusters,
and
you
know
and
Neil
will
talk
about
it
crowbar
uses.
We
use
crowbar
due
to
deploy
step
clusters,
so
you
can
use
it
to
deploy
any
application
and
it's
apache2
license
it's
all
open
source,
so
you
can
go,
get
it
out
there.
A
So
I
just
wanted
to
spend
a
little
time
about
talking
about
the
soup
versus
the
sandwich
analogy.
So
for
those
of
you
who
are
in
the
virtualization
world
right,
you're,
all
familiar
with
gold
images,
golden
images
right,
golden
images
is
what
we
refer
to
as
soup.
So
you've
got
your
applications.
You've
got
your
utilities,
your
operating
system.
A
Do
you
sort
of
build
all
these
together
and
you
create
this
wonderful
great-looking
golden
image
and
that's
what
you
deploy
right,
but
that
model
they're
pros
and
cons
of
using
that
you
know
the
downside
of
it
is
even
if
there's
a
single
change
if
there's
a
little
patch
to
the
operating
system.
Yeah,
if
you
have
a
thousand
servers
out
there,
how
we're
going
to
go
and
apply
that,
so
you
create
another
golden
image.
You
go
deploy
that
right.
So
that's
the
soup
model
or
the
single
unit
model.
It's
a
single
golden
image
model.
A
There's
the
other
approach
is
to
take
a
layered
approach
right.
So
you
have
all
these
different
pieces
that
you
see
there,
the
layers,
the
sandwich,
marble
right,
operating
systems,
applications
etc,
and
the
idea
is,
you
can
take
each
of
those
things
and
manipulate
them
in
production
layer,
one
layer
at
a
time.
So
you
get
a
lot
of
flexibility
doing
that
right.
So
this
is
how
it
works
in
an
upgrade
right.
A
In
the
case
of
an
upgrade
scenario,
like
I
just
said,
you
have
to
update
an
operating
system,
you
create
a
new
golden
image
and
you
go
off
and
deploy
to
a
thousand
servers.
It's
not
scalable,
obviously
right.
This
is
where
the
whole
DevOps
picture
comes
into
picture.
So,
in
the
case
of
the
layered
marble,
just
one
component
gets
updated
and
this
is
the
whole
philosophy
behind
crowbar
which
you'll
see
in
a
second.
A
So
this
is
a
probar
uses
layers
for
deployment
all
the
way
from
physical
resources
to
the
core
components
and
operating
systems.
The
cloud
infrastructure
OpenStack
in
this
case
all
the
way
up
to
the
AP-
is
right.
Well
get
into
more
details
here
again,
as
I
said:
it's
not
exclusive
to
Dell.
We
have
built
it
in
such
a
way
that
it's
modular
there's
something
called
bar
clamps
which
we'll
talk
about
in
a
second,
but
it's
all
modular
and
dot's.
It's
all
based
on
this
layered
philosophy.
So
how
does
crowbar
work?
A
I'm
not
going
to
go
into
too
much
detail.
You
know
if
you
want
to
drill
into
the
technical
details
come
by
the
dell
boot.
We
have
all
of
our
rock
stars,
basically
from
dell
here
technical
product
managers.
Our
engineers
are
all
here
so
they'll
give
you
a
quick
tour,
what
it
is,
but
basically
what
it
does
imagine
that
you
have
got
OpenStack
up
and
running.
Okay
now
you
found
that
all
of
a
sudden,
you're
out
of
capacity
right,
not
just
from
a
vm
perspective,
you're
out
a
capacity
from
physical
perspective.
A
Now
you
go
add
a
new
server.
How
do
you
do
that
today?
It's
a
manual
process
right.
You
go
configure
the
hardware,
you
put
it
back
into
the
cluster,
but
in
the
case
of
crowbar
the
moment
you
add
the
server
crowbar
discovers
it.
So
there's
this
thing
called
the
wii
there's
a
DHCP
server
and
we
fix
it
boot.
So
there's
a
sledgehammer
image
that
gets
downloaded
it
figures
out
what
is
on
that
server?
What
how
many
resources
does
it
have?
What's
memory?
A
A
No,
do
you
want
it
to
be
something
else
right,
so
you
can
allocate
at
that
point,
and-
and
at
that
point
you
can
say-
and
this
is
where
the
chef
comes
into
picture-
everything
that
crowbar
uses
is
chef
underneath
right,
it's
a
master
orchestrator,
you
think
of
it
that
way,
and
then
it
lays
down
the
operating
system
bits
it
lays
down
the
networking
configuration
it
lays
down
all
the
apps
on
top
of
it.
This
is
all
automated
by
the
way
and
then
there's
a
whole
orchestration
cycle
right.
A
It's
a
complete
state
machine
that
takes
you
from
bare
metal
all
the
way
up
to
a
running
app.
So
that's,
basically
what
it
is
so
so
basically
crowbar
is
a
very
configurable
system.
It's
it's.
You
can
add,
think
these
things
called
bar
clamps,
which
are
effectively
things
that
you
can
use
to
extend
the
computer
capability
of
crowbar
I'm
not
going
to
go
into
the
details
of
this.
But
again
it
has
a
crowbar
API.
It's
called
chef
recipes
in
it,
its
components
and
scripts
you
can
use
to.
A
You
can
use
to
extend
crowbar
to
deploy
your
own
application,
which
is
what
nail
we'll
talk
about
shortly.
But
again,
if
you
look
at
the
overall
picture,
all
the
physical
resources,
this
is
what
I
was
telling
earlier.
You
know:
networks,
raids
by
us
ipmi
all
of
these
things
you
can
over
up
in
any
real
cloud
deployment
and
at
scale.
This
becomes
a
huge
issue
and
then
at
the
operating
system
levels
you
may
be
using
multiple
operating
system.
A
You
know
be
a
red
hat
shop
or
a
suicide
shop
or
a
bunt
usha,
or
you
want
to
have
multiple
things
going
on.
How
do
you
deal
with
that
at
scale
again,
the
same
kind
of
problem
right
and
then,
on
top
of
that
you
have
all
the
OpenStack
components:
Nova
Swift
quantum
cinder.
You
need
to
get
those
all
those
components
and,
as
I
said
earlier,
configuration
of
all
these
pieces
in
the
right
way
in
the
right
order
so
that
they
all
work
together
is
not
easy,
even
today,
even
with
grizzly
and
open
in
a
crowbar.
A
B
Understand
to
understand
why
deployment
is
so
critical
to
us.
It
kind
of
helps
us
understand
some
of
the
evolution
that
we've
gone
through
I
think
over
cloud
with
the
private
cloud
technologies,
particularly
when
OpenStack
over
the
past
couple
years.
So
an
OpenStack
and
some
of
its
predecessors
began
a
couple
of
years
ago.
Everybody
said
what
a
way
to
do
to
wait
to
do.
Storage
was
just
used,
object,
storage
came
as
part
of
these
solutions,
and
that
was
the
brave
new
way
of
doing
it.
But
of
course
the
reality
was
the
most
applications.
B
Couldn't
do
object,
storage
that
you
were
trying
to
you
know,
but
mostly
the
readily
available
application.
You
want
to
remove
to
your
cloud,
didn't
have
any
concept
of
Salus
storage.
So
everyone
said:
okay,
you
gotta
riorca
tect.
We
can't
sorry,
we
can't
react
on
riorca
tech.
Let's
just
use
local
storage,
it's
quick
and
easy,
as
provided
as
part
of
these
default
installations,
but
obviously
local
storage
is
not
like
you
know.
The
cloud
way
of
doing
things
is
not
really
scale
out.
So
then
you
start
to
see
the
storage
admins
coming
forward
and
saying.
B
Well,
we've
got
our
existing
proprietary
appliances-
let's
just
use
those
plug
goes
into
these.
These
open
source
clouds,
but
again
didn't
really
make
sense
that
these
these
weren't
again
true
commodities
scale
out
which
is
really
what
clouds
all
about.
So
we've
arrived
them
out
at
a
point
where
people
realize
that
distributed.
Scale-Out
storage
is
the
way
you
do
things,
and
this
is
this.
B
A
B
Its
self-healing,
it's
got
a
crush
algorithm
and
so
on.
So
we
talk
about
specifically
about
some
of
the
block
components
of
ember
or
we'll
see
how
crowbar
some
helps
you
deploy
order
these
pieces
together
here
so
from
a
features
point
of
view,
Seth
you
with
the
block
storage,
gives
you
standing
kind
of
services
of
cloning
and
snapshotting,
but
it's
got
some
particularly
good
features
which
make
it
suitable
for
OpenStack
and
OpenStack
clouds.
So,
first
of
all,
remember
ray.
Das
is
an
object,
storage
system
here.
B
So
when
we
have
a
block
volume
here,
we're
just
chopping
it
up
into
lots
of
objects
and
then
with
striking
those
across
multiple
OS
DS.
Most
of
all,
multiple
disks
physical
servers
in
your
set
cluster
here,
so
just
the
abstraction
alone
makes
it
very
easy
to
sort
of
have
VMS
die
to
remount
in
a
sort
of
an
EBS
style
way
the
volumes
that
they
were
using.
It
then
also
opens
up
the
door
for
live
migration,
which
is
an
active
topic
within
the
cinder
group
and
so
on.
B
But
let's
think
about
how
do
you
spin
up
images
if
you
want
to
spin
up
a
hundred
images?
What's
actually
happening
here
well,
one
way
as
you
take
the
your
your
boot
volume
and
you
just
copy
it
a
hundred
times,
but
this
is
not
very
efficient,
so
we
use
a
thin
provisioning
and
a
copy
and
write
system
to
to
make
this
a
bit
more
space
and
speed
efficient
here.
B
So
when
you
have
your
initial
image
here,
which
is
say,
144
blocks
worth
on
the
left
hand
side
you
can
just
clone
that
four
times
and
what
we're
cloning
here
is
actually
not
cloning
data,
which
is
creating
an
empty
data
structure
which
has
a
whole
bunch
of
pointers
back
to
the
original
image.
So
the
ability
to
create
those
cloned
copies
is
very,
very
fast
you're,
not
actually
copying
any
data
at
all.
So
booting
up
lots
of
images
at
the
same
time
is
very,
very
fast,
combined
up
with
a
thinly
provisioned
initial
image
or
you're.
B
Only
maybe
saying
it's
two
gig
big,
but
actually
really
on
using
a
one
gig
in
practice,
again
officiants
based
optimization.
Once
you
actually
start
writing
data
once
you've
booted
your
volumes
and
are
actually
making
changes
for
this
initial
image
here,
then
the
point
is
get
flipped
into
actual
real
data
here.
But
of
course
the
client
continues
to
read
from
the
original
image
so
again,
very,
very
efficient
way
of
doing
multiple
boots
of
hundreds
of
volumes
now
in
terms
of
the
OpenStack
integration.
How
this
all
fits
together
here.
B
So
I
mentioned
jobs,
your
gateway
which
I
want
going
to
now,
but
on
on
the
block
device
here,
we're
completely
plugged
into
the
cinder
API.
So
all
of
the
cinder
API
calls
we
have
I
think
exception
of
one
which,
which
isn't
so
important,
are
all
implemented
here
within
asus
F
block
device,
which
men
also
allows
you
to
use
glance
and
have
glanced,
use
the
block
device
with
that
coffee
and
write
capability
to
store
your
images
in
a
very
efficient
way
and
we've
also
modified
the
queue
kvm
hypervisor.
B
So
it's
rbd
aware
it
can
see
these
volumes
it
can
attach
and
detach
them
and
so
and
so
forth.
So
all
of
this
is
natively
integrating
that
has
been
since
folsom,
we're
tracking
all
the
api
changes
and
making
sure
that
are
all
compatible.
Sef.
Ok.
So
how
does
this
come
into
the
deployment
story?
So
we
have
these
OSD
nodes.
We
have
these
monitor
modes
here.
You've
now
also
got
your
rbd
aware
nova,
compute
nodes
here
now.
Ideally,
you
want
to
have
these
homogenous
blocks,
which
are
just
scaling
out.
B
So
from
practical
point
of
view,
how
does
this
work
with
with
crowbar
so
as
commissioned
to
do
we
have
these
things
called
bar
clamps,
which
it
is
modular
pieces
of
code
which
allow
you
to
sort
of
define
specific
roles
or
profiles
about
parts
of
the
stack
here?
So
I
think
tank.
We
work
on
the
SEF
bar
clamps
and
they
do
a
couple
of
things
here.
So,
first
of
all,
you
have
a
V.
The
admin
node
itself
acts
as
a
repository
manager
for
all
the
software.
That's
deploying
out
here.
B
So
with
staff
you
can
do
rolling
upgrades.
We've
got
a
three
month
release
cycle
at
the
moment,
so
all
of
those
packages,
the
freshest
latest
bits,
are
pulled
into
the
admin
mode
itself.
Then
you
can
allocate
particular
machines
as
a
monitor
node
or
as
an
OSD,
node
it'll.
As
commotion
tit,
it
will
do
all
of
the
hardware
stuff
d
ipmi
to
networking
and
so
on
so
forth.
It'll
get
the
right
disks
in
place
and
say
we'll
be
aware
that
these
are
the
discs
which
should
be
holding
the
data,
your
partition
them
up
correctly.
B
It
will
get
the
staff
processes
running
on
all
of
them,
so
the
OSD
and
them
on
roles
all
handled
by
the
bar
clamp
and
then
using
the
Justice
standard,
Nova
bar
clamp.
This
is
now
rbd
aware.
So
when
the
the
Nova
bar
clamp
is
provisioning,
the
OpenStack
software
ensure
that
a
QM
you
is
configured
to
be
aware
that
it
can
be
mount
and
unmount
these
rbd
images
and
back
to
chemist
to
explain
a
little
better
out
some
of
our
customers
and
ongoing
work.
Thanks.
A
Neil
so
so
we've
been
working
with
ink
tank
for
for
a
long
time,
even
before
they
were
in
tank.
They
were
dreamhost
at
one
point
when
they
were
doing
stuff,
so
we
were
involved
in
the
community.
Delon
and
dream
hosts
were
working
in
the
community
and
then
last
year
we
started
really
working
with
them
on
a
more
professional
basis
right,
so
we
partnered
with
them,
and
we
built
this
crow
bar
bar
bar
clamp.
A
You
know
the
ink
tank
folks
did
it,
and,
and
so
we
have
a
joint
solution
today-
that
we
are
brought
to
market
it's
a
crow
bar
bar
clamp
right.
It
deploys
theft
clusters
as
Neal
was
referring
to
earlier.
It's
automatic
it's,
but
it's
all
real
time.
You
can
expand
your
SEF
clusters,
you
can
expand
your
open
star
clusters
and
all
magically
works,
and
of
course
you
know,
customers
still
want
professional
services,
they
want
support
training.
A
So
that's
all
that's
all
delivered
through
collaborative
support
from
dell
and
and
when
we
when
in
time
build
the
bar
clamp.
It's
not
just
the
software
piece
right.
It
has
to
work
with
the
reference
architecture
we
have
in
place.
So
we
went
through
a
whole
technology
partner
program
and
the
whole
bar
clamp
and
the
whole
open
star.
Cluster
widths
f
was
validated
against
the
reference
architecture
in
our
technology
partner
program
and
another
dell
solution.
Center
result.
A
So
it's
a
it's
now
ready
it's
available
in
the
market
and
when
we
launched
it
back
at
Dell
world
in
December,
that
was
the
official
launch
and
since
then
we
have
seen
tremendous
interest
in
this
technology
with
OpenStack
and
SEF.
It's
just
unbelievable.
The
amount
of
inquiries
that
are
coming
in
how
many
how
much
people
are
interested
in
this
stuff.
We
actually
have
a
customer
deployment.
That's
going
to
happen
next
week,
it's
a
university
and
the
situation
very
briefly.
A
I'm
not
going
to
go
into
the
details,
but
this
university
has
more
than
900
researchers
and
they
receive
hundreds
of
millions
of
dollars
in
grants
as
one
of
the
top
research
institution
doing
work
on
cancer
and
genomic
project.
So
it's
big
data
that
do
a
lot
of
work
with
large
amounts
of
data
right.
A
So
what
the
university
was
looking
for
was
a
centralized
data
repository
which
they
can
ensure
compliance,
and
they
know
exactly
how
much
consumption
is
happening,
etc,
etc,
and
they
wanted.
The
intention
was
for
them
for
the
university
to
provide
two
terabytes
of
free
data
to
all
their
researchers
and
anything
beyond
that,
the
they
would
charge
the
research
at
a
nominal
fee,
so
that
was
their
model
right.
A
I
mean
this
is
going
to
be
a
very
large
cluster
at
the
end
of
the
year,
they're
talking
about
5
petabytes,
so
the
university
looked
at
a
lot
of
different
solutions
out
there
they
looked
at
traditional
sands.
They
looked
at
the
public
cloud
storage
solutions
like
AWS.
They
even
looked
at
her
dupe
to
see.
If
that
would
be
a
solution
and
at
the
end
of
all
that
they
they
came
to
a
decision
themselves.
A
All
of
the
stuff
was
on
the
open
source
site,
so
they
checked
it
out
and
they
came
back
and
said
you
know
what
all
of
those
solutions
are
very
expensive.
The
traditional
sense
are
not
going
to
help
us.
You
know
the
Hadoop
was
not
the
right
fit
for
this,
so
they
came
back
to
us
and
said
we
want
the
deling
tank
solution
because
it
fit
our
needs.
It
was
the
right
cost.
You
know
cost
point
for
us.
It
was
the
best
of
all
the
words
for
both
compute
and
storage.
They
were
interested
in
OpenStack.
A
They
were
interested
in
self,
so
we
had
a
solution
that
best
fit
their
needs.
So,
what's
coming
next
sort
of,
let
me
finish
with
warts
coming
from
Dell
this
summer
we
are
already
working
on
grizzly.
Our
team
is
completely
focused
on
that,
so
we
will
have
a
an
officially
supported
del
grizzly
released
by
this
summer.
There's
a
lot
of
work
going
on
around
crowbar
20,
which
is
the
next
generation
of
crowbarred.
It's
all
happening
in
the
community.
It's
open
source
and
we've
been
working
very
closely
with
Souza
Souza
has
been
a
great
partner.
A
Their
sous
a
cloud
solution
by
the
way
is
also
uses
crowbar
as
their
orchestration
and
deployment
engine
and
they've
been
working
very
closely
with
us
in
the
community
for
crowbar
to
dardo
development.
We're
doing
a
number
of
things
in
crowbar
to
door,
though
I'm
not
going
to
go
into
the
details,
but
I
think
the
most
important
thing
is
we
saw
today.
If
you
look
at
all
the
cookbooks,
we
use
chef
right
and
all
the
cookbooks
for
chef
are.
A
We
want
to
upstream
them,
meaning
that
they're
available
to
the
community,
so
they
can
use
it
to
deploy
their
own
OpenStack
clusters,
so
we're
trying
to
decouple
the
the
cookbooks
from
the
crowbar
specific
pieces.
So
that's
another
key
thing
and-
and
you
know
come
by
the
dell
boot
and
we'll
give
you
more
details
on
what
that
is
and
need
we'll
talk
about.
What's
coming
next
on
the
safe
side,.
B
So,
as
mentioned,
SEF
is
now
got
a
three
month:
release
schedule,
which
is
something
we've
recently
changed,
so
Seth
cuttlefish,
which
is
the
next
major
release,
is
coming
out
in
a
couple
of
weeks,
major
features
here:
we've
got
incremental
snapshots
and
the
block
device
which
very
important
when
you're
trying
to
do
a
copy
of
a
block
image
from
one
cluster
to
another.
You
don't
have
to
be
moving
the
whole
thing
you
just
move
the
incremental
changes.
B
Coming
then,
as
well
and
as
commish
mentioned,
we're
going
to
reporting
Lee
the
bar
clamps
over
to
crowbar
v2
when
crowbar
be
tues
who
goes
GA
will
start
work
on
that.
We've
got
a
session
tomorrow,
in
fact
about
the
ceph
roadmap,
and
so
people
don't
going
to
get
involved
and
sort
of
join
us
to
to
plan
out
the
next
set
of
work,
including
new
bar
clamps
work,
but
also
leave
your
continuing
integration
of
surf
and
OpenStack.
B
Sort
of
invite
you
to
come
join
join
us
for
that,
and
then
we've
also
got
another
session
where,
if
you
really
want
to
get
into
some
of
the
detail,
one
of
our
engineers
Josh
Dugan,
it's
going
to
be
giving
a
talk
on
Thursday,
where
he'll
focus
on
a
lot
of
the
cinder
stuff,
but
just
be
going
to
the
general
changes
that
we've
had
a
previous
Reese
bobtail
nodes
which
are
coming
up
and
cuttlefish.
I.
A
A
B
You
know
the
question
was:
is
there
a
way
to
sort
of
get
it
to
not
have
to
wait
for
all
the
replicas
to
be
created
before
a
success
is
returned
back
on
the
right?
It's
already
a
configuration
and
the
crush
rules.
Where
you
can
say
if
you've
got
a
replica
of
say
five,
you
can
say
just
give
me
two
three
and
return
the
success
and
then
the
rest
will
happen
in
a
lazy
eventually
consistent
way.