►
From YouTube: Ask an OpenShift Admin (Ep 45): Bare metal deployments
Description
What's the worst part about provisioning bare metal machines? And why would you opt to deploy Red Hat OpenShift on a bare metal server over a virtual machine anyway? Join this episode for an in-depth look at bare metal provisioning with OpenShift Container Platform. We’ll examine Installer-provisioned installation, look at the prerequisites, and set up the environment and configuration. So tune in and bring your questions about deploying OpenShift on bare metal.
About Ask an OpenShift Admin:
Do you have questions? We want to answer them! Every Wednesday at 11am ET, hosts Andrew Sullivan and Chris Short sit down to answer your questions about Red Hat OpenShift.
Follow us:
Andrew Sullivan https://twitter.com/practicalandrew
Chris Short https://twitter.com/chrisshort
Subscribe to Red Hat's YouTube channel: https://www.youtube.com/redhat/?sub_confirmation=1
About OpenShift:
Red Hat OpenShift is an open source container application platform based on the Kubernetes container orchestrator for enterprise application development and deployment.
Openshift.com https://red.ht/33Fh6uV
OpenShift on github https://github.com/openshift/
OpenShift on redhat.com https://red.ht/2o4ccDk
#RedHat #OpenShift #ContainerPlatform
A
A
A
B
C
It's
all
live
now:
okay,
cool
good
morning,
good
afternoon,
good
evening,
welcome
to
a
very
special
edition
of
ask
an
openshift
admin.
I
am
joined
by
some
fellow
red
hatters
today,
I'm
technically
not
supposed
to
be
here,
I'm
supposed
to
be
at
a
doctor's
appointment,
but
they
canceled
on
me
all
morning.
So
some
point
in
time
I'm
going
to
get
a
phone
call
and
I'm
going
to
disappear
so
andrew.
What
do
we
got
cooking
today?
Buddy
yeah.
B
So
yeah
well
good
good
morning
or
good
afternoon.
Everyone
apologies
for
the
technical
difficulties.
It
turns
out
that
andrew's
still
learning
how
this
works
and
with
chris,
maybe
not
being
here
the
whole
time
I
figured
I
should
be
in
the
driver's
seat.
So
apologies
for
that
up
front
technical
issues,
no,
no!
No,
no,
not
at
all!
So,
yes,
thank
you.
Everyone
welcome
to
this
week's
stream
of
ask
an
openshift
administrator.
B
B
So
this
week
I
am
very
happy
to
be
joined
by
one
of
my
peers,
one
of
chris's
peers,
reese
oxenham,
as
well
as
on
the
product
management
team,
one
of
our
peers
and
ramon.
I'm
I'm
not
going
to
try
your
your
last
name,
because
I
know
I'm
going
to
butcher
it
and
I
don't.
I
don't
want
to
embarrass
myself.
B
E
E
D
And
hi
everyone
ramon
asilo
rodriguez
and
I'm
the
product
manager
for
openshift
on
bare
metal,
which
involves
many
things
but
many
things.
But
essentially
what
we
are
doing
is
trying
to
make
bare
metal
behave
as
a
cloud
provider
trying
to
automate,
as
we
probably
will
discuss
today,
all
the
bare
metal,
provisioning
and
management,
as
if
you
were
dealing
with
any
other
public
or
private
cloud
provider.
B
Yeah,
so
I
I
know
we
have
a
bunch
of
exciting
and
interesting
things
planned,
not
the
least
of
which
thank
you
very
much.
Reese
is
a
a
demo
of
what
all
of
this
looks
like,
and
I
I
know
I
want
to
talk
about.
You
know
openshift,
bare
metal,
the
when
the,
why
and
all
that
other
stuff,
but
I'm
going
to
hold
off
on
that
because,
as
is
sort
of
our
tradition
with
the
open
shift,
admin
ask
an
open
shift.
B
Admin
hour
is
our
top
of
mind
topics
so,
if
you're
new
to
the
stream,
this
is
essentially
a
set
of
things
that
I
think
chris
chris
and
I
think,
are
interesting
to
you-
things
that
have
happened
in
the
last
week
or
two
since
the
previous
stream.
That
might
be
relevant.
So
the
first
thing
that
I
want
to
talk
about
as
soon
as
I
find
my
notes
list
here
is:
oh
vmworld
is
this
week.
So
if
you
are
so,
I
believe
vmworld
is
free.
B
B
Gonna
quickly
share
my
screen,
then,
so
you
all
can
see
what
I
see.
So,
if
you
go
to
the
link
that
chris
just
very
helpfully
pasted
in
there
you'll
end
up
at
this
page
and
shameless
self-promotion.
One
of
these
sessions
has
me
in
it
so
down
here
in
this
integration
considerations
for
openshift
and
vmware.
So
we
did
a
panel
session
along
with
some
of
our
ibm
peers
and
vmware
peers,
so
dean
lewis
down
here
does
a
great
blog.
B
So
the
second
thing
I
wanted
to
talk
about
is,
of
course
kubecon.
I
I
hope
that
nobody
is
surprised
to
to
realize
that
kubecon
is
next
week.
I
say
that
because
I
was
surprised
to
realize
that
kubecon
is
next
week.
It
has
snuck
up
on
me
and
you
know
it's
not
like
we're
busy
or
anything,
but
the
good
news
is
red
hat,
as
you
would
expect,
has
a
pretty
substantial
presence
there,
not
the
least
of
which
includes
mr
shorts.
C
B
B
B
So
if
you
browse
through
here-
and
you
can
see
that
this
is
a
very
big,
very
in-depth
listing
of
everything
that
we
have
going
on
at
kubecon
next
week
as
a
result
of
this,
I
will
also
remind
you
that
we
won't
be
streaming
next
week.
So
or
at
least
I
know
we
will
be
streaming
other
things,
but
this
show
will
not
be
streaming
next
week.
B
So
take
that
time.
I
would
highly
recommend
that
folks
invest
that
that
time
into
listening
to
what's
going
on
at
kubecon,
remember,
openshift
is
kubernetes
and
the
things
that
happen
in
kubernetes
eventually
happen
in
openshift
as
well.
So
as
we
highlighted
during
the
last
stream
with
the
kubernetes
api
deprecations,
yes,
which.
B
C
Is
one
of
the
three
I
should
probably
mention
the
three
I'm
involved
with
so
obviously
openshift
commons?
I
will
be
around
that
and
I
think
we're
intending
to
live
stream
it.
I
it's
very
weird.
Things
are
hard
this
year,
I'll
just
leave
it
at
that,
it's
logistics
and
it's
la
so
yeah.
I
will
also
be
part
of
get
ops
com
which
is
happening
on
this
day
as
well.
But
it's
like,
I
think,
yeah
cute.
C
B
There
was
another
thing
that
I
wanted
to
bring.
Oh
tomorrow.
Tomorrow
is
the
openshift
4.9?
What's
new
live
stream?
Yes,
so
I
got
it.
Thank
you
so,
as
you
can
probably
predict,
that
means
that
4.9
is
not
too
far
away
and
we
will
be
talking
about
by
we
I
mean
the
product
product
management
team
will
be
spending
time
talking
about
all
of
the
new
features
that
are
coming
in
with
that,
so
we'll
be
live
streamed
here
tomorrow,
both
across
youtube
as
well
as
twitch.
B
I
know
I
will
be
here
helping
to
answer
questions,
helping
to
shuttle
questions
back
and
forth
to
the
product
management
team.
So
please
don't
hesitate
to
if
you're
watching,
to
ask
questions
on
whatever
platform
you're
on
we'll
make
sure
to
get
those
answered
as
best
as
we
possibly
can
so,
and
I
know
4.9
4.9
10
11
seemed
to
be
busier
releases.
I
know
at
least
in
in
my
world,
so
I
was
on
a
meeting
at
7
00
am
this
morning
talking
about
stuff,
that's
happening
in
4,
10
and
4
11..
B
B
B
B
So
I
happen
to
see
this
morning
the
docs
team
made
an
announcement
that
they
have
completed
documenting
a
feature
that
was
released
with
4.8
but
was
basically
unknown,
so
the
poison
pill
operator
is
effectively
a
way
of
determining
that
a
node
is
no
longer
accessible
and
then
taking
action
based
off
of
that
so
reese,
I'm
gonna,
I'm
gonna.
Let
you
kind
of
take
over
and
talk
about
that
because
I
know
you
have
you're
very
familiar
with
it.
E
Yeah
sure
not
a
problem,
so
I
just
want
to
back
up
a
little
bit
and
talk
about
why
these
things
exist.
So,
typically,
if
you're
running
applications
on
top
of
a
kubernetes
or
openshift
cluster,
you
may
run
certain
types
of
applications
that
you
need
to
invoke
some
kind
of
remediation
if,
for
example,
the
host
or
the
node
that
was
running
that
application
goes
away.
E
I
go
away,
I
mean
it
crashes,
someone
pulls
the
power
out
the
back
or
you
know
someone
takes
a
network
cable
out
or
something
like
that,
and
kubernetes
will
typically
mark
that
node
after
a
certain
amount
of
time
as
you're
not
ready.
It's
not
heard
from
it
for
a
little
while,
but
in
some
cases
some
applications
they
might
have
reliance
on,
for
example,
a
storage
volume,
and
you
need
some
kind
of
external
remediation
to
take
place
to
recover
that
workload.
E
Now
for
a
long
amount
of
time
you
as
a
kubernetes
administrator,
could
go
in
there
and
you
could
recover
that
workload.
You
by
you
know
deleting
the
node.
It
will
essentially
tell
the
kubernetes
cluster.
You
can
relocate
this
workload
on
another
surviving
node
and
over
time.
We've
added
in
additional
automated
remediation
methods.
E
What
that
would
do
is
it
would
monitor
all
of
your
nodes
and
if
one
of
them
went
offline
for
a
certain
amount
of
time
which
was
configurable,
it
would
essentially
fence
that
machine.
It
would
connect
out
to
the
outer
band
management
machine,
be
that
I
load
rack
or
whatever
it
might
be,
and
it
would
forcefully
reboot
that
machine
what
that
would
mean
it.
What
that
would
lead
to
is
a
guaranteed
safe
relocation
of
that
workload,
because
we
know
that
that
machine
has
been
turned
off.
This
is
akin
to
traditional,
high
availability
concepts.
E
E
Now
what
we
are
driving
towards
with
the
poison
pill
operator
is
kind
of
an
evolution
of
that
where
it
can
be
run
on
any
type
of
cluster.
It
doesn't
need
to
have
any
external.
You
know,
access
to
you
know
any
outbound
management
platforms.
Any
apis,
you
know,
doesn't
have
to
connect
into
anything
to
forcefully
reboot
a
machine.
E
E
Let's
say,
for
example,
the
machine
is
actually
still
running.
It's
just
not
contactable
the
poison
pill,
steps
in
and
it
self
fences
itself
it
turns
itself
off.
So
in
both
of
those
situations,
the
rest
of
the
surviving
nodes
know
that
either
it's
definitely
gone
or
it
has
made
sure
itself
is
gone,
and
that's
why
it's
called
a
poison
pill.
Essentially
that
node
is
taking
the
poison
pill
and
sacrificing
itself
for
the
good
of
the
rest
of
the
cluster.
E
So
this
poison
pill
operator.
Forgive
me,
I
can't
remember
exactly
when
it
is.
I
think
we
had
some
delays
on
making
this
available,
because
it
was
a
packaging
of
the
operator
and
putting
the
operator
into
olm,
but
this
is,
as
I
said,
something
you
can
deploy
on
top
of
your
cluster
requiring
no
external
integrations.
B
And
I
want
to
point
out
that
this
is
particularly,
I
won't
say,
important,
but
relevant
if
you're
using
persistent
volumes,
because
if
the
node
goes
down,
if
it's
marked
unreachable,
if
there's
pvcs
attached
those
don't
get
released,
so
it'll
hold
up
rescheduling
those
pods.
So
the
poison
pill
basically
gives
you
a
way
of
forcefully
removing
all
of
that
and
allowing
all
that
workload
to
be
rescheduled.
E
I
know
that
it
that
machine
has
gone
away.
I
know
it's
safe
for
that
workload
to
be
rescheduled
now,
kubernetes
will
go
ahead
and
do
that
it's
it's!
You
know
it's
assuming
you've
taken
that
action.
You
know.
Otherwise
you
might
end
up
with
some
data,
corruption
or
data
consistency
problems.
But
it's
assuming
that
that
action
has
taken
place
with
both
the
external
remediation
that
we
can
do
with
bare
metal,
ipi
and
the
metal
cube
integration
or
poison
pill.
It
takes
care
of
both
of
those.
E
B
Our
hope,
9,
I
see
your
question:
will
the
poison
pill
operator
be
able
to
communicate
with
the
vsphere
api?
So
no
because
it
relies
on
the
other
functions
of
openshift.
So
when
resays
it
deletes
the
node,
it
literally
just
uses
machine
operator,
machine
api
and
deletes
the
node
and
then
relies
on
the
machine
set
to
create
a
new
one.
So
it
doesn't
have
to
do
any
direct
integration.
E
So
sorry,
just
just
just
one
more
thing:
it
deletes
the
node,
but
it's
assuming
that
that
machine
or
in
that
in
the
vmware
example
that
machine
is
going
to
reboot,
it
will
reboot
and
it
will
re-register
itself
when
the
kubla
comes
up.
So
it's
it
doesn't
even
need
to
do
anything
with
the
machine
set
that
machine
set.
The
number
will
actually
stay
as
it
was.
All
we're
doing
is
telling
kubernetes
that
that
machine
has
definitely
gone
away.
B
That's
a
good
point.
I
think
it's.
The
machine
health
check
is
the
one
that
will
remove
the
node,
whereas
poison
pill
just
removes
it
and
reboots
it
and
then
lets
it
come
back
right.
So
you
you
touched
on
a
couple
of
things
inside
of
their
reese,
that
that
are
tangential
to
what
we
are
are
talking
about
today
or
or
not
really
tangential,
but
they
are
very
relevant
to
what
we
are
talking
about
today.
B
A
B
Yeah
and
ben
is
one
of
those
super
smart
technical
people
that
I
use
as
an
escalation
point.
So
just
remember
between
the
the
three
folks
who
have
joined
us
today
like
andrew
knows
nothing
all
the
hard
questions
get
get
passed
along
so
yeah.
So
the
first
thing
that
I
want
to
highlight
is
from
andrew's
perspective.
We
overload
the
term
bare
metal.
B
We
use
bare
metal
to
refer
to
both
an
installation
platform,
I.e
physical
servers,
as
well
as
an
installation
method
which
is
now,
I
think,
we've
gotten
better
about
it
in
the
docs,
but
it
is
now
the
platform
agnostic
or
install
to
any
platform
mechanism.
So
I
tend
to.
I
avoid
the
term
bare
metal
upi,
even
though
I
know
quite
a
few
folks
use
that,
because
upi
still
implies
that
there
is
a
cloud
provider
involved
bare
metal
ipi.
There
absolutely
is
a
cloud
provider
involved
and
I
think
that's
surprising
to
some
folks.
B
B
D
Sure
so
there
are
many
reasons
why
we've
been
learning
from
customers.
They
want
to
have
kubernetes
environmental
reasons
like
you
have
workloads
that
require
access
to
say
a
gpu
right,
and
it
needs
to
be
a
gpu
passed
to
the
workload
to
do
whatever
they
need
to
do
so.
This
is
direct
access
to
to
the
hardware,
sometimes
they.
D
Similarly,
they
need
to
process
large
amounts
of
data
through
the
network
and
many
servers
these
days
come
with
sri
ob
enable
mix
right
and
you
do
the
same,
but
you
need
access
to
the
hardware
in
order
for
your
workloads
to
access
this
type
of
of
nics.
So
these
are
two
examples
very
directly
related
to
running
workloads
directly
on
on
the
hardware
right
with
no
layers
in
between
then
layers
in
between
well,
when
you
have
open
shift
kubernetes
on
top
of
another
platform,
all
of
a
sudden
you
are
managing.
D
You
have
to
manage
two
platforms
right
at
least
plus
the
bare
metal
itself,
and
usually
that's
not
a
problem.
In
fact,
many
customers
come
from
using
if
you
are
on
prem,
say
openstack
or
aws,
or
you
know
any
other
public
cloud
provider
as
well,
and
then
you
start
with
kubernetes,
then
you
install
openshift
and
well.
D
You
all
have
made
like
a
transition
into
this
world
through
the
multiple
platforms
that
you
are
dealing
with,
but
then
you
realize
hey
and-
and
this
is
direct
feedback
we
have
from
from
large
customers
having
to
deal
with
very
large-scale
clusters
for
different
purposes.
Right
and
they
say,
look
if
I
can
get
rid
of
one
of
the
platforms
that
I
need
to
manage
once
I
am
only
working
with
kubernetes
working
with
openshift,
then
my
life
is
going
to
be
so
much
easier.
D
Once
you
are
working
with
openshift
on
bare
metal,
if
we
can
help
with
managing
this
bare
metal-
and
here
is
where
what
you
mentioned
before
a
metal
cube
comes
in,
or
rather
the
bare
metal
operator
that
uses
metal
cube
right
as
as
the
layer
that
manages
the
the
yeah
management
of
the
different
types
of
hardware.
So,
with
all
of
these,
we
provide
a
solution
where
the
management
of
the
hardware
is
probably
less
complex
than
if
you
did
everything
yourself
and
do
it
yourself
involves.
I
need
a
dhcp
server.
D
I
need
a
pc
server.
I
need
to
manage
images
to
configure
to
install
and
configure
the
operating
systems.
All
of
this
is
something
that,
with
bemetal
api,
we
are
taking
care
of
right.
These.
These
are
things
that
will
alleviate
a
little
the
problem
of
having
to
manage
the
the
physical
infrastructure
so
yeah.
I.
B
Want
to
point
out
that
that
is
just
like:
we
have
a
machine
api
provider
for,
say
vsphere.
You
know,
I
hope
not.
You
were
just
talking
about
that
of
I
can,
through
the
machine
set
mechanism
which
uses
machine
api
basically
say:
hey
vmware
provision
me
a
new
virtual
machine
that
I'm
going
to
use
for
you
know
whatever
we
can
do
the
same
thing
in
this
instance
with
physical
servers.
D
That's
right,
yeah
and
that's
the
magic
that
we
have
with
thanks
to
metal
cubes,
as
I
would
say,
the
core
technology
behind
this
and
metal
cube
using
another
technology.
With
years
of
experience
in
managing
hardware,
which
is
ironic
that
comes
from
the
openstack
project
and
ironic
over
the
years
has
specialized
in
managing
it.
You
may
think
it's
simple,
but
it's
it's.
D
It's
a
lot
of
operations,
a
lot
of,
say
polish,
that
we've
been
doing
to
it
over
the
years
so
that
in
this
business,
in
this
case
of
managing
hardware,
we
have
got
very,
very,
very
good.
I
would
say
so
putting
these
two
technologies
together,
wrapping
them
around
with
the
bare
metal
operator
and
using
this,
and
they
want
to
do
the
installation
over
ipi
and
on
day,
two
to
do
maintenance.
D
In
fact,
you
know
when
you
deploy
with
ipi
one
of
the
things
that
we
do
is
we
deploy
the
machine
api
and
then
the
servers
that
are
you
know
the
the
data
structure
is
bare
metal
host.
So
this
parameter
host
in
reality
is
a
machine
which,
in
turn,
is
a
node
to
the
eyes
of
open
shift
right
and
the
operations
that
you
do
in
a
node.
D
B
Yeah,
so
I
I
don't
reese,
I
know-
or
I
think
you
have
a
demo
staged
and
I
don't
know
if
you
or
ben
are
able
to
answer.
I
think
when
you
look
at
the
bare
metal
install
process.
You
know
my
favorite
is
usually
to
do
like
an
open
shift.
Install
explain,
there's
a
lot
of
things
that
go
into
that
and
that
is
effectively
and
I
giggle
a
little
bit
ramon.
When
you
say
you
know,
yeah
managing
hardware
is
simple.
Well,
no,
it's
it's
as
a
human
managing
one
piece
of
hardware,
it's
relatively
simple!
E
E
E
You
know
it's
got
all
of
the
networking
and
storage,
and
you
know
it
does
all
of
that
for
us,
so
from
a
an
onboarding
of
a
new
virtualization
or
a
new
public
cloud
platform,
it's
relatively
straightforward,
I'm
not
going
to
you
know
say
that
our
engineers
that
go
and
do
all
our
integration
that
their
job
is
easy.
I'm
not
saying
that
for
one
minute,
but
when
we
have
to
do
this
for
bare
metal,
it
becomes
a
little
bit
more
of
a
challenge.
E
Those.
So
if
you
were
a
customer
of
openshift
before
we
had
done
all
of
this
bare
metal
integration
work,
yes,
we
had
all
the
capabilities
to
dynamically
scale.
Our
infrastructure
make
use
or
make
reuse
of
underlying
storage
and
networking
efficiencies
and
push
that
all
the
way
through
into
the
open
shift
layer.
We
wanted
to
provide
a
similar
capability
for
bare
metal,
but
there
is
no
api
for
bare
metal.
D
E
D
I
I
would
say
yeah
and
one
of
the
differences
is
that
say
that
you
are
aws.
Somebody
is
managing
all
these
hardware
somewhere
right,
probably
thousands
of
engineers.
But
it's,
however,
that
they
know
it's
hardware
that
they
are
familiar
with
it's
hardware
that
needs
to
comply
with
a
series
of
automations
that
they've
put
in
in
through
the
years,
but
in
what
we
are
doing,
we
need
to
deal
with
a
customer
xyz
type
of
hardware,
and
that
can
be
it's
usually
common
hardware
right.
D
Well,
not
all
the
time,
but
usually
it's
hardware
that
you
would
know,
but
it's
hard
that
each
of
them
has
different
tweaks
different
areas
that
you
need
to
look
after,
so
that
you
can
manage
them
in
a
standardized
well
way.
So
this
is
what
we've
done
and
with
metal
cubed
and
the
integration
in
it
of
ironic
ironic
has
drivers
for
idrac
for
dell
for
ilo
in
hpe
for
irmc
in
fujitsu,
for
you
name
it
redfish,
especially.
We
probably
need
to
talk
a
little
bit
about
redfish,
which
is
a
standard
say,
not
implementation.
D
You
can
buy
a
specification
of
how
to
manage
hardware
through
apis.
Redfish,
in
fact,
is
helping
us
a
lot.
It's
not
perfect,
just
yet
it's
implementation,
at
least
it's
not
perfect,
but
it
has
helped
us
a
lot
to
treat
hardware
in
a
very,
very
similar
way,
regardless
of
which
vendor
you.
You
have
chosen
right,
but
all
of
this
to
say
that
all
these
difficulties
in
managing
different
types
of
hardware,
which
can
be
anything
that
your
customer
may
have,
they
are
solved
to
a
degree
right.
D
B
I
can
tell
you
it's
it's
light
years
better
than
what
I
used
to
do,
which
was
using
a
serial,
concentrator,
telnet
in
and
then
access
the
serial
console
for
for
sun
and
then
oracle
servers,
and
it
was
absolutely
miserable
to
try
and
automate
and
and
get
that
stuff
done
compared
to
you
know
the
the
pretty
impressive
and
amazing
things
that
we
have
available
today.
It's
true.
D
And
by
the
time
you
have
automated
something
for
this
specific
infrastructure
or
piece
of
hardware,
you
get
something
new
and
you
need
to
change
the
the
scripts.
The
way
you
address
the
bmc's
if
they
have
etc
so
having
this
abstraction
layer
and
with
the
years
of
experience
that
we
have
in
this
abstraction
layer
has
been
key
for
us
to
be
able
to
publish
and
release
all
this,
this
software
for
managing
their
method
so
quickly.
B
B
And
I
think
we
all
you
know,
have
different
opinions
or
different
perspectives
on
that
I
will
say
when
andrew
answers
that
question,
I
usually
break
it
down
to
two
things.
So
one
is
test
and
integration
and,
most
importantly,
support
of
all
of
the
components
that
make
up
openshift.
So
openshift
is
kubernetes.
It
has
a
creamy
kubernetes
center
at
the
you
know,
that
is
the
foundation,
and
then
we
build
upon
right.
We
add
on
a
bunch
of
value
to
that,
so
think
core
os.
B
You
know
red
hat
enterprise,
linux
coreos,
the
machine,
config
operator
and
all
the
things
to
manage
that
underlying
operating
system.
You
know
a
registry,
the
admin
gui
right.
All
of
that
stuff.
That
makes
openshift
open
shifted,
not
just
kubernetes
and
importantly,
taking
all
of
that
and
testing
it
together,
making
sure
that
it's
all
going
to
work
together,
making
sure
that
you
know
when
you
upgrade
from
version
to
version
you
have
I'm
not
going
to
say
a
perfect.
B
You
know
100
chance
of
it
always
working
every
time,
but
a
very,
very,
very
good
chance
that
it
will,
and
if
it
doesn't,
you
can
pick
up
the
phone
and
you
can
call
somebody
so
the
other
one
of
those
is
usually
you
know,
kind
of
related
to
all
of
that
which
is
to
really
you
know.
Red
hat's
perspective
is
to
go
into
production
with
kubernetes.
B
You
need
more
than
just
kubernetes.
You
know
you
need
things
like
life
cycle
management
of
each
one
of
those
components
to
include
the
underlying
operating
system,
and
you
know
you
need
a
logging
solution.
You
need
metric
solution,
you
need
all
of
those
things
which
you
know,
openshift's
goal
is
to
provide.
All
of
that,
so
I
saw
chris
dropped
out.
He
waved
goodbye,
so
thank
you
for
joining
us.
Chris,
we'll
see
you
next
time.
B
B
E
E
E
So
the
big
thing
you
will
notice
is
that,
on
the
left
hand,
side
of
the
the
overview
page
you'll
see
provider
is
bare
metal.
So
this
is
utilizing
all
of
the
bare
metal
capabilities
and
the
functionalities
that
ramon
was
just
explaining.
So
behind
the
scenes
we
do
have
metal,
cubed,
providing
us
with
or
providing
open
shift
with
an
api
to
aggregate
control
and
automate
physical
hardware.
E
E
Now
in
here
you
have,
for
example,
a
management
address,
because
typically,
if
you're
going
to
do
an
automated
bare
metal
installation
with
ipi,
you
need
to
provide
some
additional
information
to
the
installer.
So
it
knows
how
to
go
out
there
and
power.
These
machines
on
you
know,
set
them
to
to
boot.
Up
in
this
environment,
I'm
using
more
traditional
ipmi
with
pixi,
but
as
my
mom
was
saying,
there
is
possibilities
to
use
redfish
as
well.
Now
what
I
will
show
you
is
the
installation
convic.
E
So
this
describes
how
the
openshift
installer
or
gives
gives
all
of
the
configuration
information
to
the
openshift
installer
so
that
it
can
run,
and
there
are
a
few
very
important
details
here.
So,
first
of
all,
if
I
go
down
to
platform,
it
is
bare
metal.
So
we
are
specifically
saying
when
you
do
this:
open
shift:
installation
utilize,
the
bare
metal,
which
is
you
know,
utilizes
metal,
cubed
behind
the
scenes
to
drive
this
installation
at
the
top.
I've
specified
how
many
machines
I
want
so
three
masters
and
top.
E
We
got
two
workers
and
then
we
have
to
specify
all
of
the
individual
hosts.
We
have
to
tell
it
which
machines
to
use,
and
so
we
have
to
specify
bmc.
This
can,
of
course,
as
I
said,
be
redfish,
but
in
my
environment,
I'm
just
using
ipmi
a
username,
a
password
and
a
unique
identifier
which
in
this
case
is
going
to
be
its
mac
address.
So
when
these
machines
power
up,
they
will
attempt
to
dhcp
they'll
pixie
boot
and
they
will
be
identified
by
their
mac
address.
E
B
E
So,
in
a
very
similar
way
to
how
most
ipi
installations
work,
we,
when
you
run
openshift,
install
it
provisions
a
bootstrap
machine
now,
this
bootstrap
machine
will
essentially
help
bootstrap
the
cluster
and
then
it
will
hand
over
control
and
responsibility
to
the
resulting
cluster
at
the
end.
But
the
way
that
we
we
set
this
up
is
that
bootstrap
machine
temporarily
runs,
as
ramon
said,
openstack
ironic
behind
the
scenes
and
that's
what
we
use
to
automate
the
provisioning
of
the
bare
metal
machines.
E
So
we
spin
up
a
really
really
small
openstack
ironic
instance
on
top
of
that
bootstrap
vm.
That
goes
ahead
and
starts
the
bootstrap
process
off.
Pixie
boots
the
machine.
So,
as
you
said,
it
starts
up
a
dhcp
server
there.
It
lays
down.
The
image,
helps
get
the
cluster
running
then
that
bootstrap
machine
steps
back
and
lets
the
cluster
itself
continue
the
rest
of
the
process,
so
that
initial
bootstrap
process
is
really
only
responsible
for
the
initial
deployment
of
the
masters.
E
Openstack
ironic
then
gets
deployed.
So
I've
got
a
rogue
cat
here.
Trying
to
push
my
screen
around
the
openstack
ironic
will
then
get
relaunched
on
the
resulting
cluster.
It
will
then
go
ahead
and
deploy
the
additional
workers,
which
is
why,
on
here,
you
will
see
the
three
masters
are
considered
externally,
provisioned
because
they
were
deployed
by
the
bootstrap
vm,
and
these
two
workers
are
provisioned
because
it
it
this
cluster
has
provisioned
them
in
the
the
latter
part
of
the
installation.
B
E
It
will
work
on
any
type
of
cluster.
It
could
be
upi
ipi,
typically
with
bare
metal.
We
have.
We
have
the
external
remediation
through
metal
cubed,
so
you
can
set
up
a
machine
health
check
which
will
monitor
the
machines
and
then,
when
it
goes
over
a
certain
period
of
time,
the
one
of
the
other
machines
will
contact.
E
You
know
this
ipmi
address
of
the
failed
node
and
will
force
it
off,
and
so
it
can
short-circuit
that
remediation
process.
So
this
is
really
great
if
you
want
high
availability
and
one
of
the
really
good
use
cases
for
this
is
for
running
openshift,
virtualization
or
cnv.
Let's
say,
for
example,
you
have
a
virtual
machine
and
it's
critical
for
whatever
reason
there's
one
of
it
and
you
need
to
know
that
that
will
get
restarted
very
very
quickly.
You
essentially
have
two
choices
going
forward.
You
have
the
external
remediation.
E
If
you're
running
bare
metal
running
bare
metal
ipi,
if
you're
using
upi,
you
now
have
another
option
with
the
poison
pill
in
that
again,
going
back
to
what
I
was
saying
earlier,
either
that
machine
has
gone
away
and
it's
definitely
gone
away
or
it
has
consumed
the
poison
pill.
So
in
both
of
those
circumstances,
after
a
defined
amount
of
time.
You
know
that
again,
it's
either
gone
because
it's
caught
fire,
it's
you
know
power's
gone
or
it
has
consumed
that
poison
pill.
So
it
can
relocate
that
that
vm.
B
To
to
quickly
answer
your
question:
how
are
entitlements
calculated
so
entitlements?
You
only
need
to
entitle
compute
nodes
that,
where
you're
running
your
applications
at
so
control
plane
nodes,
unless
you
have
marked
them
scheduleable
and
have
your
applications
running
there,
you
don't
need
to
entitle
them
same
thing
with
infranodes
and
I'll,
I'm
digging
for
the
link
for
the
subscription
guide,
as
well
as
our
hope.
Nine.
Thank
you
for
posting
that
that
link.
E
Okay,
so
I
think
I've
pretty
much
shown
everything
I
wanted
to
in
this.
It's
very
similar
to
any
other
ipi
configuration
you're,
specifying
the
vips
that
you
want
to
use,
but
the
big,
the
big
change
here
is
when
you
specify
the
hosts
you're,
actually
telling
it
what
to
use
and
how
to
contact
these
things
behind
the
scenes.
E
Now,
what
you
will
find
on
a
bare
metal
cluster
is,
there
is
a
there
is
a
pod
in
open
shift
machine
api,
and
this
is
where
you
have
the
metal
cube,
pod
and
so
inside
of
here.
This
is
where
all
of
the
cluster
management,
the
bare
metal
management-
actually
happens
so
inside
here,
you
will
find
there
are
various
different
openstack
ironic
pods,
and
these
are
the
ones
that
actually
manage.
E
You
know
when
openshift
has
to
say
you
know,
restart
this
machine
again
from
a
remediation
perspective,
or
I
want
to
add
a
new
machine.
It
has
to
go
via
openstack
ironic
to
do
it,
and
so
we
just
provide
this
as
an
interface.
Essentially,
translating
all
of
the
well-known
well-loved
openshift
features
into
you
know
give
us
the
ability
to
do
the
same
on
on
bare
metal
as
well,
and
just
to
prove
that
openstack
is
actually
running
behind
the
scenes.
E
I
can
I've
got
an
openstack
client
pod
here
and
if
I
just
this
is
literally
just
a
a
pod,
that's
running
on
top
of
my
openshift
cluster,
that
just
has
the
openstack
command
line
tools
installed
and
I've
generated
a
a
convict
here.
I
just
grabbed
the
password,
which
is
just
a
secret,
and
it's
always
running
on
a
very
specific
ip
address,
and
I
just
pasted
it
in
the
password
there.
B
E
Yeah
exactly,
and
so
we
have
a
lot
of
experience
in
managing
bare
metal.
We
haven't
reinvented
the
wheel
here.
We
knew
that
we
needed
a
component
to
handle
the
you
know
the
basics,
like
turn
the
machine
on
and
off
set
it
to
pixie
boots
clean
the
instance
so
that
they
can
be,
you
know,
reused.
Should
we
want
to
and
ironic
has
all
of
these
various
different
drivers,
these
interfaces,
these
features,
it
makes
sense
to
reuse.
Those
capabilities
and
ironic
here
is
standalone.
It
doesn't
have
any
of
the
other
openstack
components.
B
E
E
The
open
shift
ui.
So
if
we
go
out
back
down
to
bare
metal
hosts-
and
we
were
to
say,
go
on
to-
let's
just
pick
our
worker
one-
we
have
the
power
state
here.
We
have,
you
know
various
different
information
about
it.
It
collects
insights
and
information
about
it.
It
also
gets
additional
information
because
we've
inspected
this
machine
before
we
know
all
about
its
network
interfaces.
So.
B
E
On
absolutely
and
again,
the
big
driver
behind
this
is
to
provide
an
equivalence.
You
know
for
customers
to
have
experience
in
running.
On
top
of
you
know
any
other
infrastructure
with
aws
vmware
openstack.
We
can
get
that
insights.
We
wanted
to
provide
that
same
experience
with
bare
metal
and
that's
really
where
metal,
cubed
and
the
openstack
sorry
openshift
ipi.
It's
really
bridging
that
gap.
B
Yeah
this
is
this:
is
it
it
completes
without
even
realizing
it
right?
At
least
for
me,
it
completes
the
whole
story
of
you
know
with
openshift,
I
I
manage
the
applications
I
manage
kubernetes.
I
manage
the
underlying
operating
system
and
I
manage
the
underlying
nodes
kind
of
regardless
of
where
those
nodes
are
deployed.
At
that's
super
interesting.
E
So
what
I
will
show
you
is
well,
let's
say:
I've
got
this
cluster
now
and
I
want
to
add
more
k
more
capacity
to
it.
I
want
to
add
more
nodes.
Well,
if
you
were
using
a
typical
provider
such
as
again
vsphere,
aws,
openstack
or
whatever
it
might
be,
you'd
simply
go
in
here.
You'd
you'd,
edit,
your
machines-
and
you
would
you
know,
add
another
one.
It
would
automatically
spawn
that
now.
This
works
exactly
the
same
way
inside
of
bare
metal.
E
E
The
first
one
is
a
secret,
and
this
is
essentially
a
username
and
password
for
the
bmc
of
my
node,
and
then
I
have
a
new
bare
metal
host
object.
I
give
it
a
name.
I
give
it
the
the
the
mac
address
of
that
particular
machine.
I
give
it
the
ipmi.
The
credentials
are
pulled
from
this
secret.
I've
defined
and
root
device
hints
again
just
saying
deploy
on
this
disk,
which
of
course,
is
useful.
If
you
have
real
bare
metal
machines
and
they
have
10
disks,
you
want
to
make
sure
deploy
onto
this
disk.
E
So
what
I'll
do
is
I'll,
just
I'll
see,
apply
bmh
and
I
need
to
put
it
into
shift
machine
api,
so
I
now
have
defined
to
this
additional
work
and
you'll
see
immediately
in
the
ap
in
the
ui.
I
have
this
additional
machine,
it's
registering,
so
it
is
going
to
go
ahead
and
it's
going
to
attempt
to
contact
that
machine.
It's
going
to
populate
it
into
openstack
ironic!
Look!
E
You
can
already
see
it
see
it's
going
into
the
inspecting
mode,
so
it's
going
to
power
on
this
physical
machine,
it's
going
to
collect
information
about
it
and
it
will
sit
there
waiting
waiting
for
us
to
consume
it
by
increasing
a
machine
set
or
you
know
getting
it
ready
to
actually
be
used
now.
This
obviously
takes
a
few
minutes
to
do.
E
If
I
go
into
my
bare
metal
node
list
again,
you'll
see
that
we
now
have
this
worker
three,
so
it's
populated
inside
of
ironic.
It
hasn't
yet
provisioned
it,
but
it's
powering
on
because
it's
state
is
inspect
weight,
so
we're
just
waiting
for
that
machine
to
actually
do
something
now.
Hopefully
let
me
see
if
I
can
bring
that
up
here.
E
E
Yeah,
I'm
actually
connecting
to
machines
in
the
data
center
here,
but
it
is
a
pretty
good
machine
right.
So
this
is
my
work.
Three,
the
one
I'm
just
provisioning
and
so
you'll
see
that
it's
booting
up
into
the
ironic,
the
ironic
python
agent
environment,
at
which
point
it
will
essentially
get
it
ready
so
that
it
can
be
consumed.
It
will
stay
there
just
essentially
just
just
waiting
for
us
to
to
to
use
it.
So
if
I
check
here
now,
it
should
be
it's
probably
okay,
it's
still
inspecting.
I
said
this.
B
So
I'm
looking
through
the
questions
here,
our
hope,
nine.
Thank
you
for
pointing
out
that
you
can
get
a
developer
subscription.
So
if
you
have
a
red
hat
developer
account
that
also
entitles
you
to
the
same
16
cores
of
openshift
that
you
would
get
with
you
know,
60.
I
think
you
get
16
rail
licenses
and
all
that
other
stuff
I
haven't
checked
recently.
There
was
an
issue
on
the
back
end
when
you
were
changing.
If
you
log
into
the
console
and
go
to
associate
that
developer
license
with
your
openshift
cluster.
B
There
was
an
error
with
that.
I
haven't
checked
on
that
in
the
last
few
weeks.
Hopefully
they've
got
that
remediated
I'll
I'll,
follow
up
on
that
and
then
oh
master
light
was
asking
about
using
fedora,
because
I
I
guess
they
noticed
that
you're
using
fedora
reese.
So
so
I
switch
back
and
forth
between
mac,
os
and
fedora,
but
there's
a
lot
of
folks
in
red
hat
who
use
fedora
as
well
as
what
we
call
the
the
rel
csb
the
corporate
standard
build.
B
E
E
So
you
have
to
deploy
bare
metal
ipi,
so
all
of
the
resources
you
need
are
automatically
deployed
and
configured
when
you
select
bare
metal
as
the
platform
that
you
want
to
use
as
part
of
your
installation
convict,
you
don't
have
to
define
any
additional
resource
definitions
to
do
this.
I
applied
this
bmh
in
the
using
the
cli.
You
could
just
as
easily
go
in
here
and
use.
I
could
use
the
dialog
and
it'll.
Ask
me
what
last
me
the
details.
E
B
That
sounds
like
some
experimentation.
That
ben
might
have
done
at
some
point,
so
I'll
I'll
point
out
that,
like
with
vsphere,
upi
or
rev,
or
no,
not
rev
or
openstack,
or
basically
all
of
the
other
upis,
except
for
rev,
when
you
install
or
you
deploy
a
cluster,
the
cloud
provider
is
still
there.
So
if
you
do
vsphere
upi,
it's
still
the
vsphere
cloud
provider,
so
after
deployment
you
can
add
in
machine
sets,
and
you
can
dynamically.
You
know
scale
nodes,
just
like
you
would.
B
B
Yeah,
so
the
the
reason
why
that's
important
is
you
can't
mix
cloud
providers
and
that's
a
kubernetes
limitation
so
effectively
you
can
technically,
you
could
add
a
node.
So
let's
say
I
have
a
non-integrated
install
on
physical
servers
right
cloud.
Pro
no
cloud
provider
provider
equals
none
and
I
wanted
to
add
some
nodes
that
have
a
cloud
provider
of
bare
metal.
They
would
probably
join
the
cluster
but
then
would
be
evicted
after.
I
think
it's
no
more
than
five
minutes
and
basically
kicked
out
by
the
underlying
mechanisms.
B
E
Time
whilst
you're
doing
that
andrew
what
I
just
wanted
to
do,
because
this
might
take
a
few
minutes,
I
know
we're
running
up
against
the
clock
here
now
that
this
machine
has,
you
know,
passed
the
inspection
stage,
it's
going
into
an
available
state,
so
this
is
kind
of
sitting
in
a
pool
waiting
for
me
to
assign
it
it's
it's.
No,
it's
not!
In
my
nodes.
I
still
have
my
my
three
masters
and
two
workers.
What
I'd
need
to
do
is
go
into
my
machine
sets.
E
I
can
scale
this
and
say
three
and
what
that
will
now
do
is.
If
I
go
into
my
bare
metal
note:
it'll
go
into
provisioning
state.
So
at
this
point
it's
going
to
write
the
core
os
disk
image
to
the
physical
disk,
and
it's
going
to
reboot
that
machine
and
it
will
join
the
cluster
just
like
any
other
new
node
would-
and
I
would
dynamically
scaled
my
environment
with
with
plenty
more
more
more
resource.
E
If
I
look
at
this,
it'll
probably
now
show
that
it
has
an
instance.
It
does
instance,
and
it
is
going
to
a
deploying
state
and
again
we're
literally
using
openstack
ironic-
to
drive
the
deployment
here,
because
it
has
well
mature
ways
of
doing
that
and
we're
literally
just
using
a
very
small
component
of
openstack
to
to
do
this.
B
Lsi,
how
do
you
manage
to
always
use
the
latest
core
os
pixy
image?
So
you
you
don't
with
ipi
so
with
openshift
and
ipi,
whether
it's
you
know:
rev
ipi,
vcr
ipi.
Basically,
when
you
deploy
the
cluster
it'll
upload
a
template
virtual
machine,
any
new
nodes
when
they
are
created
by
machine
set,
get
created
from
that
template
and
the
first
thing
that
happens
when
it
boots
is
it'll.
It
connects
to
machine
config,
operator
and
machine
config
operator
says:
go
and
download
this
new
core
os
image
and
lay
it
out.
B
Yes
same
thing
happens
here.
Basically
it
boots
up
to
core
os.
It
connects
to
machine
config
operator.
It
says:
hey
go
in
you
know
it's
rpm
os
tree
so
go
and
apply
this
image,
and
it
does
exactly
that.
So
the
good
news
is
with
core
os.
So
long
as
you
are
on
the
current
or
older,
that's
the
behavior.
If
you're
on
a
newer
version,
it
gets
weird
so
yeah.
E
A
A
Can
we
back
up
to
that
install
config
just
so
you
can
clarify
so
you
mentioned
that
you've
got
it
set
up
because
you're
doing
it
for
caching
purposes,
but
customers
that
were
using
this
in
a
disconnected
environment
also
would
have
a
similar
string
in
there
to
point
to
their
local
cache
copy
of
the
archives
image.
Correct.
B
D
Is
to
a
degree
because
zero
touch
provisioning
uses
ipi
to
deploy
the
initial
cluster
and
then
obviously
the
problem
that
it
shops
is
very
specific
right.
It's
a
provisioning
without
any
touch.
I
guess
that's
how
we're
calling
it
zero
touch
provisioning,
but
it
streams
line.
It
streamlines
the
whole
workflow
from
deploying
your
first
cluster.
That
will
be
your
cluster
say
hub
cluster
right
of
clusters
that
will
help
you
to
deploy
the
rest
of
the
nodes
with
ztp.
B
D
So
single
note,
open
shift
is
a
very
specific
use
case
and
no,
it's
not
going
to
get
you
in
trouble,
andrew,
but
first
off
we
one
single
node
openshift
many
times,
because
we
don't
even
have
space
in
the
data
center
for
more
customers
are
saying.
Look.
I
cannot
even
install
openshift
in
a
cluster
of
three
nodes
right,
which
we
support
as
well
with
ipi
what
many
people
call
a
compact
cluster,
so
you
need
a
provisioner
note
to
deploy
openshift
with
ipi
right,
the
node.
D
That
risk
was
showing
us
and
described
for
us
if
you
have
sno
and
you
need
a
node
to
provision.
Sno
single
node,
open
shift,
you're
kind
of
defeating
the
purpose
right.
That
doesn't
mean
that
we're
not
looking
into
it,
because
we
are
actively
looking
into
that
the
bootstrap
machine
that
bootstraps
the
entire
cluster
with
ipa.
This
is
something
that
we
want
to
get
rid
of
right.
D
We
want
to
do
yeah,
an
installation
that
doesn't
depend
on
a
production
or
not,
even
though
having
said
that,
with
the
current
ipi
workflow,
you
can
reuse
this
provisional
node
as
a
worker,
so
say
that
you
have
five
nodes.
You
are
not
gonna
be
using
a
four
nodes
cluster,
just
because
you'd
need
the
provisioning
nodes,
and
so
that's
there,
but
with
single
node
open
shift.
E
B
B
D
No,
I
I
wanted
to
say
that
this
is
important.
The
point
that
you
just
made,
because
this
is
what
we
call
redfish
using
virtual
media
with
virtual
media.
We
are
mapping
that
iso
remotely
through
the
vmc
and
through
redfish
and,
as
you
said,
we
don't
need
to
ask
for
vlans
for
provisioning
or
even
a
network
for
provisioning.
Nothing.
All
we
need
is
access
to
the
nodes
from
wherever
we
are
doing
the
provisioning,
and
that
can
be.
D
B
Few
minutes
over
I
want
to
be
respectful
of
everybody's
time.
Thank
you
very
much,
rhys
ben
and
ramon
for
joining.
Today.
It's
been
an
absolute
pleasure
having
you
all
on.
I
know
I've
learned
several
things
to
our
audience.
Thank
you.
So
much
for
joining
today
really
appreciate
the
conversation.
The
questions,
if
you
have
anything
that
you
weren't
able
to
get
out
here
during
the
stream,
if
there's
anything
else
that
you
would
like
to
ask,
please
don't
hesitate
to
reach
out
to
me.
B
You
can
contact
me
on
social
media
at
practical,
andrew
on
twitter,
just
like
you've
seen
me
chatting
across
the
various
platforms,
or
you
can
always
reach
out
to
me
via
email,
andrew.sullivan
redhat.com.
I
won't.
I
won't.
Have
you
all
toss
out
your
contact
information
necessarily,
but
I'm
I'm
more
than
happy
the
worst
thing
that
happens.
You
know
I've
heard
from
a
number
of
you.
The
worst
thing
that
happens
is
well.
B
I
don't
know
the
answer,
but
let's
track
down
the
right
people
who
do
and
we'll
get
those
answers,
so
don't
ever
hesitate
to
reach
out
with
that
being
said,
please
tune
in
tomorrow.
Just
a
reminder:
tomorrow
we
will
have
the
what's
new
in
openshift
4.9
live
stream
happening
that
is
at,
I
want
to
say,
10
a.m.
Let
me
bring
up
my
calendar
real
quick
here.
B
I
don't
know
I
I
know
all
of
you
all
red
hatters,
you
know
steve
steve
is:
has
this
really
crazy
talent
where
he
can,
like?
I,
I've
seen
him
present,
holding
a
microphone
in
one
hand
typing
with
the
other
hand,
and
talking
completely
separately
before,
and
it
just
blows
my
mind
like
I
can't
type
and
talk
at
the
same
time,
because
my
fingers
say
what
my
mouth
is,
or
vice
versa.
B
So,
yes,
tomorrow
at
10
a.m.
Eastern
time
apologies
for
not
converting
time
zones
is
the
what's
new
and
openshift
4.9
session
next
week
we
will
not
have
a
stream
here,
please
do
be
sure
to
tune
in
to
all
of
the
kubecon
stuff
that's
going
on,
and
I
will
go
ahead
and
replace
that
link
in
the
chat
here
and
last
but
not
least,
I
hope
everybody
has
a
great
rest
of
their
week
and
please
stay
safe
out.
There.