►
From YouTube: OpenCrowbar Community Meeting 2014 04 09
Description
Demo of the Docker Slaves nodes and sprint planning
A
Hey
everybody
and
welcome
to
april
the
9th
2014
open,
crowbar
community
planning,
meeting
we're
planning
on
today
a
little
preparatory
chatting
and
then
reviewing
the
the
pull
requests
that
came
in
over
the
past
sprint.
Talking
about
what
we're
planning
on
doing
and
then
getting.
Hopefully
a
demo
and
some
discussion
on
the
docker
workload
nodes
that
are
now
one
of
the
core
features
of
opencrowbar.
A
A
Over
the
past
week,
we've
introduced
a
lot
of
two
or
three
very
important
features.
The
workshop
support
for
all
you
chefs,
who
are
writing
cookbooks
and
would
like
to
be
able
to
deploy
those
cookbooks
and
their
dependencies
with
crowbar.
It
now
makes
it
a
lot
easier
we're
still.
This
is
just
initial
support
for
the
quickbooks
that
our
project
is
using,
but
also
in
the
previous
sprint
and
the
upcoming
spring
beginning
to
integrate
upstream
cookbooks
into
our
merch
style
system.
A
There
were
a
bunch
of
bugs
that
we
that
we
killed
this
past
sprint,
mostly
around
the
ui
and
the
the
the
last
and
most
exciting
thing
is
that
we
can
bootstrap
docker
nodes,
so
we'll
be
demoing
that
a
little
later
we
can
bootstrap
enough
docker
modes
to
show
off
some
of
the
synchronization
things
that
we
still
need
to
fix
in
the
database.
So
yay.
A
A
A
Fixing
some
of
the
synchronization
issues
that
we're
having
in
the
database,
which
is
pretty
much
just
a
consequence
of
too
many
things,
trying
to
touch
the
same
room,
the
same
table
at
the
same
time
and
also
working
on
beefing
up
the
attribute
the
attrib
model,
so
that
when
you
change
the
trig
via
the
api
or
via
the
ui,
it
will
automatically
schedule
all
the
node
roles
that
either
provide
or
want
that
attribute
to
be
rerun.
With
the
new
value.
A
B
A
It
seems
like
the
biggest
unresolved
question
in
development
is
kind
of
falls
into
two
lines.
First,
whenever
you're
just
hacking
on
a
cookbook,
how
well
will
berkshire
deal
with
needing
to
make
ephemeral
forks
like
forks,
that
need
to
last,
like
a
sprinter
three,
until
we
can
get
changes
merged
back
into
the
upstream
cookbooks?
A
If
you
have
any
kind
of
ditto
for
making
for
deploying
advent
nodes
with
local
forks
instead
of
using
up
streams
when
we
need
to
on
a
temporary
basis,
I
don't
like
having
to
go
in
to
edit
the
mercs
files
manually
whenever
we
have
to
do
that,
because
we
all
know
that
that's
going
to
lead
to
people
forgetting
to
change
things
back
and
hilarity
and
zooming
down
the
downstream
from
that
yeah.
I
haven't.
A
A
A
A
So
in
an
effort
to
not
reinvent
the
wheel,
we'll
see
what
burks
3
is
doing,
but
for
now
for
the
foreseeable
that
centralized
works
file
under,
say
your
workload
like
core
slash,
chef,
slash,
cookbook.
The
brooks
file
in
there
is
the
the
one
true
source
and
just
remember
that
when
burke's
install
gets
called,
which
is
really
a
barclay
at
install
time
and
works,
install
gets
called,
it
creates
a
works
file,
dot
lock,
and
it's
really
that
works
file.
Dot
lock.
B
A
A
A
Okay,
yeah,
because
if
you
have
that,
then
we
can
partially
solve
it
just
by
if
you're
not
making.
If
you
don't
have
a
if
you're,
not
making
hacks
locally
on
a
cookbook,
then
just
don't
have
a
local
copy
of
it,
and
if
you
don't
need
a
local,
if
we
don't
need
like
a
an
org
specific
fork
of
a
cookbook,
while
we
are
getting
bug,
fixes
or
features
push
up
stream,
then
we
just
don't.
Have
it
and
perks
would
just
automatically
fall
back
in
the
order
in
which
we
set,
where
we're
going
to
fetch
cookbooks
from.
A
A
A
A
A
A
There
was
while
we're
waiting
for
this.
There
was
an
excellent
podcast
that
I
listened
to
earlier
this
week.
On
my
way
up
from
new
york
city
called
the
ship
show
and
their
most
recent
hour
is
spent
with
three
relief
engineers,
a
couple
operations
guys
and
a
developer
talking
about
how
different
ways
to
use
docker
and
different
ways
to
be
using
docker,
and
they
were
kind
of
experimenting
with
ideas
and
tossing
them
around,
and
it
was.
It
was
really.
A
To
see
both
the
users
that
they
were
putting
it
to,
and
also
some
of
the
challenges
that
folks
have
understanding
that
docker
isn't
just
containers,
it's
not
just
creating
a
container.
It's
also
a
union
file
system,
which
is
a
layered
file
system,
where
you
can
actually
ship
around
layers
of
a
file
system
from
one
container
to
another,
if
they're,
if
they're
launched
from
the
same
image
share
diffs
from
them.
A
It
would
also
allow
the
os
to
not
necessarily
be
patched,
but
only
the
container
that
held
the
web
server
needed
to
be
patched.
You
could
really
overlay
the
new
ssl
libraries
on
top
of
the
old
ones,
without
changing
the
underlying
operating
system,
but
making
the
new
libraries
available
to
the
web
servers
reducing
your
need
for
potentially
rebooting
or
the
the
temptation
to
reboot
the
os
that
the
web
servers
are
running
on.
A
A
A
A
A
Mostly
because
the
row
in
question,
the
main
thing
that
I'm
updating
is
a
gigantic
blob
that
gets
pushed
such
a
gigantic
blob
of
json.
That
gets
pushed
straight
into
chef,
and
I
need
to
go
back
to
dynamically,
generating
it
on
the
fly.
But
in
such
a
way
that
doesn't
cause
the
exponential
slowdown,
the
more
nodes
we
get.
A
A
A
A
A
A
A
A
Which
image
are
you
using
to
create
the
container
a
custom
one
right
now,
based
on
the
ubuntu
image?
That
already
has
a
chef
solo
loaded,
so
we
don't
have
to
spend
so
much
time
loading
it
or
we
don't
have
to
spend
time
installing
it
right
great.
The
script
itself
doesn't
care
about
that.
But
if
you
don't
write
it
on
one
of
our
images,
it'll
be
forced
to
download
and
install
curl
and
chef
solo.
So
we
can
do
our
things.
A
A
And
there's
our
20
nodes
and
they've
already
checked
to
make
sure
there's
a
chef
there's
a
chef
solo
on
the
box,
they've
already
wired
up
their
admin
network
appropriately
right
now,
I'm
having
to
run
the
docker
containers
in
privilege
mode
to
do
that
future
releases
of
docker
will
allow
me
to
assign
no
assigned
container
capabilities
on
a
more
fine-grained
basis.
So
I
can
just
switch
to
letting
the
containers
have
cap
net
admin,
so
I
don't
have
to
give
them
the
full
power
the
privileged
implies
and
they've
set
up.
A
A
So
these
are,
these
are
yeah
right,
so
they'd
be
talking
out
to
the
open
to
repositories,
tactic,
repos,
get
all
updated
and
ready
whatever
you
want
into
them.
Yeah
pretty
much.
The
responsibility
of
this
role
is
to
make
sure
that
the
node
has
the
right
gym.
Rc
the
right
proxy
settings
make
sure
that
everything's
set
up
to
use
the
proxies
on
the
admin
node
and
make
sure
that
the
node
has
all
the
references
to
the
right
in
cluster
and
upstream
package
repositories
that
we
wanted
to
have
access
to.
A
Right
now,
the
docker
stuff
only
works
when
you're
running
on
the
same
physical
machine
that
the
admin
container
is
running
on
or
the
admin
node
is
running
on.
But
that's
mostly
because
I
wrote
it
as
it
is
so
that
I
can
do
stress
testing
on
the
core
bar
core
data
structures
in
the
database
in
the
future,
we'll
flush
it
out.
So
it's
more
full-fledged
about
being
able
to
spin
up
docker
nodes.
A
B
C
A
A
C
A
A
C
A
Anything
that
doesn't
need
direct
access
to
physical
devices
like
hdfs
yeah.
We
could
probably
spin
it
up
to
run
in
a
docker
node,
no
problem,
but
it
you
know
anything
that,
like
like
a
storage
node
or
a
like
a
a
center
storage
node
or
a
or
sf
sfosd
node.
All
of
those
have
to
effectively
run
on
physical
hardware
because
they
need
to
essentially
be
able
to
take
over
a
hard
drive
and
you
could
work
around
that
by
pre-formatting
file
systems
and
by
mounting
them
into
the
container.
A
C
C
C
A
You
give
us
the
freedom
to
experiment.
We
don't
have
that
yet,
and
I
don't
know
that
the
added
complexity
of
doing
that
for
a
data
release
will
be
worth
it
quite
honestly
sure
that's
one
of
the
things
that
I'm
not
going
to
add
until
I
have
until
there's
a
convincing.
You
know
business
driven
use
case
to
add.
C
C
A
Yeah
and
just
for
doing
smoke
test
workloads,
you
know
if
they
can
run
comfortably
in
a
docker
container
without
much
modification.
You
know,
there's
a
that's.
A
docker
is
a
pretty
good
way
to
do
that
sort
of
thing
like
if
we
could
spin
up
a
complete.
You
know
nova
cluster
inside
of
containers
without
without
having
to
modify
the
rest
without
having
to
modify
the
upstream
cookbooks
to
specialize
it
enough,
so
that
it's
not
really
an
accurate
test
anymore.
Yeah
it'll
be
great
for
that
sort
of
thing.
C
A
C
A
A
A
A
B
A
C
A
A
A
A
A
A
A
I'm
gonna
cut
off
going
amongst
your
neighbors,
who
are
in
similar
straits,
yeah
yeah.
No,
I
want
to
do
municipal
wi-fi,
but
I'm
afraid
of
isps,
because
the
the
incumbent
isps
really
have
a
stranglehold
and
if
you
there
have
been
recent
court
cases
where
municipalities
are
forbidden
from
competing
with
isps
even
if
the
isps
do
not
provide
service
in
that
area.