►
From YouTube: State of OpenShift on VMWare with Robbie Jerrom (VMWare) at OpenShift Commons Gathering 2019
Description
State of OpenShift on VMWare with Robbie Jeromm
at OpenShift Commons Gathering 2019
Red Hat Summit
Robbie Jerrom
NEMEA Tech Lead – Applications and Cloud Native Platforms
NEMEA Tech Lead – Applications and Cloud Native Platforms
A
Thank
you
so
I'm
here
to
talk
about
Merl,
openshift
and
vmware
and
and
bringing
to
bringing
the
two
things
together,
and
this
leads
me
to
think
about
how
do
we
get
here?
How
did
how
do
I
get
to
be
on
the
stage
and,
firstly,
it
comes
down
to
VMware
sort
of
core
values
if
you
like,
and
we
like
to
do
things
a
little
bit
differently.
A
Sometimes
it
takes
us
a
little
while
to
to
get
up
to
speed
with
those
things,
but
once
we
are
we're
all
about
executing
doing
something,
making
a
bit
of
a
difference
for
our
customers
and
being
passionate
about
how
we're
going
to
do
that.
How
we're
going
to
really
to
make
a
difference,
make
something
useful
for
our
customers
to
be
able
to
do
something
in
this
case
open
shift,
and
how
are
we
going
to
do
that?
A
A
They
got
the
guys
in
the
US
around
how
he
can
how
he
can
best
make
the
platforms
that
customers
have
worked
really
well
together
to
deliver
the
applications
in
an
easier,
more
performant
way
and
and
shout
out
to
Chris
in
the
Red
Hat
team,
they've
been
so
incredibly
helpful,
so
open
so
sharing
I'm.
So
trusting
of
working
together
that
it's
actually
been
a
really
enjoyable
experience
and
I'm
really
looking
forward
to
doing
more
with
it.
And
it's
it's
really
about
that
integrity
and
being
here
to
pull
it
together
to
deliver
joint
customer
success.
A
So
our
mutual
customers
can
just
consume
the
platforms.
They
have,
has
the
infrastructure
and
have
it
rung,
and
we
can
do
that
without
the
community,
so
the
focus
of
what
I've
been
working
on
and
the
team's
been
working
on
has
been
the
community.
It's
been
all
about
taking
the
platforms.
What
we
have
so
it
turns
out.
We've
got
more
in
common
than
we
know.
You
know
the
platforms,
the
openness
we
had
to
deliver
things,
and
so
this
is
what's
new.
A
We
have
open
to
311
on
the
VMware
software-defined
data
center,
so
the
three
components
from
the
the
VMware
side,
the
the
hypervisor
ESXi
vSphere-
is
where
most
of
our
customers
kind
of
stop.
Today,
when
you're
running
open
shift,
I
talk
to
customers
and
they're
using
the
hypervisor
part
they're
using
vSphere,
but
they
have
all
the
other
pieces.
They
have
all
the
other
pieces
of
the
software-defined
data
center
they're,
just
not
plugging
them
in
in
a
way
that
gives
them
benefit
to
open
shift,
so
storage
being
at
used.
A
V
sound
vSphere
data
stores
being
out
to
connect
to
the
persistent
volumes
down
through
the
infrastructure
to
give
visibility
across
the
whole
stack.
It
doesn't
happen
for
a
lot
of
customers
being
out
to
deliver
the
existing
NSX
software-defined
data,
a
software
networking
up
into
openshift,
so
you
can
have
consistent
networking
and
security
across
virtual
machines,
bare
metal
and
and
the
openshift
platform
doesn't
really
happen.
Today
and
when
we,
when
we
ask
customers
well,
why
doesn't
happen
turns
out
that
the
the
answer
is
fairly
very
simple.
A
A
It
turns
out
that
when
we
speak
to
a
lot
of
customers
and
customers
actually
routing
on
to
ESX
hosts
to
consider
to
configure
storage
volumes,
because
that's
what
the
documentation
said,
there's
lots
of
easier
ways
of
doing
it.
Please
don't
SSH
on
to
your
ESX
hosts
anymore.
You
really
don't
need
to
do
it.
Evi
admins
are
going
to
get
upset.
You
can
do
it
all
threat,
CK's
and
command
lines,
so
we've
documented
all
of
that
stuff
and
we
rolled
it
into
the
core
documentation
and
we've
also
updated
the
best
practices,
the
reference
architectures.
A
So
the
311
reference
architecture
document
how
to
deploy
it
and
run
OpenShift
on
the
vmware
software-defined
data
center
in
a
way
that
just
benefits
both
and
ultimately
then
benefits
the
that
the
applications
you
guys
are
all
trying
to
run.
So
that's
what
we're
doing!
That's
what
we've
done!
Sorry
and
there's
going
to
be
some
blog
posts
and
some
technical
releases
later
this
week,
I
think
Thursday,
where
you
can
actually
look
at
some
of
this
stuff
and
see
what
we've
done.
A
A
So
from
a
VMware
side,
we've
taken
the
sddc
and
that's
become
via
cloud
foundation,
so
that,
from
a
VMware
perspective,
is
a
fully
lifecycle,
managed
sddc
stack,
so
our
Software
Defined,
Networking
storage,
the
hypervisor,
it's
all
version
controlled
and
the
TAF
looked
after
for
you
from
from
an
infrastructure
perspective,
we
want
to
do
the
same
thing
with
version
4
openshift
make
it
a
workload
domain
within
the
VCF.
So
it's
incredibly
easy
to
deploy
the
automated
installers.
The
experience
you're
going
to
get
is
just
similar
to
a
cloud.
It's
quick
and
easy.
It
just
works.
A
I
need
I
need,
I
need,
opening
shifts
on
on
the
platform.
I
have
take
a
button
off.
We
go
and
once
again
we're
doing
that
through
the
community
processes,
so
once
again
continuing
committing
carrier
to
committing
documentation
into
the
OpenShift
repos
being
part
of
the
kubernetes
community.
Roughly
a
year
ago,
myself
and
some
colleagues
from
our
cloud
native
business
unit
created
the
the
sig
vmware
and
since
then,
we've
we've
been
involved
with
an
awful
lot
more
SIG's
and
we
kind
of
got
carried
away.
Sig
lifecycle,
sig
Ark,
to
cluster
OPI
and
about
twelve
others.
A
We're
actively
involved
in
so
we're
feeding
all
of
the
sort
of
VMware
stuff
into
the
kubernetes
community
and
into
the
openshift
communities
to
make
the
platform's
easier
to
work
together
to
get
the
benefit
across
the
board
and
make
things
just
better
for
our
customers,
hoping
she
have
Commons.
This
is
my
first
offensive
commons
event,
so
we're
just
getting
started
with
Commons
I've
joined
the
slack
channels.
I
said
hello
to
as
many
people
as
possible.
A
You
know
moving
forwards.
I
want
to
be
more
involved.
The
teams
are
going
to
be
more
involved,
want
to
hear
from
from
you
people
as
to
what
we
can
do
to
make
things
easier
and
we
want
to
make
it
happen
and
speak
and
make
it
easier,
and
this
is
kind
of
a
big
thing
if
you're
a
VMware
person,
a
validated
VMware
design
for
Pinterest
4.0,
so
a
complete
architecture,
all
the
VMware
pieces,
all
the
open
shift
pieces,
how
they
can
all
work
together
in
the
prescribed
fashion
to
deliver
you
an
application
platform.
A
So
this
is,
this
is
really
exciting
stuff
and
then,
finally,
at
vmworld
later
this
year,
there's
going
to
be
a
bunch
of
breakout
sessions
with
myself
and
some
others
and
and
Chris,
and
the
Red
Hat
team
sharing
best
practices
sharing
with
the
sort
of
the
VMware
community,
how
we
can
run
openshift
across
the
stack
and
deliver
deliver
those
applications
to
our
customers.
So
I'm
aware
that
I'm
sort
of
blocking
you
guys
from
lunch,
so
I'm
a
last
slide.
Why
are
we
doing
this?
Why,
to
the
end,
we're
doing
this?
And
you
know
we
have?
A
We
have
our
own
sort
of
kubernetes
solutions
and
things
that,
but
it's
really
about
our
customers.
We
have
customers
in
common
that
choose
to
run
openshift.
We
want
that
to
be
a
great
platform
or
on
the
on
the
software-defined
data
center,
and
we
want
the
applications,
no
matter
where
they're
written,
where
they're
hosted
how
they're
built
to
run
best
on
infrastructure
that
you
already
have
today
and
whether
it's
a
traditional
application.
A
It's
provisioning
is
through
OpenStack,
whether
it's
hybrid
applications
with
containers
and
some
virtual
machines,
whether
it's
cloud
native
applications
running
on
OpenShift
on
a
pass
and
it's
if
everything.
If
we've
got
a
common
platform,
then
everything
runs,
it
can
be
monitor,
can
be
managed,
it's
easier
to
understand
the
application,
it's
easier
to
scale
the
application,
it's
easier
to
manage
and
deliver
that
value
to
your
businesses
as
quickly
as
possible.
So
that's
that's
really!
Why
we're
doing
it?
A
We
want
a
platform
lets
you
run
everything
in
the
best
possible
way,
and
the
best
way
to
do
that
is
to
be
part
of
the
community,
be
involved,
listen
to
what
everyone
wants
and
then
try
and
make
it
happen
on
the
infrastructures
that
you've
got
so
I've,
just
so
everyone
by
three
seconds.
So
thank
you
very
much
for
listening
to
me
and
I.
Look
forward
to
talking
to
you
next
week.