►
Description
OpenShift 4.6 introduced some new capabilities for clusters deployed to Red Hat Virtualization (RHV). This stream we'll be joined by Peter Lauterbach, Product Manager, to discuss the changes and see some features in action. As always, bring your questions, related to the topic and guest or not, and we'll do our best to answer them!
A
Good
morning,
good
afternoon,
good
evening,
wherever
you're
hailing
from
welcome
to
another
episode
of
the
openshift
administrator
office
hours,
I'm
chris
short
executive
producer
of
here
of
openshift
tv
joined
by
the
one
and
only
andrew
sullivan
and
special
guest
peter
louderback.
Today,
andrew
you
want
to
tell
us
what
we're
talking
about
today.
Yeah.
B
Thankfully,
there's
only
one-
and
only
one
of
me,
yeah
sure
that
my
my
wife
and
kids
all
agree
so
yeah.
This
is
the
openshift
administrator's
office
hour,
which
means
that,
like
all
of
the
other
office
hour,
shows
that
we
have
here
on
openshift.tv,
it
is
meant
to
be
an
ask
me
anything
style
of
interaction
right.
We
we
live
on,
we
thrive
on.
We
want
your
questions,
whatever
the
topic
may
be
on
those,
it
doesn't
have
to
be
relevant
to
what
we're
talking
about
chris
and
I
or
peter
today.
B
Yeah
either,
if,
if
we
don't
know
it,
we
will
track
it
down.
But
that
being
said
in
the
absence
of
questions
from
you
all
from
our
loving
audience,
we
do
have
a
topic.
We
do
typically
have
something
that
we
like
to
talk
about
as
well
just
to
fill
in
the
time
if
you
will,
and
today
that
is
going
to
be
a
couple
of
different
things.
B
So
first
I
have
some
follow-ups
from
last
week
and
second,
and
the
reason
peter
is
with
us
today
is
because
we
want
to
talk
a
little
bit
about
rev,
red
hat
virtualization
and
specifically,
what's
changed
with
openshift
on
red
hat
virtualization
here
in
the
most
recent
versions,
so
we'll
be
talking
about
rev
upi
we'll
be
talking
a
little
bit
about
ipi
csi
with
rev.
So
it's
a
it's
an
all
rev
all
the
time,
except
for
when
it's
not
day
so
fear,
not
if
you
are
not
using
rev
for
your
underlying
infrastructure.
B
I
do
have-
and
chris
knows
this-
I
spent
some
time
over
the
last
week
or
so
and
came
up
with
the
episodes
for
the
next
roughly
four
months.
So
during
that
time
we
will
be
covering
basically
all
of
the
different
infrastructures
and
talking
about
different
features,
functions,
changes,
etc.
That
have
happened
across
all
of
those,
so
keep
an
eye
on
the
calendar.
A
B
B
C
Guys
yeah,
this
is
peter
lonavac
coming
to
you
from
snowy
boston.
It's
been
pretty
chilly
up
here.
I've
actually
been
in
high
tech
for
quite
a
while
now,
both
in
storage
and
performance
and
virtualization.
So
I'm
one
of
the
product
managers
in
the
cloud
platforms,
bu
focused
on
red
hat,
virtualization
and
overt,
which
is
our
upstream
and
also
openshift
virtualization,
which
is
the
new
cool
stuff
that
is
part
of
openshift
and
is
upstream
in
cuber,
which
actually
got
a
very
nice
shirt
for
that.
B
You
do
have
a
very
nice
search,
yes,
so
and
peter,
and
I
also
chat
quite
frequently
about
our
home
labs
and
all
of
the
various
machinations
that
are
happening
in
there.
My
my
most
recent
drama
is
in
my
my
one
storage
server.
I
had
to
remove
the
video
card
because
I
needed
the
pci
lanes
for
nvme,
so
nice,
it's
now
running
without
a
video
card,
and
it
seems
to
do
well
right
up
until
something
goes
horribly
wrong
and
then
I'll
have
to
adjust
things,
but
for
now
it
it
seems
to
be
functioning.
B
Michigan
is
and
boston
both
are
a
long
way
from
raleigh,
so
arts.
I
am
new
with
red
hat.
Welcome
if
you're
an
employee
and
welcome,
if
you
are,
I
say,
merely
if
you
are
one
of
our
esteemed
customers
so
regardless
of
which
new
with
red
hat
you
are
referring
to
there.
Thank
you
should
I
learn
the
new
version
or
the
old
version,
so
I'm
going
to
assume-
and
please
clarify
if
I
assume
incorrectly,
that
you're
referring
to
open
shift
3
versus
openshift4
right.
B
So
I
would
definitely
highly
recommend
openshift4
right,
so
not
not
the
least
of
which,
because
openshift
3,
so
3.11
is
the
only
version
remaining.
If
you
will
it's
the
only
one
that
is
currently
under
support
and
that
support
expires
in,
I
want
to
say,
roughly
a
year,
maybe
a
year
and
a
half,
but
it's.
B
Yeah,
and
essentially
it
is,
it
is
in
an
extended
update
status.
There
are
no
new
features
being
added
right,
that
type
stuff,
all
the
new
stuff.
All
of
the
improvements,
all
of
the
changes
that
aren't
just
bug,
fixes
and
security
fixes
are
going
into
the
openshift
four
line,
so
that
is
definitely
the
way
that
you
would
want
to
go
chris
peter
anything
to
add
there.
C
But
yeah
most
of
most
of
the
time
you
know
the
large
large
massive
clusters
you
know
in
applications
that
first
got
deployed
are
in
openshift
three
and
we've
actually
got
a
process
for
folks
to
get
from
openshift
read
openshift
for
but
yeah
all
the.
In
fact,
openshift4
has
been
out
for
18
months,
almost
two
years
now
so
yeah,
it's
it's.
I
wouldn't
even
call
it
the
new
stuff.
It's
if
it's
been
out
for
two
years.
It's
it's
it's
pretty
stable.
It's
we're
and
we're
we're
just
on
for
4.6
right.
So
right.
B
Yeah
and
kubernetes
six
year
anniversary
is
in
may
as
well.
Mm-Hmm
yeah,
so
pretty
awesome
lots
lots
of
it's
a
busy
month
for
for
the
kubernetes
world,
all
right,
so
lol,
I'm
a
I
apologize
if
I
butcher
any
names
working
with
both
3.11
and
4.
yeah.
That's
very
common
yeah!
There's
a
lot
of
folks
out
there
who
are
still
on
openshift
3.11
right.
I
don't
know
if
anybody
knows
this
or
not.
2020
was
kind
of
a
rough
year
right.
There
was
a
lot
of
going
on
yeah.
D
B
It
it
is,
you
know,
broadly
speaking,
a
lot
of
a
lot
of
organizations.
You
know
they.
They
quite
frankly
had
other
things
that
were
priorities.
Then
updating
you
know
things
that
are
running
great
and
running
fine,
and
that's
why
you
saw
us
extend
supports.
I
think,
support
for
3
out
of
11
originally
ended
roughly
the
middle
of
this
year,
but
we
extended
it
out
by
nine
months
or
12
months,
something
like
that
to
help
with
that.
B
B
Yeah,
if,
if
you
can
drop
a
link
to
that,
it's
a
great
way
to
help
migrate
those
applications
and
then,
of
course,
if
you're
learning
about
openshift4
there's
a
huge
number
of
resources,
not
the
least
of
which
is,
of
course
openshift.tv,
where
we
have
dozens
and
dozens
and
dozens
of
of
live
streams.
Both
cataloged,
as
well
as
on
the
calendar
coming
up
all
around
openshift4
so
and
please
feel
free
to
ask
questions
as
well.
Yeah.
C
C
You
go
in
and
and
everything's
all
set
up
for
you,
but
you
actually
go
through
the
process
of
understanding,
openshift
and
kubernetes
and
containers,
and
then
you
immediately
dive
into
service
mesh
and
developer
pipelines
and
the
coolest
part
for
me,
which
I
I'm
a
product
manager
right,
I'm
not
a
developer,
but
you
go
in
here.
You
change
some
java
code
and
a
build
pipeline
fires
off
and
then
a
new
application
shows
up
here
like
five
minutes
later
you're,
like
that's
crazy.
B
So
one
thing-
and
I
tried
to
show
this
while
I
was
while
we
were
streaming
and
I
failed
miserably-
was
how
do
we?
Where
does
that
information
come
from
and
it
was
at
the
top
of
my
mind
because
last
week
remember,
I
was
talking
about
disconnected
openshift
and
at
the
very
end
of
the
show
we
talked
about
the
the
openshift
updates
manager
or
the
for
we
call
it.
The
openshift
update
operator
right
where
you
can
in
an
offline
environment,
basically
pull
in
the
cincinnati
data
and
have
it
offer
you
that
same.
B
B
Very
nice,
so
a
couple
of
things
to
note
here
so
4.6.12
has
actually
been
available
for
a
couple
of
weeks
now,
if
not
maybe
the
better
part
of
three
weeks,
but
you
notice
that
just
today
it
became
available
as
an
update.
So
there
is
a
difference
between
the
different
channels
as
well
as
if
you
were
to
go
and
do
a
new
install
right
now
so
remember,
stable
is
always
when
we
feel
comfortable
having
the
vast
majority
of
folks
who
have
openshift
deployed
updating
right.
B
Typically,
that
means
that
it
is
going
to
be
a
couple
of
weeks
after
it
hits
the
fast
channel.
So
if
I
were
to
go
here
too
fast,
if
the
fast
channel
is
generally
going
to
have
newer
versions
available
than
what
we
see
with
and
right
now,
they
happen
to
align,
but
it's
going
to
have
newer
versions
available
that
might
not
have
had,
or
there
might
be
an
outstanding
edge
case
or
something
like
that
where
it's
it's
not
available
for
everybody,
but
it's
not
the
same
thing
as
a
new
deployment
right.
This
is
just
for
updates.
B
So
when
you,
if
you
saw
over
the
last,
let's
say
it's
two
weeks,
if
you
went
to
you,
know
the
cloud.redhat.com,
you
know
slash
open,
shift,
slash,
install
and
you
pulled
down
the
installer.
It
was
probably
giving
you
version
4.6.12.,
there's
nothing
wrong
with
that.
That's
expected
for
new
installs
there's
nothing
wrong
with
going
directly
to
a
version
that
is
newer
than
what
you
see
in
the
update
channel.
B
It's
just
a
a
practice
of
what
has
been
fully
tested
and
are
we
seeing
any
breaking
right
things
that
you
should
be
alarmed
about,
and
we
don't
want
you
updating
to
type
of
bugs
right.
So
the
other
thing
that
I
tried
to
look
at
and
failed
at
while
we
were
on
stream
last
week,
was
where
the
update
data
is
stored
at
so
I
browse
to
this
github
repo.
B
This
is
github.com
open
shift,
slash
cincinnati
graph
data,
so
this
is
where
we
publish
all
of
those
updates,
and
all
of
you
know
this
is
how
the
system,
how
openshift
determines
which
channels
are
or
where
I
can
update
to
and
from
and
which
ones
I
can't
update
to
are
from
so
last
week
I
looked
at.
I
went
into
the
channels
here
and
I
saw
so
stable
4.6
what's
available
and
you
can
see
that
4.6.9
is
technically
here
right,
but
we
knew
it
was
blocked.
B
B
So
the
last
thing
that
I
have
to
talk
about,
which
is
kind
of
an
extension
of
what
we
talked
about
here.
I've
also
talked
about
updates
and
upgrades
more
thoroughly
on
a
previous
show,
we'll
dig
up
that
show
and
I
will
link
it
in
what
I
am
hoping
to
start
as
the
blog
post
following
these
shows
is
the
upgrade
process,
and
this
came
from
an
email,
an
internal
email
on
our
sme
list,
where
somebody
was
asking
more
or
less.
B
You
know
my
customer
wants
to
know
more
about
the
upgrade
process
and
you
know
a
lot
of
times
we
market
it
and
even
when
we
demo
it
right,
we
just
show
you
know:
hey
come
here
to
the
cluster
settings.
You
know,
make
sure
you're
on
the
right
channel
first
and
then
you
hit
the
the
big
update
button
and
tell
it
to
go,
and
some
stuff
happens
in
the
background
and
what?
What
is
that
stuff?
How
do
I
know
what's
going
on?
B
You
know
that
so
and
most
importantly,
how
do
I
know
when
it's
done
so
there's
a
couple
of
resources
available
for
that.
So
first,
let's
talk
about
the
upgrade
process
a
little
bit.
So
when
I
click
this
button
and
I
think
it
should
ask
for
a
confirmation
yep.
So
when
I
click
this
button
and
I
select
this
version
and
tell
it
to
go-
what's
actually
happening
here.
B
So
if
I
were
to
hit
the
update
button
and
I'm
not
going
to
because
I
don't
want
to
have
this
cluster-
be
out
of
commission
for
a
few
minutes
or
during
the
show
here,
what
we're
doing
is
updating
the
cluster
version
operator.
Cvo
is
how
we
often
refer
to
it,
so
cluster
version
operator
you
can
think
of
as
an
operator
of
operators
so
which
operators
does
it
operate,
so
that
would
be
all
of
the
cluster
operators.
So,
let's
switch
over
to
my
terminal
here.
B
B
So
when
I
update
that
cluster
version
operator
and
go
to
4.6.12,
one
of
the
things
that
I'll
have
in
there
is
a
set
of
manifests
for
each
one
of
these
child
operators.
If
you
will-
and
it
will
tell
each
one
of
those
operators
to
go
to
whatever
version
is
defined
in
that
set
of
manifests
so
essentially
it'll
say
console-
go
to
version
from
version
two
to
version
three,
you
know
at
cd
go
from
version
three
to
version
four
so
on
and
so
forth
and
effectively
it
steps
back.
B
B
So
the
monitoring
operator
is
dependent
on
the
node
tuning
operator
being
updated
first,
so
it
will
determine
the
order
that
those
need
to
happen
in
as
well
as
monitoring
it
may
kick
off
and
do
steps
one
two
and
three,
but
then
it
has
to
wait
for
this
other
one
to
finish
before,
it'll
do
four
five
and
six
so
effectively.
Once
you
see
all
of
these
go
from
progressing
true
to
progress
or
available
true
and
progressing
false.
That
means
that
the
cluster
has
been
updated.
B
B
B
So
how
can
I
make
that
go
faster?
So
a
couple
of
things
to
be
aware
of
here,
so
one
by
default,
the
machine
config
operator
will
only
apply
to
one
machine
at
a
time.
So
how
do
we
know
that
so
that
comes
from
machine
config
pools?
So
let's
take
a
look
at
our
at
our
compute
resources.
Here
I
have
two
machine
config
pools
and
these
represent
a
couple
of
different
things.
So
one
is
which
configuration
and
apply.
Am
I
applying
to
any
nodes
that
match
my
machine
config
pool.
B
So
in
this
instance,
let's
go
past
all
the
noise
here
is
going
to
say
so
machine
config
selector.
So
it's
going
to
say
any
machine.
That
is
a
worker.
Excuse
me
machine
config
that
has
the
role
of
worker
as
well
as
any
node
that
has
a
role
of
worker
associated
with
it
and
we
don't
have
it
defined.
There
is
no
value
defined
here,
but
it
is
going
to
apply
this
to
one
node
at
a
time
by
default.
B
So
if
I
do
an
oc,
explain,
machine
config
pool
dot
spec
inside
of
here
we
have
this
max
unavailable
value,
so
I
can
use
this
value
to
set
a
hard
number.
I
don't
want
you
to
do
any
more
than
five
nodes
at
a
time
or
ten
nodes
at
a
time,
or
a
percentage
only
do
up
to
17
percent
of
the
nodes
at
any
point
in
time
you
know
or
13.
I
want
one-eighth
of
them
to
go
down,
so
this
is
how
we
can
potentially
expedite
that
update
process.
B
B
You
want
to
make
sure
that
those
values
are
set
so
that
your
application
is
not
affected
for
node
operations.
So
that's
kind
of
that
process
in
an
in
a
nutshell
right
when
is
it
done?
It's
done
when
all
of
the
child
operators
say
that
they're
done
kind
of
straightforward,
but
a
little
bit
a
little
bit
opaque.
So
chris,
I
think,
there's
a
question.
B
B
What
this
number
says
is
how
many
simultaneous
nodes
will
be
set
to
a
cordon
and
drain
status
and
be
unavailable
for
scheduling
now,
when
that
drain
actually
happens,
it's
up
to
the
scheduler
to
determine
what's
the
best
way
to
make
that
happen,
so
it
could
be
that
doing
the
actual
drain
operation
takes
multiple
more
minutes,
because
maybe
it
needs
to
hey.
I
need
to
turn
off
this
node.
B
I
need
to
drain
this
node,
so
I
need
to
spin
up
another
pod
somewhere
else,
and
that
takes
some
time
for
it
to
pull
an
image
and
spin
up
and
for
everything
to
be
in
a
healthy
status.
Remember:
health
checks
so
on
and
so
forth.
So,
yes,
it
controls
how
many
nodes
are
available,
but
it's
really
up
to
the
kubernetes
scheduler
and
the
rest
of
the
kubernetes
mechanisms
to
make
sure
that,
within
the
parameters
that
have
been
defined,
the
application
stays
available
and
healthy.
According
to
those
definitions,.
A
B
Let
me
rephrase
that
I
don't
know
authoritatively
right
so
we'll
have
to
check
on
that
one
to
determine
which
subscription
level
it
is
will
automatically
have
access
to
that
eos
level.
After
the
fact
between
you
me
and
the
wall
right,
I
I
strongly
suspect
that,
like
most
things
in
openshift
and
at
red
hat
for
that
matter,
there
won't
be
anything
that
technically
prevents
you
from
choosing
that
channel
at
any
point
in
time.
A
B
So
is
there
any
difference
between
stable
and
eus,
so
today
I
would
expect
the
answer
to
be
no,
and
we
will
confirm
this.
This
is
based
on
my
assumptions
and
based
off
of
some
ancillary
email,
threads
and
other
conversations
that
I've
seen,
but
we'll
make
sure
to
confirm
this
and
correct
it
next
week.
If
we
need
to
so
today,
I
would
say:
no,
where
that
will
come
into
play,
is
more
or
less
once
we
get
out
to
so.
The
support
policy
is
current,
minus
two
right.
B
So
that
means
that
once
openshift
4.9
is
released,
4.6
would
no
longer
fall
into
the
regular
support
cycle.
So
if
you
want
to
continue
to
receive
updates
to
4.6,
you
would
then
need
to
be
subscribed
right.
Have
that
premium
subscription
with
the
eus
channel
for
for
what
you're
doing
so
until
then,
they
should
be
basically
the
same
as
far
as
I
know,
but
we'll
go
ahead
and
confirm
that.
C
A
D
B
All
right
so
again,
please
don't
hesitate
to
ask
questions.
We
do
look
forward
to
those,
but
peter
has
been
exceedingly
patient
and
yeah.
We
do
greatly
appreciate
that.
So
I'm
I'm
going
to
lob
the
softball
to
you,
peter
of
let's
talk
about
rev
and
openshift
4.6.
I
know
that
there
was
a
pretty
substantial
number
of
changes,
improvements
expansions
that
happened
there.
So
can
you
give
us
a
breakdown.
C
C
We
started
working
out,
we've
been
working
on
those
immediately,
some
of
them
didn't
make
4.5
and
since
we're
actually
now
on
the
you
know,
the
release
cadence
for
rev
is
much
longer.
It's
about
18
months,
open
trips
coming
out
every
quarter
right.
So
basically,
what
ended
up
happening
is
a
pile
of
stuff
dropped
in
4.6
that
included
user
provision
infrastructure,
the
csi
storage
provisioner,
auto
scaling
was
working
and
proper
and
literally
all
the
things
that
people
were
waiting
for
kind
of
showed
up
in
openshift
4.6.
C
B
C
So
I
don't
know
if
we
have
a
good
picture
for
this,
you
might
so
so
there's
really,
and
we
need
to
be
careful
because
we
at
red
hat
tend
to
use
shorthand
and
we
say
oh
4.6,
on
4.3.
Well,
since
I
worked
in
both
worlds
right
where
I've
got
red,
hat
virtualization
or
rev,
4.3
and
4.4,
and
then
open
shift,
you
know
4.4
4.5
4.6.
C
I
actually
had
to
insist
when
people
talk
to
me
like
use
the
product
name
space
and
then
the
then
the
actual
version,
because
otherwise
we're
not
going
to
have
a
productive
conversation,
so
rev
4.3,
which
has
been
around
for
quite
some
time
it
actually
released
right
after
I
started
back
it's
about
two
years
ago
now
is
based
on
rel.
Seven,
that's
got
a
life
cycle
of
its
own
rail
8's
been
out
for
a
while
rev
4.4,
which
released
last
summer
is
based
on
rail
8.
right.
C
So
we
we're
now
trying
to
keep
up
with
the
current
modern
operating
system
that
I
mean
relates
more
performant,
more
stable.
It's
just
a
better
infrastructure
to
build
a
much
better
operating
system
to
build
your
virtual
infrastructure
on,
but
we
know
customers
don't
move
right
away.
So
what
we've
had
to
do
is
support
open
shift
on
earlier
versions
like
so
openshift,
4.3
and
4.5
on
rev4.3.
C
All
right.
The
problem
is,
is
that
now
that
we
are
moving
further
ahead
and
kind
of
the
breaking
point
or
the
the
tipping
point
was
red,
4.4
has
been
out
for
a
while
now
and
it's
going
to
contin.
You
know
we're
now
in
eus
on
rev.
So
if
there's
any
changes
that
come
they're
only
going
to
happen
in
the
hypervisor
right
and
what
that
means
is
most
of
the
interaction
in
the
ipi
is
done
through
the
rev
manager.
C
C
C
You
should
really
upgrade
your
rev
infrastructure
first
to
4.4
and
then
upgrade
your
openshift
cluster.
On
top
of
it
right,
we've
got
that's
the
that's
the
route
most
customers
are
taking.
It
will
most
likely
work
if
you
just
put
openshift
4.6
on
rev4.3,
but
it's
actually
not
a
tested,
combination
right
and
there's
actually
a.
I
can
go,
dig
up,
there's
a
separate
document
we
have
that
says
these
are
the
test,
because
we
actually
have
this
problem
on
every
virtual
platform
right
so
on
vmware
and
openstack.
B
Fantastic
and
the
upgrade
path
so
remember
today,
openshift
4.6,
4.5
4.4,
are
all
fully
supported.
If
you
are
running
openshift
4.4
on
rev
4.3,
if
you
want
to
go
to
openshift
4.6,
you
first
need
to
update
either
rev
24.4
or
openshift
to
4.5
and
then
update
the
other
one
and
then
move
to
openshift
4.6.
B
So
essentially,
all
of
those
need
to
be
updated.
They
don't
have
to
be
done
simultaneously
right
or
they
would
be
done
sequentially
in
whatever
order
you
you
happen
to
choose
to
do
those
in
so
openshift
4.4
was
the
first
rev
ipi,
as
you
mentioned,
that
brought
with
it.
The
automated
deployments
we've
talked
about
on
the
show
before.
If
there's
any
questions
feel
free
to
ask
them
the
load
balancers
that
are
used
all
right,
how
that's
done
with
ipi,
not
using
an
external
one
4.5
we
had
some
minor
expansion
in
capabilities
and
then
4.6.
B
B
Big
ones
from
my
perspective,
ipi
related,
so
we
added
the
ability
to
do
auto
scaling.
So
we'll
we'll
talk
more
about
that
in
just
a
second,
because
you
may
be
thinking,
but
I
thought,
if
you
could
deploy
nodes
with
a
machine
api,
I
can
automatically
do
auto
scaling.
No,
that
turns
out.
That's
not
the
case.
D
B
C
C
Talking
about
up
I'd
like
to
give
a
shout
out
to
a
team
of
red
hat
consultants-
and
I
don't
remember
there
in
the
northeast-
I
think
that
actually
wrote
a
lot
of
the
ansible
stuff
that
we
based
our
work
on,
because
it
was
exactly
like
you
said.
Is
you
know,
upi
has
a
specific
set
of
steps
that
you
really
need
to
and
on
some
of
the
platforms,
it's
just
here's
a
document
and
your
automation
is,
you
know
joe
engineer,
but
these
guys
actually
said
look.
We
do
this
often
enough
for
customers.
B
Yeah,
so
I
actually
want
to
talk
about
that
a
little
bit,
so,
let's
come
over
here
to
which
documentation
page
am
I
on
so
I
am.
This
is
just
the
standard
openshift
4.6
documentation,
as
you
see
I've
browsed
to
installing
installing
on
red
hat
virtualization
and
then
installing
a
cluster
on
red
hat
virtualization
with
user
provisioned,
and
one
thing
that
you'll
note.
If
you're,
comparing
this
to
rev
ipi
or
any
of
the
vsphere
deployment
methods,
is
this
one
is
pretty
substantially
different.
B
So,
if
you're
familiar
with
me
right
for
for
our
audience,
you
know
that
I
like
to
follow
the
documentation.
It
gives
me
a
great
chance
to
provide
feedback.
Likewise,
for
any
of
you
watching
providing
feedback,
providing
suggestions
on
our
documentation
is
super
easy
click.
This
big
open
an
issue
button
up
here,
takes
you
right
to
the
github
repo,
where
you
can
submit
a
hey,
there's
a
problem
with
this
every
time
I've
done
it,
I've
gotten
a
response
within
a
couple
of
hours
at
most.
B
C
Ready
to
go
yeah
that
team
is
awesome
because
they're
actually
geographically
dispersed
in
a
follow
the
sun
model,
so
I'll
I'll
work
with
some
guys
on
the
east
coast.
They'll
make
changes
they'll
get
approved
overnight
by
the
folks
in
australia,
and
it
shows
up
you
know
next
day.
When
I
wake
up,
it's
actually
pretty
cool.
B
Yeah
yeah
it's!
I
I'm
really
impressed
with
not
just
their
responsiveness
but
the
level
of
care
that
they
put
into
the
docs
right.
They
really
do
care
and
I've
even
gone
to
them
with
suggestions
of
like
major
reorganizations,
and
it
doesn't
always
come
out
the
way
that
I
envisioned
it,
but
they're
always
willing
to
entertain
those
things
so
kudos
to
the
docs
team.
B
So
a
couple
of
things
it
is
ansible-based,
which
means
that
you
need
ansible,
so
the
docs,
which
is
a
little
bit
unique
for
the
installation
methods
right.
So
you
can
see
here
the
docs
tell
you
how
to
set
up
how
to
install
ansible
into
your
environment,
how
to
deploy
the
various
ansible
modules
that
we
need
for
interacting
with
red
hat
virtualization
as
well,
as
you
know,
the
api
module
that
it
needs
to
be
able
to
do
that
by
the
way.
B
D
B
From
my
management
host
so
which
works
really
really
well,
with
the
exception
of
that
package,
doesn't
exist
in
centos,
it's
a
rel
package.
So
right
I
had
to
go
through
the
manual
steps
other
things
in
here,
and
these
are
standard,
install
things
right,
making
sure
that
you
trust
the
certificate
generating
the
ssh
key
pulling
down
the
various
installation
programs
now
where
it
starts
to
change,
is
with
these
ansible
playbooks.
B
And
inside
of
my
working
directory,
you'll
see
that
I've
got
this
playbooks,
so
these
are
the
playbooks
that
came
from
that.
I
literally
executed
that
same
script
and
it
pulled
down
these
yaml
playbook
files
and
the
important
one
here
is
this
inventory
file
and
this
if
you've
ever
deployed
openshift
3.
This
kind
of
feels
familiar
right
because
remember
with
openshift3,
we
had
an
ansible
file.
That
would
say
I
want
these
worker
nodes
and
these
control
plane
nodes
and
these
lcd
nodes
and
so
on
and
so
forth.
B
So
in
here
we're
defining
very
similar
to
an
install
config.yml.
What
we
want
our
virtual
machines
to
look
like
hey.
I
want
a
control
plane,
node
that
has
16
gigabytes
of
memory
and
four
cpus
right,
four
sockets
with
one
core
each.
I
want
it
to
have
a
120
gigabyte
disk
that
is
running
on
this
storage
domain.
I
want
to
have
a
network
adapter
that
is
connected
to
this
network
in
this
profile
same
thing
with
our
worker
nodes
and
then
down
here
at
the
bottom
we
have
which
vms
we
actually
want
right,
hey.
B
I
want
a
a
bootstrap
node
that
uses
the
control
plane
profile.
I
want
us
a
control,
plane,
node,
three
of
them.
Actually
that's
use
same
thing
right,
here's
the
name!
I
want
you
to
use
here's
the
type
in
openshift
and
here
is
the
profile
I
want
you
to
use
and
then
down
at
the
bottom,
my
worker
nodes,
so
pretty
straightforward,
right,
hey
ansible!
B
Actually,
let's
go
ahead
and
do
that
so
I'll
flip
back
over
to
the
documentation.
So
we
just
looked
at
the
inventory
before
I
get
ahead
of
myself,
because
the
next
step
is
okay,
inventory
diamo.
Here
we
go
install
config.yml
so
effectively.
We
need
to
create
our
install
config
and
the
recommended
way
of
doing
this
is
to
go
through,
like
you
were
doing
a
ipi
install.
B
So
I'm
going
to
connect
to
my
overt
infrastructure,
so
I've
done
this
before
so
it
is
cached
the
credentials.
That's
why
it's
not
asking
me.
I
wanted
to
use
this
storage
domain.
I
wanted
to
use
this
network
connection.
This
v-neck
profile
turns
out
that
these
don't
actually
matter
as
we'll
look
at
in
the
next
step.
B
I
don't
remember
if
that
one's
available
or
not,
but
it
doesn't
matter
and
we'll
look
at
pull
that
all
right.
So
inside
of
this
assets
directory,
I
have
my
install
config
and
when
we
look
at
these
commands
over
here,
it's
telling
me
I
want
to
set
the
compute
replicas
to
zero.
This
is
just
like
with
any
upi
or
bare
metal
deployments
non-integrated
deployments.
B
I
want
to
set
my
machine
network
appropriately.
This
applies
to
any
deployment
regardless
of
infrastructure
type,
and
then
I
want
to
completely
delete
the
platform
section.
So
remember
when
I
said
it
doesn't
matter
what
I
actually
provide
for
those
values,
that's
because
we're
doing
away
with
all
of
these.
B
B
A
B
B
B
B
Building
the
ignition
files,
so
that's
basically
what
we've
just
done
so
now
we're
at
this
step
of
creating
the
templates
and
virtual
machines,
and
this
is
where
it
gets
really
interesting
to
me.
This
is
something
that
I
really
appreciate
in
that
I
don't
have
to
go
through
the
manual
process.
I
don't
have
to
automate
this
myself.
Essentially,
I
execute
a
playbook.
B
A
C
A
B
B
And
what
we
see
inside
of
here
is
here's
all
of
my
virtual
machines
right
it
was
it
was
that
easy
I
didn't
have
to
go
through
and
click
new
vm
and
set
all
these
settings
or
anything
like
that.
It
it
takes
care
of
it
for
me
now,
interestingly,
if
we
want
to
do
dhcp,
we
can
go
in
and
we
can
look
at
each
one
of
these
now
and
check
our
network
interfaces,
and
I
can
pull
my
mac
address
and
I
can
do
a
static,
dhcp
reservation
and
so
on
and
so
forth.
B
D
C
Yeah,
that's
not
that's
not
part
of
that,
and-
and
it
is,
you
were
correct
to
point
out.
You
know
it's
philosophically
different
than
than
what
folks
have
done
before,
because
we
felt
that
you
know
having
a
more
complete
document
that
lets
you
do
a
ton
of
stuff
but
got
very,
very
deep
in
the
weeds
very
quickly
right,
rev
is
really
hey.
Rev
is
easy
to
use.
That's
why
people
like
it!
That's
why
people
use
it.
C
Let's
make
the
upi
experience
similar
to
that
and
that's
how
we
ended
up
with
you
know,
making
ansible
do
most
of
the
heavy
lifting
and
and
like
you
said,
if
you
need
to
go
in
and
tweak
stuff
afterwards,
it's
absolutely
possible
to
do
that,
but
we
don't.
We
don't
make
you
face
that
you
know
those
sharp
edges
right
away.
Yeah.
B
So
I'm
not
actually
going
to
turn
on
the
vms
here,
mostly
because
I
don't
have
the
capacity
in
my
lab
for
that.
But
turning
on
the
vms
is
super
duper
easy
literally.
If
I
execute,
for
example,
the
bootstrap
playbook,
what
it's
going
to
do
is
it's
going
to
attach
the
the
ignition
config
to
the
virtual
machine,
so
rev,
as
of
and
peter
you'll,
have
to
remind
me,
I
think
it's
whenever
we
first
started
supporting
ipi
so
4.3.9.
I
think
rev4.3.9.
B
So
they
they
modified
rev
to
be
able
to
attach
ignition
files,
not
just
cloud
init
files
to
the
virtual
machines,
so
it
will
attach
that
bootstrap
ignition
file
to
the
vm
it'll
turn
it
on.
So
that
way,
bootstrap
does
what
bootstrap
does
same
thing
with
the
control
plane
same
thing
with
the
worker
nodes,
so
on
and
so
forth.
So
it's
all
managed
through
ansible
right.
I
turn
on
my
bootstrap.
B
I
turn
on
my
control
plane.
I
turn
on
my
workers
when
it
tells
me
that
bootstrapping
is
complete.
I
destroy
the
bootstrap,
which
is
also
a
ansible
playbook,
and
I've
got
a
cluster
at
the
end
of
all
of
that.
So
very,
very
straightforward,
very
easy.
In
my
opinion.
Again,
I
don't
have
to
fiddle
with
you
know:
vm
images
uploading
them.
B
B
So
if
you
were
quick
eyed
there
when
I
showed
my
virtual
machines
here,
you
see
I've
got
all
of
these
other
vms
running
inside
of
here.
This
is
a
ipi
cluster.
This
is
one
that
I
was
showing
a
minute
ago,
an
ipi
cluster
deployed
into
my
rev
cluster
there
and
the
reason
I
wanted
to
deploy
this
ipi
cluster
and
have
it
ready
for
us
today
is
csi,
so
peter.
C
C
But
what
we
allowed
is
to
provision
rev,
managed,
storage
right,
essentially
a
storage
domain
to
have
it
provision
pdcs
for
the
cluster
right
and
it
originally
like.
I
said
we
started
development
in
openshift,
4.4
and
4.5,
so
it
technically
will
work
under
those
versions.
But
again
it's
not
tested,
nor
you
know
it's.
It's
not
supported
in
those
environments,
so
you'll
need
to
be
in
openshift,
4.6
right
and
that's
where
we
we've
got
ci
pipelines
and
and
it's
gone
through
a
full
regression
cycle.
There.
B
C
Yeah
and
that's
again,
philosophically
it's
slightly
different
than
some
of
the
other
virtual
platforms,
where
you
have
to
that's
an
extra
step,
but
like
we
just-
and
this
is
something
I
try
to
you-
know
instill
in
our
team.
The
default
behavior
should
just
be.
What
you
want
right
is
because,
if
you're
good,
if
you're
going
to
be
using
ipi
you're,
pretty
pretty
often
going
to
want
to
provision
storage
out
of
your
rev
cluster
to
the
to
the
openshift
cluster,
and
we
just
do
that
by
default.
C
B
So
I
can't
not
actually
it's
probably
not
deleting,
because
I
think
that
there's
a
yeah
there
is
a
pvc,
that's
already
using
it,
which
is
the
registry,
so
it'll
it'll
make
sure
that
it's
always
there.
Now
I
can
modify
it.
If
we
look
at
this
one,
I
can
do
things
like.
I
could
change
the
storage
domain
that
it's
using.
I
could
change
from
thin
to
thick
provisioning,
etc,
but-
and
I
can
change
it
so
that
it's
not
the
defaults,
but
it
will
always
exist.
There's
nothing!
C
Storage
and-
and
you
bring
up
a
good
point,
which
I
don't
know
if
it's
that
clear
in
the
documentation
right,
which
is
the
default
storage
domain,
this
class
is
created
and
is
the
default
storage
domain.
You
install
the
cluster
in
right,
the
ipi,
you
have
to
put
it
in
a
storage
room,
and
you
say:
okay,
great,
we'll
just
create
a
class
that
that
provisions
out
of
that.
But
if
you
actually
have
multiple
types
of
storage,
like
one
storage
domain,
is
you
know
gigantic,
spinning
hard
drives
and
you've
got
another
storage
domain?
That's
all
flash!
C
B
Exactly
so
real
quick
just
because
I
love
when
things
act,
exactly
the
way
that
you
expect
them
to
act,
which
I
feel
like
is
the
the
name
of
the
game,
particularly
when
it
comes
to
many
open
shift
things.
Let's
create
a
persistent
volume,
so
I'm
gonna
call
this
one.
You
know
test
because
I'm
super
creative,
like
that.
We're
gonna,
give
it
a
13
gigabyte
size
because
it's
lucky
number
13.
B
and
hit
the
create
and
you'll
note
that
it's
already
bound.
We
can
see
the
persistent
volume
down
here.
If
I
click
over,
I
can
see
my
13
gigabyte,
persistent
volume
ending
in
788
alpha
and,
if
I
flip
back
over
to
my
rev
environment
here
and
filter
these
down
some
so
that
way,
they're
easier
to
find
I've
got
a
disk
oops
there.
We
go
a
disk
right
here,
788
alpha
and
we
can
see
it
is
13
gigabytes
in
size.
B
So
it
literally
does
precisely
what
it
says
it's
going
to
do
when,
when
you
create
a
pvc,
it
creates
a
disk
inside
of
that
storage
domain
on
the
rev
side.
If
I
were
to
mount
that,
it
would
attach
it
as
a
disk
to
the
virtual
machine
and
I'm
trying
to
remember
peter.
I
had
a
conversation
with
the
engineering
folks
and
I
don't
remember
the
precise
number,
but
do
you
happen
to
recall
what
the
maximum
number
of
disks
per
virtual
machine
is?
B
C
B
B
B
Absolutely
it
can
handle
those
types
of
things
and
it
can
handle
multiple
pods
that
are
like
that,
if
you
so
choose
so
just
to
round
things
out
here,
we'll
go
back
to
our
pvs
here,
we'll
hit
the
delete.
No,
not
the
persistent
volume.
The
persistent
volume
claim
we'll
delete
the
persistent
volume
claim,
and
we
see
our
persistent
volume
over
here
is
already
gone,
and
if
we
come
up
here,
this
might
take
just
a
second
or
two
longer
there
we
go.
B
Our
disk
inside
of
the
storage
domain
is
gone
so
again,
behaving
exactly
the
way
that
you
would
expect
it
to
behave.
Chris
we
were
having
a
conversation
in
in
our
team
chat
the
other
day
about
how,
when
things
magically
fix
themselves,
it's
kind
of
terrifying,
because
you
don't
know
why
it
broke,
and
you
don't
know
why.
A
B
C
That
is
kind
of
our
rev
philosophy,
and
actually
I
do
want
to
touch
on
one
other
thing
here
that
that
does
come
up
as
well,
which
is
rev,
is
one
of
the
only
platforms
that
you
can
do
essentially
a
hybrid
cluster
right
in
the
sense
that
I
can
have
rev
managed
nodes
in
my
openshift
cluster,
but
I
can
also
attach
bare
metal
nodes
right
now.
Normally
you
can't
do
that,
but
the
rev
actually
doesn't
have
an
official
cloud
provider
right.
C
We
have
cloud
provider-like
capabilities,
so
you
can
actually
go
sneak
in
and
say:
hey
I've
got
some
bare
metal
noise
bare
metal
nodes
that
I've
deployed.
You
know
I
don't
want
to
virtualize
anything
there,
but
I'm
going
to
actually
attach
them
to
my
openshift
cluster
running
on
rev
and
that
works
just
fine.
B
A
C
B
C
Yeah
well,
let's
be
clear
right.
The
use
case
for
this
is
more
about
right.
There's
actually
two
use
cases
for
a
gpu
right.
One
is
you
know,
compute
intensive
workloads
where
I
just
want
the
the
boost
from
the
vector
processing
that
I
get
for
say
aiml
and
the
other
is
remote,
visualization
right.
So
the
the
first
use
case
is
way
easier
to
handle,
because
you
don't
have
to
worry
about
video
drivers
or,
what's
my
display
protocol
to
the
vm,
it's
just
hey.
C
B
A
C
D
C
Telegraph
something
no
this
so
the
trick
is,
you
know,
there's
some
the
nice
thing
about
red
hat,
there's
so
many
options
right.
So
there
was
the
use,
the
bare
metal
installer
on
rev
totally.
You
know
totally
non-integrated,
then
there's
ipi
and
now
there's
this
new
upi.
We
shift.
I
think
we've
talked
publicly
about
the
assistant
installer.
Yes,.
C
A
B
Before
we
steal
too
much
more
time,
I
want
to
say
thank
you
to
peter
greatly
appreciate
you
coming
on.
Thank
you
to
our
audience.
We
do
appreciate
all
the
questions.
If
you
have
additional
or
follow-up
questions,
please
feel
free
to
reach
out.
So
I
am
act
at
practical,
andrew
on
twitter
or
andrew.sullivan
redhat.com
peter
you're.
A
C
B
Open
shift
4.7
what's
new
presentation,
so
I
will
be
here
on
the
stream
helping
answer
questions
helping
pass
questions
over
to
the
product
management
team.
That's
giving
that
presentation
so
be
sure
to
tune
into
that.
One
again
feel
free
to
ask
questions
and
we'll
make
sure
to
get
those
answered
during
the
presentation
or
or
as
close
to
afterwards,
as
we
can.