►
From YouTube: OpenCrowbar Planning 2014 06 18
Description
Minutes: http://pad.opencrowbar.org/p/community-planning-meeting-2014-06-18
OpenCrowbar community website, will take pulls since this is github!
List Documentation Changes Needed
OpenStack cookbooks
IPMI integration
100 Node Challenge
Squid Proxy Feature (latest pull)
Process & Backlog Review
A
Sorry,
the
thing
we
should
do
is
actually
start
with
things
that
ads
that
were
things
that
were
accomplished
in
the
last
sprint,
so
we
should
start
with
review
victor.
Do
you
want
to
talk
about
the
the
pull
changes
that
went
through
and
some
of
the
capabilities
that
were
brought
back
or
added
from
that.
B
Yeah,
so
the
main
thing
that
I
did
over
the
last
over
the
last
week
was
to
pull
back.
It
was
to
fix
up
the
the
support
that
we
had
for
deploying
and
using
a
chef
server
that
it
fit
rotted
a
little
bit
and
got
that
back
up
in
shape
and
arranged
for
everything
to
use
it,
so
that
my
life
would
be
much
easier
trying
to
make
berkshire
from
multiple
bar
plants.
For.
B
Because
previously,
the
first,
the
we
kind
of
on
using
burp
shelf
to
help
us
manage
and
pull
in
upstream
cookbooks
that
we
don't.
We
didn't,
have
to
do
things
like
making
our
own
fork
of
the
apache
cookbook,
because
life
is
too
short.
However,
it
turned
out
that
using
that
in
combination
with
chef
solo
everywhere,
burke's
files
aren't
composable,
so
I
could
just
take
about
all
the
work
files
that
we
needed
and
glom
them
together
and
have
a
reasonable
expectation
of
it
working.
C
A
B
D
B
B
A
B
There
functions
well,
there
are
functions
that
we'll
have
to
implement
in
crowbar
a
little
bit
just
for
use
by
the
roles.
For
instance,
we
don't
have
a
provision
to
create
encrypted
data
bags
and
I'm
thinking
that
the
easiest
way
to
do
that
for
things
that
will
require
them
is
to
let
the
role
take
the
attributes
that
it
wants
to
put
in
an
encrypted
data
bag
and
put
them
in
there.
A
It
just
depends
on
what
people
see
is
invaluable,
yes,
cool.
You
want
to
talk
about
the
squid
proxy
stuff
because
to
everything
I've
been
hearing
is
that's
it's
just
it's
a
really
important
function
and
that
we
sort
of
put
it
in,
and
I
need
to
do
some
better
work
promoting
why
it's
important,
but
yeah.
C
B
Had
a
squid
proxy
in
place
so
that
you
could
deploy
a
working
cluster
without
needing
to
let
the
compute
nodes
have
an
ip
address
that
was
routable
to
the
public
internet,
so
the
mode
of
operation
that
I've
always
done.
My
development
on
was
the
compute
nodes
that
I
test
on
when
I'm
deploying
them
as
kvm
knows,
they
don't
get
bound
to
a
bridge
that
has
access
to
the
outside
world.
B
It's
a
completely
isolated
thing
and
whenever
they
need
to
pull
packages
from
the
internet,
they
always
do
through
the
proxy
that
lives
on
the
admin
that
gives
us
a
kind
of
a
layer
of
installation
from
the
internet.
It
also
gives
us
a
nice
point
for
auditing
and
caching,
because
if
you're
deploying
a
thousand
notes
question
you
don't
want
to
pull
down
a
thousand
copies
of
you
know
all
the
latest
updates
to
centos
every
time
you
want
to
let
squid
pull
down
one
and
cache
it
for
everyone
else
to
use.
B
So
the
latest
changes
that
I've
made
in
this
proxy
support
was
to
actually
list
that
out
from
being
deployed
by
the
provisioner
and
deployed
as
part
of
the
initial
bootstrap
process.
When
we're
setting
up
the
other
servers,
the
other
services,
that
crowbar
relies,
so
it
goes
that
we
download
and
install
the
packages
that
we
need
as
part
of
bootstrap.sh,
then
when
we
get
to
actually
standing
up
a
production
or
a
development
server.
C
A
B
E
E
A
All
right,
I
won't
one
one
thing:
one
thing
to
note
is:
if
you're
using
a
docker
admin,
then
your
squid
and
the
squid
cache
that's
getting
set
up
on
that
docker
admin,
I
believe,
is
getting
blown
away
every
time,
but
so
you
want
an
external
squid
cache
on
your
in
your
in
your
network.
In
addition
to
the
one
we're
going
to
set
up
on
the
admin
node.
B
C
A
A
B
A
A
A
So
I
actually
have
the
open
crowbar
and
I
flipped
the
on
switch
and
added
a
travis
ci
file,
hey
and
it
passed
hot
dog.
Look
at
that
just
echo,
but
that
was
the
goal
for
the
sprint.
So
richard
accomplished,
I
actually
did.
I
don't
think
it's
voting
yet
into
github,
but
that
was
this
is
the
start
I
like
that
it
actually
tested.
The
first
thing
it
tested
was
adding
itself
so
yay
process.
B
A
A
D
You
might
want
to
keep
it
external
to
the
to
the
to
the
installation.
Scripts
travis
can
run
those
things
in
sequence
right,
so
you
know
whatever
needs
to
be
done
for
the
initial
setup
of
the
system,
and
then
you
know,
let's
just
start,
adding
a
library
of
test
sequences
that
we
want
to
have
done.
Bdd
being
the
first.
A
A
A
C
A
I
I've
been
playing
through
some
of
the
stuff
and
building
I've
been
trying
to
work
in
the
deployment
guide,
and
so
the
deployment
guide
actually
walks
through
the
whole
create
process,
and
but
it
would
it
could.
It
would
really
be
helpful
to
have
screenshots
in
this
to
help
people
and
potentially
break
this
into
sub
documents,
and
then
I've
been
adding
things
as
I
find
them
like
troubleshooting
tips
for
deployment
and
then
victor,
I
could
use
some
help
just
building
out
the
the
port
mapping
list
of
all
the
services
that
we've
exposed.
A
A
D
So,
to
follow
up
on
a
couple
of
those
items
there
right
work
on
the
deployment
guide
consists
of
run
through
and
and
screenshots
travis
ci.
I
think
there's
there's
effectively
two
pieces
to
that.
The
first
one
is
is
a
full,
a
full
build
run
through
of
bdd
tests
and
then
a
design
for
the
further
voting
infrastructure
and
how
we're
going
to
how
the
how
the
process
flows
are
going
to
work.
A
D
A
B
B
A
All
right
other
other
deliverables.
I
know
we
made
some
progress
on
the
100
node
100
word.
I
keep
calling
100
words.
I
don't
know
how
many
words
are
in.
It
definition
see
if
I
can
find
it
and
I
think
we've
got.
We've
got
a
lot
of
text
for
the
100
node
challenge,
so
I'm
going
to
formulate
that
into
a
broader
community
thing.
So
actually
this
next
sprint.
A
E
A
A
E
B
A
A
A
C
A
I
I
think
that
what
we
could
do
is
we
could
leave
the
old
ones
in
place
and
like
let
it
be
dual
path,
but
I'm
I'm
going
to
look
into
that.
That's
that's,
I
think
a
good
topic
for
the
design
meeting,
but
the
goal
so,
but
the
goal
for
the
ipmi
workload
is
to
basically
bring
in
the
old,
bring
bring
over
cb1
code.
B
A
Easy
enough
easy
enough
to
find
out.
I
think
it
was
mostly
working.
It
was
the
proxy
bridge
that
was
was
causing
problems.
I
don't
think
we
need
that
anymore,
so,
okay,
so
that
that's!
This
is
something
we're
working
on.
If
we
actually
have
some
hardware
to
test
it,
then
we
should
be
able
to
work
against
physical
hardware.
E
A
E
E
A
B
A
A
B
D
A
I
did
make
those
changes
that
you
asked
for
so
these
things
should
be
good,
so
this
these
are
actually
both
going
to
be
fixed
together,
and
I
think
this
is
right,
but
I
was
going
to
add.
I
was
going
to
add
a
test
for
it
before
we
close
it,
and
so
that
gets
us
back.
This
is
actually
a
design
discussion.
A
D
A
A
A
A
A
So
one
of
the
so
this
this
is
all
this
wonderful
style
is
default,
github
stuff,
so
I
I
pulled.
We
cleaned
up
this
trying
to
remember
if
we
covered
this
two
weeks
is
a
long
time
for
me
to
remember
what
happened.
This
was
a
result
of
a
design
meeting
a
little
while
ago,
where
we
split
these
two
into
into
different
pieces.
A
A
A
You
know
one
one
of
the
things
I
like
about
github.
Is
it
kind
of
renders
the
markdowns
as
if
they
were
readmes,
but
the
thing
I
don't
like
is
it
doesn't
give
us
any
navigation,
any
reasonable
navigation,
so
I
I
did
some
work
about
six
months
ago
to
take
some
of
that
markdown
stuff
and
actually
build
it
into
a
site.
You
know
single
source
for
the
docs
a
little
bit
of
a
wrapper
around
it.
A
I
could
pick
that
up
and
take
a
look
at
it
right
and
one
one
thing
that
I've
been
doing
is
I
fixed.
I
fixed
the
the
documentation
full
index
and
I've
been
tweaking
it
so
mike.
I
took
what
you
had
been
doing
and
I've
been
expanding
it
a
little
bit
so
there's
a
table
of
contents
and
then
a
full
index.
A
A
Issue
is
then
you're
maintaining
the
links
in
the
markdown
and
there's
there's
kind
of
a
meta
level
where
we
can
generate
a
lot
of
those
links
off
the
same
source
code.
I
had
built
a
prototype
with
sphinx
that
mostly
mostly
dealt
with
that
problem
that
you're
you're
you're
right.
If
you
were
to
take
these
docks
and
dump
them
into
a
site,
you
could
add
a
header
for
each
one
that
basically
had
siblings
up
siblings
children
up
down
navigation,
which
is
exactly
what
the
ui
docs
do
right.
So
this
same
concept
same
concept.
E
A
That
would
be
pretty
exciting,
because
if,
if
we
have
the
same
level
of
navigation,
it
makes
it
so
much
easier
and
one
of
the
things
I'd
love
to
be
able
to
see
is
stuff
like
the
principles
documentation
which
I
don't
think
is
in
here,
which
I'm
not
sure
where
it
is
here.
Would
it
you
know,
be
nice
to
see
that
just
made
easier
for
the
community
to
been
clicking
around
too
much.
I
lost
track
of
my
tabs.
A
A
So,
let's
see,
I
think,
wiki
page,
it's
just
a
shallow
introductory
page.
I
don't
know
if
we
want
to
link
here
to
the
community
site,
but
I
just
put
in
the
deep
link
into
the
actual
documentation.
Excellent.
Thank
you
yeah.
We
don't.
We
really
don't
want
people
editing
this.
Oh,
we
can
add
custom
sidebars
that
might
this
might
be
the
way
to
handle
some
of
that.
A
C
B
A
A
E
C
E
A
So
victor,
I
I
recognize
there's
places
where
we
we
have
technical
changes
to
making
core.
I
think
that
there
are
people
who
are
interested
in
being
able
to
drive
those
cookbooks,
but
don't
know
where
to
start
right.
We
already
did
some
work
on
some
base.
Cookbooks
do
we,
you
know,
is
what
I
think
we
need
to
think
through.
If
somebody
came
in
and
said
all
right,
I
want
to
try
to
try
to
help
make
this
progress.
A
A
So,
if,
if
we
just
said
look,
this
is
how
you
use
berkshiff,
you
set,
you
know,
take
just
actually
showed
somebody
how
to
use
the
upstreams
that
we
had.
They
could
start
iterating
through
this
process.
The
things
that
you
need
to
do
to
fix
and
core
aren't
necessarily
blockers
for
somebody
just
turning
through
the
turning
starting
to
turn
the
crank
on
integrating
the
upstreams
right.
There's
fixes
to
the
upstream.
Some
patches
they'll
need
to
make
and
they're
not
blocked
on
the
other
stuff.
So.
B
Like
I
said
those
those
the
the
unbreaking
of
cluster
support
and
adding
support
for
being
declared
that
these
attributes
need
to
go
in
data
bags
is
something
that
we
need
to
have
working.
But
we
can
really
start
on
a
lot
of
upstream
stuff.
That
assumes
that
there's
a
lot
of
options
that
they
do
use
encrypted
data
bags.
A
lot
of
parts.
C
A
But
I
I
don't,
I
don't
know
which
way
to
guide
you.
I
think
that
if
we
had
people
who
were
interested
in
spinning
up
on
the
openstack
cookbooks
and
we're
clamoring
for
it,
I
would
I
would
say
that
that
would
we
should
look
at
that,
but
for
right
now
I
think
the
ipmi
is
actually
the
bigger
the
hotter
topic.
The
people
on
the
call
feel
that
that's
the
right
call
ipmi
is
first,
yes,.
C
C
B
A
A
That'll
then
drive
whether
or
not
we
fix
the
encrypted
data
bag
thing
as
a
priority
or
not
the
the
thing
to
call
out
the
community
call
is,
we
know,
there's
a
gap
as
soon
as
as
soon
as
it
becomes
a
blocking
gap.
We
can.
We
can
prioritize
it,
but
for
right
now
I
I
want
to
make
sure
everybody's
on
the
same
page.
That
ipmi
is
actually
the
the
first
feature.
B
B
A
A
A
All
right
that
was
actually
the,
I
think
what
what
I
wanted
there.
I
think
this
remains
on
my
plate
to
to
build
the
dock,
build
some
of
the
documentation
or
find
it
find
where
we
had
it,
because
I
believe
that
we
actually
documented
some
of
this
stuff
I'll
produce
video
or
something
something
fun
like
okay,
other
topics,
other
items,
I
think
we've
covered
everything
that
I'd
expected
us
to
cover
a
little
bit
more.