►
Description
NOTE: This briefing is based on a beta version of OpenShift 3 - features and content are subject to change prior to release. For the latest information on OpenShift 3 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
Hello
and
welcome
to
this
openshift
Commons
briefing
today,
we're
really
pleased
to
have
with
us
dannon
hansen,
from
cisco
to
talk
about
openshift
on
OpenStack
and
some
of
the
work
that
he's
been
doing
as
a
contributor
to
open
shift
in
the
area
of
HD
deployment
and
puppets
scripting,
as
well
as
to
give
you
some
of
his
experience
about
deploying
openshift
on
OpenStack
at
Cisco,
where
he
is
gainfully
employed
and
I've
had
the
great
pleasure
of
working
with
danyon
and
giving
presentations
at
OpenStack
summits
to
other
groups
within
an
Cisco.
And
it's
a
wonderful
speaker.
A
What
we're
going
to
do
is
let
him
give
a
little
bit
of
his
presentation.
So
you
get
a
taste
of
what's
going
on
there.
You
can
talk
through
that
and
then
we'll
do
a
little
bit
of
QA
and
open
it
up
for
discussion
and
somewhere
around
halfway
through
this
call
ken
Owens
who's,
the
CTO
of
disco
cloud
services
is
going
to
be
joining
us
and
he
can
tell
us
a
little
bit
more
about
the
roadmap
ahead
for
cisco
and
how
they're
seeing
the
use
of
open
shift
at
Cisco
and
how
it
plays
out
there.
B
So
I
put
together
a
few
slides
to
help
kind
of
guide
the
conversation.
But
this
is
a
very
much
an
open
dialogue.
So
please
jump
in
ask
any
questions
and
let's
make
this
interactive,
and
so
for
folks,
unfamiliar
with
with
OpenStack
or
specifically
heat.
You
know
heat
is
its
kind
of
that
integration
point
between
OpenStack
and
an
open
shift,
and
so
now,
if
you
want
to
deploy
a
open
shift
in
an
OpenStack
environment,
there's
definitely
different
ways
of
skinning
that
cat.
B
The
way
that
that
that
I
thought
was
best
a
year
ago,
where
I
put
my
efforts
around
was
by
using
this
orchestration
service,
AKA
heat
with
an
OpenStack,
and
what
that
allowed
us
to
do
is
to
provide
a
very
simple
format
for
users
to
deploy
a
multi-node
openshift
environment
very
easily,
not
having
to
go
in
and
monkey
around
with
different
settings
for
your
different
node
types,
it'll
look.
It
provides
a
very
simple
interface.
You
know
you
basically
supply
parameters
to
to
the
heat,
template
and
within
a
single
command.
You've
got
you
know
the
orchestration
service.
B
That
goes
and
does
all
the
hard
work
for
you,
and
so,
in
addition
to
the
presentation,
I
also
pulled
up
a
demonstration
that
I
put
together
probably
about
six
months
ago,
so
it
is
a
little
dated,
but
it
still
provides
the
concepts
that
are
important
to
this
discussion
and
again
just
quick
overview
of
what
he
does.
It's
a
service
within
within
OpenStack,
you
call
it
a
service
or
a
project
with
an
OpenStack,
and
it
is
the
orchestration
service.
B
And
here's
just
a
the
interface
to
go
ahead
and
and
access
the
heat
templates
that
were
created
and
if
you
want
to,
if
you
look
at
my
browser
here,
you
could
actually
just
follow
along.
This
is
a
reveal
presentation
that
I'm
using
so
you
go
to
date.
Dane
Hans
github
io
poured
/
v3
underscore
presentation
within
your
browser.
B
You
could
actually
move
along
at
your
own
pace
if
you'd
like,
but
the
the
heat
templates
are
hosted
on
on
github
within
the
OpenStack
repo,
and
you
know
the
the
heat
templates
repo
it
has
all
sorts
of
different
type
of
of
heat
templates,
and
so,
whenever
I'm
actually
wanting
to
create
a
new
orchestration
workflow
for
an
application,
I'll,
usually
always
start
here
to
see
what
templates
are
available
to
tube8.
You
know
to
start
my
warp
from
to
to
leverage
this.
The
work
that's
already
been
out
there
as
a
baseline
instead
of
starting
from
scratch.
A
B
And
I'll
drive
into
the
heat
templates
in
some
more
details
too,
so
ever
could
t.t
what's
going
on
there,
but
also.
I
also
added
the
this
page
here
where
you
go
to
github.com
and
actually,
instead
of
the
OpenStack
eat,
templates
repo,
you
go
to
the
open
shift,
origin,
repo
or
maybe
even
start
off
at
just
the
open
shift
repo,
and
you
can
see
all
the
different
projects
within
the
open
shift,
repo
that
you
can
contribute
to
again.
B
Does
any
if
I
want
to
kind
of
throw
it
out
there
any
questions?
Otherwise,
I
was
going
to
again
jump
into
a
quick
demonstration,
so
you
could
actually
see
what
I'm
talking
about
as
well
as
I
was
going
to
dive
into
one
of
the
one
of
the
heat
templates.
So
you
just
have
a
better
understanding
of
of
the
template
itself.
B
You
bet,
okay
and
the
demo
moves
really
crack
a
quick,
so
I.
I
may
pause
it
here
in
there,
but
this
is
just
really
quickly
heat
temple.
How
simple
it
is!
Let
me
go
back
here.
Really
quick:
we've
got,
you
know,
heat
template
that
that
a
user
applies.
The
parameters
to
you
know
that
basically
tells
heat
to
go
and
talk
to
all
the
necessary
OpenStack
services
to
realize
the
multi-node
openshift
deployment.
B
Then
I
added
this
year,
just
to
emphasize
you
know,
there's
a
lot
of
different
ways
to
interact
with
openshift
if
you're
familiar
with
that,
you
know
command-line
tools,
IDEs
or
through
the
web
interface
of
this.
This
demonstration,
by
the
end,
will
actually
log
into
the
web
interface
and
show
that
particular
example
how
you
interact
with
with
open
ship.
But
you
know
it
really
comes
down
to
whatever
the
developer
prefers.
B
Openshift
provides
different
ways
to
interact
with
it.
So
what
you're
seeing
here
is
you
know,
I'm
I'm
an
OpenStack
user
I've
have
an
account,
the
OpenStack
environment
that
that
I'm
using
supports
heat,
and
so
when
I
interact
with
heat,
I
use
the
heat
commands
in
this
particular
scenario,
I'm
doing
a
stack,
create
calling
it
Oso
dash
tach
for
openshift
origin
and
then
I
I
specified
a
template
file
right,
and
so
this
template
file
is
something
that
that
I
would
download
and
it's
a
template
file
from
the
heat
templates,
repo.
B
And
so
I
tell
where
the
template
exists,
and
here
are
all
the
parameters
that
I'm
going
to
pass
in
to
customize
this
particular
deployment
things
like
you
know
what
ssh
key
pair
am
I
going
to
use
what
dns
prefix
do
I
want
to
use
within
my
open
shift
environments?
What's
the
IP
address
or
dns
names
of
my
IP
addresses
of
my
dns
servers,
where's,
my
ntp
server,
all
sorts
of
stuff
and
again
we'll
dive
into
the
parameters
in
more
detail,
but
pretty
simple,
you
say:
hey
keep
create
this.
This
stack
and
here's
a
template
file.
B
And
heat
arts
to
create
the
stack
and
as
part
of
that
creation
process,
the
template
file
consists
of
a
bunch
of
resources.
That's
really
what
a
core
concept
within
within
heat,
and
so
this
particular
template
has
gosh
like
close
to
eight
different
resources
and
it'll,
go
through
resource
by
resource
and
and
lets.
You
know
if
that
resource
completed
properly
or
if
there
is
any
issues
or
if
it's
in
the
process
of
of
completing
that
resource.
You
see
that
right.
B
Now
it's
going
through
that
process
and
then
a
few
minutes
later
I
do
another
heat
resource
list.
For
my
particular
stack
name,
Oso
stack
and
you
see
that
remove
this
arrow.
You
see
that
all
the
different
resources
created
successfully,
and
so,
if
I
do
another
heat
DAC
list
you'll
see
my
Oso
stack
has
completed
correctly.
B
B
The
stacks
now
created
what
you
would
typically
do,
then
is
do
a
heat
stack,
show,
Oso
stack
or
a
nova
list,
and
you
would
see
the
instance
details
or
the
virtual
machine
details
that
make
up
my
open,
shipbroker,
my
openshift
nodes
and
and
then
I
would
capture
that
IP
address
of
the
open,
shipbroker
and
use
that
to
log
into
this
web
interface
that
you
see
right
here.
You
know
it's
part
of
as
part
of
that
deployment.
We
also
set
up.
B
You
know
a
username
and
password
for
the
administrators,
so
that
so
that
now
I
have
the
IP
address
of
my
broker
and
I
have
the
username
and
password
to
be
able
to
login
and
again.
This
example
shows
the
web
interface.
I
could
have
very.
We
use
my
client
tools
and
interacted
with
the
broker
from
the
command
line
or
from
an
IDE
as
well,
so
now
logged
into
the
broker
and
I'm
setting
up
my
my
name
space
I'm,
adding
my
public
keys
to
some
of
the
basic
fundamental
things.
B
We
need
to
do
to
start
interacting
with
a
broker
and
creating
the
applications.
This
example
I'm
going
to
use
a
cake,
PHP
application
and
that
source
code
is
actually
sitting
on
github.
So
all
I
have
to
do
is
say:
a
open
ship.
The
code
sits
here
at
there's,
a
github
URL
go
ahead
and
create
the
application.
B
As
long
as
again,
it
needs
to
run
heat
which
most
open
openstack
cloud
providers,
support
heat,
I'm,
just
pulling
down
the
heat,
template
and
I'm
passing
in
the
the
the
parameters
for
the
template,
so
that
I
could
customize
the
my
deployment
as
needed,
and
then
he
does
all
the
hard
work
for
you
log
in
to
the
broker
and
set
up
some.
Your
basic
information
like
the
name
space,
the
ssh
key
you're,
going
to
use
and
then
start
deploying
applications.
So.
B
And
then
a
little
piece
of
this
is
just
to
kind
of
go
through
the
different
cartridges.
Right
I
mean
this
is
the
power
of
open
shift?
Is
we
don't
have
to
build
common
applications
from
from
scratch
all
right?
So
if
it's
a
heat,
you
know
the
heat
templates.
We
don't
have
to
build
it
from
scratch,
their
stuff
out.
There
already
use
it.
If
you
need
to
add
to
it,
then
then
add
to
it
same
with
the
cartridges.
You
know,
if
there's,
if
there's
a
cartridge
out
there,
that
you
need
to
add
to
it.
B
B
You
know,
I
haven't
looked
at
the
heat
templates
in
a
little
while,
because
I've
been
working
on
other
projects,
but
you
know
put
a
big
smile
on
my
face
because
I
came
back,
I
was
like
wow.
This
has
changed
quite
a
bit
over
the
last
few
months
because
Antoine
a
has
come
back
here
and
said:
oh,
you
know,
let's
add
to
the
heat
template
right.
So
under
the
under
the
openstack
heat
templates,
I
went
to
the
path
of
openshift
origin.
B
We
could
either
go
fedora
or
sent
oz
and
then
there's
different
types
of
templates
from
hot,
which
is
a
heat,
orchestration,
template
format.
That's
the
native
format,
there's
also
an
AWS
template
format
and
then
there's
different
there's
quite
a
few
different
heat
templates
out
there
for
four
open
shifts
under
fedora
and.
A
B
B
B
They
are
oh
yeah,
it
looks
like
we
have
two
different
repos.
If
you
know,
if
you
want
to
work
on
the
origin
templates,
there
hosted
out
of
the
OpenStack
github
repo
and
if
you
want
to
use
the
enterprise
templates
they're
out
of
the
open
shift
repo,
and
so
these
openshift
enterprise
templates.
The
last
that
I
saw
they
did
have
a
che
options
here
and.
A
So
I
believe
that's
where
the
h
a
is
and
I
think
right,
you
and
you
can
fork
them
and
bring
them
into
your
own
free
throws
and
and
tweak
them
out
as
as
you
see
fit.
But
this
is
a
really
good
starting
place
if
you're
trying
to
learn
heat
too.
It's
part
of
part
of
the
reason
I
got
into
making
sure
that
we
had
good
heat
ten
places,
because
I
wanted
to
learn
that
the
heat
templating
syntax.
So
this
is
now,
if
you,
if
you're
interested
in
heat,
this
is
a
great
way.
B
And
what
I
did
now
is
I
jumped
to
the
puppet
openshift
origin
repo,
and
this
is
where
I
did
quite
a
bit
of
work
and
as
Diane
mentioned
it
did.
The
original
work
for
high
availability
and
I
bring
this
up,
because
what
the
heat
templates
actually
do.
Is
they
leverage
these
puppet
modules
and
we'll
kind
of
go
through
it
in
a
little
more
detail?
And
so
the
nice
thing
about
that
is
that
if
you're
in
an
OpenStack
environment,
you
want
to
use
heat
to
orchestrate
this
complex
deployment,
you
can
also
say
well.
B
I
just
want
to
leverage
these
puppet
modules
to
automate
the
deployment
of
my
multi-node
high-availability
openshift
environment.
So
you
really
have
both
options
now
granted
with
heat
I
showed
you
a
single
command
right,
yeah
I
mean
you're,
pulling
down
the
templates
or
you're
pointing
to
where
the
template
is
and
you're
just
specifying
some
parameters
to
customize
that
orchestrated
deployment
with
puppet
a
little
more
to
it,
not
a
whole
lot.
B
But
again
you,
you
know
it
gives
you
that
power
of
saying,
hey,
I
want
to
deploy
har,
not
a
che.
Here's
the
number
of
nodes
that
I
want.
Here's
a
lot
of
ways
that
you
can
customize
a
high-availability
deployment,
because
when
the
high
availability
to
plan
was
developed
right,
we're
looking
at
each
of
those
services
that
make
up
the
system
and
making
sure
that
they
can
withstand
failure
and
so
forth,
and
so
there's
a
lot
of
different
tuning
that
you
could
do
to
that.
B
But
if
you
don't
want
to
tune
it,
then
you
could
just
leverage
the
default
options
of
either
h-hey
or
not
a
che.
And
so
that's
why
I
bring
up
this
and
and
if
you
can
even
I,
believe
the
latest
openshift
guides
kind
of
walk
you
through
the
h.a
options
as
well
as
when
I
go
back,
I
want
to
say
six.
Eight
months
ago
I
went
ahead
and
put
together
an
H,
a
guide
under
the
cisco
documentation
on
how
to
deploy
both
options.
A
So
Ninian
we've
got
the
one
question
here
them
just
going
to
ask
for
it.
What
joseph
collins
asking
he
says,
I
understand
that
we
might.
This
might
be
difficult
to
answer
the
question
please
v3
is
still
in
development,
but
from
your
perspective,
do
you
see
more
of
a
nova
integration
with
dr.
using
atomic
instead
of
putting
open
shift
into
a
vm
instance,
and
I
think
it
might
be
a
good
time
to
bring
up
coo
benetti's
and
what
we're
doing
very
little.
B
B
So
there's
a
lot
going
on
within
you
know:
within
docker
and
COO
Burnett
days
and
I'm,
actually
part
of
a
project
called
kala.
That's
container,
rising
OpenStack
services
using
docker
and
COO
Burnett
days.
There's
a
new
project
within
OpenStack
that
started
called
Magnum
witches
containers
as
a
service
right
now.
B
I
would
see
that
it
would
be
a
similar
workflow
where
we
would
go
ahead
and
and
say,
let's
deploy
no
but
instances
that
make
up
our
openshift
environment,
but
that
could
change
here
in
three
months
or
six
months
with
some
of
these,
these
new
projects
and
specifically
magnum.
So
if
you
haven't
looked
at
magnum,
I
would
highly
encourage
you
to
to
go
launch
pad
calm,
/
magnum.
Take
a
look
at
the
project.
B
It's
hosted
at
a
staff
chord,
so
you
go
to
github.com
/
stack,
forge
you
could
search
/
magnum
there
and
you'll,
see
it
as
well
and
there's
just
a
flurry
amount
of
development.
That's
going
on
there
o
/
depot
who's.
One
of
my
peers
is
focused
on
Magnum
again,
I'm
focused
on
kala,
and
so
you
know
it's
tough,
to
tell
I
mean
if
you're,
if
you're
going
to
go
ahead
and
deploy
v3
today,
then
you
again,
I
would
say,
be
pretty
similar.
B
It's
it's
out
of
tree,
and
so
it's
also
hosted
in
stacked
forge,
and
so
you
could
potentially
deployed
as
containers
I
think
if
you
were
going
to
go
down
that
road
I
would
probably
you
know
lean
more
towards
in
Magnum,
which
is
going
to
be
a
container
as
a
service
service
and
and
then
leverage
the
containers
that
make
up
the
the
v3
deployment
and
deploy
those
specific
components
as
containers.
So
you
know
it's,
so
it's
just
hard
to
tell,
because
we've
got
the
three
that's
just
kind
of
still
on
the
cutting
edge.
B
You've
got
these
different
projects
that
I
referenced
with
an
OpenStack
there
on
the
cutting
edge,
and
so
it
really
kind
of
depends
on
how
those
projects
develop.
Along
with
you
know
what
your
requirements
are.
I
mean
if
you're
saying,
hey
I
need
something:
that's
solid
and
reliable.
Today,
then,
you
know,
I'd
say,
use
the
tried
and
true
and
use
a
standard,
livered
no
Barack,
novo
driver
and
deploy
as
virtual
machines.
A
You
testing
it
out
and
giving
us
your
feedback
and
contributing
to
the
the
origin.
V3
efforts.
So
both
both
camps
are
good
things
to
test
out.
As
I
said
they,
the
heat
templates
are
really
good
if
you're,
starting
from
laurennn
feet,
they're
very
clear
and
well
documented,
if
you're
looking
to
get
deeper
into
KU
benetti's
and
some
of
the
other
things
playing
the
v3
and
testing.
That
out
is
also
an
awesome
thing
to
do.
A
B
As
Diane
mentioning,
I
worked
with
pretty
closely
with
some
of
the
lead
developers
for
v3
of
last
month
or
so
in
preparation
for
the
paris
design,
some
at
the
OpenStack
Paris,
designed
some
and
and
so
yeah.
You
know
the
the
developers
that
know
that
are
working
on
v3
I
mean
they're.
Looking
for
feedback
like
a
feedback
that
I
gave
them,
you
know
so
they're
looking
for
the
community
to
you,
know
to
test
out
the
different
kind
of
deployment
scenarios
and
so
forth.
B
B
B
So
let's
just
take
a
look
at
origin,
so
I'm
at
the
open,
sakky
templates
go
to
the
open
shift
origin,
let's
go
to
fedora
19
and
we
have
different
template
types:
let's
go
to
the
hot
template
again
hot
as
the
heat
orchestration
template
format,
that's
native
to
that's
native
the
heat,
and
then
we've
got
different
types
of
templates.
These
are
for
scaling
scaling
your
your
your
orchestrated
heat
environment,
based
on
different
triggers,
or
we
could
just
look
at
a
simple
openshift
template.
It's
Annie,
Hamill
format.
B
So
again
you
would
most
likely
just
clone
the
heat,
template
repo
and
then
within
the
command
line.
The
heat
command
or
you
can
even
do
it
from
from
Horizon
specify
the
path
to
this
to
this
template
and
then
the
other
big
part
of
of
telling
heat.
What
to
do
is
supplying
the
parameters
and
hear
all
the
parameters.
You
see
that
the
parameter
gives
you
a
parameter,
name,
description,
type
and
default.
B
So
you
go
through
here
and
say
you
know,
I,
like
all
the
defaults
or
most
of
the
defaults
and
makes
it
even
easier
on
you,
but
more
than
likely
you're
going
to
want
to
come
in
here
and
and
and
modify
some
of
these
parameters
to
your
deployment
needs.
You'll,
see
that
tons
of
parameters
here
and
you
know
don't
get
overwhelmed
by
the
number
of
parameters.
Because
again
most
of
these,
you
won't
even
need
to
touch.
B
But
just
so
you
know
understand
that
concept
of
the
parameters,
that's
what
we
pass
into
into
heat
and
then
I
talked
to
and
showed
you
the
resources
when
I
did
that
heat
resource
list-
and
we
saw
the
eight
or
ten
different
resources
now
he
basically
chunks
through
this
stuff
and
we're
telling
hey
he'd,
hear
the
resources
that
we
want
you
to
orchestrate.
The
first
one
is
the
type
of
OS
Neutron
security
group.
B
Let's
see
what
else
you
know
now
we're
telling
heat
hey,
create
a
key
pair
now
start
setting
up
the
neutron
network.
For
me,
heat
create
the
ports,
the
subnets,
the
router,
all
the
the
networking
functionality
that
we
need
to
provide
networking
connectivity
to
my
openshift
nodes
and
broker
and
so
forth,
and
then
here's
a
piece
of
this
particular
resource,
which
is
the
OS
heat
software
config.
And
what
we're
doing
is
you
see?
B
We've
got
a
template
here,
and
it's
really
all
it
is,
is
a
bash
script
where
we're
saying
hey,
go
ahead
and
run
puppet
and
here's
all
the
different
puppet
parameters
that
the
bash
script
uses
and
here's
a
puppet
module.
We
want
you
to
use
here's
all
the
different
puppet
modules
to
install
and
that's
where
I
go
back
and
say:
hey
yeah,
you
really
can
you
know
automate
your
deployment
in
different
ways
that
you
would
like
you
know
you
don't
have
to
use
heat
and
heat.
B
B
B
Now
that
the
brokers
up
and
functioning,
let's
start
standing
up
nodes
and
then
there's
basically
a
you
know,
an
output
so
that
when
we
do
when,
when
the
heat
stack
is
created,
we
then
do
a
heat,
show
stack,
oso
stack
and
we
actually
get
some
feedback.
So
we
know
again,
you
know,
what's
what's
the
floating
IP
assigned
to
the
instances
and
now
I
could
actually
bring
up
a
browser
and
log
into
my
broker.
B
If
I'd
like
to
soham,
it's
it's
just
kind
of
a
quick
rundown
of
the
heat
template
and
so
we're
taking
now
we're
taking
an
open
shift
environment
that
normally
you
would
deploy
manually
and
simply
just
again
providing
some
parameters
to
customize
the
deployment
and
letting
heat
to
all
the
work
for
us
so
that
we
don't
have
to
go
in
and
tell
Nova.
You
know
start
up
this
number
of
instances
telling
Nova
to
create
these
key
pairs
or
telling
you
trying
to
create
all
these
network
parameters.
A
B
A
B
Don't
have
a
diagram
in
front
of
me,
but
let
me
go
back
to
the
video
here
and
I.
Don't
think
I
did
a
nova
list.
I
look
in
my
Inn
in
this
example
and
the
sheet
template
here
there's
some
time.
This
one
is
basically
kind
of
like
a
kickstart
environment.
It's
going
to
stand
up
a
single
broker,
a
single
node,
and
then,
from
that
point
forward
you
could
do
one
of
two
things
or
one
of
multiple
things.
You
could
add
nodes
to
the
environment
manually.
B
B
Now
we
have
a
separate
key
template
just
for
adding
a
node
all
right,
so
instead
again
creating
the
broker
to
know
this
template
here
really
is
kind
of
how
do
you
kind
of
kickstart,
your
open
shift
environment
from
that
point
forward
manually,
add
nodes,
use
a
puppet
module
to
to
automate,
adding
nodes
or
go
back
here
and
say.
Let
me
just
modify
or
copy
this
template
over
and
modify
it
to
create
a
very
simple
template
focused
on
just
adding
an
ode
to
the
environment.
B
B
You'd
have
a
neutron
network
could
be
the
10
dot
network
that
are
the
broker
and
the
node
and
any
additional
nodes
attached
to
and
then,
as
you
saw,
we're
setting
up
up
floating
IP
as
well,
and
so
we
would
then
go
ahead
and
map
that
private
Neutron
network,
which
consists
of
you,
know
the
neutron
router
and
then
the
neutron
virtual
ports
that
the
broker
and
the
nodes
attached
to
you
know
with
a
with
the
floating
IP.
We
would
then
say:
hey
Neutron
router
go
ahead
and
NAT.
A
So,
as
the
gentleman
on
chat
pointed
out
horizon
hat,
it
does
have
a
the
ability
to
show,
though,
that
visually,
but
this
is
actually
a
movie
that
we
made
a
few
months
back
so
I'm
pretty
sure
this
doesn't
exist
in
in
physical
form,
anymore
marbles.
Now
asking
is
now
saying
that
they
have
a
project
to
make
a
heap
appointment
or
on
cloud
wat.
A
French
Foreign
cloud
based
on
the
OpenStack
promise,
so
they're
going
to
be
doing
this
soon.
So
hopefully
we
can
get
your
feedback
on
that
and
learn
some
more
from
them.
A
You
guys
would
love
to
have
you
on
and
on
showing
off
what
we're
doing
that
that
would
be
great
fun.
They're.
Probably
what
I'm
interested
in
doing
out
of
this
session
is
setting
up
a
mailing
list.
The
people
who
are
in
particular
interested
in
learning
more
about
openshift
on
OpenStack
and
so
I
will
set
that
up
and
send
you
guys
who
are
participating
today
and
others
that
the
sign
up
for
that
mailing
list,
where
you
can
share
some
of
your
insights
here.
A
They,
as
we
have
talked
about
a
little
bit
ly,
3,
is
moving
in
the
directions
that
are
sort
of
a
little
bit
more
kuber,
Nettie's
and
maybe
Nova
driven
and
so,
but
that
is
still
a
little
ways
out.
So
the
openshift
enterprise
and
the
open
shake
origin
heap
templates
again
really
are
your
best
bet
for
testing
and
deploying
on
unopened
ship
on
OpenStack
these
days,
so
I
was
hoping
we
would
have
ken
Owens
join
us.
A
It
looks
like
he's
not
going
to
make
the
call
today
to
give
us
a
little
bit
of
insight
into
Cisco's
roadmap.
You
just
do
up
a
few
minutes
back.
I
think
that
what
we've
what
we've
covered
today
is
quite
a
bit
in
terms
of
heat
and
puppet
and
the
work
that
Damian
has
done
on
openshift
and
contributing
back
to
open
shift.
It's
been
an
amazing
year,
really
getting
the
contributions
and
getting
Cisco
on
board.
A
Cisco's
done
a
lot
of
work,
not
just
an
open
shift,
but
on
OpenStack
as
well
and
contributing
to
koala
and
magnum,
and
a
number
of
the
Google
open
source
project.
So
really
look
forward
to
working
more
with
everybody
on
the
cisco
team
and
thank
you
very
much
for
for
having
taking
the
time
today,
adidas
really
a
big.
A
Thank
you,
the
banyan
for
all
of
his
efforts
and
enter
Ken
and
Keith
than
all
of
the
other
folks
at
Cisco
that
are
working
long,
making
openshift
part
of
the
cisco
cloud
we're
looking
forward
to
learning
a
lot
more
from
you
all,
and
if
there's
no
other
questions
you
might
let
binion
get
back
to
the
riveting
on
to
all
those
wonderful
open
source
projects.
So
thank
you
very
much
Danny.
You
have
anything
else
that
you
want
to
say.
B
A
Absolutely
and
I
think
the
interesting
thing
from
from
our
perspectives
is
is
how
much
cross
community
collaboration.
It
really
is
between
the
OpenStack
and
open
shift
and
COO
benetti's
and
puppet
communities,
and
so
this
makes
for
some
really
interesting
dialogue
between
all
the
projects
and
within
the
different
customers
and
contributors.
So
it's
been
it's
very
interesting.
We
hope
to
bring
more
of
these
conversations
here
to
the
commons
briefings
and
there
will
be
another
one
next
week
on
Java
workflows
that
aren
Gupta
is
putting
together
for
us.
So
if
you
around,
please
join
us
for
that.