►
Description
Deploying OpenShift on vSphere, Azure, or AWS? We want to introduce you to SPLAT, the team that works hard to deliver OpenShift anywhere and everywhere. This week, we welcome SPLAT team members to talk about their role in the development and support of OpenShift. We’ll also talk about the vSphere Problem Detector, a SPLAT-created Operator which, as the name implies, checks for, identifies, and sometimes rectifies known problems with OpenShift on vSphere clusters.
Who is the SPLAT team?
OpenShift supports many different infrastructure types - AWS, Azure, vSphere, RHV, bare metal, etc. - and each one has different capabilities, features, and quirks. The OpenShift Specialist PLATform team is a group of specialists who focus on each of the infrastructure providers with a deep understanding of both.
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
B
Sir
sir,
thank
you
and
again
welcome
everybody
appreciate
you
joining
us
today,
so
this
is
our
second
episode
after
our
brief
hiatus
there
for
summit
and
kubecon
again,
if
you
didn't
catch
all
the
content
related
to
that,
it's
all
in
the
channel
history,
there's
blog
posts,
there's
all
kinds
of
other
stuff
out
there.
So.
B
Yeah,
it's
richard
welcome
back
to
the
to
the
stream.
You
know
you
were
here
for
our
very
first
episode,
so
it's
good
to
have
you
back,
so
this
is
one
of
our
office
hours
series
of
live
streams
effectively.
What
that
means
is
that
we
are
here
for
you,
our
audience
to
talk
about
whatever
it
is.
That
is
on
your
mind,
so
feel
free
at
any
point
throughout
the
stream
chris,
and
I
will
try
and
remind
you
periodically
to
ask
any
questions
that
you
happen
to
have
you
know.
B
Of
course
we
are
open
shift
experts
and
I
think
all
of
us
here,
probably
or
at
least
me
and
chris,
are
on
the
administrator
side.
I
think
joe
and
richard
have
a
little
more
developer
side
experience.
So
you
know
we
might
be
able
to
help
with
some
of
those
things,
but
by
all
means
whatever
it
is.
That
is
bothering
you
whatever
burning
questions
you
have
whatever
it
might
be.
You
know
let
us
know
and
we're
here
to
help.
B
B
D
D
So
the
splat
team
were
the
specialist
platform
team,
so
we,
the
the
members,
have
a
specific
platform
that
we're
supposed
to
be
experts
on
and
then
how
does
that?
Oh,
you
know
like
integrating
with
openshift
is
pretty
much
our
goal
and
how
do
we
help
our
developers
or
which
are
our
customers
principally
navigate
through
that
platform?.
B
Got
it
so
you
are,
let
me
make
sure
I'm
getting
this
right,
so
internal
to
the
engineering
teams,
you're
an
escalation
point
for
when
they
have
questions
about
how
aws
or
vsphere
or
red
hat
virtualization,
how
they
work
and
how
they
should
integrate
with
that
platform,
exactly
right
got
it
and
we
are
also
joined
by
richard
vanderpool
and
richard.
As
I
said
you
you
were
on
our
very
first
show
and
now
you're
on
our
29th
show.
But
your
your
role
over
the
last
wait.
Eight
nine
months
has
changed
pretty
significantly
right.
C
Yeah,
it
sure
has
so
I've
been
with
red
hat
for
gosh
about
26
27
months.
At
this
point,
it
feels
like
it's
been
10
years,
because
it's
just
been
an
absolute
blast
and
there's
so
much
to
learn
and
develop
your
skill
set
here
at
red
hat.
It's
just
been
a
really
great
time,
but
yeah.
So,
prior
to
about
nine
months
ago,
I
worked
in
openshift
support
so
likely
a
number
of
the
folks
in
the
stream
have
either
talked
to
me
over
the
phone
or
have
corresponded
with
me
via
case
updates.
B
Yeah,
I
can
only
imagine
how
much
the
engineering
teams
value
that
perspective,
because
I
know
like
any
time
I
interact
with
engineering
folks,
they're,
always
kind
of
begging
for
that
customer
perspective
like
well.
Why
are
customers
doing
this?
What
does
this
mean
to
them
like?
How
can
you
know-
and
they
love
it
when
we
bring
them
on
customer
calls
too?
So
I
I
can
only
imagine
how
valuable
that
is
and
yeah
to
say
that
red
hat
is
a
fire
hose
in
your
first.
B
B
B
B
So
first
I'm
going
to
share
my
screen
and
then
I'm
going
to
grab
this
link
and
I'm
going
to
paste
it
into
here.
So
this
blog
post,
which
is
kind
of
a
meta
blog
post,
has
links
to
all
of
the
other
various
what's
new
in
8.4
blog
posts
and
other
things
that
are
interesting
or
should
be
interesting
to
you,
based
off
of.
B
So
this
one
is
great.
I
haven't
seen
all
of
it
yet
because
I
haven't
I.
I
need
to
also
learn.
What's
new
in
8.4,
so
definitely
recommend
if
you
like,
I
do
you
have
a
video
or
something
running
in
the
background
that
you
can
kind
of
half
listen
to
while
you're
doing
other
things.
This
is
a
great
way
to
learn
about
what's
new
in
a
top
four
as
well,
so
definitely
check
out
both
of
those
resources.
I
know
we
have
a
lot
of
crossover
between
rel
admins
and
openshift
admins.
B
You
can
see
the
last
updated
date
here
is
may
18th,
so
this
is
actually
posted
in
two
places.
It's
on
redhat.com,
as
well
as
on
openshift.com.
I've
only
got
the
redhead.com
one
up
here,
so
I'll
paste
that
link
so
inside
of
here.
The
major
changes
from
being
a
part
of
the
editing
process.
We
added
in
a
bunch
of
stuff
around
openshift
platform
plus.
So
if
you're
curious
about
what
openshift
platform
plus
is
what
the
components
are
right.
All
of
that
other
stuff.
B
B
So
there
is
an
infrastructure
node
here
section
here.
It
includes
a
lot
of
clarification
on
what
does
and
doesn't
qualify.
So,
for
example,
you
know
if
you
are
using
the
infrastructure
node
paradigm,
it's
not
going
to
valid
or
invalidate
that
you
know
subscription
exception.
If
you're
using
like
a
custom
monitoring
agent
like
hey,
we
wrote
our
own
monitoring
agent.
I
need
to
deploy
that
we
don't
consider
that
application
workload.
So
therefore
it's
still
an
infrastructure
node.
B
If
you
need
to
deploy
like
vmware
tools,
you
know
or
whatever
that
happens
to
be
all
that
stuff.
So
definitely
read
through
that.
If
you
are
curious
about
any
of
the
details,
if
you
are,
if
there
are
things
that
you
think
might
qualify
for
a
infrastructure
nodes,
qualification,
yeah,
again
lots
and
lots
of
details
inside
of
there
so
and
I
did
post
that
link
so
be
sure
to
check
that
out.
B
So
the
third
thing
I
wanted
to
talk
about,
which
is
one
that
I
will
kind
of-
I
want
to
make
everybody
aware
of,
but
I
don't
have
any
additional
knowledge
than
what
you
see
here
and
that
was
or
is.
I
think
it
was
yesterday
it
might
have
been
early.
This
morning
there
was
an
announcement
of
this
cve
around
a
sim
link
exchange
attack
with
run
c.
That's
very
bad!
B
B
B
C
B
And
it's
used
by
openshift,
it's
used
by
rel,
et
cetera.
You
can
see
all
the
details
inside
of
here
one
thing
to
note
from
a
red
hat
perspective,
I
think
we
mark
this
as
reduced
impact.
If
we
come
down
here
to
the
faq,
it
talks
about
se
linux
helping
to
mitigate
this.
That
doesn't
mean
that
it
is
not
an
impact.
It
just
means
that
se
linux,
you
know
systems
with
sc
linux
and
they
will
have
a
reduced
impact.
So.
B
B
Users
to
run
containers
in
your
environment,
environment
or
allow
trusted
users
to
deploy
untrusted
containers
in
your
environment.
So
if
you
qualify
it
for
either
one
of
those,
please
keep
an
eye
on
this
security
bulletin
it'll
be
updated
constantly.
If
you
saw
I'm
going
to
jump
to
the
top,
if
you
saw
up
here,
it
was
updated
an
hour
ago.
B
To
update
that
with,
what's
going
on
so
the
last
thing
that
I
wanted
to
to
talk
about
is
something
that
actually
came
out
of
a
phone
call.
I
had
this
morning,
so
I
was
on
a
customer
call
with
with
a
customer
over
in
europe,
it's
bright
and
early
seven
a.m.
This
morning,
that's
why
I
might
seem
a
little
more
wired
than
normal,
because
I've
had
like
a
whole
lot.
B
So
they
asked
us-
and
it
was
myself
and
one
of
our
peers
that
were
presenting
and
they
asked
us-
you
know
hey.
Sometimes
you
know
if
we
open
a
support
case
or
even
if
we're
just
searching
through
you
know
the
red
hat
material
we'll
find
stuff
in
the
kcs.
You
know
on
access.redhat.com
that
is
either
in
addition
to
or
sometimes
contradictory
to,
what's
in
the
documentation.
B
So
how
do
we
know
or
how
do
we
deconflict
right?
How
do
we
choose
which
one
of
those
is
the
authoritative
source
and
I'll?
Tell
you
my
off
the
cuff
answer,
and
I
definitely
want
to
get
richard's
perspective
here,
because
I'm
I'm
sure
having
been
in
support
that
he
has
some
some
opinions
on
this.
So
my
off
the
cuff
response
was
essentially
the
documentation
is
the
source
of
truth,
except
where
the
kcs
supersedes
it.
So
the
kcs
is
often
my
perspective
to
be
clear.
B
C
Yeah
for
sure,
I'm
actually
quite
familiar
with
this
specific
issue,
because
it
has
been
a
long
running
topic
for
almost
since
the
inception
of
four
has
been
how
to
set
up
infra
nodes
and
the
one.
The
one
bit
of
caution
that
I'll
give
when
judging
kcs
versus
doc
is
doc,
is
the
source
of
truth.
But
it
doesn't
cover
all
possible
scenarios
if
you're
looking
at
a
kcs.
That
is
18
months
since
the
last
update
approach
it
with
caution,
because
things
change
fast
right.
C
Now,
if
we
find
a
situation
where
this
is
a-
and
this
is
a
good
example
where
we
have
infrastructure
nodes
being
being
discussed
in
this
kcs
article,
this
is
a
situation
where
we
need
to
be
raising
a
bug
back
to
docs
and
say
look.
This
is
a
missing
piece
of
the
documentation
that
numerous
customers
are
running
up
against.
C
What
is
the
best
practice,
because
we
may
not
want
support
to
finding
the
best
practice
on
how
to
set
up
in
pronouns,
because
we're
going
to
do
what
needs
to
be
done
to
help
the
customer
through,
but
it
may
be.
The
product
has
a
very
different
view
of
how
to
approach
setting
up
for
nodes
which
they
did
and
and
so
making
the
product
team
aware
via
bugs
is
really
key,
because
otherwise
they
may
not
be
aware
that
this
is
a
massive
question
out
in
the
customer
base.
B
B
You
know
with
your
deployed
cluster
and
it
was
nothing
more
than
just
a
reorganization
of
the
docs
and
I
think
it
took
two
versions
of
docs
for
them
to
then
incorporate
that
you
know
it
was
like
4.6
time
frame
was
when
that
was
made
into
a
section
in
the
docs,
and
it's
just
you
know,
keeping
up
with
all
the
things
going
on
in
the
product
consumes
a
massive
amount
of
time.
So
you
know
doing
those
reorganization.
Things
is
not
that
it's
a
lower
priority,
but
it
can
often
involve
a
lot
of
effort.
C
B
B
B
Yeah,
I'm
I'm
happy
to
you,
know,
work
on
behalf
of
you
all
our
audience:
right,
customers,
the
field,
etc
to
bring
back
that
information
to
the
docs
team
and
and
provide
that.
So
you
know
if,
if
there's
things
that
are
wrong,
please
open
a
bz
or
a
github
issue,
but
if
it's
like
hey,
it
would
really
be
easier
to
use
these
docs
if
they
were
like
this,
you
know
that
type
of
stuff.
I
am
super
interested
in
that.
So
please
don't
don't
hesitate
to
send
me
a
message
and
you
can
do
that.
B
Just
standard
contact
information,
andrew.sullivan
redhat.com,
you
can
send
me
a
dm
on
twitter
practicalandrew
if
you're
watching
any
of
the
chats.
It's
the
same
as
my
twitch
username
here,
practical
andrew
yeah,
so
yeah,
please
don't
hesitate
to
reach
out
if
you
have
any
feedback
on
on
the
documentation.
Ux.
B
Docs
yep
yeah,
and
it's
so
funny
thing
so
christian
now
that
you
bring
that
up
I'll
use
this
as
an
opportunity
to
so
the
docs.
Actually,
almost
every
one
of
the
little
subsections
really
is
a
link.
The
problem
is
they're,
not
always
obvious,
so
I'm
just
choosing
a
random
section
here,
so
I
can
go
to
like
obtaining
the
installation
program
and
you
see
this
is
a
link.
It's
got
the
little
hyperlink
you
can
see
up
here
in
the
bar.
It's
got
the
the
ending
to
it.
So
this
one
does
two.
B
D
C
B
Right
click
and
go
to
inspect,
and
then
I
need
to
move
this
over
here.
So
it's
easier
to
read.
So
if
I
go
to
the
dom
inspector
here
inside
of
chrome,
so
you
can
see
it
actually
does
have
an
id
tag.
So
it's
literally
in
this
instance
called
load
balancers.
So
I
can
copy
that
id
tag
out
and
then
just
depend
on
the
url
pound,
sign
or
hash
tag,
load,
balancers
and
then
I'll
go
right
there.
B
So
you
know
a
little
little
docs
hack,
so
yeah.
It
took
me
a
while
to
figure
that
one
out
that
you
don't
always
have
to
link
just
these
top
level
ones
or
here's
network
topology
requirements,
there's
another
one
see,
there's
no
link
associated
with
it.
If
I
do
the
inspect,
it
comes
up
with
network
topology
requirements,
and
I
can
do
the
same
thing.
D
B
B
B
Maybe
it
only
links,
you
know
certain,
you
know
down
to
an
h3
or
something-
and
this
is
an
h4
and
an
h5
right
now,
yeah,
so
yeah
anyways
a
little
a
little
tip
there
cool
all
right.
So
today's
topic,
so
the
specialist
platform
team,
which
again
very
privileged
very
happy
to
have
both
joe
and
richard,
join
us
to
talk
about
what
it
is
that
they
do
and
how
that
interacts
with
engineering
so
kind
of
joe.
B
You
mentioned
that
you
are
effectively
an
escalation
point
for
the
engineering
folks
and
how
like
specific
platforms,
work
and
like
just
this
morning.
I
included
you
all,
because
I
know
you're
you're,
both
kind
of
vsphere
specialist.
I
included
you
on
an
email
where
it
was
like
hey
how
do
we?
You
know
what
are
some
of
the
low-level
things
that
we
can
check
to
do
like
performance
and
all
these
other
things
which
I
know
is
not
necessarily
directly
in
your
your
day-to-day
responsibilities.
D
D
I
I
actually
think
this
is
one
of
the
great
things
about
this
role.
Is
you
don't
really
know
so?
I
know
that's
really
vague,
but
so
you
know
we're
all
on
slack
and
then
in
in
gchat
just
fielding
questions
at
least
part
of
the
day
from
it
could
be.
Anybody
within
you
know,
within
red
hat
that
you
know,
has
a
problem.
D
Definitely
ci
is
a
big
focus.
This
morning
I
was
making
a
change
in
nci
to
run
our
upgrade
process
between.
You
know
a
major
version
for
seven
to
four,
eight,
more
often
so.
Definitely
ci
monitoring,
ci,
making
sure
that
you
know
our
specific
platform
that
we're
responsible
for
is
passing
accordingly.
D
D
We
recently
said
that
statically.
So
we
got
six
nodes,
we
run
12
open
shift
clusters
concurrently
and
usually
we're
hitting
that
max
most
of
the
time
it's
all
vsan,
you
know,
vmc
is
very
a
very
opinionated
design,
so
we
get
what
we
get,
but
that's
the
reason
why
we
wanted
it
to.
We
would
rather
not
be
vcr
admins.
We
just
want
to
use
it,
so
we
can
get
into
more
details
of
of
the
of
how
it's
set
up,
but
that
was
that's
kind
of
the
gist.
B
D
B
Which
speaking
of
which
I
I've
been
meaning
to
invite
our
product
manager
for
managed
services,
hey
chris?
I
think
you
saw
that
me
discussing
that
idea
of.
I
want
to
have
the
managed
services
folks
come
on,
and
I
want
a
really
inflammatory
title
about.
You
know
like
how
managed
services
is
the
death
of
the
administrator
or
something?
Oh.
A
A
B
D
B
And
I
know
you
all
get
involved
in
a
lot
of
different
areas
and
in
particular
you
know,
I'm
thinking
of
I
saw
both
of
your
names
in
like
every
other
message
on
the
recent
bz
about
the
the
vmxnet
offload
issue
that
delayed
openshift
4.6
to
4.7
upgrades
right,
so
so
one,
I
think-
and
I
know
like
jp
did-
who
I
saw
here.
I
know
I
think
he
was
one
of
the
ones
who
was
waiting
on
that
to
be
fixed
along
with
many
many
other
folks.
B
You
know
that
were
impacted
by
by
it,
so
one,
I
think,
would
be
interesting
to
get
your
perspective
on.
You
know
one
maybe
a
little
bit
about
what
the
actual
bug
was,
but
but
two
kind
of
the
process
behind
that
like
how
do
we
find
these
things?
How
do
we
address
these
things?
How
do
we
fix
these
things
on
your
side.
D
Right,
so
we
so
it
was
kind
of
an
interesting
way
that
it
came
up
originally
so
richard
and
I
were
asked
by
the
there's.
I
don't
know
if
you
guys
have
discussed
this
on
the
channel
or
not,
but
the
the
assisted
installer,
so
those
folks
reached
out
to
us
they
were
saying.
Well,
we
kept
keep
having
issues
installing
vsphere
on
4.7,
and
you
know
at
first
we
were,
we
were
you
know,
kind
of
you've
got
to
be
doing
something
wrong
and
the
more
that
we
looked
at
it.
D
D
But
so
I
think
the
original
offloading
feature
was
a
a
higher
level,
one
that
I
disabled
and
the
cluster
just
kind
of
just
kind
of
sprung
back
to
life,
so
the
so
the
gist
on
the
the
bug
all
right.
It's
not
really
a
bug
per
se,
at
least
from
especially
from
vmware's
perspective.
They
don't
they
don't
feel
it.
That's
a
bug,
so
vxlan
uses
can
use
two
different
ports.
Four,
I
can't
remember
four,
seven,
eight
nine
and
I
can't
remember
the
other:
don't
worry
about
port
numbers,
okay,
yeah!
D
I
don't
remember
so
so
they
vmware
added
offloading
features
for
udp
for
those
for
vxlan,
which
is
you
know,
that's
awesome
right
because
we're
sending
we're
everything.
Openshift
sdn
is
vxlan.
So,
but
if
you
change
the
port
for
vxlan
to
the
non-default,
the
the
nick
bmx
net,
three
nick
just
drops
those
packets,
which
is
what
was
the
real
cause
of
the
problem
so
in
in
ralph
in
route
8.5.
I
think
the
current
kernel,
bz
they've,
implemented
not
a
fix
but
a
workaround
to
default.
B
I
I
tell
you
so
I
didn't
know
it
at
the
time
and
it
didn't
occur
to
me
until
I
don't
know
two
weeks
ago.
So
when
4.7
was
first
released,
I
was
deploying
a
new
cluster
like
I
always
do,
and
for
whatever
reason
at
that
time
I
was
deploying
a
cluster.
It
was
all
bare
metal
or
a
you
know:
platform
equals
none
non-integrated
platform
agnostic,
and
I
had
my
control
plane
on
vsphere
and
my
worker
nodes
on
rev,
and
I
could
not
get
the
cluster
to
deploy.
B
I
was
banging
my
head
against
it
for
like
two
weeks
or
something
and
finally
just
gave
up,
and
I
would
switch
between
all
vsphere
and
all
rev
instead
of
the
mixture,
so
it
didn't
occur
to
me
until
about
two
weeks
ago
that
I
bet
I
was
hitting
that
bug
and
I
actually
went
in
and
I
manually
turned
off
the
settings
so
on
last
week's
stream.
I'll
dig
up
the
link
here
in
just
a
second
on
last
week's
stream.
You
know
I
showed
how
to
how
to
manually
do
those
things
yeah
you
can.
B
B
D
D
Right,
because
what
you
must
mentioned
andrew
is,
if
I've
got
platform
done
and
but
I'm
still
running
on
vsphere
I've.
I
can't
just
apply
the
fix
to
the
vsphere
section
of
mco,
because
only
that
will
be
templated.
If,
if
I
know
that
I'm
running
on
you
know
in
the
install
config
platform,
colon
vsphere.
B
B
This
pretty
frequently-
and
here
I'm
going
to
pick
on
one
of
these
right-
we'll
go
in
here
and
look
at.
Actually,
I
don't
want
common.
I
want
like
I'll
look
at
the
control
plane
and
if
we
look
on-prem
and
files
we've
got
like
this
keep
alive
d
keepal
id.
So
this
is
what
manages
the
api
virtual
ip
address
right,
that's
associated
with
the
on-prem
ipi
cluster,
so
I
use
these
again
pretty
frequently,
but
what
you
might
notice
here
is
that,
like
some
of
these,
I
don't
know
if
it's
on
this
one.
B
Some
of
these
have
like
templates,
that
it
uses
inside
of
here
like
this,
is
a
template
file,
so
here
like,
where
does
that
lb
config
lb
port
come
from,
and
so
I've
been
like
digging
through
and
learning
more
about
how
all
of
this
stuff
works
in
order
to
determine
you
know
where,
where
that
val
those
values
come
from
and
how
they're
impacted
and
where
changes
happen
at
and
all
this
other
stuff.
So
it's
one
of
those
like
working
for
an
open
source
company.
B
It's
phenomenal
that
I
can
just
go
and
look
at
the
code
and
at
the
same
time
I
can
go
and
ask
the
engineers
on
the
back
end.
You
know
we're
working
at
other.
You
know
previously
non
open
source
companies
where
it's
one
of
those
like
well,
you
got
to
know
the
right
guy
who
knows
the
right
guy
who
can
enable
your
account
to
access
the
source
control
system
with
the
right
permissions,
but
we
also
have
to
trust
you
and
make
sure
you're
not
just
going
to
sell
the
code
like
yeah.
It's
it's.
B
Yeah,
so,
okay,
so
splat
the
specialist
platform
team
right.
So
I
I
think
joe,
I
know
you're
a
vsphere.
You
know
you're
one
of
the
very
specialists
and
richard,
I
believe,
you're,
the
other
vsphere
specialist,
but
sure
on
the
team.
I
know
you
all
have
other
other
folks
that
focus
on
other
platforms.
C
Yeah,
we
sure
do
our
the
other
platform
that
we're
managing
at
the
moment
is
azure
we're
looking
at
expanding
to
two
other
clouds
in
short
order,
but
right
now
our
primary
focus
is
vsphere
and
azure
and
joe,
and
I
usually
hang
out
in
forum
vmware
in
slack.
We
have
other
folks
that
hang
out
in
forum
azure,
kenny
woodson
is
is
also
one
of
our
colleagues
and
he's
he's
primarily
working
on
azure.
We
do
also
have
someone
working
on
arm,
which
is
a
pretty
which
is
pretty
cool
too.
C
D
A
A
A
B
So
yeah,
that's
already
on
the
calendar
a
month
away,
yeah,
it's
time.
Time
flies
when
you're
having
fun
yeah.
So
lorbis.
I
see
you
commenting
here.
Mco
is
openshift
secret
sauce.
You
know
it's
funny
to
have
you
know,
I'm
I'm
an
old
vsphere
administrator
as
well.
You
know
that's
what
I
did
for
a
decade.
I
was
an
admin
and
architect.
So
I
look
at
mco
and
like
openshift's
relationship
to
core
os
and
the
bridge
of
mco
is
very
similar
to
how
vcenter
manages
esxi
right.
B
It's
it's
all
done
from
within
the
platform
or
it's
almost
entirely
done
from
within
the
platform,
and
it
gives
all
of
that
configurability
and
manageability,
and
all
that
stuff.
That's
inside
of
there.
So
yeah,
I'm
I'm
also
a
big
fan
of
the
machine.
Config
operator
it
does
take
a
little
bit
of
a
mindset.
Shift
right.
B
You
know
christian's
full
of
aphorisms.
Today,
yeah
yeah,
it's
it's
a
very
inspirational
workout.
Today,
I'm
kidding
so
yeah
so
richard.
I
wanted
to
ask
you
with
your
perspective,
you
know
and
again
coming
from
the
support
side,
where
you
had,
you
know
some
influence
and
some
input
into
what
engineering
is
doing.
Like
hey,
there's,
there's
a
problem.
We
need
to
fix
this,
but
now
from
your
side,
how
does
that
influence
like,
or
how
does
that
change?
And
what
I
mean
by
that
is.
B
C
Why
why
there's
so
many
cases
opened
up
and
that's
just
an
example
of
of
one
of
the
efforts
we've
undertaken
to
try
to
just
holistically
look
at
the
customer
experience
of
vsphere
and
look
at
and
then
look
at
ways.
We
can
go
back
and
either
improve
things
ourselves
or
if
we
can
go
back
and
file
bugs
or
rfes
to
try
to
push
improvements
back
in
and
and
have
them
considered
for
implementation
on
down
the
line.
C
So
our
team
is
actively
engaged
in,
I
wouldn't
say
necessarily
in
the
support
process,
but
certainly
engage
with
the
data
that
we're
getting
back
and
joe,
and
I
still
get
on
the
phone
with
customers
from
time
to
time.
I
wouldn't
say
it's
frequent,
but
I
would
say
maybe
monthly
we're
we're
on
a
call
with
a
customer
working
through
and
trying
to
understand
pain
points
to
either
push
a
bug
along
or
see
if
we
can
help
out
ourselves
in
the
resolution.
B
C
It
is
yep,
absolutely
yeah,
so
this
is
an
example
of
an
issue
that
is
just
pervasive.
Throughout
vmware
cases
we
have
an
ambiguous
statement
of
my
masternodes
are
slow,
okay.
Well,
what
does
that
mean?
It
could
be
that
the
host
itself
is
over
committed
or
it
could
be
something
wrong
with
openshift.
We
really
don't
know
or
have
the
tools
to
dig
in.
D
Andrew
you
were
saying,
you're
a
vcr
admin,
I'm
sure
you
and
I
was
a
visa
admin
at
one
point
you
know:
there's
a
network
team,
there's
a
storage
team
and
there's
a
vmware
team
and
now
there's
an
open
shift
team,
and
you
know
the
silos
at
least
on
customer
calls
you
can.
You
can
see
that
those
still
are
still
are
definitely
alive
and
sometimes.
B
Well,
there's
an
operating
system
team:
that's
in
there
sometimes
there's
a
security
team.
That's
in
there
yeah
it's.
That
was
sure.
When
I
was
a
customer
I
was
I
was
the
vsphere
administrator,
but
I
had
to
work
with.
You
know
the
network
team,
the
storage
team,
the
security
team.
We
we
didn't
know
what
was
inside
of
the
virtual
machines.
We
were
handed
basically
os
templates.
Here's
your
windows
server!
You
know,
2012
template,
here's
your!
You
know
rel
at
the
time
it
was
rel3
and
rail4
template.
B
You
know,
and
whenever
somebody
asks
for
one
of
these
deploy
one
of
those
you
know
type
of
things
so
yeah
that
that
kind
of
top
to
bottom
troubleshooting
is
hard.
How
do
you
know
where
it's
at
and
looking
at
this
there's
some
really
interesting
stuff
inside
of
here?
Nick
I
I
didn't
know
that
we
had
a
podman
command
here
to
to
do
the
fcd,
perf
openshift
scale
at
cd
perf.
That's
right,
yeah.
C
C
So
there's
a
set
of
queries
that
are
down
the
bottomless
article
that
that
that
you
can
run
to
pull
back
the
data
that
we
can
analyze
or
support,
can
analyze
in
conjunction
with
the
esxi
metrics.
So
it
gives
you
both
the
the
host
and
the
guest
perspective
of
things
and
it's
helpful
in
pinning
it
down.
B
Very
cool-
and
I
I
I
want
to
use
this
as
a
a
jumping
off
point
or
a
a
another
tangent
point
around
the
v
sphere-
problem,
detector
and
but
both
of
you
actually
very
helpfully
corrected
me
because
I
have
been
kind
of
casually
associating
your
team
with
the
vsphere
problem
detector
when
in
fact
it's
not
so,
can
you
can
you
kind
of
give
us
some
background
there?
What
is
the
problem
detector?
Where
does
it
fit
in
and
and
what
does
it
do
and
I'm
going
to
pull
up
the
github
page
here.
C
C
A
recent
example
of
that
is,
I'm
sure
everyone,
if
I
run
into
this
at
some
point,
the
encoding
of
a
password,
but
the
trailing
line.
Feed
is
something
that
is
really
difficult
to
pin
down
unless
you
know
that
that's
a
problem,
so
we've
got
a
pr
in
place
right
now
to
add
detection
for
that,
something
they
can
waste
days
and
it
can
have
a
real
business
impact
to
our
customers
because
they
can't
scale
their
workloads
effectively.
B
B
You
know
issues
before
they
become
issues
you
know
so,
previous
company,
we
we
got
a
new,
you
know
svp
of
supports,
and
I
remember
she
kept.
You
know
she
she
came
in
and
one
of
the
things
she
was
talking
about
was
we
want
to
get
out
of.
You
know
proactive
support
and
we
want
to
get
into
preemptive
support
right
proactive
is
I
found
something
I'm
taking
care
of
it
preemptive?
B
A
C
Yeah,
so
so,
just
for
those
that
don't
know
if
you
installed
following
the
vmware
following
the
vsphere
installation,
guidance
pre-47
and
you
did
not
provide
a
valid
username
and
password,
let's
say,
for
example,
your
vster
administrator
wouldn't
allow
you
to
have
the
credentials
necessary
to
install.
But
you
still
follow
the
upi
guidance
for
vmware
installs
when
you
upgraded
a
47,
your
storage
operator,
degraded,
because
we're
checking
for
that
now.
So
it's
a
it's
a
valid
catch,
but
we're
softening
it
from
a
degradation
to
an
alert
and
yeah
kind.
C
D
Yeah
to
help
us,
so
I
think
one
of
the
biggest
biggest
things
within
the
problem-
detector,
at
least
from
our
perspective.
Moving
forward
to
get
you
know
like
the
auditory
csi
is
to
determine
which
versions.
Customers
are
running
vsphere
versions
that
our
customers
are
running
so
that
we
can
better
determine
when
to
be
able
to
roll
out
like
the
auditory
csi,
which
requires
you
know,
six.
Seven,
you
three
and
higher
and
hardware
15.
D
C
C
Kind
of
touching
back
briefly
on
the
ci
testing
we
discussed
earlier
one
of
the
key
things
you
run
as
part
of
that
is
the
openshift
end-to-end
test
suite,
which
is
a
massive
set
of
tests.
Yeah
over
1200
tests
get
kicked
off,
so
what
we
theorized
was
that
v-motion
in
and
of
itself,
wasn't
actually
causing
problems,
but
it
was
the
underlying
infrastructure
that
was
causing
problems
when
bmotion
was
invoked.
A
C
So,
in
order
to
proof
that
what
we
did
was
we
wrote
this
chaos
script,
that
what
it
does
is
it
v-motions
almost
continuously
the
control
plane
nodes
of
the
worker
nodes
while
running
the
openshift
tests,
and
we
measured
to
see
if
there
was
a
marked
increase
in
the
number
of
failures
we
there
was
not
a
significant
uptick
now
this
does
assume,
because
I
so
I
have
two
environments.
I
have
my
environment
behind
me,
which
is
a
dell
2u
that
I'm
sorry
it's
an
hp,
2u
server.
It
does
not
hold
up
as
well.
C
V,
motioning
takes
a
small
amount
of
time
there
versus
on
my
one
gigabit
network,
and
so
in
my
environment
it
had
problems
in
vmc.
It
did
not,
and
it's
simply
because
if
your
environment
is
performance
enough,
it
can
handle
the
load.
If
it
is
not,
then
free
motion
and
control
plane
nodes
may
not
be
the
right
choice,
because
you
may
see
an
api
outage.
A
D
So
that
goes
back
to
when
we
were
having
edrs
enabled
so
now
we've
set
that
statically
it.
I
don't
think
it's
growing
as
much
as
or
as
fast
as
it
was,
but
okay,
because
it
would
pull
it
pulls
hosts
out
of
the
cluster
once
you've
reached
the
threshold
too.
So
we
were,
you
know,
increasing
and
decreasing
hosts
quite
often,
but.
A
B
Know
actually
give
the
vms
the
ability
to
have
their
bandwidth.
You
know,
especially
at
cd.
I
can
imagine
because
vmotion
from
what
I
recall
is
there
there's
no
limit
on
the
amount
of
throughput
that
it'll
consume.
So
if
it's
sharing
bandwidth
with,
for
example,
the
network
adapters
being
used
by
the
control
plane,
you
know
for
scd
communication.
That
would
be.
That
would
be
bad.
C
B
Yeah
that
makes
sense
I'll
dig
up
the
link
for
vmware's
or,
if
you
have
it
handy,
you
can
just
post
it
over
to
me
I'll
see
if
I
can
dig
up
the
link
for
their
best
vmotion
best
practices,
and
we
can
share
that
in
the
blog
post.
So
again,
I
know
we've
only
got
a
couple
minutes
left.
I
actually
do
have
a
hard
stop
at
the
top
of
the
hour.
B
So
if
we,
if
words,
please
keep
an
eye
out
on
friday
for
the
blog
post,
so
in
those
blog
posts,
if
you
saw
earlier
right,
I
put
a
timestamp
in
where
we
answer
questions
and
stuff
like
that,
try
and
turn
those
into
a
reference.
I
know
that
having
a
60
minute
recording
to
find
you
know
the
the
30
seconds
where
we
answer
your
question
is
sometimes
you
don't
want
to
listen
to
60
minutes
of
me
babbling.
B
So
I
do
try
and
do
that
some
as
well
as
we
include
links.
You
know
all
the
links
that
we
shared
here
we'll
have
all
of
that
stuff
inside
of
there.
So
with
just
about
four
minutes.
Left
five
minutes
left.
Please.
If
you
have
any
other
questions,
anything
that's
top
of
mind,
please
let
us
know
so
to
circle
around
and
answer
that
question
about
vmotion.
B
B
D
Not
from
what
I've
the
storage
team
was,
we
were
in
a
chat
about
a
month
ago
and
it
sounded
like
it
didn't
like
the
the
original
plan
for
the
audit
tree
csi
was.
It
was
going
to
support
storage
of
emotion
and
it
sounds
like
it's
being
backtracked,
though,
though,
if
you
look
at
the
recent
prs,
there
was
one
if
you
were
running
in
a
vsan
environment,
so
maybe
that
changes
how
they
can
handle,
but
I'm
not
quite
sure
if
you
have
vsan,
why
are
you
storage
of
emotioning,
but.
B
So,
okay!
Well,
I
don't
have
any
more
questions
for
you
all.
I
just
want
to
say.
Thank
you
very
much
for
coming
on
today.
I
know
we
we,
our
originally
scheduled
subject
for
this
week,
was
licensing
entitlements,
but
our
guests
had
to
delay
out
a
week,
apparently
there's
some
pm
thing
going
on
today,
so
we'll
be
covering
that
next
week
for
anybody
who
is
watching.
So,
thank
you
very
much
joe
and
richard.
B
B
Yeah
for
sure,
so
for
anybody
in
the
audience,
if
we
either
didn't
adequately
answer
your
question,
if
you
didn't
get
to
answer
answer,
ask
your
question:
if
there's
something
that
comes
up
to
you
after
the
fact
whether
or
not
we're
on
the
air
here
streaming,
please
don't
hesitate
to
reach
out
to
me.
Andrew.Sullivan
redhat.com
chris
is
short
at
redhat.com.
Now
you
can
also
reach
out
on
twitter,
practicalandrew
or
chris
shorts
on
twitter,
we're
more
than
happy
to
field
any
and
all
of
those
questions
at
any
point
in
time.