►
From YouTube: Crowbar Sprint Planning 2013 09 05
Description
Crowbar Project Planning for Sprint 2013-09-05
A
C
A
A
Is
there
anything
you
want
to
talk
about
rob,
there's
a
couple
of
things.
I
have
the
agenda
list
that
we
started.
Did
anybody
add
to
it.
A
And
so
we're
moving
we're
moving
this
to
the
crowbar.
A
You're
right
the
the
move,
it
will
be
moved
to
the
promo
repo
because,
oh
well,
I
think,
there's
a
better
space
for
it.
I
think
adam
corrected
the
copyright
issues
and
those
by
the
way
they
don't
bother
me
too
much
only
problem
is
that.
Well
you
know
I
I
mean
I
think
it's
your
copyright,
so
it
should
be
added
to
it,
but
that's
all,
but
yeah
so
he's
gonna
go
and
and
and
move
it
over
into
the
crowbar
repo.
A
A
The
mesa
branch,
a
hyper-v
pull
request-
and
I
would
add
to
this
now
the
the
rel
pull
requests.
A
Status
of
ci
progress,
I'm
not
sure
we're
ready
to
talk
about
that.
If
we
know
the
right
people
and
then
crowbar
to
update
some
status.
A
A
Not
from
me
adam,
I
don't
know,
we
there's
the
calls
showing
that
we've
got
a
whole
bunch
of
people,
but
only
adam
is
identified.
A
Okay,
sorry
guys
yeah,
there's
a
holiday
for
some
of
our
team
members,
so
they're
they're
out
judd
and
arkady
specifically.
B
Well
so
so
the
the
forks
of
my
repository
are
now
forks
of
the
crowbar
one.
So
in
particular
the
souza
fork
is
now
looks
like
it's
derived
from
crowbar,
just
like
all
the
other
ones,
which
is
what
we
wanted.
A
A
D
So
I
I
did
a
quick
review
on
these,
and
so
there
were
a
few
issues
and
I
think
they
got
fixed.
But
I
didn't
do
a
second
review
after
the
fixes.
A
A
D
D
D
That
was
showing
so
that
it
was
containing
the
cookbook
for
ipv
for
really
running
chef
and
deploying
stuff
on
the
windows
note,
and
it
was
also
containing,
I
would
say,
the
proposal
stuff
for
hyper-v,
which
was
more
or
less
a
fork
of
the
the
nova
bar
clamp
and
had
a.
I
had
a
discussion
with
cloud
base
in
octavian
and
since
the
nova
bar
clamp
now
supports
assigning
nodes
to
different
hypervisor
hypervisors.
D
A
D
So
we
want
to
keep
that
separate,
but
from
our
ui
perspective
it
should
really
belong
to
the
notable
clamp.
D
A
Cool
okay,
so
that
looks
like
it's
it's
it's
rolling
forward.
We
don't
need
additional
discussion
on
it,
because
it's
good.
A
Okay,
we're
trying
to
spin
up
a
team
here
that
knows
hyper
v
to
do
some
do
some
test
and
review
of
it
against
the
pebbles
branch.
Although
we'll
talk
about
we'll
talk
about
havana
work
and
in
a
minute,
and
that
this
guy
will
probably
want
to
focus
on
that
now,.
A
And
just
we're
we're
updating
the
mesa
branch.
I
know
this
is
more
of
a
stable
branch,
but
there'll
be
some
activity
on
it,
we're
updating
it
to
the
grizzly
three.
We
back
ported
the
vlan
support
that
was
already
in
pebbles
and
then
we're
going
to
be
doing
our
hadoop
work
on
off
of
the
mesa
branch.
A
A
Cool
good
any
other
topics
before
I
move
to
havana
and
branching.
A
Potentially
as
early
as
today,
but
I
I
think
it's
more
likely
that
it's
going
to
be
sometime
in
the
next
two
weeks
or
potentially
or
even
it
in
two
weeks,
exactly
because
that'll
be
our
boundary.
A
There's
already
there's
already
work
going
forward
on
havana
using
the
pull
from
source
pieces
and
the
aha
work
that
we've
been
doing
is
targeted
to
be
focused
towards
havana
as
a
havana
delivery
and
the
the
goal.
The
goal
for
this
is
to
be
able
to
have
havana.
A
We
know
we,
this
is
pretty
typical,
for
one
of
the
objectives
for
us
is
to
be
able
to
deploy
the
current
release
at
the
summit.
A
A
Yes,
I'm
waiting
for
a
response.
I
think
that
makes
sense
yeah
I
I
mean
you
know,
and
I
think
it
will
coincide
nicely
with
kind
of
the
release
of
the
suitsu
now
and
then
more
of
a
break
fix,
pull
request
scenario
rather
than
a
net
new.
A
Right
well,
the
the
consequence
would
be
I'm
expecting
the
pebbles
branches
to
stabilize
right.
So,
let's
left
new
code
change,
most
of
the
new
functionality
would
be
focused
around
pebbles,
and
so
the
timing
is
such
that
I
want
to
make
sure
that
everything
that's
in
flight,
that
ideally
the
biggest
changes
in
pebbles
are
already
in
right.
Since
I
know
you
guys
are
stabilizing
for
your
2-0
release,
and
so
structural
structural
changes
should
especially
the
krebs.
Our
core
should
be
minimal
would
be
my
expectation
right.
A
A
We
briefly
talked
about
about
that
before
you
came
on
on
the
call,
and
I
think
the
expectations
you
would
have
in
kind
of
the
plans
that
you
were
laying
out
match
up
with
with
what
what
what
adam
has
said:
okay,
they're
going.
A
And
pouches
and
stuff
like
that
to
the
2.0
stuff,
it
sounds
like
there
isn't
for
a
while
a
plan
to
do
a
major
o
release
and
instead
move
to
like
a
more
iterative
approach
to
the
things.
So
I
think
that
should
also
translate
into
less
frantic
activity
on
the
pebbles
branch
is
my
guess,
and
is
what
somewhat
was
confirmed
by
adam
as
well?
A
Okay,
because
what
I
would
like
to
be
able
to
do
is
spend
a
lot
less
time.
You
know
validating
and
doing
and
doing
reviews
of
pebbles.
A
We
still
want
to
maintain
code,
quality
and
stability,
because
it
should
become
the
stable
branch.
But
if
there's,
if
there's
still
a
lot
of
structural
changes,
then
that's
going
to
be
harder
to.
You
know
we're
going
to
be
splitting
effort
and
that
doesn't
that
doesn't
make
sense.
I
just
want
to
make
sure
we're
alive.
E
A
And
no,
it
looks
like
it's
been
settling,
which
is
why
I
think
it's
a
it's
a
good
time
to
do
this.
The
biggest
thing
that's
been
been
hanging
out.
There
is
the
change
to
add
a
database
to
capture
sessions
so
that
that
poll
is
still
hanging.
A
We
should,
ideally
that
is
either
agreed,
not
to
do
it
or
it's
in
before
before
we
fork
or
before
we
branch.
A
It
looks
it
looks
like
we're
pretty
reaching
a
good
time.
I
want
to
make
sure
that
what
what
I'm
seeing
it
matches
your
expectations.
E
A
Yeah
I
mean
I
I
would,
I
would
say
even
even
down
to
you
know
any
significant
ui
changes
or
enhancements,
or
things
like
that.
We'd
wanna,
I
mean
small
small
stuff.
It's
not
that
big
a
deal,
but
I
I
just
making
sure
that
we're
not
we're
not
creating
divergence
that
we,
because
what,
when
we,
when
we
branched
mesa,
there
were
a
whole
bunch
of
things
that
have
since
changed
in
pebbles
and
so,
which
is
fine.
That's
why
we
why
we
did
the
branch
it
allowed.
E
A
Cool,
I
mean,
I
don't
think
we're
gonna
get
the
zero
pull
requests
in
q
in
q
before
before
we
branch,
but
I'm
hoping
we
can
get
to
relatively
close
to
zero
and
it
might
make
sense
to
either
accelerate
or
hold
polls.
A
A
Okay,
so
we'll
we'll
announce
that
beforehand,
so
people
have
time
to
do
it,
but
I
would
say
tentatively,
you
know
next
sometime
next
week
for
early
the
week
after
any
any
concerns.
A
A
D
D
A
D
So
far
for
vmware
it
doesn't,
but
for
for
ipav
actually
does.
D
A
A
Cool
good
question,
and
I
would
suggest,
if
you're,
trying
to
whoever
asked
the
question,
if
you're
trying
to
do
this
and
bring
it
up
through
the
list
or
chat
and
we'll
see
if
we
can
help
you,
I
would
I'd,
be
very
interested
to
see
you
guys
if
there's
some
zen
server
capability,
you
know,
even
if
it
doesn't
work
in
in
the
other
operating
systems,
I'm
assuming
it's
it's
in.
It's
just
not
doc.
It's
just
not
not
tested
on
the
other
platforms.
A
All
right
so
mesa
brandt,
we
talked
about
mesa
branch
talked
about
havana
branch,
hyper
v,
rail.
We
are
still
working
on
on
getting
our
ci
infrastructure
in
place
to
do.
Tesla
polls.
A
The
guys
aren't
here
to
talk
specifically
about
it.
It's
still,
it's
still
a
priority
for
us
to
do
it,
but
since
the
it
seems
like
full,
full
request
manual
test,
support
request
is
still
paying
that
the
changes
are
less
dramatic
and
so
less
risky.
A
Let's
talk
about
the
the
sliding
all
the
meeting
schedules
back
by
week,
now's
a
good
time
to
talk
about
changes.
If
we
want
to
change
the
these
community
meetings,
we've
been
missing
a
lot
lately,
so
it's
worth
saying
that
they
are
they
still
working
it's
this
something
we
want
to.
We
want
to
get
back
into
the
rhythm
of.
A
All
right,
my
expectation,
is
that
crib
r2
stuff
is
heating
up
and
having
a
regular
cadence
of
design,
review
and
planning,
and
coordination
on
chrome
r2
is
going
to
be
useful
and
it
actually
looks
like
philosophy
on
crowbar
overall
is
heating
up,
and
we
having
these
things,
think
points
are
really
helpful.
So
unless
somebody
has
a
strong
objection,
I
would
prefer
that
we
keep
these
cadences.
A
A
So
not
somebody
objects,
we'll
keep
the
basic
cadence
thursday
mornings
for
community
community,
sprint
coordination
and
planning
coordination,
and
then,
on
the
alternate
weeks
of
design
meeting
where
we
talk
about
design
concepts,
there's
a
significant
backlog
of
topics
that
we
have.
So
we
need
to
start
it.
You
know
making
sure
we
have
a
prioritized
list
and
then
we'll
start
knocking
those
things
out.
A
I'm
also
planning
to
start
doing
videos
and
docs
about
crowbar
2
and
how
that
operates
the
infrastructure,
building,
cookbooks
and
things
like
that.
So
that
expect
to
see
those
things
starting
to
come
up
and
I'll
post
as
I
post
them
I'll
post
through
the
list.
So
all
that,
all
that
all
that
pieces
will
come
and
as
a
reminder,
the
crowbar
tooth
system
has
an
integrated,
integrated
docs,
and
so
you
will
see.
A
That
we
are
trying
to
maintain
documentation
in
these
in
these
stock
directories.
Somebody
is.
A
So
I'm
I'm
trying
to
keep
these
docs
up
to
date
and
if
people
have
items
or
or
anything
if
they
watch
videos
and
see
useful
information,
please,
let's,
let's
make
an
effort
as
we
as
we
start
development
and
ramping,
crowbar
ii,
that
we
we
stay
ahead
on
the
dock
side,
certainly
making
sure
we
stay
up
on
test
and
docs
for
the
semester
code.
I'm
doing
right.
A
That
makes
a
lot
of
sense.
Yes,
that
makes
a
lot
of
sense.
B
I
mean
I,
I
think
I
think
it's
just
maybe
just
a
difference
in
in
the
way.
The
way
we
work,
but
generally
you
know
we're
very
email
and
list
oriented
and
from
from
what
I've
seen
in
the
past,
some
of
the
design
calls
unless
you're
regularly
attending
them
and
regularly
sort
of
hands
in
the
code.
B
It's
pretty
hard
to
follow
along
some
of
it.
I
mean
less
so
for
me,
but
I
think
for
some
of
my
colleagues
who
you
know
especially
having
not
been
involved
in
the
design
discussions
in
in
austin.
When
I,
when
I
was
there,
you
know
I
they've
been
there
being
discussion
since
then
that
I
I
could
follow
along,
because
I
had
that
background
understanding.
B
But
anyone
who
hasn't
been
privy
to
those
kinds
of
live
conversations
is:
is
it
it's
just
not
really
what's
going
on,
whereas
if
you,
if
you,
if
you
do
it
via
ongoing
discussions
on
the
list
where
people
have
are
able
to
sort
of
mentally
digest
the
information
in
their
own
time
and
and
to
you,
know
cross-reference
it
by
looking
at
code
or
design
documents
or
you
know,
schema
diagrams,
and
that
kind
of
thing
I
think
that
way
can
work.
B
A
Fair
enough,
I
I
one
of
the
things
that
I'd
like
to
see
and
we
need
we
need
some
help
with
is
to
transcribe
things
that
are
going
on
in
those
when
we
have
the
synchronous
meetings
and
create
and
create
reasonable
leap
behind.
A
So
I
I
adam
I
I
hear
what
you're
saying
and,
and
we
will
we
will
step
up
efforts
to
make
sure
that
we
pump
things
out
to
the
left
and
do
it
one
of
the
the
challenges
that
I
wanted
to
see
figure
out
how
to
get
past.
We
have
the
same
issue
on
our
team
because
not
everybody's,
actually
relatively
few
people
have
been
involved
in
the
crowbar
ii
design
of
late
and
so
we're
going
to
have
to
educate
people.
So
they
have
the
contacts
to
understand
the
email
threats
right.
A
The
email
threats
can't
can't
completely
rehash
everything.
So
we
have
to.
We
have
to
build
some
background
materials,
so
people
can
understand
what's
going
on
and
then
then
have
the
targeted
email,
email
conversations
about
it
and
we
need
help
helping
capture
this
that
information.
So
people
understand
it.
B
Yeah
I
mean
I
appreciate
it's
frustrating
for
you
guys,
because
you
know
you're
sort
of
working
together
on
a
daily
basis,
face
to
face
and
you're
able
to
make
a
lot
of
progress
quickly
by
just
you
know,
whiteboarding
stuff
and
whatever,
and
it's
it's
frustrating
to
then
have
to
take
extra
time
to
you
know
to
share
that
to
to
write
it
out
on
the
list
or
document
it
and
draw
diagrams
and
so
on,
but
like
if
yeah,
if
you,
if
you
want
the
community
to
you,
know
the
development
community
to
grow
outside
naval.
B
I
think
that's
that's
outside
dell,
at
least
they
rhyme,
then
that's
the
only
way
really.
A
One
of
the
things
that's
been
happening
in
the
design
work
is
we've
actually
transitioned
over
into
sort
of
the
the
validation
of
the
design
components.
It's
still
almost
identical
to
what
we
discussed
out
of,
but
I
realize
very
few
people
understand
that
so
in
the
next
sprint.
My
expectation
is
that
our
team's
going
to
be
doing
an
education
effort
and
the
first
thing
in
doing
that
is
going
to
be
creating
the
docs
and
making
sure
that
we
have
leave
behind
and
those
things
are
written
down
in
a
comprehensible
way.
A
I
won't
need
help
to
do
it
doing
that
I'll
post
videos
of
training
sessions.
I
do
and
we'll
create
as
much
documentation
as
we
can
as
we
get
and
do
it
in
a
place
where,
where
people
have
questions,
we
can
have
people
come
in
and
add
and
extend
one
of
the
things
that
I
want
to
make
sure
we
do
as
a
community
is
transition,
transfer
those
email
discussions
into
documentation,
and
that's
that's
going
to
take
a
pretty
broad
spectrum
effort.
B
A
A
Are
enough
to
actually
run
the
system
and
make
it
work,
I'm
still
trying
to
build
a
complete
bdd
test
coverage
for
the
annealer,
and
that
means
I'm
testing.
Basically,
I
have
to
test
everything
to
get
there
and
then
we've
we're
actually
having
crowbar
2,
building
a
admin
server
and
all
the
capabilities
for
the
admin
server,
which
includes
installing
shaft
using
the
script
jig
and
then
using
chef
to
install
ntp,
dns,
dhcp
logging
and
now
and
then
the
networking
pieces.
And
then
that
means
we
can
finally
start
building
up
the
provisioner
and
the
deploy.
A
A
A
One
of
the
advantages
of
doing
that
is
that
it
eliminates
the
need
to
pre-populate
the
the
glance
cache,
which
makes
the
glass
bar
clamp
much
smaller
if
you're,
if
you're,
if
you're
having
to
transport
it.
A
So
if
people
are
familiar,
docker
is
a
galaxy,
it's
basically
an
extension
lxd
that
adds
some
some
extra
capabilities
and
improves
the
portability
of
containers
in
the
lxe
system.
So
you
can
treat
docker
docker
containers
as
effectively
portable
virtual
machines
they're
not,
and
one
of
the
the
things
that
I've
been
being
asked
about.
A
lot
is
bare
metal
and
fair
metal
performance
and
how
crowbar
compares
or
interacts
with
ironic.
A
That's
that
that's
a
another
topic
topic
for
another
day,
but
it's
definitely
something
that
I'm
working
out
a
position
for,
and
I
can
certainly
as
a
as
we
start
to
document
it.
People
are
interested.
We
can
extend
that
conversation
to
the
list
because
I
suspect
other
other
people
who
are
using
crowbar
are
getting
similar
questions.
A
I'm
I
I'm
getting
a
lot
of
enthusiasm
around
docker
for
because
it
we
can
talk
about
over
subscription
and
bare
metal
performance
without
having
to
deal
with
all
the
mess
of
bare
metal
provisioning
which
kerber
is
built
to
do.
But
cloud
deployments
aren't.
C
A
All
right
that
that
was
a
significant
agenda.
Anybody
want
to
take
time
to
talk
about
topics
we
didn't
cover
and
should
cover
for
the
next
week,
or
we
can
just
build
that
up.
In
the
background.
A
And
it
sounds
like
we're:
we
we
were
done
so
we'll
get
together
wednesday.
One
of
the
agent
items
will
be
that
adam
will
do
the
ucs
demo.