►
From YouTube: OpenShift Commons Briefing #47: OpenShift on OpenStack
Description
Judd Maltin of Dell has been working closely with Red Hatters’ Jan Provaznik and Sylvain Baubeau on making sure that OpenShift deploys and runs seamlessly on OpenStack and integrates with Keystone, Cinder, Heat, Neutron’s LBaaS and other OpenStack resource natively.
In this session, Judd will walk us thru a deployment on Dell’s reference architecture with 192 cores and whole lot of RAM, Ceph and/or Compellant and/or Equallogix storage backends.
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
Hello
and
and
welcome
everybody
to
yet
another
OpenShift
Commons
briefing
and
this
time
I'm
really
pleased
to
have
this
reference
architecture
being
talked
about.
I've
talked
about
it.
A
lot
coming
from
Dell
of
running
openshift
on
OpenStack
and
Dell
Mountain
who's
been
a
longtime
OpenShift
fan
and
a
good
friend
of
the
OpenStack
community
and
worked
on
lots
of
stuff
with
us
from
heat
templates
to
unbelievably
think
strange
things
and
made
them
all.
A
Work
for
us
and
Judds
been
doing
a
lot
of
work,
making
sure
that
OpenShift
runs
on
OpenStack
and
on
the
Dell
release,
so
I'm
gonna,
let
Judd
introduce
himself
he's
gonna
talk
for
20,
30
minutes
demo,
some
stuff,
you
can
ask
questions
in
the
chat
and
we
will
try
and
answer
them
through
via
chat.
But
after
he's
done,
we're
gonna
have
a
QA
and
do
more
chat
questions,
but
also
but
the
microphone.
So
we
can
have
a
conversation
as
well.
So
without
further
ado,
I'm
gonna,
let
Judd
introduce
himself
hi.
B
B
We
have
an
Enterprise
Services
Group,
aren't
about
I'm,
sorry
Enterprise
Systems
Group,
the
head
of
our
Enterprise
Systems
Group,
spoke
at
red
hat
summit
and
touted
this
particular
solution.
On
top
of
red
hats,
OSP
OpenStack
platform
we've
been
collaborating
with
Red
Hat
on
the
OpenStack
platform
for
three
years
now,
and
what
we
do
is
we
we
build
up
a
hardware
reference
architecture.
B
We
deploy
OSP
on
it
in
all
of
its
beta
releases,
communicate
very
closely
on
a
daily
basis,
with
Red
Hat,
sending
bugs
upstream
or
committing
directly
to
OpenStack
to
get
things
fixed
up,
so
it
were
runs
great
on
our
hard.
It
makes
it
super
easy
for
our
customers
to
order
up
a
small,
medium
or
large
size,
OpenStack
cluster,
and
what
I've
been
tasked
to
do.
I
am
the
lone
resource
who
is
doing
Paz
and
containers
on
our
particular
version,
our
particular
release
of
OSP.
We
are
actually
not
distributing
the
software.
B
Software
all
comes
from
Red
Hat.
We
are
just
distributing
the
the
documentation
and
a
little
bit
of
the
open
source
code
for
some
of
the
automation
we've
done
to
make
it
really
easy
to
just
get
the
Dell
gear
up
and
running
and
OpenStack
deployed
in
my
job
to
automate
the
deployment
automate
tests
and
deliver
the
deployment
of
OpenShift
and
cloud
forms
to
make
even
OpenShift
more
valuable
on
on
this
OpenStack
platform.
B
So
a
little
bit
about
me,
I,
started
a
long
time
ago
as
assisting
and
a
perl
developer
did
a
lot
of
work
in
web
dev
and
administration
in
midsize.
Msps
I
did
video
delivery.
I
did
the
first
online
shopping,
cart
in
the
Middle
East,
when
I
was
living
in
Israel,
doing
graduate
work
and
as
an
SI
and
Perl
developer
back
in
2007
did
a
really
interesting
virtual
world
deployment
on
open
on
sorry
on
Second
Life
and
automated
by
hand
200
ec2
instances
or
for
a
television
tie-in
future
that
we
did
that
lasted
for
a
night.
B
Up
until
today,
where
now
I'm
focused
on
cloud
and
containers
and
paths
and
automating
that
infrastructure
I
came
to
Dell
to
work
on
the
crowbar
project
which
has
since
on
out
of
Dell
and
they're,
based
their
own
business
on
it
and
have
renamed
it
digital
rebar.
So
let's
talk
about
OpenShift,
no
we're
talking
about
all
this
past.
B
B
We
produce
three
technical
guides
or
OpenShift
on
OpenStack,
one
focused
only
on
OpenShift,
the
the
second,
a
cloud
forms
deployment
guide
and
the
third
guide
would
be
is
to
integrate
OpenShift
and
cloud
forms
together
to
get
a
really
robust
experience.
And
then,
finally,
the
I'll
talk
briefly
about
how
we're
using
how
we're
integrating
Howard,
deploying
and
integrating
cloud
forms
with
with
openshift
and
and
finish
up
with
a
little
walkthrough
of
what
I've
deployed
and
documented
for
managing
the
whole
stack
from
the
metal
to
the
containers
in
in
cloud
forms.
B
So
back
to
our
initial
question,
why
run
openshift
on
OpenStack
first
thing
most
places
have
some
sort
of
OpenStack
investment
and
they've
gone
through
the
radical
transformation
of
from
from
brick
and
mortar
to
cloud.
Basically,
whether
it's
an
on-premise
cloud
or
they're
buying
their
OpenStack
from
somebody
as
a
service,
they
have
made
the
intellectual
leap
and
the
business
leap
into
a
cloud
way
of
thinking
about
resources.
B
People
are
putting
firewalls
and
virtual
machines,
routers
switches,
doing
all
that
stuff
within
VM
and
then
packet
inspection
in
VMs.
That
investment
is
living
our
living
in
virtual
machines
living
on
OpenStack
great
that
our
container
containers
would
have
access
to
them
in
close
access
to
them,
if
they're
all
on
the
same
infrastructure
as
a
service.
B
You
have
in
place
also
for
self-service
if
you've
already
set
up
divisions
of
your
company
or
your
partners
to
be
able
to
deploy
resources
and
your
infrastructure
through
OpenStack.
This
just
continues
that
paradigm.
It
makes
things
easier
for
you,
I
see
the
biggest
win
in
the
in
a
second
to
last
bullet
point
where
you're
taking
advantage
of
existing
operational
procedures
operations
is
the
heart
of
your
or
without
that
you
can't
we're
not
in
business
anymore
and
people
of
generally
corporations.
B
Small
businesses,
medium-sized
businesses,
when
operations
fails,
their
entire
business
goes
down,
and
so
the
investment
you
put
into
the
operational
procedures
around
your
cloud
around
your
infrastructure
in
your
virtual
machines,
is
nothing.
You
want
to
pivot
away
from
very
quickly
if
you're,
gonna,
pivot
away
from
it
at
all,
especially
features
like
workload,
migration,
snapshotting
and
especially
disaster
recovery.
B
Those
are
probably
well
tried
and
true
tested
in
in
your
organization
and
don't
give
that
up
layer
open
shift
on
top
of
that
and
you'll
be
able
to
you'll
have
the
same
recovery
that
you
had
in
the
previous
instance,
or
very
similar,
and
also
in
interacting
with
vendors
like
Dell
you're
gonna
continue
the
similar
purchasing
patterns.
It's
it
makes
it
easier
for
everybody
if,
when
an
architecture
is
defined
and
ability,
riyals
is
well
defined,
that
it
makes
it
a
lot
easier
to
order
and
allow
more
predictable
to
order.
B
So,
when
gear
arrives
on
your
loading
dock,
it's
actually
what
you
expect
and
your
operators
and
your
data
center
managers
are
able
to
put
together
gear
that
you're
familiar
with
and
you've
already
done.
All
the
work
for
OpenStack,
there's
almost
no
stretch
at
all
to
do
it
with
openshift
the
so
now
I
want
to
talk
about
the
details
of
our
reference
architecture
and
how
they
compare
to
the
requirements
of
open
shift
and
what
I
had
to
do
so.
B
We'll
talk
about
the
sizing
goals
of
our
reference
of
Dells
reference
architecture
of
OpenStack
and
those
deltas,
how
we
scale
our
reference
architecture
and
some
of
the
and
how
we
promised
AJ
and
some
of
the
flexible
hardware
details
allocated
a
little
bit
of
the
security
issues
and
then
review
those
three
documents
that
I
produced
for
you
in
order
to
make
this
stuff
happen.
First
of
all,
our
architecture
goal
when
looking
at
virtual
machines,
our
minimum
configuration
was
to
have
something
that
was
scalable
and
flexible.
B
That
is
flexible
if
you
wanted
more
storage
than
compute
or
you
wanted
more
compute
than
storage
you'd
be
able
to
easily
size
that
and
order
it
from
us
with
really
a
minimum
of
hassle.
We've
a
bill
of
materials
guide
that
gets
you
everything
that
we've
tested
a
million
times,
and
we
actually
do
our
ordering
for
over
our
little
team
within
Dell.
We
don't
do
we
don't
order
our
ear
through
Dells
internal
ordering
system.
We
use
the
same
ordering
system
that
any
of
our
customers
do.
B
So
we
know
exactly
what
kind
of
customer
experience
you're
gonna
have
with
Dell.
When
you
use
our
RA,
we
try
to
make
it
as
easy
as
possible
for
you,
so
we
figured
our
base.
Virtual
machine
would
be
two
cores,
a
four
gigs
of
ram
with
40
gigabytes
of
local
ephemeral
storage
and
that's
what
we
sized
it
off
of
we
did.
B
Then
we
did
a
lot
of
work,
validating
our
storage
solutions,
the
EqualLogic
back-end,
the
dell
storage
center,
which
used
to
be
called
Compellent
back-end,
and
we
wrote
drivers
for
OpenStack
did
a
lot
of
work
on
cinder
and
all
of
that
is
upstream
in
OpenStack,
and
all
of
it
is
available.
Thanks
to
kubernetes
implementation
of
a
cinder
driver
being
able
to
mount
cinder
volumes
is
available
within
openshift
yay.
B
We
also
looked
very
closely
at
the
networking.
There
will
be
even
more
network
traffic
with
openshift,
with
containers
talking
to
each
other
in
kubernetes
in
order
to
keep
things
alive,
so
we
have
at
the
bottom.
The
last
line
there
is
is
our
basic
switch
configuration
and
here
on
the
next
slide,
I
detail
a
little
bit.
How
that
minimal
storage
plays
out
you're
doing
one
solution,
admin
host,
which
has
your
OpenStack
director,
your
your
your
SEF
front-end,
and
your
tempest
testing
virtual
machine.
B
So
we
we're
giving
you
the
opportunity
and
the
capabilities
to
test
and
retest
your
OpenStack
deployment
when
you
deploy
it.
You
there's
no
second
step
that
you
need
to
take
to
test
your
what
you've
deployed
when
you
use
our
reference
architecture,
we're
deploying
three
controllers:
three
compute
nodes:
you
give
your
choice
of
three
different
chassis
x'.
B
If
you
want
to
port
put
more
nicks
in
the
box
and
the
three
major
storage
options
that
the
bar
730
XD
is
really
just
a
nice
to
you
just
jammed
with
drives
and
you
you
would
normally
run
SEF
on
top
of
that
and
have
just
plenty
of
storage
space.
If
you
have
the
operations
folks
for
it,
you
have
an
investment
in
Compellent
or
EqualLogic.
B
We
totally
support
it,
and
then
this
is
how
we
scale
up
from
3
compute
nodes,
we've
tested
in
our
first
rack,
8,
compute,
nodes
or
7
storage
nodes,
and
you
can
also
mix
mat,
mix
and
match
and
get
4
computes
and
3
storage.
If
you
just
want
to
scale
up
that
first
rack
or
you
can
go
to
3
racks
and
just
end
up
with
tons
and
tons
of
compute
and
RAM
and
mix
and
match
the
storage,
as
you
like.
B
If
you're
gonna
have
a
lot
of
network
throughput,
we
also
indicate
this
the
first
align
on
the
left
under
network.
The
Z
9100
switch
can
really
handle
very
high
data
rates
that
you
might
have,
depending
on
how
you'll
be
using
losing
a
lot
of
NFV.
You'll,
probably
want
to
use
the
Z
9100
switch
in
your
central
rack.
B
So
I
looked
at
what
our
minimum
configuration
was
and
what
it
was
offering
us
and
how
many
how
this
would
translate
into
open
shifts
terminology,
so
Red
Hat
recommends
our
each
master.
Vm
have
a
minimum
of
2
virtual
CPUs,
plus
one
CPU
per
every
additional
thousand
pods
eight
gigs
of
RAM,
another
2.5
gigs
of
ram
per
thousand
pods
and
30
gigs
of
storage
that
compares
to
and
the
nodes
I.
B
Don't
really
have
to
read
all
this
off,
but
really
what
you
end
up
with
is
well
what
you've
purchased
if
you
purchase
the
minimum
is
over
here
on
the
regular
physical
solution
of
72
cores
available
to
you
in
348
gigs
of
RAM,
making
about
approximately
five
gigs
of
RAM
a
little
more
per
core.
The
in
Andover
thrives
in
a
non
oversubscribed
situation,
where
you're
really
using
you're,
giving
every
node
every
pod
one
to
one
virtual
CPUs.
You
can
deploy
14
instances
of
four
CPUs,
so
you
would
have
of
the
56
cores
available.
B
You
could
have
probably
make
probably
create
14
instances
virtual
machine
instances
with
the
OpenShift
node
running
on
it,
and
then
you
probably
if
you
really
want
to
maximize
your
availa
performance
for
each
of
the
nodes
and
for
each
of
your
pods,
you
would
just
deploy
four
pods
or
maybe
five
pods
per
node
is,
if
you're
doing
incredibly
compute
intensive
work.
If
you're
not
here
on
the
next
one,
let's
compare,
subscription
versus
non
or
subscription
with
over
subscription.
B
B
Pivoting
here,
a
little
bit,
switching
to
a
whole
of
their
subject
on
the
left
column
is
what
we
are
offering
you
as
tested
and
validated
in
our
labs
on
Red
Hat's
OpenStack
platform.
These
are
the
OpenStack
and
open.
A
second
sociated
features
that
we're
offering
we're
doing
the
OSB
director
deployment.
Everything
is
automated,
with
Keystone
and
and
Keystone
authentication
and
and
just
the
whole
list
of
typical.
B
Basic
OpenStack
features
for
open
shifts
on
the
right
column.
These
are
the
features
that
I
to
enable
grabs
and
packages
off
of
OSP
that
don't
come
out
of
the
box
for
us
I
had
to
add
the
Neutron
load,
balancer
so
I
to
reconfigure
the
controllers,
a
little
bit
also
to
support
the
heat
cloud
formations
and
the
heat
metadata
service
and
I'll
go
into
a
little
bit
of
the
complexity
of
how
open
chef
an
open
stack
works.
This
metadata
service
provides
data
into
ansible
and
then
to
open
shift
to
get
open
shift
set
up
properly.
B
Here's
the
eye
chart
network
diagram.
It's
a
complex
network
to
be
able
to
support.
All
of
this
storage.
Have
an
out-of-band
management
network,
provide
the
OpenStack
API
provide
a
floating
IPS
to
openshift
after
more
than
one
deployment
of
OpenShift
and
all
the
red
stuff
in
the
middle.
Those
are
the
the
virtual
machines
that
are
running.
B
The
security
issues
that
I
found
as
I
embarked
on
this
were
first
thing
was
the
the
divisions
of
concerns
that
we
had
set
up
on
the
previous
slide
by
network
who
suddenly
had
some
holes
in
it
when
we
tried
to
do
full
stack
management
with
cloud
forms,
and
the
second
issue
that
jumped
out
at
me
was
that
there
was
no
immediate
Keystone
integration.
It
wasn't
something
that
folks
were
that.
Red
Hat
was
testing
in
the
open
shipped
on
OpenStack
project.
B
B
Here's.
What
I
really
went
through
discovered
the
project
that
was
very
nascent
to
build
open
ship
at
home,
open
stack
as
heat
templates
and
scripts,
calling
out
the
ansible
work
discovered
it
about
eight
months
ago,
saw
that
there
were
a
bunch
of
feature
Delta's
that
would
have
to
have
be
addressed.
B
Osp
actually
was
not
initially
supported,
and
there
were
a
few
features
that
I
had
to
add
in
order
to
make
it
for
the
common
customer
outside
of
Red
Hat.
To
be
able
to
use
their
OSP
licenses
in
addition
to
their
open
licenses,
and
then
we
have
time
dig
into
some
of
the
how
you
go
about
debugging
and
coordinating
the
the
deep
layers
of
many
technologies
that
are
used
to
deploy
all
this
stuff
to.
What
is
this
project?
The
project
is
very
well
coordinated:
heat
templates,
bash
scripts,
ansible
modules,
customizable
modules
and
gamal
configs.
B
Those
all
work
together
in
order
to
do
the
steps
in
these
two
columns.
First
heat
creates
the
the
networks
necessary
the
security
groups,
etc,
etc.
Within
OpenStack
creates
the
alarms
and
selamat
err
and
then
first
deploys
the
infrastructure.
Server
is
not
a
part
of
openshift,
it's
something
that
this
team
has
created,
nor
that
provides
secondary
services
such
as
DNS
such
as
the
the
hosts
to
kick
off
all
the
ansible
runs
in
order
to
deploy
OpenShift
and
configure
the
cluster
on
all
these
nodes.
B
So
then
heat
goes
ahead
and
deploys
the
master
VMs
and
runs
the
cloud
init
scripts
to
set
up
the
master
vm
boxes.
Then
it
deploys
the
nodes
and
then
gets
them
started
and
then
deploys
the
load,
balancer
and
checks
that
all
of
that
network
connect
connectivity
is
working.
Then
it
goes
ahead
and
does
the
ansible
runs
the
right
column
off
of
that
infrastructure,
server
that
in
for
V
M,
and
so
it
deploys
the
which--if
masters
and
nodes
and
then
can
deploy
an
open,
shipper,
router
and
in
openshift
registry?
If
you
so
choose
the.
B
B
Here's
a
little
tip,
just
you're,
going
to
be,
if
you're,
using
this
to
test
out
and
you're
developing
along
with
us
to
make
this
a
great
product.
The
meaningful
stack
names
becomes
really
important.
So
this
is
a
little
script.
I
put
together
to
just
create
stacks
that
were
had
unique
names
and
that
I
could
update.
B
Over
and
over
again,
the
I
was
doing
parallel,
multiple
symbol,
simultaneous
deployments
of
OpenShift,
which
were
just
fine
as
the
long
as
the
networks
didn't
collide
with
each
other,
and
since
our
architecture
is
if
sold
to
our
customers
in
a
farm
or
waterfall
method,
Dell
is,
is
far
more
traditional
that
way
and
we
towards
our
customers.
It's
far
more
waterfall
we're
not
an
agile
software
company.
Yet
the
the
PDFs
and
the
documentation
that
I
release
is
really
bleeding
edge.
Stuff.
B
B
Early
in
my
testing
notice
that
my
all
this
great
open
source
code
that
was
doing
the
deployment,
although
there
was
not
a
feature
in
the
heat
templates,
to
indicate,
what's
the
pool
idea
of
your
OpenStack
that
you
bought
from
you,
bought
a
subscription
from
Red
Hat,
so
I
added
a
feature,
and
if
we
have
time
it's
a
little
hard
for
me
to
see
how
much
time
I
have
left.
But
I
can
even
just
take
a
quick
walkthrough
of
how
to
on
this.
This
we.
B
B
So
let's
have
a
quick
look
at
it
and
when
I
first
joined
the
project,
there
was
only
only
this
value,
only
the
so
that
was
great.
That
was
my
open
shift
license,
but
I
couldn't
indicate
my
OpenStack
license
to
get
access
to
the
repositories
that
I
needed,
though
I
added
added
this
variable
here.
Where
does
what
did
I
have
to
change
in
order
to
enable
them?
Well,
let's
look
at
it
the
really
easy
way
with
our
friend
grep.
B
The
first
file-
that's
important
is
the
is
the
open
shift.
Llamo
I,
just
I
went
in
and
I
opened,
I
checked
out.
The
open
shift,
Gamal
and
I
saw
that
there
was
the
rhn
pool
lost
like
I
need
another
HN
pool
so
I
copied
that
structure
and
changed
its
type
from
a
string
to
a
comma
delimited
list.
Who
will
allow
folks
to
add
even
more
pools
needed
to
and
really
just
went
through
and
added
those
parameters?
B
B
C
B
C
C
B
This
has
changed
a
lot
than
the
last
time.
I
did
it,
but
it's
really
just
hacking
these
shell
scripts
that
get
coalesced
into
one
shell
script.
That
becomes
the
cloud
init
script.
That
runs
as
the
first
thing
that
runs
the
first
time
of
a
virtual
machine
is
brought
up
and
it
updates
the
operating
system.
It
pulls
in
some
client
utilities,
from
OpenStack
and.
B
C
B
Exactly
is
my
extra
pool
ID.
This
is
the
this.
Is
the
code
right
here,
it's
so
simple
to
add,
to
add
more
pool
IDs
and
attach
to
them
because
they're
the
issue
that
I
was
seeing
was
I,
didn't
have
access
to
all
of
the
OpenStack
tools
that
the
folks
inside
Red
Hat
or
the
folks
who
were
using
CentOS
had
access
to.
So
it's
a
very
simple
change.
B
Just
cook
took
me
an
hour
to
of
work
and
and
testing
and
I
was
able
to
get
the
feature
added
really
quickly
and
the
guys
yawn
and
the
other
guys
on
the
project
took
my
patch
really
quickly.
I
think
might
have
cleaned
it
up
a
little
bit
and
I
was
able
to
go
to
start
committing
to
the
project,
which
was
just
wonderful,
really
easy
folks
to
work
with.
B
They
are
not
yet
available
on
the
Dell
website.
They
are
available
through
me.
They
are
available
through
our
systems,
engineers
to
our
sales
engineers.
We
don't
have
a
spot
on
our
website
where
they're
being
published
just
yet
I'm,
where
we're
reconfiguring
our
Tech
Center
to
have
more
content
from
the
cloud
team.
The
overall
reference
architecture
is
available
there.
C
B
A
B
B
Those
batch
scripts
come
together
to
create
the
cloud
init
script
that
I
said
runs
at
the
beginning
that
at
the
first
boot
up
of
your
VM
and
appropriate
to
the
type
of
VM,
whether
it's
infrastructure
or
the
master,
node
ID,
sorry,
the
master
or
the
nodes
of
open
of
openshift
and
openshift
ansible
itself
is
another
really
big
project
out
on
github.
That
Red
Hat
is
spearheading
to
automate
sophisticated
deployment
of
open
ship
on
a
variety
of
different
infrastructures,
bare
metal
out
on
the
AWS
cloud
or
Google's
cloud
or
on
top
of
OpenStack
the.
B
So
this
is
a
big
project,
that's
moving
very
quickly
and
my
feature
initially
failed
on
open
ship
danceable,
but
they
were
also
so
incredibly
responsive.
That
I
was
able
to
get
my
feature
fixed
in
opens
shift
ansible
within
a
day
there
also
a
few
habits
that
I
picked
up
you
to
make
debugging
all
this
stuff
easier.
The
way
we
set
up
the
director
is,
we
have
keys
already
set
up
private
keys
and
public
keys,
ssh
authentication
set
up
between
the
director,
node
and
all
of
the
over
cloud
nodes.
B
C
B
B
The
OpenShift
on
OpenStack
deployment
tool
deploys
to
networks
for
you.
It
asks
Neutron
to
create
two
networks.
It
creates
a
network
that
is
only
the
core
components
of
OpenShift
and
a
second
network
that
includes
the
the
that
also
includes
their
infrastructure
server,
and
you
can
see
the
difference
right
here
where
this
master,
one
virtual
machine
has
one
network.
That's
two
networks
and
it
has
three
networks.
B
The
infrastructure
server,
which
is
not
a
core
component
of
openshift,
has
the
floating
IP
and
it
has
the
fixed
network.
So
it
can
communicate
with
the
OpenShift
cluster,
but
it
does
not
have
an
IP
address
on
the
cluster
Network
and
the
networking
goes
so
far
as
to
prohibit
the
nodes
themselves,
which
are
far
behind
the
scenes
from
having
a
floating
IP
address.
So
anybody
who's
on
the.
B
Openstack
on
any
of
the
OpenStack
under
cloud
I'm,
sorry
any
of
the
OpenStack
over
cloud
boxes,
the
compute
nodes
or
the
or
the
controller
nodes
cannot
SSH
in
directly
to
the
workloads
of
their
customers,
cannot
cannot
SSH
into
the
open
ship
nodes
where
the
pods
are
running.
They
can
only
get
into
the
masters.
B
B
B
B
Now,
once
you
kick
off,
the
heat
stack,
create
I
timed.
It
and
I
offer
documentation
of
what
log
files
you
want
to
look
at
for
how
long
to
ensure
the
process
is
running
correctly
may
not
want
to
go
through
all
of
this
here
and
now
it's
here
in
the
presentation.
It's
also
in
the
documentation
that
I
released
it's
it's
a
further
fleshing
out
of
the
documentation,
that's
available
on
github
within
the
project,
in
short
form.
B
It
there's
over
20,000
ansible
place
that
gets
executed
to
ensure
this
is
all
set
up
properly
for
the
first
10
minutes,
you're
watching
heat
for
the
the
heat
that
the
heat
event
list,
which
is
just
on
the
OpenStack
level,
using
the
OpenStack
API,
but
for
the
next
15
minutes,
you're
looking
at
the
infrastructure,
VM
and
its
cloud
in
it
and
as
it
prepares
ansible
and
then
for
the
next
10
minutes,
you're
watching
you
have
to
log
into
wellnot
for
the
next
10
minutes.
You
are
watching.
B
All
of
this
is
documented
in
excruciating
detail
in
these
three
deployment
guide
in
these
three
technical
guides
and
the
one
into
well.
The
two
technical
guides
and
one
integration
guide,
I
thought:
if
I
had
a
little
time,
I
would
show
y'all
how
how
I
can
show
you,
the
the
openshift
front-end
by
running
containers
might
deployed
applications
but
also
show
you
how
cloud
forms
is
giving
visibility
and
monitoring
and
even
reporting
to
all
of
these
resources.
A
B
Okay,
the
one
important
thing
I'd
like
to
call
out
here
that
my
boss
keeps
fetching
about
is
the
fact
that
open
claw
opened
I'm,
sorry
that
cloud
forms
has
access
to
everything
and
it
looks
really
really
dangerous.
That
cloud
forms
has
access
to
the
management
networks
in
order
to
log
into
the
the
director
node
into
the
compute
hosts
into
the
storage
hosts
and
then
log
into
all.
B
B
Here
we're
looking
at
the
over
cloud
nodes
that
have
been
deployed
here.
You
could
see
cloud
forms
one
you
could
see
the
these
are
all
the
virtual
machines
that
are
making
up
all
of
OpenShift,
plus
any
others
that
I
happen
to
launch
giving
you
quick
at
a
glance
status
for
how
the
machine
is
doing
what
it's
made
up
of.
B
It's
saying
you
know
this
is
running
rel,
it's
an
open
shift,
I'm!
Sorry,
it's
an
openstack
VM!
It's
got
I,
don't
remember
what
zero
is,
but
that
it's
it's
running.
You
could
also
take
a
look
at
different
parts
of
the
infrastructure.
The
first
thing
that
you
set
up
when
you
start
cloud
forms
other
than
cloud
forms
itself.
Is
the
infrastructure
provider
which
is
whoops.
B
Which
is
to
tell
it
that
you'll
be
using
OpenStack,
and
this
is
I-
have
nine
nodes
in
my
OpenStack
deployment,
that
is
three
controllers:
three
storage
nodes
and
three
compute
nodes,
and
if
we
drill
into
this,
we
can
see
a
summary
of
all
those
and
all
of
the
all
of
its
nodes.
I've
done
what
they
call
smart
state
analysis,
which
is
a
fantastic
feature
of
cloud
forms
which
goes
in
and
does
deep
interrogation
that
even
ball
the
processes
on
these
boxes.
So,
if
I
look
at
one
of
the
compute
nodes.
B
Sorry,
the
smart
state
analysis,
which
is
called
fleecing
to
the
developers
where
what
happens
is
cloud
forms,
will
take
a
snapshot
of
the
running
virtual
machine,
bring
that
snapshot
on
to
the
cloud
forms
machine
and
mount
that
drive
mount
the
the
image
and
interrogate
image
for
all
the
processes.
All
the
software
that's
been
been
ployed
on
that
really
doing
a
very
deep
inspection,
but
out
of
band
and
not
impacting
the
performance
of
that
virtual
machine.
C
B
Each
one
of
my
OpenShift
deployments
is,
do
is
doing
and
right
now,
I
only
have
one
deployment
of
open
ship,
one
provider.
It
has
five
nodes.
That
would
be
the
the
the
masters
and
the
and
the
the
nodes.
So
I
have
two
masters
and
three
nodes,
and
each
of
those
has
a
certain
amount
of
pods
and
services
that
have
been
configured
by
OpenShift.
B
A
A
A
A
B
A
You
see
if
anyone
has
a
mark,
I
have
mark
la
Morena
I've,
also
unmuted
you
as
well.
So
if
you
want
to
add
anything
in
here,
we've
we've
done.
We've
seen
a
couple
of
different
reference.
Architectures
for
open
opening
shift
on
OpenStack
and
mark
was
one
of
the
folks
that
talked
in
an
earlier
podcast.
A
That
all
includes
a
Lincoln
and
doing
some
of
this
work,
but
you've
definitely
done
a
whole
lot
more
work,
I'm
waiting
to
see
all
that
technical
documentation
come
online
because
I
think
that's
going
to
be
incredibly
useful
for
the
community
and
to
get
started
so
we'll
have
to
see
how
we
can
incorporate
that
down
the
line.
The
other
thing
that
happened
just
the
other
day,
there's
a
blog
post,
Jeremy
eaters,
been
doing
some
work
on
performance
tuning
around
on
using
the
CNC
F's
cluster
and
I'm
gonna
push
Dell.
A
If
you
haven't
guys
haven't
joined
the
the
cloud
native
foundation,
yet
you
really
ought
to
I'm
sure
EMC
is
at
some
level
so,
but
you
need
to
get
warm
up
because
they
have
some
hardware
that
they're
making
available
as
well,
though,
you
have
your
own
hardware,
which
is
wonderful,
but
there's
a
great
blog
post
about
doing
that
that
just
came
out
deploying
a
thousand
and
I
dropped.
The
URL
in
there
and
Judd
has
very
nicely
offered
to
chair
an
open
shift
on
OpenStack
special
interest
group
for
the
open
shift
Commons.
A
So
he's
coercion
is
my
game.
Here
there
are
a
lot
of
people
in
the
open
ship
community
that
are
also
part
of
the
OpenStack
community,
so
I
think
it's
a
natural
to
do
that
and
we'll
try
and
launch
that
cig
in
the
next
coming
weeks.
Probably
after
Labor
Day
after
already
comes
back
from
holidays,
and
then
we
are
also
going
to
be
hosting
on
November
7th
in
Seattle
and
Jed
has
also
been
coerced
coming
there.
What
we're
calling
the
first
open
shift,
Commons
gathering
it's
going
to
be
co-located
with
coop
con.
You
can
register
today.
A
C
C
Just
a
minor
note
about
the
CN
CF
CN,
CF
distinct,
our
project
was
actually
involved
in
this
distinct
and
we
we
had
the
part
of
this,
of
these
resources
available
for
testing
Oh,
conscious
on
open
stroke
and
really
quite
a
successful
gala
testing.
We
were
able
to
scale
up
up
to
100
notes
with
these
he
templates,
which
was
the
primary
goal
for
this
this
project
so
well.
This
is
just
make
about
the
Jeremy's
book
and
also
thanks
for
the
awesome
presentation.
It
was
pretty
cool.
A
A
lot
of
collaboration
went
on
to
make
all
of
this
happen
so
and
we're
really
thrilled
with
the
work
that's
Jed's
been
doing
over
the
past
three
years,
keeping
up
to
all
of
our
revisions
of
open
shifts,
and
so
you've
got
a
slide
up
here
about
what
your
future
plans
are.
Once
you
go
through
that
Jed
yeah.
B
Yeah,
we're
expecting
to
be
able
to
advertise
support
of
a
lot
more
storage
backends,
especially
and
I,
want
to
use
our
labs
to
test
storage
performance.
We
got
a
lot
of
storage
here
and
we
a
lot
of
folks
who
are
really
good
at
testing
performance
that
way
and
I
want
to
collaborate
more
with
red
hat.
In
order
to
show
some
real
numbers
there.
We
want
to
do
some
net
workload.
Examples
we
find
a
lot
of
our
customers
are
very
interested
in
being
able
to
deploy
net
into
such
a
flexible
and
reliable
infrastructure.
We'll.
B
And
we
will,
we
Adele
will
be
documenting
in
further
detail
the
details
of
expanding
our
OpenStack
cloud,
because,
right
now
we
just
give
you
specifications
but
no
documentation
and
actually
how
to
go
about
it
in
in
a
way
that
covers
all
three
all
three
racks
and
all
the
networking.
So
as
they
expand
that
part
of
the
documentation
I'm
going
to
expand
my
documentation
for
to
match
our
reference
architecture,
I'd
like
to
try
to
get
to
these
are
sort
of
nice
to
have
now
the
deeper
OpenStack
integration,
especially
with
authentication.
B
My
my
colleagues,
my
product
managers,
keep
asking
for.
You
know
one
account
for
a
from
OpenStack
and
OpenShift
and
we're
also
hearing
a
lot
from
our
customers,
the
need
for
the
network
segmentation
for
tenants
and
the
billing
in
chargeback.
They
really
want
to
be
able
to
do
the
chargeback
within
their
organization
or
if
their
managed
services
provider
like
the
big
telcos,
they
want
to
be
able
to
offer
bills,
and
so
I've
already
asked
my
questions.
A
A
It's
been,
it's
been
a
wonderful
collaboration,
so
yawn
and
sylvain.
Thank
you
very
much
for
your
efforts
and
mark
my
marina
as
well
in
the
past,
has
done
a
lot
of
the
the
heavy
lifting
and
contributing
the
code
to
this.
To
make
this
out
all
happen.
So
it's
much
appreciated
again
we're
going
to
be
all
gathering
together
on
November
7th
for
the
open
ship,
Commons
gathering.
A
So
please
do
join
us
for
that
day
and
I
will
make
sure
that
judge
there
and
available
and-
and
you
can
have
your
own
open
shift
on
OpenStack
breakout
room
and
go
into
even
more
deep
dives
in
comparison
on
that.
So
looking
forward
to
supplying
the
beer
for
that
and
making
that
happen
in
Seattle.
For
you
all
so
again,
thanks
judge.