►
From YouTube: Red Hat OpenShift on IBM Power and IBM Z | OpenShift Commons Gathering 2020 at Kubecon/NA
Description
Red Hat OpenShift on IBM Power and IBM Z
OpenShift Commons Gathering 2020 at Kubecon/NA
November 17, 2020
Christy Norman (IBM) | Marcel Mitran (IBM)
Red Hat OpenShift enables businesses to easily develop and deploy applications across the hybrid cloud. In many enterprises the latter includes on-premises IT infrastructure such as IBM Power and IBM Z. In this breakout, Marcel Mitran from IBM Z and Christy Norman from IBM Power show how the user experience remains the same, and then explore the reasons why businesses would want to deploy Red Hat OpenShift on IBM Power and IBM Z. Backed up by common use cases and customer examples, they describe the technical scenarios possible, and then review the special considerations in deploying Red Hat OpenShift on IBM Power and IBM Z.
466766 Red Hat OpenShift on IBM Power and IBM Z
A
B
A
A
And
so
the
openshift
platform,
of
course,
is
a
you
know,
is
a
is
a
pervasive
pervasively
available
platform.
It
runs,
of
course,
in
all
the
big
public
clouds
aws
google,
on.
It
also
runs
in
your
private
cloud
and
and
within
your
private
cloud.
It
runs
on
key
infrastructure
platforms
like
the
ibm
z
platform
and
the
ibm
power
platforms,
which
are
really
at
the
core
of
a
lot
of
enterprises.
A
It
infrastructure,
really.
These
platforms
have
formed
the
center
of
truth
around
which
a
lot
of
enterprises
have
built
and
and
grown
their
it
capabilities
and
their
I.t
solutions,
and
so,
when
we
think
about
pervasive,
you
know
openshift
being
pervasively
available
and
being
the
foundation
of
this
broader,
hybrid
cloud
platform.
You
know
in
inherent
in
that
is
you
know
the
ability
to
fold
into
that
platform
existing
and
new
investments
on
ibm
z
and
ibm
power
systems,
and
so
people
are
always
asking
you
know
what
does
what
does
open
shift?
A
Is
it
looks
exactly
the
same
as
the
open
shifter
you
might
be
familiar
with
running
on
on
intel
and
other
platforms
and
and
to
make
that
point
you
know
here:
we've
got
basically
the
you
know.
We've
got
a
view
of
the
dashboard
from
openshift
on
ibm
z
and
I
on
intel,
and
I
you
know
I
I
dare
you
to
figure
out
which
one
is
which
right
they
look
identical,
and
so
the
experience
the
whole
point
here
is
that
this
experience
needs
to
be
the
same.
A
Whether
you're
running
on
you
know
an
op
public
cloud,
whether
you're
running
on
intel
in
your
data
center,
whether
you're
running
on
z
or
power,
it's
the
same
experience.
It's
the
same
consumption
model.
It's
the
same
developer
experience.
You
can't
really
tell
the
difference,
and
you
know
if
you
want
to
find
out
more,
you
want
to
give
it
a
try.
You're
welcome
to
go
to
our
public
linux,
one
community
cloud.
A
We
allow
anybody
in
the
world
to
gain
access
to
those
systems
and
provision,
ibm,
z,
linux
instances
and
you
can
go
off
and
you
can
do
you
know
a
test
drive
of
openshift
on
on
ibm
z
on
linux,
one
and
and
see
it
for
yourself
in
action.
So
the
next
question
that
people
also
ask
is
you
know?
Why
would
you
do
this?
A
There's
there's
a
need,
for
you
know,
applications
that
are
developed
or
that
are
being
brought
to
bear.
It's
a
those
applications
need
to
be
near
the
data
that
they
consume
all
right
and
that
data
gravity
is
bringing
cloud
native
based
applications
nearer
to
that
data,
so
they
need
to
co-exist
and
be
co.
Co-Located
with
that
data
that
sits
on
ibm,
z
and
power,
and
then
there's
just
you
know
the
qualities
of
services
of
these
platforms.
A
Where
you
need,
you
know,
you
need
to
host
the
data
and
the
transactions
that
just
cannot
fail,
that
your
business
depends
on
that
are
mission
critical
to
your
business
and
then,
of
course,
a
lot
of
that
data
is
sensitive
in
nature
and
has
you
know
a
lot
of
a
lot
of
business
sensitivity
around
it
as
well,
and
so
the
ability
to
to
build
security
and
compliance
around
them
in
a
very
natural
and
holistic
way
is
also
fundamental
to
the
way
the
platform
is
engineered,
so
why?
You
know
why
open
shift
on
on
z?
A
Well,
largely
because
all
those
qualities
of
service
make
as
much
sense
in
a
world
the
cloud
native
world
as
they
did
in
the
in
the
traditional
I.t
world.
You
still
need
those
qualities
of
service,
there's
nothing
about
a
cloud
native
environment
that
removes
the
need
for
highly
resilient,
highly
secure,
highly
scalable
infrastructure.
Underneath
your
cloud
native
platform
and
to
be
honest,
a
lot
of
the
investment
you've
made
that's
running
on
top
of
these
platforms
needs
to
be
able
to
be
modernized
and
leverage.
A
The
cloud
native
experience
as
well,
and
so
we've
seen
three
core
patterns
evolve
around
ibm
z
and
linux,
one
with
respect
to
container
technology.
The
first
one
is
essentially
what
we
call
cloud
in
a
box
where
you
know
the
ability
to
host
massive
amounts
of
scale
on
a
very
small
physical
footprint,
bringing
down
data
center
footprint,
bringing
down
the
data
center
power
envelope
significantly.
A
Why
to
get
to
that
2.4
million
containers
per
box.
I
mean
that's,
that's
not
that's!
That's
a
cloud
in
a
box
experience
where
customers
can
really.
You
know
our
customers
can
really
get
to
a
very
high
density,
low
power,
low
physical
footprint,
compute,
and
that
gives
them
very
good
business
flexibility
so
that
their
business
can
grow
very
quickly
as
they're
as
and
not
be
held
back
by
their
it
infrastructure.
The
other
one
is
the
digital
transformation.
A
Modernization
where
you
know,
there's
an
existing
investment
on
that
runs
on
z,
the
ability
to
modernize
that
investment
without
having
to
completely
disrupt
that
investment
is
significant
for
clients
and
then
the
ability
to
do
consolidation
and
data
serving
at
scale
and
to
bring
down
the
cost
of
of
doing
that.
So
we've
seen
we
have
studies
that
say
you
can
bring
down
the
cost
of
running
openshift
infrastructure
by
up
to
almost
48
by
consolidating
it
onto
that
that
much.
B
A
You
know
highly
available
footprint,
and
so
an
example
here
of
you
know
a
client
that
has
that
has
a
significant
investment
in
their
their
core
banking
infrastructure.
It's
a
cobalt
application
running
on
a
cics
db2
on
zos
environment
and
that
they
wanted
to
extend
this
this
this.
You
know
that
investment,
but
they
wanted
to
extend
it
in
a
cloud-native,
containerized
fashion,
and
so
the
idea
here
is
they
wanted
to
incrementally
grow.
The
workload
grow,
the
transactional
workload.
A
They
tried
to
place
that
incremental
workload
off
on
an
intel
based
infrastructure
and
the
data
latency
of
going
off
to
that
intel
based
infrastructure
for
what
is
essentially
going
to
be
a
very
chatty.
You
know
application
because
you're,
you
know
incrementally
growing
the
the
business
logic
it's
going
to
be
very,
very
chatty,
getting
back
and
forth
between
the
old
and
the
new.
The
fact
that
it
was
the
the
the
the
the
the
latency
to
get
to
those
intel
boxes
was
so
high.
A
They
could
not
do
it
that
way
and
what
they
recognized
is
they
needed
to
run
open
shift
co-located
on
the
same
physical
infrastructure
as
where
those
cobalt
db2
zos
assets
existed,
and
that
allowed
them
to
bring
down
the
latency
by
almost
of
an
order
of
magnitude.
It
allowed
them
to
improve
the
slas.
The
service
level
agreements
for
their
transactions
bring
down
their
batch
times
for
their
workloads
and
and
get
to
a
much
more
resilient
outcome,
and
it
positioned
them
very
well
for
more
modernization.
B
A
A
On
a
single
linux,
one
or
ibm
z
system,
you
can
host
actually
five
different,
hypervisors
and
so
85
different
hypervisors,
each
of
which
can
host
thousands
of
linux
environments
and
obviously
millions
of
containers
right
and,
and
you
can
grow
or
extend
or
add
new
hypervisors
or
new
linux
guests
non-disruptively.
You
never
have
to
bring
down
the
system,
never
have
to
reboot
it.
You
can
also
move
resources
around,
be
it
memory
io
and
to
see
compute.
A
You
can
move
all
of
that
around
transparently
non-disruptively,
so
that
for
databases
which
you
know
like
to
scale
up,
you
can
scale
them
up
in
a
very
holistic
and
natural
way
for
applications
that,
like
to
scale
out,
you
can
scale
them
out
in
a
very
natural
and
holistic
way.
You
can
network
everything
software,
it's
all
software.
When
you
talk
about
the
networking
in
this
world,
there's
no
physical
networking.
A
Everything
is
done
in
software,
so
it's
highly
resilient,
it's
highly
low
latent
low
latent
and
it's
it's
it's
highly
secure
because
the
data
never
leaves
the
box,
and
so
you
get
this
really
wonderful
elastic
system.
When
you
throw
in
the
fact
that
you
can
compute
that
you
can
consume
all
of
that
elasticity
and
you
can
experience
all
of
that
elasticity
and
that
scalability
from
an
open
shift
value
proposition.
Where
you
know
again,
it's
the
same
experience
you
would
have
on
any
other
platform.
A
You
really
get
to
something:
that's
unique
and
distinct
in
the
industry,
and
that's
why
we
like
to
call
this.
You
know
a
cloud
in
a
box
experience
and
then
so
the
last.
The
last
key
point
that
I
wanted
to
highlight
about
ibm,
z
and
linux.
One
is
some
of
the
differentiation
that
the
platform
holds
around
confidential
computing.
We've
been
investing
in
trusted
execution,
environments
and
confidential
computing
on
this
platform
for
over.
A
Nobody
else
in
industry
has
that
level
of
certification
on
on
their
hsms.
We
do
and
we
offer
them
in
our
public
cloud
under
our
hypertext
hypertech
crypto
services,
we
offer
it
as
a
service,
and
that
allows
you
to
keep
your
secrets
and
your
keys
secure
in
a
manner
that
nobody
else
can
in
in
a
cloud
in
a
public
cloud
setting,
and
so
all
of
this
is
really
also
part
of
the.
You
know
why
why
hybrid
cloud,
why
clown
with
with
ibm
z,
okay,
so
I've
covered
z?
A
B
Marcel
so
my
name
is
christy
norman
and
on
the
flip
side
at
ibm,
I
work
in
the
power
organization
and
my
team
focuses
on
openshift
as
well
as
a
lot
of
other
open
source
projects
that
are,
I
guess
you
could
see
the
backbone
of
this
new
containerized
world
that
we
live
in.
So
over
the
past
seven
or
eight
years.
We've
done
a
lot
of
focused
work
to
make
sure
that
so
many
of
these
projects,
including
kubernetes
and
openshift,
run
really
well
on
power
systems.
B
So
I'm
going
to
talk
about
is
a
little
about
deploying
openshift
on
power
and
some
ways
to
make
that
easier
and
also
a
small
sampling
of
what
you
can
deploy
on
top
of
openshift.
If
you've
ever
done,
an
on-prem
openshift
install
even
on
another
any
platform
across
the
board.
Actually,
then,
you
know
it's
a
bit
of
work,
and
that
makes
us
very
thankful
for
our
devops
teams,
so
hopefully,
after
I'm
finished,
you'll
have
the
confidence
and
some
tools
to
help
you
tackle
this
yourself.
B
I'm
not
going
to
spend
a
lot
of
time
on
this
first
slide,
since
this
is
a
recorded
video,
you're
free
to
pause
and
read
the
fine
print.
The
first
thing
I
do
want
to
highlight,
though,
is
a
feature
that
gives
us
a
real
boost
with
regard
to
kubernetes,
and
that
is
our
ability
to
dynamically
adjust
cpu
capacity
based
on
the
current
workloads,
and
this
is
pretty
advantageous
with
respect
to
openshift,
as
it
gets
you
around
a
limitation
that
kubernetes
faces.
B
So
some
of
you
might
be
aware
that
kubernetes
at
startup
allocates
all
of
its
resources
to
various
components,
which
means
in
essence,
that
you
can't
later
hot,
add
cpus
or
memory,
but
on
power
the
system
can
adjust
the
capacity
of
a
cpu
at
the
hypervisor
level.
So,
instead
of
having
to
add
any
worker,
node
or
even
add
cpus
and
then
reboot
your
node,
your
nodes
already
doing,
the
work
can
simply
just
be
given
the
right
amount
of
processing
power.
B
And
then
the
other
thing
I'll
call
out
here
is
that
if
you
do
have
existing
power
workloads-
and
this
is
similar
to
what
marcel
mentioned
about
z-systems-
maybe
you're
running
ibm
I
or
aix
on
your
power
hardware
already,
then
you
can
have
linux
vms,
running
openshift
alongside
those
same
workloads
and
make
those
transactions
a
lot
faster.
Keep
your
data
all
in
the
same
place,
and
so
your
latency
is
extremely
low
and
it's
more
secure.
You
don't
have
to
move
your
data
outside
the
platform.
A
B
A
B
So
currently,
the
officially
supported
ways
of
installing
on
power
are
both
upi.
There
are
a
couple
of
development-only
ipi
options
that
we've
used
in-house,
there's
a
single
node
cluster
project
that
you
would
not
want
to
use
in
production
because
it
does
put
everything
into
a
single
virtual
machine
running
on
the
linux
box.
B
It's
really
great
for
development,
though
we've
used
it
in-house
for
some
testing,
and
so
it's
it's
been
really
good.
It
spins
up
pretty
quickly
and
then
the
other
is
a
liver
based
ipi,
which
is
also
helpful
for
dev
and
test
and
allows
you
to
have
multiple
nodes
on
the
same
system
and
it
takes
advantage
of
services
that
liver
provides
to
get
the
nodes
running
for
the
installer.
B
B
So
there
are
two
projects
that
I
think
are
extremely
helpful
for
anyone
who
is
installing
openshift
using
upi
they're
linked
here.
The
first
is
created
by
or
created
and
owned
by
my
team
within
ibm.
It
does
require
that
you
have
power
bc
in-house
to
assist
with
some
of
that
provisioning,
it'll
right-size,
your
notes
for
you,
install
them
and
configure
those
necessary
services
on
the
dedicated
helper
node
that
I've
mentioned
just
a
second
ago.
B
The
second
project
is
maintained,
maintained
primarily
by
red
hat,
but
since
it
is
an
open
source
project,
of
course,
contributions
are
welcome
by
anyone
and,
let's
see
the
link
that
I
put
on
this
slide
is
a
link
to
a
quick
start
for
installing
on
power.
Vm.
If
you
don't
have
power
vc,
but
I
do
want
to
make
sure
it's
clear
that
this
project
is
not
only
for
power
hardware.
B
So
these
are
really
helpful.
We
use
them
for
all
of
our
deploys.
We
recommend
them
for
customer
deploys
and
we
have
done
a
lot
to
make
sure
that
our
best
practices
are
baked
in
so
make
sure.
Even
if
you
don't
want
to
use
this
automation,
I
think
it's
helpful
for
anyone
who
wants
to
do
a
upi
install
to
be
aware
of
these
projects
and
go
take
a
read
through.
A
B
At
least
so,
in
addition
to
deploying
openshift,
I
do
also
want
to
make
sure
to
do
kind
of
a
quote-unquote
demo
using
openshift
on
power,
since,
as
marcel
mentioned,
the
user
experience
is
the
same
across
all
platforms.
I
thought
I
would
highlight
something
that
won't
look
identical
on
all
platforms.
It
does
and
it
doesn't.
It
sounds
a
bit
illogical,
but
bear
with
me
here
so
openshift
provides
some
operators
out
of
the
box
that
you
can
take
advantage
of
when
building
your
applications.
B
One
of
these
is
a
pretty
boring
operator,
actually
called
node
feature
discovery.
It's
boring
in
the
sense
that
it
doesn't
take
a
lot
to
set
up,
but
it's
really
useful.
So
let's
say
you
want
to
run
certain
workloads
on
a
node
that
only
has
a
very
specific
capability,
so
this
operator
is
specialized
in
that
it
and
very
securely.
B
I
will
say
this
probably
sounds
scary
to
a
lot
of
people,
but
it
queries
all
the
hardware
and
software
capabilities
of
your
notes,
so
it
then
turns
that
information
into
kubernetes
labels,
which
you
can
use
to
target
nodes
in
your
job
specs,
since
this
operator
just
takes
a
couple
of
clicks
to
deploy
and
the
default
values
are
provided
and
fine
to
use.
Then
I
just
put
a
screenshot
here
on
this
slide.
To
give
you
an
idea
of
what
operator
hub
looks
like
and
which
of
the
operators,
I'm
talking
about.
B
Okay,
so
after
you've
installed
and
deployed
the
operator,
the
labels
that
it
populates
show
up
in
the
top
of
the
output
of
your
oc,
get
node
for
the
this
specific
node.
So
this,
I
think,
is
a
worker
zero
in
my
cluster
and
then
a
little
bit
further
down.
Unfortunately,
for
this
presentation
that
shows
up
at
the
top
of
the
output,
you
can
see
those
labels
actually
populated
with
the
values.
B
So
you
can
see
how
this
would
be
really
useful
if
you
had
an
application
that
you
wanted
to
only
run
parts
of
on
the
very
specific
nodes
in
your
clusters.
You
can
use
this
operator
which
again
just
ships
out
the
box
with
red
hat,
is
supported
on
power,
z
and
intel
platforms
to
do
really
specific
targeting
for
any
workload.
That
requires
something
like
this
so.
A
B
Some
of
their
applications,
so
I
just
wanted
to
give
this
as
a
sort
of
a
demo,
but
not
so
much
a
demo.
It's
not
super
flashy,
but
I
thought
I
would
mention
it
and
then
I
do
also.
This
is
a
customer
use
case
that
I
wanted
to
show
to
make
sure
that
it
was
clear
that
you
can
do
a
lot
more
interesting
things
on
openshift
on
power.
B
Kafka,
notably,
was
what
they
used
to
stream
all
of
the
data
that
they
were
using
to
in-house
to
speed
up
their
application,
and
then
they
used
ibm
storewize
as
their
backend
and
an
ibm
cloud
pack
called
ibm
compact
for
data,
which
we
didn't
really
go
into
ibm
cloud
packs
here,
which
is
sort
of
a
bundle
of
things
that
you
can
install
on
top
of
openshift
and
a
lot
of
other
things
that
are
offered
by
ibm.
So
they
combined.
B
B
Project
that
I
mentioned
earlier
on
is
also
contains
a
repository
that
will
allow
you
to
deploy
openshift
into
power
bs.
So
there
are
lots
of
different
automation
scenarios
in
that
first
repository
for
power
systems.
So
if
this
is
something
that
you're
interested
in,
I
just
wanted
to
mention
that
briefly
and
go
take
a
look.
This
is
a
screenshot
actually
of
the
tutorial
for
using
that
repository
to
deploy
openshift
due
to
our
power
bs.