►
From YouTube: OpenCrowbar Community 2014 09 24
Description
Notes: http://pad.opencrowbar.org/p/community-planning-meeting-2014-09-24
Planning Call for Broom.2 sprint.
Work includes hardware support, Centos 7, Salt & Chef Metal
A
Hello,
everybody
and
well
the
timber
24th
open,
crowbar
planning
meeting,
as
is
normal.
This
is
our
it's
a
bite.
We
have
a
weekly
meeting
with
a
biweekly
cycle,
so
every
other
week
we
talk
about
sprint,
planning
objectives
and
then
the
other
weeks,
the
midweeks.
We
talk,
design,
topics
and
review
review
work
in
progress
so
that
we
actually
can
exchange
ideas
and
the
just
work.
A
A
Can
actually
do
this
so
you'll
notice
that
we
actually
went
back
and
group
things
into
different
release.
Sprints
and
releases
I
have
time
in
here
where
I
do
a
about
release
planning,
because
I
believe
we're
coming
to
a
point
where
I'd
like
to
close
the
broom
release,
what
we're
going
to
need
to
review
what
the
what
the
deliveries
are
for
that.
A
B
A
A
A
C
A
A
A
A
C
A
About
six,
my
typing
is
degrading
before
before
your
eyes,.
B
A
State
wizard
right
there
off
the
menu
hot
dog.
Look
at
that
there's,
no
there's
no
pm's
in
it
right
now,
but
and
then
so.
The
readystate
wizard
under
utilities,
bootstrap
are
sorry.
The
bootstrap
employed
and
I
will
show
you
what
how
this
works,
so
we
can
close
it.
So
what
what
we,
when
we
change
the
attributes
the
screen
had
to
get
refactored,
and
so
the
way
it
works
is
if
there's
no
admin
network
you
can
gives
you
a
button
to
create
it.
In
this
case
it
exists.
It
gives
you
a
link.
A
A
A
B
A
C
A
Right
so
here's
here's
the
deal,
I'm
going
to
remove
that
section
or
change
it's
a
downed
roles,
so
you
can
see
them,
and
I
can
add
logic
that
says
if
it
doesn't
have
curve
our
admin
node
flag
it,
but
I
I
have
to
work
through
I
haven't
worked
through
the
walked
through
the
workflows
of
the
zombies
sort
of
the
zombie
mode
install
right
now.
Maybe
this
is
just
the
way
we
do
it.
If
you,
we
assume
you
run
production
on
that
server.
It
turns
that
server
into
an
admin
node.
A
Until
we
have
somebody
who
doesn't
use
it,
I
I've
mixed
feelings
about
showing
it
here
so
I.
If
please
open,
a
bug
asked
me
to
remove
the
adding
44
room,
2
and
I
will
I
will
do
that?
Call
it
a
bug,
then
we'll
get
it
fixed,
and
then
this
is
this
is
the
other,
so
there's
a
set
of
attributes
that
are
editable
in
this,
and
so
the
only
one
is
DNS
forwarders
here,
and
so
you
could
actually
edit
it
and
save
it.
A
And
it's
this
this
review
key
attributes
was
the
key
was
the
the
fundamental,
the
important
change,
and
then
you
can
go
to
the
anneal
and
watch
all
this
stuff
going.
If,
if
the
admin,
if
you've
created
the
admin
role,
it's
not
committed,
you
actually
have
to
commit
the
deployment
there's
a
button.
For
that
too.
A
B
A
Way
down
deep
and
out
so
the
way
crowbar
just
put
it
on
record
the
way
this
works
is
we
do
a
bunch
of
pre
configuration
in
production
SH
and
against.
So
the
cricket
have
been
server
using
the
API.
We
do
a
whole
bunch
of
configuration
in
production
SH
which
could
be
done
manually
if
you
didn't
use
production
of
SH
and
then
the
last
thing
that
that
script
does
is
it
marks.
A
The
admin
note
is
alive
at
which
point
the
annealer
goes
in
and
and
acts
on
it
and
so
there's
a
flag
that
you
can
set
in
production
on
SH.
That
does
all
the
work
except
marking
the
note
alive,
which
I
humorously
called
zombie
mode,
because
your
servers
not
alive
and
then
you
get
to
mark
you
mark
it
alive,
and
then
it
finishes
the
annealing
okay.
A
B
C
B
A
What's
a
shiny
issue,
oh
you
got
my
shiny
issue.
So
if
I
look
at
my
room
to
work
for
broom.
B
B
A
A
B
B
A
A
B
C
A
A
You
you
move
back,
they
took
public
key
convert
documentation
to
mark
down
I,
don't
see
Mike
on
the
call.
So
I
don't
know
if
we
can
commit
this
one.
But
I'd
like
to
see
this
done
before
they're
released
and
then
we
need
to
pull
all
the
UI
code
generation.
Stuff
out
is
included
in
that
convert
you
our
pages
to
refresh
I'll
work
with
messiest
on
that
might
be
able
to
spend
them
now
add
interface,
UI
right!
That's
a
bug!
I
need
to
fix
that.
A
A
B
A
C
B
A
B
B
B
B
B
B
A
B
C
C
B
A
A
C
Had
to
grab
some
eat
button,
it
was
like
7
layers,
deep
of
my
phones
in
particular
to
what
it
as
far
as
hitting
the
CentOS
7
support,
yeah.
A
A
A
A
A
C
A
C
A
B
A
B
Gonna,
like
just
to
change
that
just
you
know
at
it,
give
you
a
new
key,
a
unique
name
and
added
into
that.
The
hash,
that's
basically
yes
and
any
new
know
they're
discovered,
will
have
that
key
injected
into
them.
At
all
points
in
the
lifespan
where
we
agreed
with
them
were
set
up.
Ssh.
A
A
A
Ok,
let
me
change
this
to.
B
B
A
A
A
I
and
then,
from
that
perspective,
I'm
going
to
move
it
I
think
moving
it
to
broom.
3
is
probably
appropriate,
not
all
the
way
two
camshafts,
because
I
think
it
might
be
a
needed
for
needed
for
the
camshaft
before
the
camshaft
release
that
it's
this.
This
to
me
is
a
fact.
You
know
what
I'm
going
to
move
it
to
camshaft
and
will
consider
it
a
nice
to
have
feature
if
it.
C
A
C
B
A
So
that
perspective,
what
I
would
I
think
we
should
do?
Is
this
document
poof
been
typing
doctor
too
much
SSH
key
injection
work
around.
A
A
C
C
A
It's
all
good
I've,
ad
hoc
stuff
that
we
can
get
to
chef
metal,
we're
going
to
have
to
demo
next
Wednesday
tall
stack
integration,
demo
next
Wednesday,
so
we
had
some
dip.
I
was
coming
during
the
review
meeting
the
design
meeting
open
stuck
Scott.
Do
you
want
to
talk
about
camshaft
and
thoughts?
For
that?
Are
you.
C
C
Briefly,
go
over
or
what
I'm
thinking
about
it
I
think
it
might
also
make
sense
just
to
you
know,
as
part
of
the
design
meeting,
just
go
through
a
little
bit
of
roadmap
work.
So
perhaps
you
can
do
that
next
week,
but
the
the
basic
thing
I
was
thinking
of
up
at
at
this
point
is
that
you
know
broom
is
effectively
the
base
hardware
provisioning
release
and
it
brings
you
up
through
through
the
the
bios
and
the
raid
functions,
and
you
know,
basics
network
setup
in
those
sort
of
components.
C
C
Handing
off
to
these
other
these
other
infrastructures,
such
as
you
know,
salt,
the
salt
integration
back
stack,
those
sort
of
functions
so
I
think
that's!
You
know,
that's
what
I'm
proposing
that
we
target
for
for
the
camshaft
release,
but
it's
something
we
should
discuss
in
the
desired
section.
A
C
A
C
That's
pretty
much
what
we're
looking
at
is.
We
have
some
work
ahead
items,
but
primarily
what
we
should
be
focused
on
is
getting
the
you
know.
The
base
rate
and
hardware
provisioning
functions
into
the
system
is
part
of
room
right.
The
the
camshaft
release
is
really
targeted
towards
those
integrations.
If
we
have
some
proof
concepts
and
some
rarely
work
or
some
MVPs
that
are
happening,
you
know
that
are
happening
now
is
we're
getting
people
to
speed
or
whatnot
on
the
next
slide.
A
C
But
it
also
is
a
you
know.
A
good
place
for
I
mean
some
of
the
underlying
components
that
we're
doing
really
only
makes
sense
when
you
you
move
it
up
through
the
through
the
stack
and
it.
You
know,
it
makes
sense
to
work
up
through
the
through
the
stack
and
at
least
some
limited
passion
for
some
of
these
components.
A
C
Well,
no,
those
are
really
broom
functions,
I
mean
you
know
these
things
are
you
know
they
don't
muddy
up
right.
I
mean
we're,
obviously
not
going
to
implement
every
operating
system.
We
think
people
could
possibly
want
without
a
you
know,
without
a
driving
need
to
do
so.
So
this
time
goes
on
right,
though,
if
they'll
get
dropped
in,
but
from
a
really
see
type
of
Fame
thing
based
off
of
a
few
know.
What
I'm
just
said
right
and
it's
in
again,
we
haven't
all
gone
over
agreed
with
it.
C
B
B
B
B
You
I
mean,
ideally,
we
have
one
of
the
things
that
needs
to
be
on
our
to-do
list
for
sending
up
technical
debt
is
going
back
in
the
refactoring
how
the
provision
of
works
to
you
know
kind
of
brainstorm
about.
If
you
still
need
our
current
provisioner,
we
could
know
just
drive
something
like
razor
or
you
know,
modularize
our
current
provision,
your
layer
or
something
wrong
with
one.
B
A
B
A
A
B
B
A
C
B
A
I
feel
like
we've
covered
planning.
I,
don't
see
a
need
to
extend
the
time
if
we've
covered
all
the
topics
feasible.
What
we're
holding
off
road
map
I
think
we
covered
in
some
detail,
but
not
as
much
scott
as
I'm
hoping
we'll
go
to
in
the
future
and
openstack
options.
I
can
talk
about
a
little
bit
at
hawk.
A
So
it
seems
like
there's
a
lot
of
interest
for
people
who
want
centos
to
use
packs
back
in
our
do,
which
makes
sense
to
me,
and
so
we're
sort
of
talking
to
people
who
are
going
through
that
path
and
looking
for
an
RDO
pack
stack
on
CentOS
7
is
one
of
one
of
the
paths
and
then
I'm
still
still
optimistic.
That
susa
team
is
interested
in
taking
their
cookbooks
and
bringing
them
over
to
open
crowbar.
A
They
might
I,
don't
know
how
that
you
know
they
want
to.
They
want
to
be
part
of
the
OpenStack
chef
community,
although
I
don't
know
that
at
this
point
is
really
feasible
to
reconcile
the
work
that
Zeus
is
done
with.
What's
in
the
upstream
community
and
watching
the
chef
upstream
community
and
and
trying
to
get
their
stuff
through
a
gate.
A
I'm
I'm
interested
I'm
happy
to
have
one-on-one
conversations
I'm
out
I'll,
stop
talking
in
a
second
and
open
up
the
floor.
I
really
think
we
need
to
have
some
type
of
gate
says
an
auto
NCI
system
around
these
workloads
to
make
them
effective,
but
I
think
it's
going
to
have
to
be
a
multi-node
deployment
different
than
potentially
different
than
the
OpenStack
gate
system.
A
A
All
right,
it's
still
it's
still
preliminary
I'm
just
trying
to
get
it
out
there,
because
I
I
haven't
heard
anybody
very
happy
with
how
the
physical
side
of
the
deployments
going,
and
it
seems
to
me
that
we
could.
We
could
actually
play
a
really
helpful
role
in
without
being
supporting
these
communities
without
having
to
be
embedded
in
the
communities
and
so
I'm.
Looking
for
people
who
can
do
be
that
bridge
very
simply,.