►
From YouTube: OpenCrowbar Community Meeting 2014-12-03
Description
Agenda:
Broom.4 / 2.1 Release
Branching Strategy Implementation
OpenStack Packstack Workload available
Backlog
Camshaft Themes and Objectives
Minutes: https://groups.google.com/forum/#!topic/opencrowbar/qlMWz32MKqM
A
A
Hello,
this
is
Robert
felt
and
I
am
hosting
today's
up
in
creve,
our
community
call.
So
we
have
a
couple
of
things
we've
built
into
the
agenda
already
and
then
we
can
entertain
some
other
items
as
we
go.
This
should
be
enough
to
get
us
started.
Oh,
we
should
look
at
the
backlog.
I
wasn't
in
the
last
meeting
or
to
greg.
Did
we
do
backlog
grooming
all
right?
No.
B
B
So
we've
cut
room
for
and
we're
going
to
name
it
open,
crowbar
two
dot,
one
there's
some
issues
with
the
centos
upstream
repos
that
once
that
fixed
will
generate
official
rpms
for
the
two
thousand
over
lease
and
create
a
tag
for
that.
At
that
point,
the
features
around
it
are
some
stability
stuff,
install
cleanups,
like
your
writing,
packaging
to
do
a
more
traditional,
install
versus
a
get
pulled
and
a
development
install
we've
updated
the
docks
to
represent
that
give
you
a
way
to
run
it
in
the
load.
B
B
A
B
Master,
which
will
be
the
20
21
tag
once
we
get
all
the
stuff
long
down
from
then,
if
you've
looked
at
the
repos
recently
you'll
notice
that
there's
now
a
develop
branch,
it's
now
been
made
a
default
branch
and
all
of
the
trees
are
in
all
the
repos.
This
is
where
development
of
camshaft
will
take
place.
B
So
as
we
talk
about
camshaft
will
create
a
camshaft,
we
may
do
it
for
sprint.
We
don't
think
this
friends
are
sufficient
content
wise
then
we'll
do
them
every
couple
of
friends.
The
idea
is
that
master,
won't,
necessarily
change,
and
so
we've
got
a
reasonable
amount
of
content
that
we're
happy
with
the
development
will
be
representative
of
camshaft
and
maybe
we'll
tag
development
with
sprint
boundaries
or
something
mix-ins.
B
A
B
Based
upon
what
we
decide
for
size
of
content,
camshaft
is
currently
not
looking
huge
so
or
it's
large
and
some
of
its
value.
But
it's
not
necessarily
going
to
be
changing
core
a
lot
we
shouldn't
I
would
guess
so.
It'll
probably
be
a
minor
release,
but
if
we
turn
out
needing
to
add
some
major
features,
we
may
choose
to
rev
the
major
release
as
well
right.
A
A
A
A
A
A
B
A
A
A
A
B
A
A
A
A
B
B
A
A
A
A
A
A
A
So
we
talked
about
the
broom,
we
talked
about
branching
strategy,
though
I
was
going
to
talk
about
pack
stack.
We
talked
about
the
backlog
a
little
bit.
We
can
talk
about
pulling
things
over
and
then
cap
camshaft
themes
objectives.
We
probably
need
to
do
camp
chef
needs
and
objectives.
First,
let
me
talk
about
the
tax
back
stuff.
Briefly,.
B
B
A
A
So
there's
a
sadist
a
couple
different
ways,
but
Bracken's
not
racking
in
the
curb
our
team
Iraq
and
are
really
not.
We
know
a
lot
about
OpenStack,
but
we're
not
trying
to
become
an
OpenStack
company.
We
are
working
for
with
OpenStack
partners
and
people
who
know
how
to
use
OpenStack.
So
we
want
the
demo
to
be
available,
so
people
can
try
it,
but
it's
we're
not
going
to
be
able
to
help
people
can
figure
obvious
bridges
and
OpenStack
to
under
pack
stack.
That's
only
would
we
expect
people
together
and
expertise
for.
A
And
that's
what
so,
in
the
for
the
broom
release,
I'm
trying
to
prepare
a
series
of
videos
like
a
like
a
traditional
done,
but
I'm
going
to
break
it
into
small
pieces.
So
the
pack
stack
is
just
this
one.
Little
and
end
point
just
show
how
that
goes,
but
we
have
a
whole
bunch
of
other
pieces
to
show
off
argos
to
release.
That's
just
good
thing.
A
The
the
theme,
the
theme
for
broom
was
hard,
we're
getting
the
hardware
stuff
going
and
sort
of
the
whole
way
we
operate.
This
is
we
try
and
have
most
of
the
theme
pieces
done,
the
beginning
of
the
release
cycle,
and
then
we
end
up
building
it
in
advance
pieces,
as
we
harden
so
camshaft
we've
already
done
some
integrations.
A
A
A
A
A
A
And
then
so
we're
talking,
we
want
to
talk
about
the
cobbler
piece
a
little
bit
or
not,
because
I
think
that
this
actually
ties
in
with
integration
like
this.
So
one
of
the
one
of
things
that
we've
been
talking
about
from
that
I've
dns
integrations
because
one
things
that
you
have
to
have
a
good
day
in
SF
integration
to
dns
integration
can
be
part
of
that.
So
this
will
be
turning
making
it
more
more
extensible
and.
A
Right
with
the
idea
being
that
those
are
crowbar
does
a
lot
more
consistently
an
orchestration
system
and
those
other.
There
are
multiple
ways
to
lay
down
at
LS
maintain
provisioning,
so,
instead
of
maintaining
our
own
being
able
to
hook
into
one
or
more
and
more
of
other
ones,
that
I
think
is
actually
just
a
design
discussion
meeting
on
its
own
I
know
from
our
our
conversations.
It's
been
like
that.
A
A
A
A
A
B
A
A
A
B
A
A
B
A
B
B
A
So
the
other
thing
that
I
was
looking
to
do
was
to
add
a
ticketing
tickets
to
the
node
rolls
so
a
sink
node
roll
want
action
so
I.
In
order
to
do
some
of
the
testing
for
the
UI
and
the
Ajax
pieces
of
the
UI,
we
actually
need
a
way
for
the
simulator
to
drive
a
new
role
in
overtime,
not
all
not
all
up
front
like
it
does
right
now,
because
otherwise,
it's
very
difficult
to
test
the
Ajax
updates
right.
B
A
A
The
idea
would
be
when,
if
I
have
a
jig,
that
says
are
actually
no
trolls
action.
This
is
hey
I'm,
not
you're,
not
going
to
do
anything
here,
I
created
a
ticket
for
you,
then
it
would
I'm
going
to
have
to
add
a
field
to
know
trolls
to
store
the
ticket.
I
guess
I
could
store
it
in
the
notable
data
itself.
Good
night
and
I.
Don't
wanna.
A
A
A
But
that
that
should
then
it's
actually
good
I
need.
Oh
I,
have
to
add
a
waffle
item
for
donor
which
I'll
do,
but
so
the
idea
would
be
that
would
allow
you
to
then
do
an
external
integration
that
come
back
and
say:
hey
I'm
done
here's!
You
report
this,
take
a
completed
report,
this
ticket
sales-
oh
the
other
one-
that
we
talked
about,
was
sort
of
the
dummy,
node
validation
steps
leave
a
ticket
for
that
to
the
now.
B
A
So
what
what
my
thought
here
is
that
we're
I
consistently
hear
people
ask
for
a
physical
system
that
does
validation,
that
the
physical
system
that
you've
installed
is
set
up
right.
Networking
for
endor,
like
actually
do
a
hardware
qualification,
run
some
some
memory
tests.
So
there's
there's
two
aspects
to
this
they're
like
this,
so
one
is
what
is:
is
this.