►
Description
Since version 3, OpenShift has been built around Kubernetes, the cluster manager released by Google. Red Hat have been one of the main contributors to the open source Kubernetes project since it’s release. Puppet recently released a module for managing Kubernetes resources (like Pods, Replication Controllers and Services) using Puppet. In this briefing, Gareth Rushgrove will give us an overview of using Puppet to manage and power up your OpenShift deployment.
OpenShift is Red Hat’s Platform-as-a-Service that allows developers to quickly develop, host, and scale applications in a cloud environment. OpenShift is also available in an open source distribution called OpenShift Origin. OpenShift provides an integrated set of tools for managing your container based applications, everything from deployment to container repositories to access control and built-in metrics and monitoring services.
For the latest information on OpenShift 3.2 and available briefings, please visit http://commons.openshift.org or subscribe to the OpenShift Blog (https://blog.openshift.com).
The OpenShift Commons exists to provide a platform for customers, partners, developers and other open source technology initiatives to collaborate, share and accelerate the pace of innovation and adoption of OpenShift globally.
The OpenShift Commons represents a new open collaborative community model designed to facilitate communication and sharing of best practices, feedback and development across the many open source initiatives that integrate with OpenShift. The best way to get involved is to join the conversation today at http://commons.openshift.org
A
A
Well,
hello
and
welcome
everybody
yet
again
to
another
open
ship.
Palmer
is
briefing
this
week.
We
have
gareth
rush,
go
from
puppet
with
us.
I'm
really
pleased
to
have
him
not
just
because
he's
a
puppet
expert,
but
because
he
really
wanted
one
of
the
wonderfully
opinionated
well
researched
persons
that
I
always
love
to
hear,
speak,
and
so
we're
really
lucky
to
have
him
here
and
especially
straight
off
dr.
Khan.
So
please
feel
free
to
pick
his
brain
in
the
QA.
A
If
your
we're
going
to
let
Garrett
through
his
presentation
first
do
a
couple
of
little
demos.
You
can
ask
questions
in
the
chat
and
then
we'll
leave
time
at
the
end
for
Q&A
and
we'll
open
it
up
for
a
conversation
there.
So
without
further
ado,
Gareth
I'm
going
to
let
you
get
started
and
we
will
learn
all
about
puppet
and
open
shift
and
how
to
use
it
with
the
new
Cooper
Nettie's
architecture.
B
B
Quick
introduction,
I'm
Gareth
forest
grove,
I'm,
one
of
the
senior
software
engineer,
Zack
of
it
and
I
mainly
work
on
a
building
out
of
it
and
doing
a
lot
of
integration
with
tools
like
over
chieftain
committees
and
I'm.
Gareth
are
pretty
much
everywhere
on
the
internet,
so
I
I'm
sort
of
assuming
people
are
familiar
with
a
bit.
I'm
not
going
to
go
into
a
lot
of
sort
of
the
details
and
but
come
it's
a
configuration
management
tool.
It's
a
dsl
based
language
with
a
whole
suite
of
tools
for
managing
all
sorts
of
infrastructure.
B
Committees
is
still
a
relatively
low
level
component
and
I'm
worth
things
I
found
out.
I
was
doing
that
education
was
how
easy
it
was
to
get
up
and
running
with
aperture,
so
that
ended
up
with
open
shift.
Being
me,
the
environment
I
was
using
to
demonstrate
and
to
sort
of
develop
against
Lolich
unit
for
the
puppet
integration.
So
it's
nice
to
like
then
come
from
full
circle
and
demonstrate
a
bunch
of
that
back
to
result.
B
B
It's
about
in
this
example
a
sort
of
trivial
pod,
but
it's
also
about
all
of
those
primitives
in
the
API,
the
replication
controllers,
services,
deployment,
managers,
etc,
and
but
those
are
familiar
with
committees
already.
What
you'll
notice
about
the
code
example
is
on
your
screen
is
that
it
follows
the
same
format
in
puppet.
B
Broadly
speaking,
data
format,
yeah,
mol
and
or
I
can
describe
it
in
the
format
that
I'm
showing
there's
not
really
much
value
there
and
I'd
agree
with
that,
and
really
the
advantage
comes
because
puppet
is
a
programming
language
and
yes,
it
can
be
treated
as
sort
of
quite
key
value,
Paris
esque
data,
but
only
you
can
create
your
own
abstractions.
So
those
are
familiar
with
puppet.
We
have
defined
types
and
classes
and-
and
you
can
build
those-
and
this
is
an
example
of
a
defined
type.
This
isn't
part
of
the
module.
B
This
is
just
something
I
put
together
and
add,
while
doing
some
work
around
the
committee's
guestbook
example.
So
one
of
the
things
you
find
with
the
sort
of
just
taking
a
purely
dated
but
eccentric
approach
to
convince
configuration
and
like
handwriting,
the
yomim
files,
which
is
really
the
wire
format
for
the
API.
You
end
up
with
a
lot
of
repetition,
because
it's
the
wire
format
for
the
API
and
but
we
pop
it.
You
can
actually
abstract
and
users
away
from
that
and
provide
high-level
interfaces.
B
So
one
of
the
things
that
I'm
often
seeing
is
that
you
often
end
up
with
a
pair
of
controller
and
a
service
and
often
like
they
go
hand
in
hand
and
the
API
should
treat
them
as
individual
things.
However,
the
user
interface
to
that
does
not
necessarily
need
to
do
so
and
in
public
you
can
just
create
your
own
user
interface,
build
your
own
abstractions,
just
using
the
built-in
standard
profit
tool,
and
so
that's
a
simple
example
and
I'll
and
I'll
show
at
some
examples
of
that.
B
It's
sort
of
declarative
nature
means
that
is
very
good
for
that
sort
of
like
high
level
like
change,
control,
managed
sort
of
Jane,
and
where
is
the
something
like
that
user,
modest
or
graphical
user
interface
in
the
air
committees
console
is
fantastic.
Southern
like
they're
like
skiing,
the
state
knowing
what's
going
on
at
any
given
moment
and
I'm,
also
going
to
add
a
quick
going.
This
example
turns
probably
relevant
folks
here.
I
recently
done
a
little
bit
of
work
around
using
public
with
atomic
lamb
and
with
atomic,
often
being
used
under
the
hood
of
object.
B
I
thought
that
would
be
hopefully
interesting
to
the
same
audience
as
well
and
and
all
of
that
scoured
by
a
seer,
Excel
and
I
open
source
images
that
we've
pushed
to
hook.
So
I'll
talk
about
that
a
little
bit
as
well.
So,
hopefully
that's
a
reason,
like
example,
and
it's
not
white
introduction,
roller
and
people
are
still
here
and
I'll,
hopefully
be
able
to
click
through
to
the
my
console,
interesting
demos,
yeah.
B
B
We've
just
got
granted
running,
there's
nothing
else
that
totally
fresh
buster,
I'm
I'm.
Also
I've
done
the
configuration
I
put.
The
the
puppy
module
simply
uses
the
standard
coupe
configs,
so
you
just
need
to
put
them
into
the
realm
of
place,
so
it
to
discover
them
and
then
everything
just
worked
and
again,
like
the
blog
posts
cover
setting
things
up.
B
B
Okay,
open
up
a
public,
comforting
file
and
so
k
web
died.
You
can
see
the
public
until
has
types
for,
and
they
see
all
the
the
primitives
and
communities.
So
we've
got
a
committee
and
scale
replication,
underscarf
controller
type
and,
and
here
we're
setting
up
master,
we're
providing
the
next
of
data
and
we're
probably
providing
respect.
And
again.
This
is
a
very
low
level
part.
So
you
can
see
here
there's
a
lot
of
duplication
in
the
same
way
as
the
Amal
file.
B
I'll
come
on
to
how
puppet
can
be
used
to
solve
that
repetition
problem
charlie,
but
this
is
demonstrations
to
the
Lord
most
level
parts.
So,
if
I
go
down,
obviously
a
service
you'll
see
another
replication
controller
for
sort
of
masters
and
slaves,
so
we're
saying
it
but
problem
bad,
the
master
and
slave
based
committees,
Fausto
and
so
far
that
this
will
follow
exactly
the
same
format
as
the
Amal
file.
If
we
had
a
ya
know,
file
that
describes
this,
we
could
actually
run
the
generate
command
and
that
would
give
us
the
public
code.
B
A
B
Is
that
the
public
module
simply
reads
the
topic
code
and
converts
that
into
the
relevant
API
calls
to
committees
on
top
of
local
shift
and
open
chip
does
the
rest.
So
if
we
flick
to
the
sort
of
outputs
you
can
see
it's
checking
if
a
few
things
existing,
it's
creating
the
things
that
armed.
So
it
creates
that
they're
into
seeing
that
a
couple
of
replication
controls
a
couple
of
services.
So
in
theory
we.
B
Should
be
able
to
see
them
now
open
running
in
object,
so
I'll
see
you
get
services,
we
can
see,
rallies
master,
ready,
slow
and
we
should
see
a
number
of
pods
starting
to
launch
are
already
running,
and
so
so
far
this
is
very
similar
to
how
you
might
use
coupe
CTL
and
do
exactly
the
same
sort
of
thing
with
Kip
CTL
apply.
But
when
things
I
can
do
here
is
use
puppets
I'd
important
nature.
So
we
can,
we
can
keep
running
the
same
commands.
B
A
B
B
They're
here
I'm
running
the
folder,
which
then
runs
up
into
the
files
in
there,
and
we
can
see
they're
actually
very
similar
output
to
the
previous
one.
It
created
that
it
created
two
services
to
replication
controllers,
so
we
should
be
able
to
see
those
then,
and
you
can
see
that
the
ones
that
are
perfect
kids
first
so
that
setup
took
that
size
of
two.
And
if
you
look
here,
we
have
a
single
master
and
two
slaves.
B
It
contains
everything
and
it
would
be
nice
to
sort
of
format
that
better
for
users
for
in
a
CLI
here
and
that's
the
thing
something
I'm
interested
in
doing
and
the
change
results
are
there
and
if
you
had
a
report
on
the
other
side,
you'd
have
something
past
that
our
anyway.
So
what
we
should
see
now
is
well.
We
updated
that
the
replication
controller,
the
replication
controller
then
said
well
I'm
running
two
replicas,
apparently
only
and
now
should
have
five
and
the
pods
have
all
launched
and
and
we
could
go
the
other
way.
B
So,
rather
than
something
having
to
know
all
of
the
implementation
details.
Now
we
know
what
already
sister
is:
we
can
create
lots
of
them.
We
have
we've,
we've
got
high
level
interface
just
by
using
pop
it
as
their
own
language
and
that
that's
the
real
key
to
solve
the
advantage
here
and
on
top
of
just
using
data.
So
you
can
see
here,
there's
now
a
second
master
starting
to
come
up
a
few
slaves,
and
you
could
imagine
changing
those
numbers
and
adding
more
and
like
doing
that
at
a
very
high
level.
B
Rather
than
and
we'll
look
at
the
implementation.
Here,
though,
under
the
hood
readies
cluster
is
simply
a
defined
type
in
puppet
and
it
takes
an
argument
of
the
size,
but
it
has
a
default
to
so.
You
won't
even
have
to
provide
a
size.
You
could
just
say
like
give
me
a
Redis
cluster,
and
it's
called
this
because
they
haven't
seen
of
it
for
has
full
typing
hints.
So
even
here,
I'm
saying
that
this
has
to
be
integer.
B
If
you
pass
a
string
or
an
array
of
it,
will
give
you
a
nice
error
but
again
like
we
can
create
these
high-level
interfaces
with
fully
typed
parameters
and
which
really
helps
sort
of
people
avoid
errors.
Yeah
we've
got
a
controller
service,
Pam
I
mentioned
this
is
another
abstraction,
so
we've
got
a
few
abstraction
is
going
on
here,
but
you
can
keep
digging
in
and
it's
only
at
the
bottom
layer.
B
It's
only
here
where
you
you
see,
like
that's
all
that
the
low-level
committees
types
being
used
and
I
mentioned
before
about
that
lot
of
the
communities.
Wire
format
is
quite
repetitive
and
but
ultimately
hope
it
doesn't
have
to
be,
because
we
have
the
ability
to
use
variables.
So,
yes,
we're
passing
and
the
labels
into
the
metadata
and
into
the
spec,
so
everything's
wired
up
correctly,
but
we're
not
having
like
if
I
want
to
change
the
value
of
a
poor.
B
The
value
of
role
well,
I
change
it
at
variable
level
and
that's
going
to
propagate
through,
like
in
the
number
of
places
used,
including
multiple
different
resources
in
the
committee
service
in
communities,
replication,
alert
role.
In
this
point,
I'm
using
my
flesh
controllers
and
services
as
good
high
level
examples,
but
the
modules
false
that
pretty
much
all
of
the
like
the
different
resources
and
committees,
as
I
mentioned,
because
actually
the
code
is
all
generated
from.
B
So
that's
really
something
a
good
introduction,
hopefully
to
the
committee's
module,
I,
say:
yeah,
you
could
create
a
comp
accepts,
you
could
create
the
rest
of
it.
We
could
go
on
and
make
actually
an
entire
set
up
and
other
high-level
types
that
are
specific
to
like
sort
of
our
business
problems
and
we
could
demonstrate
it
integrating
with
all
this
all
the
rest
of
the
proper
tools.
Bio
leave
a
bit
of
an
exercise,
but
people
who
are
interested
in
following
up
so
I.
B
One
of
the
advantages
of
doing
that
is
that
we
can
run
on
top
of
something
like
atomic,
where
the
unit
of
software
is
in
an
RPM.
The
unit
software
is
a
container
or
suddenly
week
by
shipping.
Those
we
have
pretty
good
atomic
spot.
I'll
just
demonstrate
that
really
quickly,
I'm
bad,
not
running
on
an
atomic
host,
but
I
have
bad
thinking
of
running
I,
have
a
virtual
machine
running
atomic
and
that,
hopefully,
should
be
up
and
running
the
the
code
for
this
is
actually
available
in
the
examples
repository
for
the
puppet
in
dhaka
project.
B
B
So
this
is
just
a
shortcut
to
running
things
over
s
sake,
so
how
weddings
is
that
the
container
mount
the
volumes
from
the
atomic
host
and
connects
to
the
host
network?
So
the
output
here
isn't
all
like
the
container
context.
It's
of
the
outlying
I'm
atomic
host.
Oh
so
they're
a
bunch
of
things
around
otherwise
developer
and
telling
us
we
can
see
things
from
the
host
not
from
here
we
are
at
the
new
OS.
You
can
see
what
it's
saying.
B
B
A
Great,
can
you
pop
over
to
that
github
repo
that
you
were
just
talking
about
and
just
throw
that
up
from
the
screen
so
that
we
end
on
that
and
that
and
people?
You
know
where
to
find
out
these
examples
as
pretty
mind-boggling
all
the
ways
that
you
can
schedule
stuff
on
Cooper
Nettie's
in
elgin
shift
and
then
why
might
then
and
I've
always
had
a
great
love
for
a
puppet,
so
I'm
looking
forward
to
getting
to
use
it
some
more
again
and
yeah.
A
All
right
well
opening
up
the
questions.
We've
got
a
couple
of
basic
yeah,
really
basic
ones,
which
I've
tried
to
answer
in
the
chat
about
KU,
benetti's
and
other
things,
and
no
there's
always
you
talking
to
open
shift.
Someone
always
brings
up
ansible,
but
there
are
so
many
tools
out
there
right
now.
The
different
enterprises
are
using
whether
they're
using
n
puppet.
We
really
just
want
to
make
sure
that
that
whatever
the
tool
of
choices
is
available
for
people
to
use
and
I
think
there's
puppet
is
one
of
them.
C
C
C
What
can
puppet
with
kuba
nedick's
to
make
this
as
painless
process
as
possible?
Because
I
my
concern
is
we
we
often
throw
up
sound
like
well
to
get
to
our
unfamiliar
technology.
You
have
to
learn
two
or
three
other
technologies
to
get
their
war,
so
these
guys
probably
don't
know
puppet.
They
a
cooper
nedick's,
they
don't
know
openshift
and
there's
just
sort
of
going
like
look
for
the
love
of
God.
We
just
want
to.
We
just
want
to
get
this
thing.
You
know
coordinated
with
with
one
of
our
other
products.
C
A
Think
a
good
question:
I,
don't
really
want
to
make
puppet
invisible
to
them.
I
think
what
it
is
is
that
a
lot
of
people
already
have
the
puppet
expertise
in-house
they're
already
using
it
to
do
their
see,
icd
workflows,
they're
already
using
it
the
script,
Oh
kinds
of
things,
because
it's
wonderful
and
what
we're
trying
to
do
is
keep
them
in
a
familiar
world
and
then
allow
them
to
use
the
tools
they
know
to
move
forward
into
a
cloud
native,
openshift
proven
Eddie's
universe.
Well,.
B
Like
others,
anything
indirect,
III
think
pub,
it's
probably
not
going
to
be
the
sort
of
the
de
facto
sort
of
default
entry
point
to
people
coming
in
light,
as
you
described,
and
but
actually
puppet
in
widespread
use
across
lots
of
organizations.
So
there's
a
lot
of
prior
art
around
the
puppet
language
and
what
we're
finding
is
that
cop.
It
has
a
universal
tool
in
particularly
in
organizations
where
they
have
that
sort
of
they're
running
a
bunch
of
X
stuff
that
running
a
lot
of
rail
stuff.
B
The
running,
maybe
even
sure
we
say
some
windows,
bits
and
pieces
and
they're
now
looking
towards
running
open
ship
and
okay,
other
Universal
tool
and
language
across
that
sort
of
diverse
infrastructure
is
the
sort
of
sweet
spot.
But
not
everyone
will
have
that
sort
of
diversity
and
the
result,
though
there
were
clothes
or
a
Solomonic
native
committees,
tools
and
native
of
chip
tools.
I
think
all
of
them
can
will
coexist
mainly
around
the
strength
of
the
committee's
API
yeah.
C
C
What
they
would
like
is
they
go
to
a
website.
They
upload
their
app
hit,
submit
and
magic.
It's
on
openshift
as
an
available
container.
You
know
kind
of
like
one
of
the
old
gears
where
other
people
can
use
it
now
and
it
can
be
used
in
spun
up
and
and
integrated
with
everything
else.
I
mean
that's
everybody's
ask,
is,
you
know,
make
make
me
an
easy
button?
Yes,
how
close
can
we
get
to
an
easy
button?
We're.
A
Pretty
close
to
that
easy
button
right
now.
Actually
that
was
the
image
that
that
big,
easy
button.
That
is
one
of
them.
There's
two
prongs
to
this
conversation:
one
is,
we
can
make
it
we
could
we
make
open
ship
the
easy
button
for
enterprise
coover
Nettie's
deployments,
so
if
you
want
to
deploy
open
shift
and
you're
in
a
customer
situation
or
an
end-user
somewhat
some
operations
house
and
they
want
to
deploy
crew,
benetti's
an
open
shift
and
with
a
real,
simple
set
of
scripts
and
sorry
they're,
all
ansible
Gareth
uh-huh,
that's
one.
C
A
Fat
then,
and
the
other
path
in,
if
that
Rob,
that
I'd
ask
you
to
take
a
look
at
now.
Is
the
open
shift
online
using
open
shift
three
using
the
new
version
of
open
shift
is
now
up
and
available
for
the
developer
preview
and
what
you're
describing
is
a
little
bit
based
on
your
memories
of
open
shift
to
with
our
cartridges
in
years
and
are
sort
of
the
marketplace
and
quick
starts,
and
all
of
that
so
that
you
could
really
get
in
quickly
and
you
reuse
and
save
the
QuickStart.
C
Right,
I
think
we
what
we're
departing
in
Middle,
where,
where
these
are
not
just
Java,
these
are
not
just
the
ear
and
war
locations
that
we
tradition
to
we're
recruiting
things
like
machine
learning,
companies,
big
data,
analytics
long
chain,
others,
often
it's
not
a
moral
reason,
I'm
interested
because
and
I
know
it's
it's
a
nothing
but
our
engine.
So
it's
not.
These
aren't
even
written
in
Java
frequently,
and
so
it's.
How
do
we
bridge
that
gap
as
a
result.
A
So
I'd
actually
asked
you
to
partners.
We
have
take,
take
a
look
at
the
the
new
online
experience
and
also
take
a
look
at
under
open
shift
to
zoom.
Would
further
yeah
I
will
and
a
link
and
take
a
look
at
the
source
to
image
set
of
tools
because
once
got
once
people
start
creating
their
images
and
they
push
them
to
private
registries,
which
are
often
hosted
on
openshift
as
well.
A
Then
that's
how
you
get
your
reusable
images
that
people
can
other
people
from
within
that
company
or
organization
that
have
access
to
that
registry
can
use
and
deploy
from
the
open
shift
console.
So
that's
I,
think
is
the
methodology
and
and
I
know
we've
gotten
off
track
Gareth
because
that's
always
doing
these
sessions.
But
when.
B
Nearly
back
to
my
talk,
a
doctor
come
around
just
and
the
sort
of
diversity
balls
are
like
barely
early
stage
of
a
lot
of
the
container
build
tools,
but,
as
we
were
talking
there,
I
was
like
the
next
6-12
months.
Is
gonna
seem
at
that
like
a
better
tooling,
like
improvements?
What's
there
and
probably.
C
C
Sorry
I
didn't
mean
to
get
you
all
your
now.
I
didn't
need
to
get
a
job
topic,
but
for
us
this
is
a
big
one,
because
we're
steering
this
way
me
for
anything
that
makes
their
life
easier
to
get
there
and
and
it's
you
know
so
that
we
don't
have
to
say.
Okay,
you
guys
are
absolute
experts
in
our
and
you
know
every
statistical
app
ever
ever
built,
but
we
need
you
know,
but
you
know:
here's
how
you
get
into
da
da
da
yeah,
also
at
the
kinetics.
A
But
there
is
with
source
to
image
you're
building
the
tooling
or
someone
is
building
the
tooling,
whether
it's
one
of
the
python
folks
and
the
evangelist
crew
or
one
of
the
engineers.
But
you
can
build
reusable
tooling
to
build
out
as
many
images
you
as
you
want
for
the
art
community,
for
example,
and
so
you
starting
to
get
the
base
line
tool
chain
for
build
services
and
continuous
integration
and
deployment
of
images.
A
You
centered
around
the
tools
like
sty
and
some
of
the
other
ones
that
Gareth
mentioned
it
is
dr.
convent.
So
the
high
level
tools
for
doing
all
this
and
pushing
them
to
private
registries,
which
you
can
then
expose
to
your
organs
organization,
wise
and
set
the
user
access
to
them.
So
there
is
a
whole
work
full
and
that's
probably
a
topic
for
yet
another
briefing
sometime
soon.
So
it's
a
good
question
and
I
think
the
documentation
is
probably
lacking
more
than
the
tooling
at
this
point,
so
you'll
have
to
work
on
that.
A
I
think
a
bit
more
good
question
a
couple
other
folks
on
the
call
on
the
briefing
right
now.
If
there's
any
other
questions,
you
can
toss
them
in
chat.
If
not,
this
is
about
the
normal
length
that
we
do
our
briefings
for
so
it's
pretty
good
in
great
content.
I
really
love
the
atomic
demo,
so
I
think
we're
going
to
have
to
push
a
little
bit
more
content
around
that
as
well,
so
I
think
that's
some
great
great
use
of
atomic
and
puppet
together.
A
So
thanks
Garrett,
I,
love,
cooking,
all
right
by
spotting
me
all
right
and
there
will
not
be
a
briefing
next
week
because
it's
red
hat
summit
week
so
we'll
be
giving
ourselves
a
break
and
which
is
not
really
a
break
but
and
then
coming
on
back
on
in
the
following
week.
So
thanks
again-
and
everyone
have
a
great
weekend-
hopefully
we'll
see
you
all
at
red.
That
summit.