►
From YouTube: OpenCrowbar Planning 2014 05 21
Description
OpenCrowbar Planning Meeting.
Topic was focused on how to grow community beyond Dell Support.
Notes: http://pad.opencrowbar.org/p/community-planning-meeting-2014-05-21
A
There
we
go
hello,
everybody
welcome
to
the
may
21st
open
crib,
our
community
meeting
I'm,
not
exactly
sure
where
we
fit
on
our
cycles,
so
I'm
going
to
treat
this
like
a
planning
meeting
and
then
hopefully
we'll
go
back
as
needed
to
have
bi-weekly
cadence.
Next
week
we
talked
about
design
and
choice,
about
design
based
on
things
we
discussed
planning
and
then
we'd
be
back
every
other
week
doing
planning.
A
We've
working
on
the
agenda
here
and
the
number
one
thing
I'm
assuming
part
of
the
reason
for
people's
interest
today
is
to
talk
through
the
announcement
for
dell
to
full
engineering
resources
off
of
the
up
and
comer
project.
I'm
not
going
to
go
through
and
read
the
email,
but
the
effect
is
that
dell
has
completed
funding
of
Crowborough
activities
and
full
release.
A
Sort
of
puts
open
crib
are
in
a
very
good
state
or
community
to
pick
it
up
and
start
running
with
it,
and
I've
been
asked
to
continue
to
help,
maintain
and
grow
the
community
as
much
as
much
as
the
communities
interested
in
participating
in
that
I've
taken
inventory
of
a
lot
of
what's
going
on
in
the
space,
I'm
always
happy
to
hear
more.
There
might
be
something
we
want
to
do
on
an
etherpad.
A
Actually,
I
think
that's
exactly
what
we
should
do
is
do
it
on
a
drip
pad,
but
I
haven't
seen
any
other
projects
that
have
the
breadth
of
capabilities.
Frankly,
if
even
crowbar,
one
is
still
advantaged
over
a
lot
of
other
systems
that
we
have
seen
crowbar
to
is
the
whole
nother
level.
Because
of
the
orchestration
capabilities.
A
A
Okay,
good
I
thought
it
was
pretty
straightforward,
but
because
and
then
I
as
a
separate
topic
and
I
was
going
to
talk
through
community
support,
not
options
for
that,
but
Adam
I
think
you're
right,
crowbar
versus
open
crowbar
is
probably
the
next
next
area
to
go.
You
want
to
lead
that
off,
or
did
you
have
just
questions.
B
Yeah,
just
questions
really
I
mean
I
mean
all
I
know
is
that
Sousa
is
very
actively
developing
on
the
crowbar.
You
know
effectively
on
Roxie
branch
and
don't
you
following
that
and
we
haven't
touched
open
crowbar,
but
I
I've
heard
from
people
outside
like
last
week
in
Atlanta
people
were
sort
of
asking
me.
What's
you
know,
what's
the
future
directions
to
open,
proviron,
Hannah
pounded
regulated
in
one
community
that
you
communities,
none
I,
couldn't
couldn't
really
answer
with
any
surety?
No.
A
And
so
one
of
the
questions
I
think
one
of
the
assumptions
I've
made
is
that
the
architectural
limits
in
crowbar
one
would
effectively
limited
its
life,
and
changes
of
Zeus
has
made
in
supporting
you
know.
Working
on
the
stony
branch
may
have
addressed
some
of
those
architectural
limitations.
We
should
put
those
put
those
on
the
table
and
figure
out
if,
if
there's
a
sustainable
path,
the
the
code,
the
code
between
the
two,
the
core
code
between
the
two,
is
effectively
totally
different.
A
And
so
I
think
the
question
to
me
is
is
from
a
community
perspective.
Is
there
a
reason
to
migrate?
There
I
mean
there's
clearly
shared
lineage
is
clearly
from
the
actual
workloads.
There's
a
there's,
a
high
degree
of
overlap
and
the
skill
sets
translate
and
a
lot
of
the
approaches
and
designs
translate.
So
my
my
hope
had
been
that
the
community
would
come
over
to
open
crowbar
because
architectural
ii
it
has
it
addresses
the
limitations
in
crib,
r1
and
we'd
be
able
to
keep
it
as
a
single
community,
but
that
only
that
only
really
works.
A
B
Yeah,
well,
I
mean,
I
think,
what
speaks
for
anyone
else.
I
hand
side
caesar,
but
I
think
was
prevented
up
from
coming.
It
fosters,
but
we
just
need
you
to
get
a
product
out
the
door
and
you
know
open
crowbar.
This
is
still
not
there,
and
so
we
didn't
really
have
any
choice
and
them,
as
I
understand
that,
there's
probably
still
quite
a
bit
of
work,
left
to
get
it
to
the
stage.
Where
could
the
toy
OpenStack
and
be
one
feature
parity
with
a
sort
of
vanilla
crow
valve
on
decks?
B
So
the
question
becomes
for
us
and
presumably
for
other
people
in
the
community.
You
know
by
the
by
the
time
open
crowbar
is
capable
of
doing
that.
What
other
solutions
are
going
to
be
able
to
see-
and
you
know,
there's
question
of
investment
and
I
mean
I
agree
with
you
and
of
course
we
would
probably
prefer
both
biased
in
this
respect
that
the
orchestration
engine
in
crowbar
to
is
is
a
in
a
really
nice
thing.
It's
got
a
lot
of
promise.
B
You
know
I'm,
obviously
biased,
because
I
was
involved
in
the
planning,
rather
the
design
of
that,
but
some.
Thus
you
know
without
momentum,
in
the
project
and
and
a
community
behind
it
all
that
kind
of
nice
design
and
core
technologies.
It's
really
not
much
use
when
it's
pitched
against
something
else,
that's
kind
of
bigger
than
even
if
it's
you
know,
potentially
kind
of
uglier
competitor
at
the
end
of
the
day
that
community
momentum
is
is
really
critical
thing.
A
No
I
completely
I
completely
agree
with
you.
That's
the
charge
for
me
is
to
see
if
what
we've
done
attracts
a
community.
I
actually
I
believe
that
the
state,
the
anvil
release,
puts
open
krub
are
in
a
I
believe
it's
a
head
of
crowbar
one
feature
set
as
far
as
the
it
doesn't.
It
doesn't
have
the
the
field
trials
and
and
burn
in
that
crowbar.
One
has,
but
from
it
from
parody
with
the
base
I
can
deploy
in,
alas,
and
install
an
OS
and
set
up
a
network
and
do
those
things
it's
it's.
A
It's
there,
it's
a
head
from
it
from
a
scale
perspective
right
and
what
the
transparency
and
addressing
a
lot
of
the
issues
that
we
had
and
bringing
features
like
ipv6
and
being
able
to
be
heterogeneous.
Os
I
mean
there's
a
are
you
you?
You
understand
the
architectural
pieces
very,
very
well
getting
out
of
the
chef
limitations
and
addressing
this
thing.
So
those
are
all
there.
A
It
is
a
question
really
of
user
momentum
and
developer
support
for
that,
and
this
is
why
I
think
it's
important
to
fruit.
You
know
and
I'll
get
this
built
to
do
a
comparison
matrix
and
show
how
crowbar
stacks
up
against
another
infrastructure,
because
to
make
this
work
there
will
somebody
will
have
to
take
the
leap
that
says:
okay,
this
can
work
if
I
start
using
it
it
can.
It
can
do
this
work
for
me
and
well.
I.
A
Guess
we'll
talk
about
that
in
the
community
piece
as
far
as
the
open
openstack
pieces,
which
I
think
are
a
primary
driver
for
this,
you
know
it's
it.
That's
a
matter
of
porting
to
the
up
streams.
Actually,
our
team
and
there's
some
people
on
the
team
who
are
doing
this
work,
we're
actively
doing
the
Icehouse
cookbooks
and
bringing
in
the
up
streams
for
that,
and
so
it's
not
a
matter
of
going
off
and
doing
it
on
your
own,
like
we've
had
to
do
in
the
past.
A
It's
really
a
matter
of
being
part
of
the
open
source
community,
the
upstream
community
for
OpenStack,
and
so
that's
I,
think
it's
I
think
it's
very
doable.
It's
going
to
take
evaluating
and
seeing
what's
going
to
happen,
somebody's
got
to
be
the
first
people
to
step
in
the
community
and
be
there
11
recent
one
thing:
I
guess
to
put
a
fine
point
in
the
crowbar
one
discussion
versus
crowbar
to
I.
Don't
see
any
realistic
way.
B
You
so
I
suppose
I'm
one
question
did
occur
to
me
on
the
little
gals
in
the
Dell
enhancement
just
occurred
to
me
off
the
back
of
what
you
just
said
about
the
openstack
fits,
so
so
this
means.
So
there
were
people
on
a
dell
team
who
were
had
made
some
progress
on
the
OpenStack
bar
clamps,
and
does
this
mean
that
that
man
becomes
a
spare
time
kind
of
hobby
effort
for
them?.
A
And
unless,
unless
somebody
sponsors
it
it
right,
then
that
would
be
the
alternative,
but
yes
for
the
dell
employees,
it's
a
spare
time
activity
they'll
be
in
there
in
the
community,
and
if
people
are
trying
to
pick
it
up,
we
can
be
resources
for
people
who
are
trying
to
spin
it
up.
That
is
right.
Bells
bells
not
trying
to
kill
the
project,
we're
trying
to
launch
it
into
the
community,
and
so.
A
You
that's
actually
that's
the
exact
thing
that
I'm
looking
for
so
there's
a
certain
degree
of
crowbar
work
that
you
know
I
think
they'll
be.
There
are
people
who
wanted
who
will
do
spare
time,
but
it's
much
more
of
a
project
that
accomplished
as
a
business
function,
bringing
up
hardware
things
like
that,
so
sponsoring
specifically
means
a
company
that
wants
to
implement
crowbar.
That's
going
to
pay
for
consulting
individuals
to
do
consulting
work
on
it.
I've
been
approached
by
individuals
who
want
to
do
crowbar,
consulting
and
would
do
crowbar
consulting
as
contracts
were
available.
A
Obviously,
I
can
act
as
an
intermediary
with
that,
but
I'm
not
going
to
at
this
point
create
a
list
of
names
because
that
would
not
be
kosher
and
and
or
companies
who
want
to
have
have
a
developer
or
person
on
staff
who
have
some
degree
of
time
dedicated
to
running
this.
You
know
actually
building
the
system
and
making
it
work.
So
del
had
a
certain
degree
of
engineers.
Souza
has
a
certain
degree
of
engineers
who
are
effectively
committed
to
making
crowbar
operations
work.
A
A
Who
see
what
we're
doing
and
understand
that,
if
that
they
can
cut,
you
know
they
can
work
with
Roberto
accomplished
similar
objectives
or
I
provisioning
physical
gear,
and
they
might
be
coming
in
to
support
their
solutions
or
their
capabilities
so
that
that
would
be
a
corporate
sponsor,
like
a
user
sponsor
where
you're
trying
to
accomplish
a
specific
goal
and
can
put
some
development
time
on
to
it.
The
same
type
of
person
who
was
actually
but
able
interested
in
hiring
consulting
to
help.
A
Do
that
and
then
an
actual
vendor
who
would
come
in
and
provide
support
for
that,
so
Souza
decided
to
move
to
open
crowbar.
They
would
effectively
be
the
vendor
spot
I
love
to
see
over
time
an
actual
ecosystem
where
you
could
buy
paid
support
and
things
like
that
and
if
that
occurs,
that
would
be
another
category
of
responsible
for
the
project.
C
A
Exactly
and
and
I
can
tell
you
that
there
are
people
who
are
interested
in
supporting
the
community
and
I've
talked
to
people
on
both
sides.
It's
it's
a
bootstrapping
exercise
of
understanding
the
value
proposition,
which
is
part
of
my
job,
to
help
explain
the
value
proposition.
What
we've
built,
because
atoms
are
exactly
right
right
now,
it's
a
project
that
has
a
lot
of
interesting
potential
until
we've
got
a
thousand
no
deployment.
A
It's
a
it's
bit
its
potential.
You
know
to
me:
that's
that's!
The
milestone
we
want
to
achieve
I
feel
very
confident
in
the
capabilities
to
do
that,
because
we've
been
testing
in
22.
You
know
up
into
the
hundreds
so
far
and
we
could
actually
to
me
a
good
topic
for
next
week's
design.
Call.
We
can
talk
about
figure
out
what
we
want
to
talk
about
as
its
scale.
Is
it
OpenStack,
and
this
is
why
I
was
prioritizing
this
list
I'm
getting
ahead
of
myself
on
the
call?
A
C
A
A
And
so
from
yeah
I,
don't
want
to
cut
that
I
want
to
keep
going
on
that
topic
a
little
bit,
but
I
do
want
to
talk
through
some
of
the
things
and
add
to
this
list
too,
of
places
where
I've
heard
people
have
a
lot
of
interest
around
well.
If
you
could
do
that,
that
would
be
a
really
powerful
story
and
I
put
together
some
of
the
document,
some
of
the
items
in
the
agenda,
but
I'd
love
to
hear
people.
You
know
sort
of
validate
those
and
here's
in
here.
A
Oh
then,
I
had
one
eye
Logistics
note
the
long
does,
maybe
that's
a
good
transition.
What
other
questions
about
community
support?
What
that
means,
and
what
we're
trying
to
do
I
am
happy
if
somebody
else
wants
to
help
act
as
a
clearinghouse
there.
You
know,
please,
please
let
me
know
or
speak
up
or
send
into
the
list
for
now
I'm
perfectly
willing
to
do
that.
People
have
already
been
coming
to
me
that
in
that,
in
that
capacity.
A
Just
from
a
small
logistics
note,
we
had
been
moving
towards
using
dell
infrastructure,
the
the
giro
server
the
dell
had
set
up
for
tracking
features
and
bugs
and
backlog
for
open
crowbar,
and
I'm
going
to
suggest
that
we
just
moved
to
github
for
that
activity.
So
I
already
started
doing
that
to
an
extent,
but
if
you
were
actually
using,
the
release
is
somewhere
in
here,
we're
already
using
releases
and
bugs,
and
things
like
that.
So
if
you
have
feature
ideas
or
bugs
things
like
that,
please
just
log
them
using
github
and
we'll
start
tracking
them.
A
A
A
I'd
know
that
there's
some
we're
playing
with
a
couple
of
different
things
in
the
background
I'm,
specifically
working
to
clean
up
the
documentation
index,
was
a
hanging
Chad
from
the
anvil
of
the
lease.
So
the
number
one
thing
I
would
ask
people
to
do
is
if
you're
playing
with
with
open,
crowbar
and
learning
it.
Please
take
you
know,
second,
to
fix
documentation,
errors
or
add
to
documentation
that
that
that's
we
tried
to
leave
that
in
a
very
good
position,
but
it
always
needs
more
work
and
I'll.
A
Oh
and
all
the
documentation
for
up
and
crowbar
is
in
the
core
Doc's
directory.
We
have.
We
have
no
other.
This
is
the
authoritative
source.
It's
one
of
the
things
we
cleaned
up
from
the
migration
from
crowbar
one
atom.
If
you
want-
and
perhaps
this
is
a
top
another
topic-
I
don't
want
to
spring
it
on
you,
but
we
can
talk
about
reopen
the
cleaning
up,
crowbar
one
repose
and
that
that
website
and
things
like
that,
because
I
think
it
is
a
matter
of
confusion
for
people.
B
A
And
it
sounded
it
sounded
like
we.
That
would
be
a
future
conversation.
We
need
to
figure
out
how
to
do
it,
because
I
really
don't
want
to
lose
the
momentum
either
for
bar
one
or
carb
are
too
because
I
know.
Soos
has
done
some
amazing
work
with
OpenStack
deployments
that
I'd
loved
to
see
the
community
is
able
to
converge
again,
but
at
the
same
time,
I
also
want
to
make
sure
that
we
we
don't
keep
things
around,
that
limit
limit,
crowbar
one's
ability
to
deliver.
A
B
Yeah
I,
don't
really
know
how
to
do
it
back.
I
mean
there's
a
question
it
like.
If
new
people
come
along
and
they
hear
about
crowbar,
you
know
I
guess
the
first
question
is
wet.
Where
do
they
gravitate
towards
you
know?
Do
they
they
find
crowbar,
don't
get?
How
do
I?
Oh
then
they
get
a
bunch
of
instructions
for
Pro,
Bowl
language,
I,
generally
broken
I.
Think
and.
A
See
I
think
they
are
quick
so
that
the
request
I
would
have
is
a
half
there's.
There's
some
sub
may
be
able
to
join
us
today.
I
had
somebody
approached
me
at
the
summit,
who
is
interested
in
helping
create
the
open,
crowbar
website
and
help
help
get
a
dedicated
landing
page.
For
that
think.
The
question
freeverse
Susa
and
crowbar
and
the
crowbar
as
proxy
for
the
curb
or
one
community
is:
how
do
you
want
to
link
those
together
because
I
would
love
to
see
us
take
that
crowbar
github
do
site
and
make
it
very
clear.
B
B
Yeah
I
mean
there's
a
question
about
how
reset
expectations
about
you
know
that
people
can
hear
come
to
the
project,
so
I
guess
different
people
expect
different
things.
Maybe
some
people
heard
about
the
potent
crowbar
but
and
the
you
know,
they're
interested
in
this
sort
of
newer
generation
of
orchestration
engine,
and
maybe
they
want
to
get
involved
in
that
I
suspect.
Most
people
will
come
to
it
through
that
the
need
to
for
the
desire
to
provision
OpenStack
automatically
in
some
way,
and
so
there
we
need
to
set
expectations
around.
B
You
know
what
they
can
achieve
with
which
code
base
and
then
then
to
have
a
recommended
like
a
quick
start
guide
for
getting
that
working,
because
at
the
moment
you
know
we
get
a,
we
get
a
male
or
two
every
every
week,
maybe
on
the
mailing
list
of
somebody.
Who's
like
you
know,
try
to
build
the
crowbar
one
like
a
rock
CIO
or
something
like
that
and
then
run
into
problems
every
time
and
PLL
through
like
a
sauna
I
see,
you
know
generally
not
get
a
reply
asked
on
the
mailing
list.
Well,
they're.
B
A
Actually
brings
up
a
question
because
we
have
the
bunt
too
and
centos
versions
of
stony.
They
could
address
some
of
these
issues,
but
Dell
is
no
longer
positioned
to
help
support
those.
If
people
have
community
questions
around
them,
we
didn't
sell
them.
So
there's
no,
no
support
requirements
around
it
is
but
I
think
that
would
help
drive
adoption
for
the
work
that
has
been
done
on
crowbar
one.
If
we
made
those
available,
can
your
team
help
troubleshoot?
That
is,
that
of
interest.
B
A
That
was
ID'd
so
for
people
who
haven't
tracked
us
that
carefully
at
this
is
this
has
been
a
long-standing
sore
point.
Susa
rightly
felt
that
dev
tool
was
very
hard
to
maintain
and
built
a
different
way
to
create
the
iso
s
actually
rpms.
That
became
the
model,
the
blueprint
model
we
used
in
open
crowbar
when
we,
when
we
cut,
but
because
we
were
so
invested
in
the
dev
tool,
we
couldn't
do
it
with
a
we
had
to
fork.
A
A
A
B
There's
one
thing
I
can
say,
which
is
that
if
anyone
comes
along
to
the
comarca
museum
wants
to
try,
you
know
like
a
rock,
so
you're
stony-faced
crowbar
the
openstack,
then
we
can
certainly
support
them
in
in
trying
out
Cesar
Clyde
I
mean
it's.
You
know
we
even
you
know
before
they
give
us
a
percent.
B
You
know
relegates
free
software,
obviously
were
always
keen
for
people
to
try
it
out
and
if
you
know
and
help
them
with
that,
and
if
they
don't
like
it,
they
can
just
walk
away,
but
you
know
hopefully
will
help
them
get
it
working
and
turn
them
into
interested
customers.
So
I
think
we'll
always
have
time
to
invest
in
in
that.
But
up
till
now
the
you
know
the
main
sort
of
port
of
entry
for
crowbar
newbies
has
been
pick
up
and
I.
B
A
I
would
I
would
suggest
that
we
replace
that
homepage
just
with
links
to
direct
people
to
use
creber
one
with
opensuse,
and
if
you
can
give
them,
you
write
up
specific
directions
for
that.
You
know:
I've
promoted
the
work
you're
doing
my
personal
blogs
and
I
feel
like
you
know
that
that
deserves
a
lot
of
props
and
so
I'd
like
to
get
a
clear
track
to
that,
because
I
think
that's
important.
I
would
like
to
be
able
to
say
more
definitively
that
we're
maintaining
one
community
that
the
goal
of
what
crowbar
does
is.
A
You
know
DevOps
around
these,
these
deployments
and
the
public
or
changed
the
goal
structure.
A
lot
of
the
approaches
haven't,
and
so
the
communities
or
we
can
stay
together
as
one
community
make
those
types
of
statements
from
the
github,
but
in
that
based
landing
page
and
then
point
people
to
crow
bar
open,
crowbar,
a
landing
page
for
that
and
then
the
Susa
cloud
pieces
for
crowbar
one,
because
I
think
at
this
point
you're.
B
Will
you
know
to
buy
an
ad
with
no
deploy
to
control
the
notes
and
the
compute
node
and
then
set
them
all
up,
and
all
you
need
really
is
the
git
repository
with
the
vagrant
file
in
hands
and
a
couple
of
boxes
which
I
intend
to
upload
to
the
grid
cloud,
and
so
I
mean
that
might
be
one
one
quick,
stop
approach
that
we
could
we
could
publish
on
on
the
website.
Okay,.
A
You
know,
if
there's
a
strong
sense
on
from
anybody
side
that
we
want
to
fork
the
community.
Then
let's
talk,
we
can
talk
about
that
at
the
next
caller
in
two
weeks
and
see
what
the
ramifications
would
be
and
how
to
do
that.
I
have
a
strong
preference
to
not
fork
the
community
if
we
can
avoid
it,
otherwise
I
would
have
just
renamed
crowbar
when.
D
A
B
I
guess
it
depends
on
what
you
really
mean
by
for
the
community,
I
mean
that
you
know
development
is
already
forked,
to
all
intents
and
purposes
and
and
and
along
with
it.
You
know,
obviously
when
different
github
organizations,
which
means
different
different
wiki,
different
issue,
tracker
and
so
on,
and
so
the
thing
the
only
things
that
are
really
shared
up
amongst
the
whole
community
now
are
the
IRC
channel
and
the
mailing
list,
like
most
anything.
B
A
I
this
is
the
the
question
I
think
comes
back
to
is
there
an
ad
and
I
don't
want
to
go
too
much
longer
glad
you
actually
want
to
talk
about
the
prior,
the
future
development
priorities,
but
24
for
future
conversation
we
should
talk
about.
Is
the
goal
to
migrate
into
into
open
crowbar
or
to
extend
the
life
of
crowbar
in
such
a
way
that
they
actually
never
know
that
the
work
that
never
Rican
virgin
that
that
to
me
is
the
community
is
the
question
about
the
communities
the
destination,
and
this
is
a
delicate
topic
right.
A
A
E
E
A
There's
no
indication
that
Del's
going
to
shut
down
the
list.
I
agree
with
you.
It
would
be,
it
wouldn't
be
very
hard
to
move
it
to
it
to
a
new
site.
It's
just
a
bootstrapping
question
so
but
my
preference
would
be
to
change
as
little
as
possible
while
we're
sort
of
reforming
the
community.
And
then,
although
you
I,
don't
have
to
be
sorry,
I,
don't
know
a
great
question.
It
might
be
easier
to
fix
it
now
and
then
reform
onto
the
new
list,
but
we
might
lose
people
by
doing
that.
C
A
A
A
And
I'm
not
actually
and
I'm
not
sure
which
cop
I
think
for
dell
employees
contributing
on
their
own
time.
We
wouldn't
change
copyrights,
but
new
files
would
show
up
as
individual
copyrights
we'd
still
at
least
off
to
maintain.
The
apache
sauce
should
maintain
the
apache
to
license,
and
then,
if
they're
sponsored
work,
people
are
sponsoring
the
work
their
bail
assert
their
copyright
with
the
Apache
to
license
just
which
is
pretty
typical.
A
A
I'll
read:
I'll
read
this
list
of
things:
I
heard
people
interested
in
and
I'd
love
to
hear
additions
or
have
somebody.
You
know
people
plus
one
on
these
getting
the
openstack.
This
is
specifically
up
in
crowbar
focused
getting
the
OpenStack
upstream
integrations
working
and
but
the
thought
here
would
be
the
minimal.
So
it's
Nova
Keystone
glance,
there's
others
but
I
think
just
that.
Would
let
people
the
entire.
E
C
A
Could
talk
about
doing
a
lot
more
than
this?
What
what
I'm?
What
I'm
trying
to
do
is
until
we
have
sponsored
work
and
whoever
sponsors
the
work
chooses
with
whatever
prayers
they
want,
where
I
would
say,
people
who
want
to
be
active
in
the
community,
but
but
do
it
on
their
own
time.
What
they
would
look
at
is
some
of
some
of
what
I'm
driving
here.
I
think
that
neutron
is
very
doable
with
what
we've
done,
but
it's
going
to
require
more
effort
and
the
community
cookbooks
are
less
mature
there
I
hit,
maybe.
A
C
A
C
A
C
A
Upstream
integration
yeah
that
or
were
we're
getting
I'm
getting
some
scuffing
done
on
that
it
could
be
if
you're,
just
doing
the
basics.
That
could
be
pretty
fast.
There's
there's
some
engineers
I,
don't
see
him
on
the
call
anymore,
who
were
doing
that
work
and
could
give
a
more
exact
estimate.
We
talk
more
about
it's.
A
But
there
is
a
SEF
workload
for
open
crowbar
will
deploy
SEF
its
ipv6
only
right
now,
but
that
work
could
also
be
sponsored
and
continue
and
that
actually
uses
sefs
upstream
cookbooks,
which
I
think
need
to
get
moved.
What
I
heard
was
the
OpenStack
version
of
the
South
cookbooks
was
better
and
probably
want
to
migrate
to
that.
A
Dell
had
stopped
the
anvil
release.
We
were
just
about
to
start
doing
the
WS
men
interfaces
for
the
dell,
our
series
gear
and
so
that
that
work.
So
all
the
code
is
open
but
porting
it
to
open
crowbar.
It
hasn't
been
completed.
I
think
that's
really
interesting
to
do.
Although
I
got
a
lot
more
interest
from
an
open,
compute
perspective
and
being
able
to
use
crowbar
to
do
it
computing.
These
are
all
these
are
both
doable.
A
Talking
for
a
while,
I'm
jumping
to
core
OS,
so
open
crowbars,
the
only
thing
I've
seen
that
can
manage
physical
infrastructure
under
VMS
and
containers
docker
specifically,
and
one
of
the
things
that
we've
been
talking
about
internally,
was
the
idea
of
employing
core
OS
as
letting
down
the
physical
infrastructure
for
it
and
then
allowing
at
CD
or
lend
or
Brooklyn
or
whatever,
whatever
management
you
want.
On
top
of
that,
to
do
it,
do
it
stuff,
I,
think.
A
We've
been
looking
at
doing
that,
it's
just
it's
adding
another
OS
and
then
at
the
summit,
I
heard
quite
a
bit
about
this
pattern
of
using
ansible
to
install
sheffer
puppet
because
people
like
the
ssh
approach,
creve
are
open.
Crowbar
uses
this
the
same
very
similar
control,
plane
ssh,
to
talk
to
the
nodes,
but
I
think
there's
less
cognitive,
dissonance
between
that
and
salt,
using
using
crowbar
for
salt
sheffer
puppet.
A
We
already
have
the
chef
and
puppet
pieces
in
code,
so
I'm
interested
in
seeing
if
there's
a
community
interest
in
using
probar
for
that
instead
of
ansible.
For
that,
because
then
you're
conceivably
get
the
bare
metal
bring
up
piece.
The
danceable
doesn't
do
ansibles
moving
towards
chef,
the
view,
chef
parity,
not
physical
infrastructure,
parity
things
to
add
on
the
list.
That
was
my
list.
B
A
B
B
A
A
B
You
mean
right
and
iterating
through
the
firewall
for
downloading
boxes
or
something
else,
because
I
would
have
thought
that
I
didn't
like.
Ideally,
you
can
just
like
cloner
the
git
repository
or
even
download
the
zip
from
github
and
download
the
box,
and
and
then
you
should
be
good
to
go
with
even
without
any
network
might
well.
A
A
Are
the
open,
especially
the
open
one
things
that
we
changed
it
open
crowbar?
Was
we
stopped
pre,
caching,
all
of
the
dependencies
on
that
I?
So,
but
one
of
the
reason
was
and
so
open
crowbar
is
a
naught
is
online
mode
by
default,
which
makes
it
a
lot
smaller
in
that
perspective,
but
also
means
that
you
have
to
be
able
to
do
a
deployment
without
being
connected
to
the
area.
B
E
B
A
I
thanks
I'll
yeah.
It
does
still
proxy
through
the
admin
node
and
we've
added,
there's
a
squid
proxy
actually
built
into
it.
So
you
get
a
certain
degree.
Caching
from
that,
and
it
sets
up
that
relationship.
But
it's
still,
you
still
have
to
have
the
admin
node
connected
doing
outbound
and
we
did
that
we
did
that
work
and
got
it
got
it
going.
A
C
A
A
A
And
actually,
from
this
perspective,
we
had
weed
in
the
curve,
are
one
REE
posters
actually
Cloudera
API
integration
and
being
able
to
integrate
with
Cloudera?
That's
part
of
the
open-source
work
so
I
you
know
once
again,
this
is
you're
installing
100
nodes.
At
a
time,
it's
amazingly
powerful
to
be
able
to
get.
E
A
A
Doing
is
it's
coming
up
to
ready
state
and
that's
part
near
the
whole
raid
BIOS
configuration
networking,
the
whole
base
level
ready
state
and
then
a
lot
of
the
things
we're
talking
about
our
workloads
on
top
of
relations,
which
I
think
that
are
also
valuable.
But
some
of
what
crowbar
does
is
it's
this
ready
state
infrastructure
management
and
then
the
bulb
or
clothes
on.
If
that
makes
sense
in
the
past
and
one
we
got
very,
the
workload
got
very
connected
into
a
crowbar
was,
and
it
became
impossible
to
extricate
the
openstack
piece.
D
Hey
rob
I
I
just
wanted
to
mention
what
we
were.
What
we
were
looking
at
was
potentially
having
a
Hadoop
readiness
bar
clamp
that
just
configures
nodes
for
a
generic
Hadoop,
rather
than
something
clutter
a
specific,
thankfully.
So
that
was
some
work
in
progress
before
we
get
off
the
vagrant
environment.
I
hate
to
drag
us
back,
but
one
of
the
historical
things
with
crowbar
is
it
was
kind
of
tied
to
supporting
a
windows
environment
because
of
the
dell
corporate
setups
I
would
love
to
toss
it
out
there?
A
D
C
D
D
A
B
That's
one
of
the
advantages
I
seen
in
vagrant
is
that
because
it's
you
know,
got
multiple
providers,
it
does
keep
up
options
open
in
terms
you
know
virtual
box
or
doko
libvirt
or
whatever,
and
it
in
theory
shouldn't
be
too
much
of
a
stretch
to
support
more
than
one
approach,
because
the
you
know
the
bits
that
are
specific
to
one
hypervisor
can
go
in
that
chunk
of
the
vagrant
farm.
The
bits
which
are
common
can
be
shared
across
all
of
them
and
that
can
be
managed
in
a
sort
of
DevOps
approach
to
the
development
environment.
A
A
A
Don't
like
we
have
I
was
hoping
to
do
next
week
is
prioritize
this
list
and
then
talk
through
what
it
would
take
to
to
start
building
these
things.
I'll
circulate
this
list
on
a
hat.
I
will
circulate
the
new
list
to
the
old
bless,
and
then
we
can
start
a
discussion
on
the
new
list
about
prioritizing
these
topics,
and
if
people
want
to
pull
them,
pull
them
in
and
add
them.
A
If
I
can
be
a
resource
for
your
team,
please
let
me
know
I'm
happy
to
do
a
demo
and
bring
you
guys
up
to
speed
and-
and
if
you
want
to
talk
about
you
know
some
of
the
one-on-one
conversations
I've
been
having
about
building
the
community.
I
can
happily
do
that.
We're
still
at
the
face
where
a
lot
of
the
community
building
is
happening.
Start
abbott
are
starred
from
me.
We're
not
yet
at
a
point
where
the
community
is
connecting
to
each
other.
Yet.