►
From YouTube: OpenStack Austin Meeting
Description
OpenStack Meetup (OSATX) http://www.meetup.com/OpenStack-Austin/events/71475222/
Anne Gentle starts at 15:00 (slides: http://www.slideshare.net/annegentle/openstack-documentation-in-the-open)
Greg Althaus starts at 54:30
A
A
A
A
A
A
B
C
D
E
D
B
B
B
B
Oh
and
then
that's
just
more
and
we'll
figure
out
if
we'll
close
with
tdd
and
things
we're
going
to
do,
we've
got.
I
think
I
guess
really
good
topics
this
week,
we'll
talk
about
topics
for
next
month,
if
you,
if
there,
if
anybody
wants
to
start
organizing
out
of
like
additional
events
like
and
set
up
bug
squash
day
to
day,
I'm
hoping
you'll
give
a
summary.
If
you
know
I
don't
know
what
the
community
did.
F
B
C
C
B
C
Was
we
worked
with
a
diablo
before
essex
because
we
really
wanted
to
harden
it,
and
that
was
one
of
the
things
that
we
found?
We
also
found
was
still
in
essex
that
we
identified.
We
are
we're
in
the
process
right
now,
really
merging
back
a
lot
of
other
things
that
we've
discovered
so
we're
going
to
right
now,
merging
a
bunch
of
stuff
that
we've
identified.
E
B
B
A
And
all
you
really
know
is
food,
so
it's
children
and
drinks
and
stuff.
I
highly
recommend
sponsoring.
Oh,
I
forgot
to
mention.
We
are
hiring,
so
let
your
friends
know
are,
you
are
welcome.
Please
contact
me
or
go
to
our
website.
We
have
lots
of
positions
open
product
management
and
development
all
across
the
board.
Even
dell.
Folks,
please
come
join.
B
D
B
You
know
those
are
the
types
of
things
that
we
want.
We
want
to
talk
about
even
something
as
simple
as
you
learn
how
to
use
dev
stack,
you
close
the
bug
in
openstack
and
here's
what
the
bug
was.
You
talked
about
that
for
30
minutes
and
showed
people
the
process
you
went
through
and
how
you
closed
the
bug.
That
would
make
amazing
presentations,
because
we
want
people
unable
to
do
that.
So
please
think
about
how
what
speakers
you
want
what
types
of
things
things
that
you
have
that
you
can
share.
C
Yeah,
that's
cool
right,
so
yeah,
I'm
man,
I
work
completely
on
openstack
documentation
was
hired
to
do
that.
I
have
a
really
strange
view
of
the
world's
documentation,
so
I'm
actually
insane
enough
to
take
this
right
so
and
I
literally
go
into
like
training
groups,
and
I
have
people
come
up
to
me
and
say
thank
you
for
trying.
I
don't
even
know
you,
so
I
want
to
start
off
with
that,
because
everybody
has
to
understand
here.
This
is
big
period.
Audacious
goal
right,
we're
trying.
F
C
C
I
actually
started
with
a
kind
of
an
internship
apprenticeship
approach
by
going
to
an
open
stack
project
that
happened
to
write
openstack
manuals
like
open,
going
to
an
open
source
project
that
happened
to
write,
open
manuals
right,
and
that
was
the
way
that
I
started
learning
about
this.
So
you
know
I'm
trying
to
point
out
that
there
aren't
a
lot
of
people
who
are
willing
to
take
this
on
and
it's
actually
a
really
great
challenge,
and
so
in
about
2009.
After
about
four
years
of
experimenting.
D
C
F
C
Actually
doing
now
is
trying
to
integrate
more
okay,
what's
content
strategy,
what
is
open
source
documentation?
How
do
you
use
level
analytics
to
be
small,
so
all
of
that
is
wrapped
into
some
of
my
goals
around.
Why
I
even
try
to
do
this
right,
so
we
want
to
increase
openstack
adoption
number
one
goal
provide
support.
I
think
a
lot
of
documentation
just
naturally
does
that.
C
F
D
C
F
C
A
E
D
C
So
this
is
a
like
brief
overview
for
anybody
who's
new
to
openstack.
Maybe
I
can
just
skip
it,
but
it's
mixed
with
collaboration.
It's
a
amazing
product
that
projects
that
actually
build
open
source
clouds
right.
So
maybe
I
don't
have
to
review
this,
but
I
actually
give
this
internally
to
rackspace
people
too,
so
that
they
understand
what
documentation
is
all
about.
Broken
stack
so.
C
Our
design
process,
oh
and
apache2o,
license
and
I'm
going
to
talk
about
licensing
and
content
a
little
bit,
but
it's
an
important
part
of
what
it
means
to
bring
contributions
to
either
code
contributions
or
documentation
that
oversight
so
an
open
design
process.
We
go
meet
together
every
six
months
lately
in
california
right
so
right
now,
it's
you
know
very
much.
C
C
F
C
C
So
I
actually
added
the
operations
audience
and
said
we're
going
to
build
a
site
that
actually
brings
in
operators
and
users
as
well.
So
this
right
here
is
the
site.
Watch
right
here,
bam
gets
put
in
a
press
release
fan
three
thousand
hits
one
day
right.
So
this
is
how
important
docs
are-
and
I
know
about
this
right-
because
I'm
looking
at
this-
what
is
going.
F
C
This
this
is
you
watch
on
the
clip
because
you
had
to
go
do
something.
Even
if
you
knew
it
was
a
terrible
video.
I
mean
the
content
was
awful.
You
know,
I'm
totally
not
ashamed
to
say
that
it
was
just
awful.
But
when
I
talk
about
these
things,
I
want
people
to
understand.
We
started
with
nothing
so,
and
I
don't
even
say
we.
I
started
with
nothing.
A
C
F
C
A
C
C
That
you
know
gives
users
images
to
use
your
computer.
It
also
includes
a
dashboard,
a
user
interface
level
way
of
looking
at
your
openstack
applications.
It's
also
now
a
network
connectivity
service.
This
begins
with
wholesome.
It
is
an
incubation
in
the
essex
signal,
and
then
the
volume
service
is
what
is
being
quite
energetically
talked
about
on
the
mailing
list
today.
C
C
F
C
F
D
F
C
C
C
C
F
D
C
Figure
out
what
works?
Well,
once
you
are
in
the
final
release
candidates,
you
have
to
get
an
exception
for
a
new
feature
that
you
want
to
merge
into
the
base
mode,
so
they're
called
future
freeze
exceptions.
That's
you
know
where
it's
kind
of
interesting.
In
the
last
four
to
six
weeks,
the
release
naming
is
actually
based
on.
C
C
C
F
C
It
more
accurate
to
build
a
pattern,
so
we
launched
it
and
it
was
hardly
enough.
It
didn't
get
nearly
the
hits
that,
like
the
long-form
documents
did,
but
just
last
week
I
checked,
like
I
checked
it
two
months
ago.
Three
I
checked
it
in
april
and
I
was
like
well
it's
not
too
great,
but
now
I
just
checked
it
again
and
it
is
starting
to
flip-flop
and
actually
took
me.
C
C
C
Shop,
so
what
we're
going
for,
so
we
have
for
this
release
in
the
two
and
a
half
hour
track.
We
came
up
with
these
four
blueprints.
Very
operations
focused
what
is
a
deployment
template,
and
so
what
I'm
doing
is
working
with
like
tristack
tristack
is
a
a
free
cloud.
Sandbox
that's
made
with
donated
hardware
from
a
lot
of
people
that
work
with
companies
in
this
room.
F
C
E
B
E
C
So
you
know
after
them
in
the
morning,
sometimes
a
lot
about
up
in
the
afternoon.
This
has
happened
once
or
twice,
and
it's
usually
like
I'll
leave
them
like
a
dog
task
like
this
needs
to
get
in,
and
I
had
a
person
in
china
pick
it
up
and
it
was
merged
by
the
next
morning
by
the
guy
in
the
store.
So
there
are
like
exciting
things
that
are
happening
because.
C
D
C
So
it
doesn't
mean
that
oh
there's
a
magic
wand
designed
to
have
a
collaboration,
because
there's
still
just
a
lot.
But
it's
really
interesting
how,
when
you
start
to
make
sure
that
you're
tracking
work-
and
you
start
to
make
sure
that
you
know
what's
coming
down
the
pipeline,
the
amount
of
stuff
you
can
get.
B
C
F
C
C
But
a
lot
of
what
I
do
is
I
just
one-on-one
try
to
touch
basic
intruders.
So
that's
what
happens
and
then
we
also
use
github
and
git,
and
everything
goes
through
the
garrett
review
process,
just
like
the
code.
So
I
like
to
talk
about
this
too,
because
if
you
want
to
learn
how
to
code
and
notice
that
you
can
absolutely
do
documentation
patches.
C
F
C
D
C
C
F
C
F
C
Can
hit
those
two
plus
one
on
all
of
those,
but
I
very
judiciously
use
that
that
ability
right,
but
the
thing
that
we
need-
and-
and
this
is
what
I'm
talking
about
now
is
like
we
need
not
to
just-
have
specs.
We
need
to
have
api
guys
that
let
people
understand
how
to
use
the
api.
What
are
all
of
the
things
I
can
do
with
this?
You
know
create.
C
So
that's
you
know,
kind
of
and
I'll
tell
you
the
future
plans
too,
but
that
should
give
you
an
idea,
like
the
manuals.
They're
considered
official
they're
in
need
for
sort
of
positive
work,
they're
governed
just
like
code
is
you
only
have
a
certain
number
of
votes
to
get
it
in
it's
already
affected.
C
C
C
All
right,
so,
where
do
we
need
to
merge?
Where
are
we
different?
I
don't
track
milestone
releases
because
it's
just
it's
been
just
too
difficult
lately
and
I
think,
probably
in
the
next
release,
we
really
could,
but
it's
not
like
the
doc
team
is
resourced
in
such
a
way
that
I
could
say
you
you're
going
to
track
what's
happening
with
volumes
and
volumes
on
it.
You
know
it's
not
resourced.
That
way.
C
I
I
I
think
I
mean
I
don't
know
if
you
guys
know
like
how
most
of
the
ratios
are
like
writer
to
developer
or
something
like
eight
to
one.
I
don't
even
think
we're
close
we're,
probably
like
one
two
one
hundred
so
that
you
know
it's
just
I'm
not
gonna
promise,
but
I
can't
deliver
right.
So
that's
why
we're
not
packing
monster
releases,
yet
inflation
itself
is
not
yet
set
up,
but
just
this
week.
C
F
C
Teams
have
a
burden
that
they
cannot
put
features
into
production
unless
a
minimum
amount
of
assistance
to
you
to
get
it
documented.
You
come
with
every
release
and
the
panicking
weeks
that
come
before
release.
I
can't
possibly
myself
gate.
I
have
to
rely
on
other
developers
to
gates
some
are
good
at
it.
Some
are
not
so.
F
C
C
F
C
That
is
a
rule
of
online
communities.
It
says
90
people
will
read
everything,
you've
written
and
take
a
look
at
everything.
You've
written
nine
percent
might
do
a
few
edits
here
and
there,
but
they're
not
going
to
be
huge
contributors.
One
percent
will
be
your
contributors.
I
need
to
get
that
percentage
higher
and
I
need
that
one
percent
to
be
pulled
more
from
the
operators
community
and
the
cloud
users
community,
because
I
think
that
community.
C
000
people,
then
I
think
it's
60
about
contributors.
Instead
of
you
know,
300
developer
contributors,
you
know.
So
that's
when
I'm
looking
at
that,
but
I'm
very
happy
to
say
starting
from
zero.
I
have
people
like
I
said
that
are
just
kind
of
picking
stuff
up.
I
have
people
that
I
completely
trust
to
do
reviews
with
the
documentation.
C
C
To
work
on
openstack
there's
actually
grad
students
that
have
worked
on
openstack
projects,
so
I
mean
it's
pretty,
it's
pretty
cool,
but
it's
also
that
I
also
need
to
work
on
getting
that
nine
percent
group
really
able
to
really
enabled
if
they
see
a
small
on
the
because
it
just
shouldn't
be
hard
right.
So
that's
that
just.
C
F
C
The
the
team
in
san
francisco
for
respect
said
we
need
extension,
documentation,
here's
how
we
want
to
do
it,
and
I
said
I
have
this
entire
api
that
opens
up
framework.
Can
you
do
it
this
way
and
they
said
sure?
So
you
know
out
of
you
know
out
of
nothing
came
something
so
we
have
all
of
the
almost
all
of
the
compute
extensions
documented.
I
think
I
want
to
take
all,
but
I
never.
F
C
Magic,
but
I
know
that
people
are
much
more
trusting
the
dots
and
much
more
willing
to
sleep
with
god,
so
I
actually
was
able
to
push
through
100
patches
in
a
month
like
to
me.
That's
really
awesome,
I
don't
know
if
you
work
with
like
enterprise
documentation
teams,
but
that
doesn't
happen.
You
don't
get
100
changes,
you
don't
get
100
reviewed
changes
on
that
quizzes.
So
I'm
just
really
pleased
with
I'd
like
to
talk
about
this
because
part
of
the
entire
tool
changing
field
is
open
and
the
process
results
was
open.
C
C
C
Right,
the
other
thing
that
happened
is
at
about
the
six
month
mark
I
started
to
have
more
commenters.
I
didn't
have
to
be
the
only
one
answering
comments,
so
that
was
another
really
good
flip-flop
that
we
managed
to
do
and
then
so
it
means
that
they
are
answering
each
other,
that
the
dots
themselves
are
able
to
help
people
support
each
other
right
and
then
10,
000
visitors
a
week.
It's
actually
really
good
and
I'm
especially
appreciative
of
the
ones
that
say
right
so.
C
D
C
F
C
D
C
F
C
C
Always
exploring
translations
right.
That
scares
the
jesus
out
of
me,
but
I
I
think
it's
absolutely
necessary,
because
when
I
look
at
westjet
people
are
coming
from
china.
People
are
coming
from
korea.
People
are
coming
from
japan,
they're
going
to
need
documentation
that
serves
them
as
well,
so
and
then
always
always
always
working
on
developers
don't
put
something
in
unless
you
at
least
have
a
little
bit
of
documentation
to
go
with
or
you've
met
with
the
doc
rider
or
you've
flagged
it
so
that
the
operator
knows
this
needs
to
get
documented.
D
C
C
Lot
of
good
conversations,
you
know,
even
with
third-party
publishers,
o'reilly
pearson's
hacked
function.
They
all
want
books
about
openstack.
We
have
an
entire
day
at
a
widely
event,
because,
frankly,
I
think
openstack
was
second
most
popular
after
html5.
The
technology
is
very
interesting
to
people.
You
used
to
be
writing
it
down.
C
C
I
want
you
to
look
at
the
documents
that
are
incoming,
see
if
you
can
triage
it
and
see
if
you
can
test
out
a
doc
fix
and
then
put
it
in
the
comments
I
want
you
to
when
you
are
a
developer
and
you
put
in
a
piece
of
code
that
needs
documentation,
tag
it
with
a
flag.
So
we
know
where
to
prioritize
it.
C
F
C
F
C
F
E
D
F
C
Open
segment
is
every
bit
as
much
as
any
other
project,
any
code
development
project
now
just
logging
in
and
I'm
having
these
conversations.
Like
look,
I
have
a
guy
from
australia
who
treats
his
neighbours
every
day.
He's
gonna
get
an
invite
right
and
they're
like
oh
yeah,
but
the
thing
is
most
of
the
people
that
are
treating
those
at
that
level
are
also
submitting
patches.
So.
F
D
C
You
know
mirrors
and
also
I
mean
I
think,
we're
trying
to
steer
the
conversation
not
around
the
past
to
the
summit,
but
more
around.
I
am
an
active
technical
contributor
to
openstack.
That
means
I
have
voting
privileges.
That
means
that
I
can
be
part
of
a
registry.
That
means
that
people
will
know.
I
am
an
active
contributor
on
this
project.
B
So,
a
year
ago,
or
so
I
started
picking
this
stuff
up
as
well,
and
I
knew
very
little
about
it,
so
I
just
wanted
to
give
you
feedback
on
the
documentation.
First
of
all,
I
think
the
documentation
back
then
you
know
it
was
fairly
young
and
I
was
surprised
of
how
good
it
was.
So
it
was
step
by
step,
however,
finding.
B
Working
on
versus,
like
you
know,
that's
not
obvious
when
I'm
on
a
ubuntu
box
and
I'm
like
you,
know,
app,
get
install
openstack
common
or
whatever.
It's
not
obvious
to
me
that,
okay,
this
is
diablo.
This
is
sx
or
whatever
else,
and
then
I
go
to
the
doors
and
I'm
like
okay,
you
know
I
was
able
to
figure
it
out
like
I
knew
about
this
pattern
right,
but
if
I'm
somebody
that
is
actually
new
to
this
and
it's
kind
of
like
coming
from
the
world
completely
outside
then
they'll
be
like
okay,
I'm
looking.
B
Yeah,
exactly
I'm
looking
at
the
exact
same
page,
yet
the
content
of
of
both
like
in
terms
of
you
know,
once
it's
essex,
one
is
once
it's
diablo
and
the
only
way
I
could
discern
this
is
the
dual
role
is
slightly
different,
so
that
that
is
one
of
the
feedback
things
that
has
frustrated
me.
I
think
you
should
kind
of,
like
I
don't
know
like
do
it.
E
Having
like
a
series
of
links
to
the
different
releases
and
then
just
have
the
one
that
you're
on
be,
you
know
plain
text
and
just
be
able
to
click
on
the
link.
So
if
I'm
looking
at
the
documentation
for
swift
and
then
being
able
to,
if
I'm
looking
at
diablo
ones
and
say,
oh,
I
need
to
go
to
sx.
You
could
just
have
an
sx
link
there
versus
trunk
and
whatever
yeah.
C
C
B
Yeah,
well,
I
I
think,
and
if
you
go
to
like
the
official
page,
I
think
it's
nothing
short
of
extremely
professional,
what
you
get
presented
with
like
in
terms
of
pdf
and
all
of
that
kind
of
stuff.
You
know
like
I,
I
mean
help.
You
know
you
go
to
like
any
enterprise
company
actually
sells
this
software
for
a
living
and
you'll
probably
not
find
the
documentation
as
easily
accessible
as
as
easily
to
consume,
as
that
so
have.
D
C
Well
right,
so
I
actually
have
full-out
waging
debates
of
people
about
why
and
I
have
a
history
with
xml
documentation
where
I
use
dita
for
a
number
of
years,
which
is
an
ibm
standard
that
they
gave
as
an
open
scanner
the
thing
about
facebook
and
xml
in
general.
It
gives
me
the
ability
to
do
things
that
I
couldn't
do
with
other
things:
translations,
eventually
working
with
third
party
publishers,
pdf.
C
F
C
C
B
B
D
C
D
C
D
F
B
A
F
C
B
It's
interesting
one
of
the
things
about
openstack
is
it
doesn't
I
mean,
except
for
the
web
portal,
which
is
really
a
user
portal,
there's
no
user
interface
for
openstack,
and
actually
it's
one
of
the
things,
but
the
crowbar
layer
on
top
of
openstack.
The
way
we
do
it.
We
actually
have
contextual
help
around
nova,
where
you
would
actually
go
if
he
had
a
place
to
say:
okay,
nova,
this
setting
does
this
and
nova.
A
A
B
C
C
A
C
C
To
separate
the
nova
volume
components
out
of
the
nova
project
and
into
its
own
project,
so
there's
been
a
lot
of
movement
in
the
industry
to
provide
a
block
storage
service
right.
So
if
you
think
about
it,
openstack
had
nova
and
swept
swift
is
an
object.
You
can't
really
use
an
object
storage
for
raw
storage
in
a
vm
right,
so
you
need.
D
B
B
C
C
So,
if
you
wanted
to
make
a
change
in
that
environment,
you
had
to
go
through
updating
all
of
nova.
Nova
itself
is
a
set
of
services
right,
scheduler,
api
service,
a
compute
service,
currently
a
volume
service,
a
certificate
service,
a
vnc
service
right.
All
of
these
things
currently
make
up
nova
and
so
trying
to
make
a
change
in
just
the
volume
part
often
makes
you
the
gyrator
part,
so
it
made
sense
to
split
that
out
into
a
separate
project,
so.
D
E
B
C
D
C
So
what
is
cinder
cinder?
I
think
in
some
regards,
if
you
followed
the
whole
quantum
experiment
of
generation
chose
a
slightly
different
path,
so
quantum,
so
we
need
a
network
service,
we're
going
to
start
building
it
we're
going
to
try
and
get
there,
and
it's
going
to
replace
this
thing
over
here.
One
of
these
days
that
was
kind
of
the
clunky
path
now
makes
some
sense,
because
it's
doing
networking
in
kind
of
a
completely
different
way
than.
C
For
you
know
the
volume
and
the
center
project
they
decided.
What
we're
going
to
do
is
we're
going
to
clone
the
existing
noble
volume
code
as
it
exists
today
and
put
it
in
this
project
and
get
it
working
once
we
have
it
working
we'll,
try
and
shift
everybody
over
to
it
and
then
we'll
start
adding
new
features
to
differentiation,
to
allow
vendors
to
add
additional,
plugins
and
stuff
like
that.
That
is
that
the
difference
between
the
volume
today
and
cinder
as
it
comes
out
in
full
sun
should
be
zero.
C
D
C
Services
instead
of
the
mobile
buying
service,
okay,
this
matches
very
nicely
because
the
nova
volume
service
right
now
runs
as
a
separate
api
endpoint,
it's
its
own
public
kind
of
service
providing
its
own
set
of
apis.
So
when
you're,
using
the
nova
volume
service,
you're,
basically
getting
its
own
kind
of
stuff.
C
C
A
B
C
So
that's
kind
of
the
ongoing
debate
right
now,
which
is
the
best
way
and
operational
friendly,
and
so
in
some
regards
the
community's
kind
of
rushed
into
getting
this
done,
which
I
think
is
a
good
thing,
because
in
guys,
if
you've
watched
quantum,
it's
kind
of
lingered-
and
it's
been
this
gyrating
kind
of
mess
of-
is
it
compatible
yet?
Is
it
functional
yet
can.
D
C
C
C
Kind
of
block
slice
or
some
kind
of
storage
back
in
it's
designed
to
be
pluggable
on
the
back
end,
so
that
you
can
provide
different
sets
of
back-end
storage
providers.
So
right-
and
this
is
one
of
the
frustrations-
is
a
lot
of
companies
like
zenta
and
sunfire,
and
dell
and
hpe
had
various
and
netapp
had
various
plugins
for
these
storage
components.
C
B
C
So
currently
they're
very
tight,
well
kind
of
convoluted
well,
even
in
center,
because
sender's
good
copy
of
that
right
to
try
and
minimize
compatibility
interactions
right
copy
code.
So
how
that
works
right
now
is
you
have
to
think
of
cinder
as
two
layers?
The
top
half
is
the
api,
that's
providing
the
basic
function
and
then
that
calls
out
to
a
single
driver
right
now
that
you
specify.
C
C
C
So
that
driver
replacement
was
getting
tricky
by
tying
it
into
nova,
so
the
goal
is
to
make
cinder
a
more
a
smaller
contained
bucket
for
that
set
of
resources
and
control
better.
Now,
this
is
an
interesting
aspect
of
it.
The
sender
team
at
folsom
made
a
decision.
They
said
we're
not
adding
features
for
wholesale.
C
C
One
of
the
first
set
of
options
is
selectable
back-ends
right
to
be
able
to
have
multiple
backings
to
have
a
effectively.
What
this
did.
You
call
us
in
the
cinder
scheduler.
The
idea
is
that
I
may
want
to
create
a
volume,
and
it's
part
of
that
volume
creation
send
in
metadata.
That
says
this
needs
to
be
high-speed
storage.
This
needs
to
be
archival
storage.
This
needs
to
be
that
kind
of
stuff
right.
That
thing
can
go
into
a
volume
scheduler.
C
If
you
will
right
that,
could
then
choose
a
back-end
based
upon
fed
up
metadata
from
the
actual
blogging
services
to
the
scheduler
right.
Very
cool
features
right
that
way,
I
could
say
you
can
see
vendor
services
that
sell.
I'm
I'm
going
to
charge
you
five
bucks
for
the
high
speed
storage
and
three
bucks
with
our
cars
right.
That
kind
of
enablements
is
a
very
cool
feature,
but
it
was
acknowledged
that
you
don't
want
to
do
that,
because
that
introduces
compatibility
problems
that
we
reduce
people
that
you
share.
C
That
were
scheduled
for
nova
and
folsom.
The
sender
team
said
well.
We
will
pull
those
in
to
the
essex
code
base
that
we're
copying
to
make
sure
that
that
compiler
will
be
supported,
so
you'll
be
able
to
use
cinder
as
a
boot
target
for
your
boot
from
volume.
The
other
decision
that
was
made
at
the
time
and.
D
C
C
A
C
C
E
C
E
C
C
Right
now,
the
thought
is
we're
maintaining
the
one-to-one
ownership
kind
of
blocked
it
policy.
I
think
in
grizzly,
there's
some
blueprints
out
there
to
talk
about
beginning
to
do
some
of
that
work
to
enable
multi-ownership-
or
at
least
multi-access,
we'll
see
to
be
honest,
cinder
has
turned
out.
There
was
a
lot
of
interest
at
folsom
the
community
around
it.
The
ptl
john
griffith
is
very
active
in
it.
He's
driving
in
fact
he's
kind
of
like
the
reason
it
exists.
C
C
C
E
C
So
some
of
the
and
in
some
regards
that's
good
because
we
haven't
had
a
lot
of
extra
resources
to
say:
hey,
let's
meet
with
each
other
and
to
be
honest,
I
think
this
has
also
been
a
place
where
I
think
the
nova
side
and
fish
in
particular
learned
a
lot
from
the
quantum
experiment
and
took
an
active
interest
in
saying.
Okay,
we're
going
to
take
this
code
and
click
here.
We're
going
to
do
these
things
and
we're
going
to
follow
this
process
in
a.
D
C
E
I
know
my
vote
would
be
to
just
enable
being
to
turn
on
and
say:
okay,
you
can
do
it,
but
don't
treat
yourself
in
the
foot,
it's
all
in
your
hands
kind
of
thing.
Just
so
I
I
have.
You
know
multiple
instances
that
I
want
to
make
a
service
highly
available
between
the
two
and
that
kind
of
stuff,
or
you
know
something
along
those
lines,
provide
a
parallel
service
for
low
balancing
and
something
like
that.
E
C
C
Say
create
this
volume
from
that
image
making
it
available
to
that
instance.
So
you
can
do
a
shadow
copy
well
so
that,
instead
of
because
right
now,
if
you
think
about
how
you
have
to
build
a
volume
in
anova,
you
have
to
say
I'm
going
to
create
this
volume
and
mount
it
over
here
somehow
get
the
data
into
it.
Then
I'm
going
to
boot
it
where
I'm
going
to
take
a
snapshot,
try
and
get
that
snapshot
out
of
it.
C
So
some
of
the
first
blue
currents
that
I
think
the
synergy
wants
to
do
has
to
do
with.
How
can
I
tie
glance
injection
or
even
just
raw
image
injection
into
my
volume
so
that
I
don't
have
to
go
through
this
interesting?
Mount
booth
cd
installed
some
kind
of
gyration
thing
to
get
my
data
into
this
resistance
storage
right,
especially
as
you're
looking
at
live
migration,
or
even
just
node
migration
or
vm
migration
across
nodes,
so
that
cases.
C
C
Is
you
ask
volume
for
a
us
sender
or
no
volume
or
a
volume,
and
it
says:
okay,
here's
your
id,
then
you
pass
the
instance
and,
along
with
the
instance,
the
volume
id
is
never
compute,
and
it
says
attach
this
to
that
as
a
target
that
I'm
requesting,
and
so
in
the
case
where
the
volume
driver
is
the
local
file
system.
That's
a
high
skill
target
on
that.
E
C
C
C
A
big
component
of
this
as
well.
What
if
I
backed
my
images,
my
glance
back
in
store
was
also
the
same
thing,
providing
my
block
data
store
so
now,
when
I
need
a
copy
of
this
image,
this
cacao
image
for
my
vm,
instead
of
copying
it
into
compute
and
copying
it
as
a
volume.
I
just
snapshot
this
glance
image
and
then
immediately
provide
that
as
nice
as
a
target,
or
in
case
of
like.
D
C
E
B
D
C
You
keep
saying
eye
scheduling
any
plans
for
other
protocols,
fcoe
srp,
so
sure
the
drivers
to
currently
talk
of
one
driver
there's
actually
two
drivers
involved.
One
is
a
nova
compute
side
driver
of
how
it's
well,
it's
kind
of
a
driver,
perhaps
overstating
it's
a
set
of
code.
That
knows
how
to
attach
and
right.
C
E
C
E
C
C
C
D
A
C
Well,
so
what
what
is
an
approach
if
you've
got
a
running
cloud?
That's
running
of
the
volumes
of
migration
yeah,
so
the
biggest
trick
right
now
with
regards
to
know
the
noble
volume
to
send
your
migration
is
the
database
data,
because,
right
now
the
volume
data
is
stored
in
the
node
database
sender
will
have
its
own
database,
so
the
first
step
will
be
a
script
to
copy
that
data
into
sender.
E
C
D
A
D
C
C
E
E
C
Now
is
some
people
consider
that
enough
now
to
me
that's
light
years
ahead
of
what
we
did
for
houston
right
so
to
me,
that's
a
huge
step
improvement
and
so
okay
and
the
community
the
operations
community.
I
think
that
we're
running
it
was
burned
by
just
some
of
those
migrations
and
transfers
and
upgrade
paths.
C
C
D
D
B
This
is
to
me
goes
back
to
the
open
ops
thing
that
I
think
is
really
important
for
openstack
in
general,
which
is,
if
you
know,
if
we
don't
share
operational
best
practices
with
openstack,
then
these
debates
become
impossible
to
resolve
right.
If,
if
you
said
all
right,
here's
how
openstack
is
deployed-
and
these
are
some
of
the
best
practices-
and
at
least
you'd
say
here's
how
you
would
migrate
it.
But
until
that's
right,
open.
C
E
C
C
A
D
C
D
D
B
Been
coordinating
our
talk
today,
tuesday,
we're
going
to
be
talking
a
lot
about
what
it's
going
to
take
for
the
community
to
start
having
a
conversation
about
meaningful
upgrades,
because
right
now
we're
having
we're
having
a
trip
we're
having
enough
trouble
with
the
conversation
around
shared
budget
practice
and
we're
you
know,
that's
that's
a
big
conversation.
That's
coming.
B
Operational
people
focus
on
and
it's
been
unique.
Openstack
is
really
interesting.
I'm
proud
of
the
role
that
our
team
has
played
in
this
of
having
people
start
talking
about
ops,
devops
and
openops
from
the
very
early
days
of
this
project,
so
it
wasn't
just
a
bunch
of
coders
going
off
and
writing.
After
my.