►
From YouTube: Bringing OpenShift to IBM Cloud | Chris Rosen (IBM Cloud) | OpenShift Commons Briefing
Description
OpenShift Commons Briefing
Bringing OpenShift to IBM Cloud
Chris Rosen (IBM)
2020-04-19
A
Hello,
everybody
and
welcome
to
another
Red
Hat
OpenShift
Commons
briefing
and
this
time
we're
going
to
talk
about
bringing
Red
Hat
open
ships
through
the
IBM
cloud
with
crisp
Rosen,
I'm
gonna.
Let
Chris
introduce
himself
and
take
us
on
a
tour
and
talk
about
his
journey
with
open
shipped
on
IBM
cloud
and
give
us
a
bit
of
a
demo
and
there'll
be
live
Q&A
at
the
end.
So
Chris
take
it
away
all.
B
B
I
want
to
quickly
touch
on
the
use
cases,
because,
when
we're
developing
offerings,
you
know
it's
it's
cool
when
we
build
new
things
and
new
widgets
and
new
capabilities,
but
the
reality
is:
if
they're
not
solving
some
of
our
customers
problems,
then
you
know
really
what's
the
premise
of
doing
that.
So,
when
we're
building
things
like
Red
Hat,
open
shipped
on
IBM
cloud
from
here
on
I'll,
basically
just
call,
it
managed
open
shift
for
short,
because
it
is
quite
a
long
name.
B
What
are
the
use
cases
that
we're
really
trying
to
identify
and
the
first
one
is
really
about
innovation
and
its
enabling
our
users,
who
are
generally
developers
and
they're,
building
new
applications,
and
they
need
to
be
able
to
do
so
and
move
quickly
and
automate
everything
and
there's
the
icd
pipeline.
So
that
way,
it's
all
source
code
controlled
and
they've
got
the
right
teams
that
have
the
right
access
to
be
able
to
make
those
pushes
and
changes
and
and
do
so
in
a
very
secure
manner.
B
So
some
of
the
offerings
that
we
build
around
this
use
case
are,
of
course,
using
the
managed
open
shaft.
We
see
some
things
like
IBM
quad
functions
for
our
event-driven
server,
less
and
obvious.
So
that's
a
very
dynamic
space
as
we
get
into
K
native
starting
to
become
more
prevalent
in
those
use
cases
and
really
enabling
developers
with
CI
CD,
tooling
things
like
the
IBM
garage.
B
If
that's
a
new
term
to
you,
it's
basically
a
way
that
think
of
it
as
IBM's
consultant
branch,
where
they'll
go
out
and
they'll
work
with
our
customers
through
a
garage
session
and
what
that
means
is
the
customer
brings
their
real
problem.
I'm
trying
to
solve
X
and
you'll
go
through
a
design
thinking
session,
where
at
the
end
of
it,
you'll
have
a
thousand
post-it
notes
all
over
the
walls,
and
you
think
about
how
to
solve
your
problem.
B
What's
the
ultimate
lighthouse
kind
of
solution
for
it,
then
you
sit
down
in
pair
program
with
IBM
and
by
the
end
of
that
session
you
have
a
real
prototype.
So
what's
great
is
it's
not
just
a
you
know
workshop
where
you're
giving
hands-on
with
the
technology,
although
that's
very
valuable
as
well.
This
is
actually
solving
your
problems
and,
at
the
end,
you've
got
a
prototype
you're
thinking
about
how
do
I
solve
these,
not
only
technically
but
then
generally,
the
biggest
hurdle
is
culturally.
B
So,
let's
get
into
the
actual
offering
you
know:
we've
been
running,
managed,
kubernetes
and
containerized
loads
for
nearly
five
years
in
IBM
cloud
through
several
iterations,
and
so
we're
excited
when
we
launched
this
offering
on
August
1st
2019
after
you
know
the
acquisition
with
Red
Hat
and
bringing
them
on
board.
So
we're
excited
to
bring
all
of
the
value
of
open
chef.
So
iBM
has
not
done
anything
to
open.
B
Red
Hat
and
we
provide
all
of
the
same
capabilities
as
the
managed
service.
Openshift,
obviously
could
run
on
any
infrastructure
and
cloud.
So
how
do
we
make
it
optimize
and
the
best
landing
spot
to
be
able
to
run
those
workloads
in
public
cloud?
So
that's
really.
Our
focus
is
bringing
the
the
value
to
this
managed
service.
So
we
leverage
our
existing
sre
management
capabilities
for
the
20,000
plus
production
clusters
that
were
running
and
we
bring
that
to
managed
OpenShift
and
so
you'll
see
some
things
around
not
only
the
day.
B
One
deployment
of
your
compute,
your
networks,
your
storage,
but
then
day,
2,
lifecycle
management,
whether
it's
a
rail
pass.
Anything
in
that
stack,
whether
it's
open
shipped
itself,
which
obviously
Red
Hat
vets
and
make
sure
that
those
things
that
updates
are
validated
and
ready
or
anything
in
that
entire
stack.
Ibm
is
gonna,
manage
that
lifecycle
for
you
and
you'll
think
about
kind
of
the
line
of
roles
and
responsibilities
where,
as
a
customer,
you
want
to
focus
on
those
use
cases
whether
it
is
delivering
innovation
or
app
modernization.
B
B
Some
of
the
things
we're
very
focused
on
building
in
operational
characteristics
to
the
offering
so
things
like
with
every
cluster,
having
highly
available
masters
and
with
a
multi
zone
cluster
now
I'm
distributing
masters
and
worker
nodes
across
three
different
data
centers
at
a
given
IBM
Cloud
region.
So,
for
example,
if
there
were
some
catastrophic
network
outage
in
one
of
those
data
centers
well,
my
API
endpoint
is
still
accessible.
I
still
have
workloads
running
in
those
other
two
data,
centers
and
then
I
could
auto
scale
out
to
get
the
right
capacity
required
to
run
those
workloads.
B
B
Compliance
is
something
that
we
take
very
seriously
in
IBM
cloud
as
well.
Our
managed
open
shipped
offering
one
at
G
aid
back
on
August
1st,
had
all
the
things
around
sock,
one
sock
to
type
1
and
type
2
HIPPA
readiness,
PCI
compliance
and
compliance
is
a
two-way
street.
So,
obviously
you
know
we've
got
responsibility
to
control
the
compute
side
of
this
and
you,
as
a
user,
have
responsibility
as
well,
and
how
do
you
maintain
access
and
encryption
and
all
of
those
capabilities
within
workloads
running
inside
your
clusters?
B
Isolation
choices,
including
bare
metal.
So
if
you
need
that
amount
of
resource
or
GPU
or
ten
gig
bonded
Ethernet,
you
can
get
that
as
a
part
of
the
managed
service
and
then
the
last
point
here
is
an
industry-leading
99.99%
SLA
for
that
multi
zone
cluster.
So
because
all
of
our
control,
plane
and
most
of
the
services
running
in
IBM
cloud
have
standardized
to
run
on
top
of
kubernetes.
B
That
built
in
resiliency
and
availability
has
allowed
the
platform
to
increase
its
SLA
to
the
99.99
and
the
far
right,
bringing
the
fact
that
open
shift
as
I
said
earlier,
is
openshift
consistently.
Wherever
you
run
it.
That's
the
real
value
prop
of
hybrid
cloud
and
multi
cloud
and
using
open
shift
as
that
platform.
B
Now
I
can
consistently
run
workloads
wherever
I
want
to
run
and
wherever
I
have
I
as
the
far
right
column
is
really
talking
about
taking
that
platform
in
integrating
it
to
the
IBM
cloud
capability,
so
things
like
bring
your
own
key
with
IBM
key
protect
or
keep
your
own
key
with
IBM
hyper
protect
services
in
the
difference,
they're
being
with
keep
your
own
key.
It's
FIPS,
140
new
level
for
encryption,
we're
the
only
public
cloud
to
be
able
to
get
that
level
of
encryption
and
customers
own
the
keys.
B
So
even
though
it's
a
managed
service
from
IBM,
we
don't
have
access
to
your
data.
If
you
lose
the
keys,
we
have
to
replace
the
physical
HSM
that
stores
those
keys
so,
depending
on
the
level
of
encryption
and
isolation
of
those
workloads,
our
users
can
determine
which
level
works
best
for
their
use,
cases
and
requirements,
and
they
may
mix
and
match,
depending
on
different
projects
or
different
life
cycles,
of
an
application.
B
This
chart
yeah,
obviously
there's
a
lot
of
words
here,
but
we
start
to
when
we
think
about
the
word
managed
and
at
least
in
IBM.
The
word
managed
means
something
different
to
everyone
for
a
cloud
managed
service.
Essentially,
what
it
means
is
that
we're
taking
off
a
lot
of
the
operational
burden
for
our
user
or
that
instantiation
of
the
cluster
originally
or
that
ongoing
updates
and
lifecycle
management
tying
out
with
the
rest
of
the
platform.
B
So
that
way,
as
you
start
to
focus
and
build
or
add
cognitive
capabilities
to
your
apps,
and
you
want
to
bind
a
watson
service
or
create
a
chatbot
or
use
weather
data
or
IOT
or
analytics,
you
can
securely
consume
those
within
your
Red
Hat,
open
shipped
on
IBM
cloud
cluster
and
just
extend
those
apps
make
them
work.
Smarter
work
better
with
the
existing
code
base
that
you
have
and
now
you're
leveraging
these
higher
value
services
from
IBM
cloud.
B
Well
show
a
lot
of
these
things
in
the
demo,
but
quickly,
just
kind
of
you
know
talk
through
a
few
of
these
points.
The
first
one
is
around
simplified
cluster
management.
You
know,
you'll
see,
there's
a
lovely
UI
where
you
can
point
and
click
through
things,
but
the
reality
is
most
of
my
users
will
do
that
once
and
then
they're
gonna
automate
that
either
through
the
CLI
or
the
API.
B
So,
if
they're
running
on,
for
example,
openshift
4.3
and
we
say,
hey
4.4
is
available,
they
determine
when
is
the
right
time
for
them,
and
even
though
we'll
roll
through,
like
I,
mentioned
earlier,
they
still
control
and
determine
when
that
upgrade
will
take
place.
All
they
need
to
do
is
click
the
button,
and
then
we
take
care
of
the
rest
of
the
magic
for
them.
B
Essentially,
the
way
it
works
is
we
take
the
first
node
we
drain
all
the
deployed
pods
from
it
once
it's
quarantined,
then
we
reload
it
top
to
bottom
when
it's
online
and
healthily.
We
move
on
to
the
second
node
third
node,
so
on
and
so
forth.
Until
we've
completely
rolled
through
your
clusters
capacity,
we
also
support
worker
node
Auto
recovery.
You
know
the
reality
is
we're
just
dealing
with
hardware
and
software,
so
things
can
and
will
go
wrong.
B
So
it's
really
about
again
simplifying
the
operations
building
in
that
chaos,
monkey
mentality
when
we're
building
our
apps
and
ensuring
that
they
are
architected
to
be
able
to
handle
those
types
of
failures
and
outages,
and
then
the
last
thing
is
worker
node,
auto
scaling.
So,
as
you
need
to
add,
add
additional
capacity,
you
can
do
so
and
control
when
to
scale
up
or
down
designing
your
own
cluster.
You
know
it's
really
about.
One
is
about
compute
isolation,
choice,
an
IBM
cloud:
you
could
have
shared
compute,
which
is
a
single
tenant.
B
Virtual
machine
multi,
tenant,
hypervisor
Hardware,
just
think
of
any
public
cloud
VM.
We
also
have
what's
called
dedicated
compute,
where
it's
single
tenant,
VM
hypervisor
hardware,
so
I'm
the
only
tenant
running
out
a
physical
piece
of
hardware
in
IBM
cloud,
and
then
the
last
option
is
bare
metal
like
I
said
earlier.
If
you
need
that
amount
of
compute
and
resources
and
one
node,
you
can
get
that
as
a
part
of
the
managed
service.
B
The
other
thing
that
we
provide
are
something
called
edge,
nodes
and
think
about.
This
is
just
minimizing
the
attack
surface
of
your
cluster.
So
instead
of
one
worker
pool
where
everything
is
running
now,
I've
got
an
edge
tool
and
all
of
my
inbound
and
outbound
traffic
route
through
this
well
there's
my
IPS
and
my
IDs
are
all
running.
My
actual
containerized
workloads
are
in
a
fully
separate
pool
that
only
have
private
IBM
backbone.
Networking
so
again
just
adds
a
layer
of
protection
from
your
workload,
security
and
isolation.
B
You
know,
obviously
we
could
spend
an
hour
on
this
one,
a
few
other
things
that
we
we
enable
here
for
our
users.
We
used
Lux
encryption
by
default
and
all
of
the
secondary
drives
where
your
containers
are
running.
If
you
are
running
some
high-performance
workload,
you
could
opt
out
of
that
or
you
know
whether
it's
at
the
work
of
pool
or
cluster
level,
so
you
can
determine
the
amount
of
encryption
and
the
isolation
that
we
talked
about
before.
We
also
integrate
with
image
signing
with
Red
Hat
notary.
B
B
Or
other
industries
having
that
weather
data
can
make
our
app
smarter
and
they
can
make
our
engagement
models
more
more
engaging
with
our
end
users.
So
we're
really
focused
on
that.
The
other
thing
that
I'll
mention
here
and
we'll
see
this
in
the
demo
are
things
like
integrating
with
IBM
cloud
Identity
and
Access
Management.
So
now,
I
can
be
very
fine-grained
and
prescriptive
over
the
amount
of
control
that
I
give
users,
because
some
of
my
customers
will
create
different
clusters
for
different
teams
or
different
stages
of
that
applications.
B
Lifecycle,
but
other
customers
will
create
a
larger
internally
multi-tenant
cluster,
such
that
within
that
I've
got
different
projects
and
I've
got
team
a
in
this
project
and
that
I've
got
team
B
in
this
one
and
I
can
give
access
down
to
that
project
level.
So
it
allows
me
to
control
and
leverage
my
underlying
resources
much
more
efficiently.
B
The
fifth
thing
you
know
open
source,
obviously
very
important
to
IBM
and
Red
Hat.
Both
have
not
only
been
core
contributors
to
these
technologies,
but
also
consume
and
build
our
commercial
offerings
on
top
of
open
source.
So
that
was
you
know
really.
Obviously,
Red
Hat
and
IBM
have
been
partners
for
over
20
years
and
bringing
the
acquisition
last
year
just
brings
that
to
a
closer
relationship
where
we
both
continue
to
contribute
and
run
these
open
source
projects.
So
I
think
that's
great.
B
When
I
talk
to
customers,
obviously
they
want
this
whole
limiting
vendor
lock-in
and
that's
what
container
technology
has
given
them.
So
now,
they've
got
that
ability
to
package
up
their
apps
and
all
their
dependencies
and
have
that
movement.
But
the
reality
is
these
open
source
projects
are
hard.
When
you
look
at
all
of
the
components
that
go
into
OpenShift
and
into
our
managed
OpenShift
offering
there
are
a
lot
of
open
source
projects,
so
let
IV
m
and
Red
Hat
handle
the
complexity.
B
So
if
an
update
in
one
community
ensuring
that
it
doesn't
adversely
affect
anything
else
in
the
stack
or
making
sure
that
when
new
updates
are
available,
that
they
are
in
fact
secure,
upgradeable
operational,
you
know
all
those
things
that
are
important
to
you
is
end
consumers
of
our
offerings
and
then
the
last
thing
is
around
integrated
operational
tools.
As
I've
said
several
times,
OpenShift
is
a
platform,
so
there's
a
lot
that
comes
baked
into
openshift
itself.
To
have
that
consistently
consistency
anywhere
that
it's
running
in
IBM
cloud.
B
We
also
have
managed
services,
whether
it's
monitoring
or
logging
or
security
tools
that
can
live
outside
of
the
lifecycle
of
an
individual
cluster.
You
can
also
leverage
those
from
other
computer
Isis
or
other
solutions,
whether
it's
an
IBM
cloud
other
cloud
or
on
Prem
to
give
you
operationally
debt
now.
The
great
thing
is
that
if
your
customers
have
already
chosen
some
other
vendor
to
provide
monitoring
or
logging
or
security
or
CITV,
you
know
fantastic.
B
No
one
is
advocating
that
you
scrap
what
you've
invested
in
then
those
technologies
you
can
deploy
those
very
easily
and
open
ship
and
send
those
metrics
out
to
your.
You
know
the
source
of
truth,
whether
it's
a
SAS
offering
or
something
running.
On
Prem
and
again,
your
operations
teams
don't
need
to
learn
the
new
model
of
managing
an
environment,
even
though
they
may
be
running
Red,
Hat,
open
shipped
on
IBM
clouds
for
the
first
time.
It's
really
about
consistency
and
easing
that
adoption
curve.
B
One
quick
topic
before
I
jump
into
the
demo
is
around
IBM
cloud
packs
and
I
want
to
talk
about
that
briefly,
just
to
kind
of
make
sure
everyone
is
aware
of
what
we're
doing
and
I'm
sure
we'll
have
a
deeper
dive
into
these.
As
we
proceed
through
these
sessions,
a
cloud
pack
is
basically
think
about
IBM
bringing
its
standard,
middleware
stack
of
applications
and
capabilities
to
a
containerized
ecosystem
and
from
a
cloud
pack.
B
If
I'm
a
software
seller,
I
obviously
want
to
be
able
to
sell
that
cloud
pack
that
solution
to
run
on
any
openshift
environment
in
any
of
these
public
clouds
in
a
consistent
manner,
so
openshift
becomes
that
vehicle
to
provide
IBM
cloud
packs
in
your
data
center,
an
IBM
cloud
or
any
of
these
other
public
clouds
that
are
listed
here
today.
There
are
six
cloud
packs.
You
know.
Each
of
the
cloud
packs
are
really
targeted
toward
an
individual
kind
of
use
case
or
mission.
B
So,
for
example,
let's
just
use
cloud
pack
for
multi
cloud
management
as
our
example
and
coming
back
to
this
relationship
with
Red
Hat
and
IBM
Red
Hat
owns
the
multi
cloud
management,
open
source
technology,
they're
developing
it,
then
a
cloud
pack
around
it,
which
includes
that
and
some
other
capabilities
as
well.
So
now
I
deploy
this
cloud
pack
for
multi-cloud
management,
and
it
gives
me
insight
to
my
clusters
in
different
clouds.
It
gives
me
governance.
It
gives
me
access
in
a
through
a
single
pane
of
glass
to
these,
regardless
of
where
they're
actually
running.
B
So,
as
I
said,
each
of
these
cloud
packs
can
run
anywhere.
My
challenge
as
the
offering
owner
in
IBM
public
cloud
is:
how
do
we
make
IBM
Club
the
best
place
and
most
optimized
place
to
not
only
run
open
chef
but
also
cloud
packs,
so
the
things
that
we've
already
talked
about
with
manage
open
shaft
around
our
compliance
and
our
security
isolation.
All
that
operational
experience,
that's
all
consistently
true
here
as
well
to
run
that
cloud
pack,
but
a
few
other
things
that
we've
done
to
make
it
easier.
B
The
first
thing
is
around
discoverability
and
that's
really
with
our
IBM
cloud
content,
catalog,
bringing
content
or
software
as
a
first-class
citizen
to
IBM
cloud.
So
now
you
would
discover
all
of
the
cloud
packs
that
are
out
there.
Other
software
from
IBM
and
Red
Hat,
so
discoverability
is
easier.
Now,
I
find
this
cloud
pack
from
multi
cloud
manager
and
I.
Think
you
know
that
sounds
pretty
awesome.
Let
me
deploy
it
now
through
a
one-click
installation
with
IBM
cloud
schematics,
which
is
I
mentioned
earlier.
That's
our
chair
form
and
soon
to
be
ansible
based
infrastructure.
B
As
code
offering
I
can
deploy
that
to
an
existing
Red
Hat
over
check
on
IBM
cloud
cluster
now
I've
easily
discovered
it
number
two
I've
easily
deployed
it
now.
I'm
running
that
cloud
pack,
software
stack
in
my
open
chef
cluster
now
I've
got
all
of
the
benefits
around
deploying
and
lifecycle
management
right
here
now.
B
So
with
that,
let's
jump
over
to
a
demo
I
think
you
know
that
will
speak
louder
to
of
what
we've
just
talked
through
dan
I'm,
sure,
you'll,
jump
and
yell.
If
you
cannot
see
my
web
browser
where
I've
logged
into
IBM
cloud,
you
can
see
my
overview
dashboard
of
all
my
resources,
all
the
things
that
are
happening,
whether
it's
maintenance
or
my
usage,
my
users,
all
that
is
a
quick
overview
when
I
log
into
IBM
cloud,
let's
jump
into
the
catalog
and
you'll
see
here
before
I.
Look
at
this,
this
software
tab.
B
B
Let's
go
back
and
take
a
look
at
the
the
offerings,
because
that's
what
we
really
want
to
demo
here
today,
you
can
see
right
here
under
my
featured
or
I
could
navigate
under
containers
and
I
can
see
Red
Hat
openshift
on
IBM
cloud.
Of
course
my
login
has
expired,
so
it
always
works
out
best
for
a
demo
and
I
have
to
log
in,
in
the
middle.
B
It's
hard
to
plan
that
any
better,
so
this'll
load
here
and
they'll.
Take
me
back
to
my
landing
page
for
Red
Hat
OpenShift
on
IBM
cloud,
where
I've
got
some
as
I
get
started,
some
basic
cluster
information.
So
what
do
I
want
to
call
this
nothing
better
than
calling
it
demo
under
resource
group
here
I.
Could
this
is
what
I
talked
about
earlier
with
allocating
resources
to
different
people
within
my
IBM
cloud
account.
So
maybe
this
is
going
to
go
to
my
prod
resource
group,
because
it's
a
very
important
demo.
B
Cluster
I
can
also
tag
it
so
that
way,
I
could
find
it
later.
As
I
scroll
down
here,
you'll
see
location.
Now,
here
I've
got
single
zone.
We
support
all
six
of
the
existing
multi
zone,
regions
or
MGRS
for
short
and
35
single
zone
regions
or
SCRs,
so
if
I
needed
to
deploy
something
in
San
Jose
or
in
Montreal
or
Toronto,
when
I
create
a
cluster
they're,
the
masters,
the
workers,
everything
remains
in
that
boundary.
So
when
I
talk
to
customers
in
Canada,
you
know.
B
They
need
to
ensure
that
date
logs
etc
are
not
leaving
the
Canadian
boundary.
So
now
they've
got
that
option
they
could
deploy
to
Montreal
or
Toronto
and
have
that
deaf
isolation.
You
can
see
it's
out
here
querying
that
I
have
no
VLANs
and
those
data
centers
so
would
go
ahead
and
create
one
for
me.
Let's
go
back
to
multi
zone
because
I
think
that's
slightly
more
interesting
thinking
that
you
know
capability
at
cluster
creation
time.
So
under
geography
I
can
search
whether
I
wanted
to
do
ap
or
Europe.
B
For
this
example,
let's,
let's
just
pick
Europe
under
the
Metro
I,
can
do
London
or
Frankfurt
and
we'll
use
Frankfurt
here.
So
these
are
the
three
different
data
centers
that
I
talked
about
no
VLANs
there
I
there,
which
is
no
problem.
Let
me
scroll
down
so
now.
We've
got
our
default
worker
pool
today,
we're
g8
on
3.11
when
we
developed
this
offering
it
was
during
our
accusation:
quiet
period.
So
we
couldn't
actually
talk
to
red
hat
and
say
hey.
This
is
what
we're
gonna
build.
B
What
do
you
think
we
had
to
go
build
it
once
the
acquisition
closed?
Then
we
could
go
back
to
the
team
and
say:
hey
look
it.
This
is
how
we
run
it.
This
is
how
we
operationalize
open
shift
and
then
go
from
there
based
on
that,
we
needed
to
do
some
joint
work
with
an
open
source
project
called
the
hyper
shift
toolkit
which
basically
enables
how
IBM
manages
our
infrastructure
and
what
that
means
is.
B
When
we
create
this
cluster,
the
master
nodes
deploy
to
my
infrastructure
account
in
a
separate
cluster,
then
the
worker
nodes
that
deployed
your
infrastructure
account
in
a
different
cluster.
So
that's
where
this
joint
collaboration
with
Red
Hat's
openshift
team
and
my
team
came
into
play
to
make
that
a
reality.
So
now
we're
currently
in
an
open
beta
on
4.3,
we
will
GA
on
April
1st
here
in
just
a
few
weeks,
so
we're
very
excited
to
be
able
to
get
this
live
and
out
the
door
for
our
customers.
B
So
let's
use
the
beta
because
that's
more
exciting.
On
the
left
hand,
side
I've
got
some
filters
so,
as
I
mentioned
earlier,
if
I
want
that
bare-metal
or
different
virtual
machine
isolation
choices,
I
can
like
that
and
then
I
could
scroll
through
and
read
different,
basically
t-shirt
sizes
or
flavors,
with
a
baked
in
amount
of
virtual
CPU
in
memory.
So
let's
just
use
a
four
by
sixteen
here's,
the
encryption
that
Lux
encryption
that
I
talked
about.
You
could
turn
it
on
or
off,
and
then
you
know
how
many
nodes
do
I
want
in
each
zone.
B
So
when
I
think
about
my
Frankfort
Oh
204,
no
six
data
centers
by
default
I'm
going
to
put
three
workers
in
each
of
those
zones
and
then
the
last
little
check
is
I've
got
an
infrastructure
or
permissions
checker,
because
if
I'm
running
a
multi-tenant
account
maybe
I've,
given
you
access
but
I'm,
not
allowing
you
to
create
and
deploy
resources.
So
then
you
would
see
a
red
X
in
here.
This
is
you
know,
maybe
you
don't
have
the
right
permissions
to
create
networks
or
storage.
B
This
is
my
account,
so
you
can
see
that
I
can
go
ahead
and
deploy
it.
One
thing
that
you'll
notice
that,
because
this
is
a
Veda,
we're
not
metering
and
billing
for
the
OpenShift
license
itself
once
we
GA
all
beta
clusters
will
will
be
removed
after
30
days
and
you'll
have
to
redeploy
new
production
clusters
where
we
are
in
fact
metering
that
so
I'm
gonna
click
create
and
it'll
go
off
in
churn
once
this
jumps
me
out
to
the
right
page,
you
know,
since
that
will
be
less
exciting,
to
watch
that
deploy.
B
Let's
take
a
look
at
something.
That's
already
running
an
IBM
cloud.
On
my
left
hand,
nav,
you
can
see.
I
can
take
a
look
at
different
types
of
compute
or
resources
that
I'm
running
in
the
catalog.
When
I
look
at
my
open
shift
clusters
landing
page,
here's,
the
new
guy,
you
can
see
him
he's
off
and
churning
and
creating
my
master
knows
and
getting
that
ready
to
go.
For
this
example.
Let's
take
a
look
at
there.
B
We
go
so
when
I
look
at
my
cluster
again,
I've
got
a
big
blurb
across
the
top,
which
is
again
doesn't
play
very
well
in
a
demo.
But
it's
telling
me
that
this
is
a
beta
cluster
and
it
will
be
purged
after
we
GA,
but
I
get
a
lot
of
relevant
information
to
my
cluster,
the
ID,
the
version
where
it's
running
my
ingress
sub
domain,
which
is
very
pay
full
long
name
I.
Obviously,
if
I'm
running
production,
workloads,
I'm
gonna
bring
my
own
domain
name
to
this.
B
That
way,
it's
just
Chris's
app
com,
not
this
whole
big
arbitrary
name.
So
you
can
do
that
as
well.
Under
worker
nodes,
I
can
see
additional
detail
around
individual
nodes.
What's
the
flavor,
what
are
their
public
and
private
VLANs?
What's
their
hardware
isolation
choice,
and
this
is
where
I
would
do.
Lifecycle
management,
so
here
I
could
select
all
three
and
say
update
and
it's
gonna
take
me
to
4.3
dot,
5,
15,
14
and
say
yep.
Let's
do
it!
B
Worker
pools
it's
a
fairly
common
constructs.
What
and
I'm
the
first
time
I
create
a
default
pool
if
I
later
said
well,
the
four
by
sixteen,
it's
not
big
enough
I
need
some
larger
some
additional
capacity.
Obviously
I
can't
change
that
on
the
fly,
but
what
I
can
do
is
create
a
new
pool,
so
I
call
this
pool.
2
and
I
need
this
to
have
16
by
16.
My
apps
are
very
CPU
intensive,
so
I
need
that,
and
here
I
could
create
a
multi
zone.
Pool
or
I
could
keep
it
as
a
single
zone
tool.
B
So
now
it's
all
running
in
Dallas
ten
in
this
example
I'm
saying
yep,
let's
go
ahead
and
create
that
let's
jump
back
out,
but
it
allows
you
now
in
this
model
if
I
wanted
to
now,
I
could
delete
the
default
pool
and
essentially
will
automatically
redeploy
anything
from
that
pool
to
the
second
one.
So
that's
how
I
would
grow
and
expand
and
add
new
capabilities.
B
This
other
tab
is
called
the
add-ons
tab.
These
are
things
that
IBM
is
managing
as
a
part
of
the
overall
offering.
So
we've
got
something
called
the
Diagnostics
and
debug
tool,
I'll
open
that
up
here
and
that
will
essentially
allow
me
to
run
some
queries
against
routes
and
against
other
services.
That
part
of
my
managed
service
and
make
sure
that
they're
running
properly
gives
me
some
great
insight.
B
So
as
I
start
to
troubleshoot
things
and
try
and
figure
out,
you
know
that
networking
is
that
something
in
my
yamo
really
trying
to
identify
the
root
cause
of
that
problem.
And
then
the
last
tab
is
DevOps,
and
so
this
is
bringing
from
a
broader
view
of
the
ICT
tooling
from
IBM
cloud,
which
is
moving
toward
the
checked
on
base.
If
I've
got
some
workload,
if
I
already
had
us
the
ICT
pipeline
deploying
to
this
cluster,
it
would
show
up
here,
but
I,
don't
so
with.
B
This
would
allowed
me
to
create
that
tool
chain
that
lives
outside
of
that
cluster.
So
now,
I
could
be
deploying
from
from
here
to
this
cluster
or
to
other
clusters
running
anywhere
consistently.
So
it
kind
of
gives
me
that
ability
to
control
the
CI
CD
to
language
n,
what
I
want
to
directly
an
open
shift
or
if
I
want
to
do
it
from
an
IBM
cloud
services
capability.
B
The
last
thing
that
I
want
to
show
because
I
talked
earlier
about
a
native,
consistent
user
experience,
which
is
obviously
really
important
for
our
users.
If
you're
using
OpenShift
on
Prem
or
in
any
other
cloud,
you
want
the
same
capabilities
when
you
come
and
try
Redhead
OpenShift
on
IBM
cloud,
so
things
like
making
it
easy
one-click
to
get
out
to
the
open
chef
console.
You
can
do
that
yeah.
B
You
may
have
seen
that
I
got
asked
to
reallocate
again
security
extremely
important
here
at
IBM,
so
we
need
to
make
sure
that
we're
we're,
checked
and
updated,
but
once
I
do
get
in
now,
I've
got
access
to
the
same
capabilities
that
you
would
see
an
open
chef,
4.3
anywhere
I've
got
my
administrator
view.
I
could
go
in
here.
I
could
discover
operators
I
could
go
up
here
to
the
dev
console.
I
could
look
at
my
bills,
my
pipelines,
my
deployment,
topologies
I
can
see
all
of
that
in
this
cluster.
So
you
know.
B
A
There
have
not
been
any
questions
from
outside,
but
I've
actually
learned
quite
a
bit
about
things
that
I
hadn't
realized
about
the
IBM
offering,
including
the
H,
a
availability,
bare
metal
and
the
edge
stuff.
So
I
think,
maybe
when
you
get
to
the
end
of
this,
if
you
can
talk
a
little
bit
more
about
how
to
go
about
using
maybe
the
bare
metal
or
that
piece
and
also
totally
blown
away
by
getting
to
see
4.3
beta
live
demoed,
though
this
is
totally
on
target
with
what
you're
delivering
so
keep
on
motoring
on
here.
Excellent.
B
If
I
could
find
it
extra
storage
for
software-defined
storage-
and
this
is
providing
additional
local
disk,
so
you
don't
need
to
use
file,
block
or
object
storage
from
IBM
cloud
I
as
its
directly
built
in
to
that
flavor,
and
now
you
can
consume
that
one
of
our
largest
users
runs
all
bare
metal
with
this
attached
local
desk.
That
way
they
have
the
ability
to
be
able
to
run
that
workload.
Keep
all
the
data
in
proximity
for
much
faster
you
time.
The
other
use
case
is
really
around.
B
You
know
machine
learning,
or
we
have
a
lot
of
data
scientists
that
are
running
workloads
and
that
allows
them
to
run
that
in
very
you
know,
resource
intensive
manner
and
what's
great,
is
that
I
don't
have
to
be
an
I
as
admin
when
I
deploy
this.
If
I
select
this
and
it
goes
and
deploys
IBM's
gonna
handle
deploying
that
bare
metal
server
and
all
of
the
lifecycle
so
to
you
as
a
consumer,
it
just
looks
like
bare
metal
resources
that
I'm
deploying
my
openshift
worker
nodes
to
I'm
running
my
workloads.
A
B
So
we've
we've
been
working
with
a
number
of
customers
on
the
beta,
getting
their
feedback
working
very
closely
with
the
OpenShift
team.
They've
just
got
us
some
fixes
this
week,
so
we're
excited.
We
should
have
everything
tied
out
with
a
ga
announcement
on
April
1st,
so
everyone
keep
that
between
us
friends
right
now
and
stay
tuned
for
all
of
the
blog
announcements
and
all
the
Twitterverse
noise.
That
will
happen
when
we
are
virtually
popping
champagne,
since
we
all
have
to
be
isolated
from
each
other
right
now.
Yes,.
A
B
A
A
Hopefully,
we
will
get
more
beta
testers
and
a
lot
of
people
using
this
one
of
the
things
that
always
is
the
toughest
is
getting
all
those
industry
level
compliance
offerings
and,
and
so
I'm
pretty
impressed
with
with
that
achievement
on
on
your
half
with
OpenShift,
so
I
think
you're
gonna
see
some
real
interesting
use.
Cases
come
your
way
so
looking
forward
to
having
you
back
again
soon,
Chris
to
hear
from
your
customers
and
more
feedback
on
OpenShift.
So
thank
you
very
much
for
taking
the
time
today
absolutely.