►
From YouTube: OpenCrowbar Community 2014 09 10
Description
No description was provided for this meeting.
If this is YOUR meeting, an easy way to fix this is to add a description to your video, wherever mtngs.io found it (probably YouTube).
A
A
Hi
welcome
to
the
open,
crowbar
community
planning
meeting
of
September
the
10th
2014,
we're
just
finishing
up
putting
our
agenda
together
and
planning
our
next
two
weeks
of
work.
B
Not
much
to
show,
but
I
can
tell
you
I
could
describe
what
the
plan
is,
which
I
think
needs
to
be
vetted
with
everybody.
So
the
the
current
mechanism
is,
I
had.
I
had
pulled
the
docs
out
of
the
repo
kind
of
run
them
through
some
pre-processing
to
convert
them
to
restructure
txt
run
time
for
spinks.
They
end
up
on
read
the
docs
org.
So
it's
really
running
a
script
to
do
the
conversion
kind
of
pushing
them
out
to
read
the
docs
that
worked
reasonably
well.
B
My
plan
for
the
actual
code
will
be
to
go
into
crowbar
and
convert
the
documentation.
Do
a
one-time
conversion
of
the
documentation
from
mark
down
to
restructure
text
within
the
current
repro,
so
that'll
be
step,
one
that
happens
with
the
Panda
process,
but
the
lease
and
cleanup
needed
so
I
will
do
that.
I
will
then
go
into
crowbar
and
update
the
doc
view
or
the
help
you
I'm
actually
not
sure
if
it's
called
doc
or
help
there
are
links
to
both.
B
But
my
plan
is
to
update
that
view
to
render
HTML
documentation
if
it
exists,
you
know
mainly
in
developer
mode,
but
if
not
to
just
ignore
it
and
include
a
link
back
to
read
the
docs
org
and
then
the
third
part
of
this
is
in
the
tree.
There
will
be
a
make
file
that
will
run
the
sinks
restructuredtext
mechanism
to
generate
the
actual
HTML
docks
locally
in
the
tree.
B
Because
we
can,
we
can
set
up,
read
the
docs,
so
it
triggers
off
a
check
in
it.
Basically,
it
triggers
off
emergent
to
get
so.
It
will
rebuild
docks
for
us
on
the
read
the
dock
site,
but
when
we,
when
we
do
the
conversion,
we
can
also
have
local
docs
in
the
tree
and
the
reason
for
having
the
reason
I.
It's
pretty
easy
for
me
to
just
remove
the
view
and
point
everything
to
read
the
docs.
B
A
A
B
B
A
Since
this
is
primarily
a
ruby
projects,
there's
a
think
it's
r
dot
org
that
I
found
incredibly
useful.
Oh
no.
E
B
Mm-Hmm
and
I've
done
something
similar
in
the
past
on
a
on
a
Python
documentation
project
and
it
worked
really
well
I'm,
I'm,
all
in
favor
of
generating
docs
from
source
code,
whether
it's
yard
or
Ruby
ducks
I
still
think.
We
need
written
kinda
user
and
developer
documentation.
That's
more
pros,
but
it's
really
nice
to
have
links
directly
to
docs
generated
from
the
code.
B
A
B
Yeah
they're
easier
to
navigate
and
one
of
the
things
that
can
happen
when
we
switch
formats
is
restructured.
Text
actually
gives
you
a
little
more
formatting
control
arm.
The
problem
with
mark
down
isn't
the
mark-up
as
much
as
the
many
flavors
of
the
markup,
including
the
latest.
What
is
it
standard?
Markdown
flap
that
happened
a
week
ago,
but
the
to
me
that
my
real
complaint
with
markdown
is
it's.
E
E
Yeah,
that's
that's.
The
approach
that
I've
been
I've
been
taking
is
pretty
much
is
to
head
yard
available
and
then
just.
A
A
Anything
else
in
Doc's
world,
oh
I,
this
path
that
I've
been
sharing,
went,
went
dead
a
last
week
when
my
Colo
was
rooted,
and
they
were
using
me
for
an
open
proxy
for
like
a
month
and
I
move
the
moved
everything
without
any
data
loss,
plus
an
upgrade
to
the
OS
and
and
etherpad
software
to
the
colo
over
at
net
access
day,
and
it
should
survive
pretty
well
there
of
created,
upstart
scripts.
That
will
respond
it,
so
the
pad
should
be
more
reliable
now.
A
D
D
B
A
E
A
The
lanky
was
the
top
of
the
list
again
with
the
markdown
arm,
and
so
anybody
want
to
speak
out
and
take
any
of
these.
Maybe
pitchers
head
on
stuff
I've
been
dealing
with
this
in
a
is
in
a
different
repo.
D
D
E
E
A
That
should
be
closed.
Yeah.
C
E
D
D
A
D
C
C
E
Yes,
for
the
raid
stuff,
that
needs
a
case.
E
C
D
E
D
D
D
D
The
boost
what
happened
when
we
switched
our
workflow
to
attributes
so
in
May,
April
May,
we
started
using
attributes
in
a
much
more
prescriptive
way.
Then
the
bootstrap
screen
had
to
actually
set
attributes
her
roles,
not
just
roll
assignments,
and
so
I
made
those
changes
so
that
you
could
just
you'd
set
the
attributes.
You
wanted
to
sat
on
the
screen,
that's
part
of
the
bootstrap
process,
so
what
you
have
to
do
is
you
have
to
start
crowbar
without
going
through
the
foot,
all
the
bootstrap
steps
in
the
in
the
automated
script.
D
You
actually,
ideally
you
modify.
You
either
modify
the
production
on
SH
or
use
production
SH
with
the
dash
zombies
flag
that
zombie
flag
and
then
that
would
let
you
go
into
the
bootstrapping
screen,
which
I
can
never
say
because
of
the
ten
cluster.
The
in
that
screen,
you
actually
would
be
able
to
review
the
deployment
before
it
starts.
Annealing
right
the
challenges
we
all
if
we're
using
the
production,
SH
script
that
automatically
anneals,
and
so
you
don't
get
a
chance
I'll
make
modifications
in
with.
D
B
D
A
E
A
All
right,
that's
all
the
issues,
so
the
open
issues.
A
Gender
is
nothing
else.
I
had
clean
up
github
stories,
but
I
think
that's,
basically
what
we
just
did.
No
yeah.
A
I've
made
a
whole
bunch
of
progress
in
seminole
crowbar
in
my
repo.
It's
allocating
notes,
bringing
them
from
the
system
deployment
into
a
ready
deployment
and
I'm
about
to
set
of
the
work
of
ensuring
that
all
the
node
roles,
implicit
in
the
ready
deployment
to
be
a
crowbar,
managed,
node,
actually
get
executed
and
then
set
the
available
flag
to
false
and
letting
them
stay
in
the
in
whatever
they
really
want
to
call
this
deployment.
But
the
default
is,
is
called
ready.
A
E
D
A
And
I
guess:
if
it's
warming
connectable,
then
it
will
install
chef
client
on
it
if
it
deems
necessary,
I
haven't
gotten
there
yet
I
want
to.
This
is
exactly
where
I'm
at
to
see.
If,
if
the
machine
object
that
it's
created
down
here,
he
uses
whatever
took
their
transport,
whether
it's
age
or
some
window,
something
and
then
and
it'll
get
the
chef
client
on
it.
If
it
needs
to
I'll,
see
how
smart
chef
metal
is
about
that
I'll
put
it
I
assume
we're
going
to
need
something
to
come.
A
D
A
A
A
Plaster
work
so
I'd
like
to
take
this
ouch
and
on
a
design
call
work
through
this
to
create
a
proper
API,
proper,
proper
client
library,
proper,
crowbar,
ruby
gem
to
make
you
know
things
like
proposed
deployments
and
you
know
get
the
brings
up.
The
community
say
what
we
want
in
this
Ruby
AGI.
What
we
wanted
to
do.
A
And
yeah
that
can
paralyze
and
it
handles
a
lot
of
stuff
and
it
has
no
other
dependencies
and
it
like
automatically
does
Jason
so
like
here.
So
this
is
all
you
need
to
dump.
You
know
everything
that's
going
on
to
standard
error
and
to
expect
all
transactions
in
Jason,
and
this
is
how
do
you
set
up
ties
us
off?
That's
it
and
then
every
following
and
that's
how
you
set
up
the
base,
positive
acri
and
everything.
It
really
makes
life
a
lot
easier
for
me,
ugly.
D
A
D
D
D
People
be
all
right
with
that.
Like
I
guess
it
would
be
a
909
10
room,
909
10
for
this.
This
past
sprint
use
the
dates
of
the
09
28
/
09
24.
E
D
Why
don't
we
distance
variant,
broom,
dot11,
I,
just
do
atomically,
increasing,
yeah
and
then
and
then
we'll
just
because
we're
a
little
squishy
on
sprint
boundaries?
It
might
make
more
sense
that
two
months
sprint
to
a
month,
long
sprint.
For
that?
Oh,
we
so
I
don't
want
us
to
try
and
get
into
formal
sprint
planning
with
estimates
yet,
but
I'd
rather
us
do
is
say,
look
these
are
the
things
that
we
think
are
coming.
These
are
the
things
we
think
are
farther
in
the
future.
D
I
want
to
stop
turning
on
things,
I
hate
feeling
bad
that
we
didn't
do
it
I
do
for
when
we
know
we're
not
doing
to
do
work,
though
you
know,
I'll
connect
with
Randy.
Let's
we'll
start
doing
this
convention
of
adding
the
next
milestones
in
the
in
the
release,
push
out
the
things
that
aren't
in
that
and
then
we'll
review.
We
can
review
them
more
systemically
like
that.
Do
it
like
we
could
actually
do
a
release,
print
release
review.
You
know.
C
D
C
C
Almost
anybody
else
I
haven't
whether
versus
them.
You
know
how
much
you
care
about
him
acknowledge
or
harder
one
panel
that
and
I
don't
read
article
ottoman
and
I'm
from
painting
this
part
of
work.
Experience
was
setting
up
a
series
of
milestones
in
and
get
and
pulling
our
work
into.
Those
milestones
make
me.
D
D
A
D
Greg's
work
was
actually
setting
up
a
salt
server
and
then
automatically
connecting
the
minions
to
that
I
I
know
that
there
were
you
got.
We
got
some
feedback
from
Victor
that
it
didn't
follow.
All
the
conventions
and
greg
was
adjusting
that,
but
the
basics
are
in
there
for
the
assault,
work
and
we're
looking
for
the
prototype
customer
person
using
it
to
sort
of
say
all
right.
This
is
this
works
for
me.
We
actually
want
to
start
or
active
ready
for
use.
D
A
D
C
Does
and
Greg
needs
to
update
it
with
how
that
how
he
wants
just
test.
We
should
get
somebody
validated
whether
it's
the
end
user
or
someone
on
this
game.
It
doesn't
matter
to
me
and
then,
if
we're
good
for
at
the
mall,
you
know
follow
the
future
and
leave
it
there
if
it
suits
the
criteria,
I'm
not
sure
what
the
criteria
was
so.
D
D
D
D
C
D
So
this
is
I'm
not
ready
to
do
the
vs
cowboy.
Yet,
let's
talk
about
open
ice
house,
so
one
of
the
challenges
with
ice
houses
there's
a
pretty
big
matrix
of
options.
Here,
the
right
we
have
ubuntu,
vs,
santos,
vs,
red
hat
versus
Susa,
and
so
the
red
hat
stuff
is
usually
their
enterprise.
Os
e
centos
is
our
do
and
then
that
the
problem
is,
we
also
have
the
matrix
includes
chef,
vs,
puppet
versus
salt.
A
C
D
The
community
ones
appear
a
little
bit
stuck
I'm,
sorry,
chef
people
if
you're
listening,
but
they
seem
like
they're
not
making
as
much
progress
in
the
Susa
team
on
creb
are.
One
has
really
been
been
making
a
lot
of
progress
on
those
chef
cookbooks.
The
problem
is
there:
they
only
are
being
supported
for
crowbar
one
Susa
pretty
narrowly
they're,
not
they're,
not
very
generic,
so
it
would
be
a
pretty
big
lift
so
that
I
mean
theater.
So
it's
a
small
lip
small,
smaller
lift
for
centos
support.
D
D
D
D
D
D
We're
going
to
need
to
describe
the
value
of
crowbars
added
complexity
against
cobbler
I
think
it's
would
be
very
hard
to
say
that
your
simpler,
simple
is
cobbler,
because
the
things
that
make
it
simple
are
the
very
things
that
limit
its
function.
So
the
lack
of
the
NS
integration
that
at
some
point
Victor
you
should
talk
about.
D
We
should
get
you
to
talk
about
the
console,
DNS
concepts,
but
the
lack
of
the
NS
integration,
the
lack
of
IP
assignment
the
law
and
chef
and
then
the
lack
of
actually
handing
off
to
chef,
puppet
or
salt
or
all
things
that
I
think
make
cobbler
less
attractive.
It's
why
razors
been
able
to
get
a
beachhead
in
that,
and
we
just
need
to
do
a
better
job,
showing
people
how
to
do
those.
Those
simple
tasks
then
I
think
that
will
make
cobbler
less
attractive.
I
think
we
also
need
to
have
a
easy
way
to.
E
D
And
that
takes
so
I
hope.
That's
coherent,
I'm,
sort
of
dumping,
a
whole
bunch
of
information
about
generalized
trends
that
I've
been
collecting
this
or
it's
worth
getting.
It
noted,
so
people
are
aware
of
things
I'm
hearing
and
if,
if
there's
concerns
or
people
want
a
challenge
edition,
just
let
me
know.
A
D
D
A
D
A
Or
an
advertising
man
at
heart
all
right,
so
that
looks
like
all
of
our
agenda
and
it's
the
top
of
the
hour.
So
if
nobody
has
any
other
anything
else,
I'll
close
this
down
and
thanks
for
listening
through
I'm
sticking
with
us
through
this
open,
crowbar
planning
meeting,
and
we
look
forward
to
the
design
meeting
where
we
get
to
demo
a
whole
bunch
of
new
stuff.
This
we've
been
working
on
the
past
2-3
weeks.