►
Description
Red Hat’s senior leadership is having to execute at an ever-increasing pace. That means that today's technology decisions have to balance short-term risk with long-term gains. This unique series provides host Chris Short inviting thoughtful and candid discussions with each guest.
An hour with the one and only Stefanie Chiras, Senior Vice President & General Manager, RHEL Business Unit
A
Good
morning,
good
afternoon,
good
evening,
hello,
everyone
and
welcome
to
another
episode
of
in
the
clouds
with
red
hat
leadership
here
on
open
shift
tv.
We
are
joined
today
by
the
one
and
only
and
recently
promoted,
so
I
have
to
actually
look
at
my
notes:
stephanie
sheares
senior
vice
president
and
general
manager
of
the
red
hat
enterprise
linux
business
unit.
Congratulations
on
your
promotion!
First
of
all,
long
overdue
and
and
like
I
can't
tell
you
how
excited
I
am
to
have
you
on
today,
so
welcome
to
the
show
welcome
to
the
channel.
Oh.
B
A
B
B
A
B
Have
them
find
value,
pull
them
onto
the
architecture
that
combined
with
the
visibility
to
the
culture
at
red
hat,
how
red
hat
worked
pulling?
All
of
that
together
made
it
very
very
interesting
for
me
to
move
into
the
linux
space,
but
it
was
a
very
interesting
way
to
come
in
and
find
that
appreciation.
A
That's
yeah
like
it's.
It's
enlightening
to
hear
that
you
have
a
very
deep
engineering
background
and
you're
in
leadership.
You're
at
red
hat.
Right
like
that
makes
me
feel
like
I
want
to
stay
right
like,
as
you
know,
someone
with
an
engine.
You
know
a
technical
background
that
makes
me
feel
like
this
is
the
right
place
for
me
right.
So
it's
it's.
A
It's
very
good
to
hear
that
story
and
to
let
the
world
know
that,
like
the
person,
that's
leading
the
the
red
hat
enterprise,
linux
business
actually
has
been
on
the
ground
trying
to
get
linux
like
installed
in
data
centers
and
actually
out
there
right
like,
because
that's
not
always
a
skill
that
people
that
make
that
senior
vp
level
like
have
right
like
they
don't
have
that
in
the
field.
Experience
sometimes.
A
B
People
didn't
appreciate-
and
you
know
I
went
from
this
world
where
being
on
that
power
side,
where
you
had
your
you
know,
you
had
an
os
and
you
had
a
hypervisor
all
built
on
that
hardware.
You
know
if,
if
there
was
an
issue
in
the
chip
or
if
there
was
something
that
you
know,
you
called
up
the
bios
team
or
the
firmware
team,
and
you
said
hey,
we
got
something.
We
need
your
help
with
and
you
could
you
could
leverage
the
whole
stack.
B
A
Yeah,
I
bet
right
like
the
the
amount
of
yeah
the
amount
of
time
it
takes
to
get
something
into
the
kernel.
I
can't
imagine
how
long
it
takes
something
to
get
in
the
hardware
yeah,
so
so
rel
has
been
at
the
core
of
our
product
portfolio
for
literally
decades.
Right,
like
I
mean
I
can't
believe
how
old
redhead
is
given
that,
like
I
remember
red
hat
when
it
went
like
ipo
like
back
in
2000
right
like
yeah,
it's
it's
gone
by
so
fast.
How
is
red
hat
adjusting
to
the
times
of
smaller
work?
A
C
A
B
So
I
think
it's
it's
such
an
interesting
time
and
it's
a
it's
a
pulling
of
what's
happening
in
the
industry,
but
also
what
we
have
been
doing
in
red
hat.
When
I
look
at
why
I
was
so
excited
and
to
take
the
rel
roll
and
and
why
I
I
love
this
role
every
day
is
because
I
view
the
rel
business
as
two
things.
It
is
a
product
for
sure
it
has
a
commitment
to
customers,
it
has
a
roadmap
to
deliver,
but
that
is
rel
the
product.
In
addition,
rel
is
a
technology
right.
B
It
is
a
technology
that
feeds
into
openshift
and
it's
a
technology
that
feeds
into
openstack
as
the
base
linux
for
those
things,
and
we
have
responsibilities
to
the
company
and
the
market
in
both
and
we
have
to.
We
have
to
balance
those
two
things.
So
I
love
that.
I
love
that
kind
of
combination
of
the
responsibility
and
the
balancing
of
that
that
it
has
to
have
now
you
layer
on
to
that
in
both
of
those
dynamics.
You're
looking
at
what's
happening
in
the
industry,
things
in
the
industry
around
now.
B
B
I
think
the
ability
that
linux
has
brought
to
the
world
is
the
ability
to
is
to
make
that
simple
to
consume,
so
all
the
magic
that's
happening,
whether
it
be
an
arm,
whether
it
be
in
power,
whether
it
be
an
x86,
whether
it
be
in
a
smart
neck,
whether
it
be
you
know,
nvidia,
gpus,
right,
accelerators,
fpgas,
you
pull
all
of
that
fantasticness,
but
who
can
create
right
the?
How
do
you
access
all
of
that
for
when
you
pick
and
choose
it
for
the
applications?
You
run?
B
That's
where
linux
starts
to
become
an
equalizer,
but
it's
an
equalizer,
not
just
technically,
but
it's
an
equalizer
from
from
the
from
the
community
and
the
ecosystem
that
it
supports.
Like
we
don't
just
deliver
technology
and
bits,
we
deliver
a
ecosystem
that
we
have
worked
with
to
make
sure
that
it
all
builds
upon
one
another.
B
B
I
mean
it's
like
how
do
you,
where
is
the
right
point,
to
start
to
aggregate
that
now
clearly
we're
not
we're
not
focused
on
doing
your
your
little
tiny
sensors,
but
those
sensors
are
pulling
in
data
that
data
needs
to
be
aggregated
and
analyzed
at
some
point
before
the
data
center,
and
there
is
that
edge
case
right.
That
is
really
really
important.
It
has
to
be
stable.
B
So
that's
this
is
a
place
where
rel
plays
really
well
and
I
think,
as
it
becomes
more
specialized
out
there,
things
like
arm
things
like
accelerators.
All
of
that
plays
a
different
role.
What
we
have
done
in
the
data
center
to
sort
of
equalize
and
provide
that
more
level
playing
field
to
that
hardware
and
the
stability
and
security
plays
just
as
well,
is
equally
important
when
you
move
out
to
the
edge
and
most
folks
who
are
going
to
run
edge,
are
running
core
data
centers.
B
B
Also,
it
doesn't
provide
the
ability
to
leverage
the
the
communities
upstream
so
we're
seeing
a
pivot
in
this
edge
space
in
the
embedded
space,
where
there
is
a
thirst
for
some
amount
of
standardization
where
they
can
pro
they
can
get
access
to
an
innovation
cycle.
So
what
we
had
done
for
the
data
center
years
and
years
ago
is
now
start
that
edge
space
is
starting
to
mature
in
many
in
many
industry
verticals,
where
they're
like
listen,
I
I
can't
see
a
sustainable
model
where
I'm
going
to
have
a
custom
os.
B
I
need
something
that
I
can
count
on.
That
is
going
to
be,
and
so
we're
having
a
lot
of
interesting
discussions
in
the
market
with
partners
around
that
space.
But
I
think
those
are
kind
of
the
two
things
that
are
happening,
but
I
love
the
fact
that
different
architectures
are
starting
to
be
used
out
there
right
because
it's
provided
it's
so
fun
right.
It
provides
a
whole
new
level
to
change
the
game.
I
mean
you
look
at
you.
B
Look
at
the
you
look
at
the
fugaku
announcement
right
number,
one
on
the
super
computing
list
built
on
arm
for
the
first
time
ever
and
it's
running
rel.
So
that
is
just
you
know,
and
hpc
world
has
changed
so
much
it's
now.
You
know
aggregations
of
small
systems
but
boy
that
that
that
provides
a
whole
new
opportunity
to
take
architectures
use
them.
It
becomes
a
horses
for
courses
right.
You
know
you
can
pick
the
architecture
you
need
and
you
can
still
use
the
same
linux.
That's
a
beautiful
thing!.
A
B
B
Degree
right
where
we're
going
is
this:
data
center
has
expanded
out
because
it
is,
it
is
trying
to
get
closer
to
the
data,
which
makes
perfect
sense.
The
use
cases,
however,
are
different
out
there.
Many
times
it's
much
lighter
weight.
Many
times
you
want
to
be
able
to
deploy
the
operating
system.
Have
it
update
in
a
atomic
way
right?
Have
it
update
roll
back?
If
you
need
it
to
roll
back,
we're
learning
a
lot,
and
this
is
a
place
where
our
model
in
the
community
has
really
paid
off
right.
B
Fedora
iot,
which
is
a
very
active
sig,
is
a
place
where
we've
gotten
a
ton
of
insight
on
what
people
want
in
this
world.
It
is
very
active.
Customers
are
looking
at
it,
they're
providing
us
feedback
on
it.
So
you
know,
if
you
look
at
our
development
model.
Fedora
iot
as
a
sig
has
been
very
helpful
for
us.
We
talk
to
customers,
but
we
do
have
to
figure
out
how
we
take
the
standardization
capabilities.
B
We've
done
in
the
data
center,
pull
that
out
to
the
edge
and
and
tailor
it
for
the
use
case
of
how
it
wants
to
be
used.
How
does
it
get
updated?
What
are
the
architectures
that
are
being
used?
There
is
rapidly
changing
things
out
there
likely
the
magic
of
how
to
deploy
an
application
via
a
container
provides
a
very
simple
way
to
deploy
out
there.
It
could
be
one
container,
it
could
be
unorchestrated,
it
could
be
a
very
simple
deployment,
but
that's
a
place
where
running
a
container
on
your
operating
system
works
really
well.
B
Now
things
like
app
streams
which
which
you
mentioned,
I
think
we
in
the
rel
space
in
order
to
be
make
sure
we
we
stay
relevant,
have
looked
at
kind
of
two
things
in
the
operating
system
that
we
want
to
make
sure
we're
driving
we're
driving
forward.
One
is,
as
the
world
gets
more
complicated
as
as
footprints
like
edge,
become
more
prevalent
as
architectures
start
to
broaden.
B
What
do
we
provide
in
our
standardization
capability
to
really
keep
operational
efficiency
capabilities
right,
because
our
goal
is
to
provide
that
sort
of
that
layer
that
delivers
operational
efficiencies?
So
you
don't
have
to
redevelop
re
redo
everything.
Every
time
you
deploy
a
new
architecture
or
a.
B
A
B
Accelerated
and
so
that
that
brings
up
kind
of
this
next,
the
other
kind
of
half
of
the
coin
that
we
are
focused
on
in
rel
is:
how
do
we
make
sure
that
rel
is
providing
access
to
the
next
layer
of
innovation?
And,
to
me,
app
streams
is
exactly
that
you
know
no
longer
is.
It
is
the
only
way
to
deploy
your
operating.
B
Way
right,
your
user
packages
may
need
to
be
updated.
You
may
need
to
be
able
to
access
multiple
versions
of
that
of
a
package
in
a
user
space
and
that's
what
app
springs
app
streams
brings
right.
It
provides
that
capability
of
access
to
innovation
at
the
modularity
at
the
package
level,
in
your
user
space.
That
really
makes
sense,
and
so
I'd
say
you
know.
As
as
we
look,
we
we
assess
everything
we're
trying
to
do
with.
How
do
we
do
operational
efficiency
and
never
compromise
on
giving
access
to
innovation?
B
App
streams
is
exactly
one
of
those
spots,
so
is,
so
is
the
container
deployments
that
you
talked
about?
We
put
the
container
tools
of
build
a
pod
man
scopio
directly
into
rel,
exactly
for
the
same
reason
right,
it
was
to
make
sure
that
the
operating
system
provided
that
first
step
into
that
world
of
innovation
and
while
clearly
it
doesn't
provide
things
like
kubernetes,
orchestration,
etc.
That's
what
openshift
does
it
at
least
provides
that
first
step.
B
A
A
lot
of
the
things
that
we
we
got
from
core
os
we're
paired
up
with
the
things
we
do
in
rel
to
make
red
hat
core
os
linux
right
like
that,
that
operating
system
and
all
the
innovation
behind
it
is
what
has
driven
all
this
innovation
lately
so
having
it
all
based
on
rel,
I
feel
like
is,
has
got
to
feel
like
a
big
win
for
you
right,
it's
it's.
It's
has
to
feel
like
a
big
responsibility
as
well.
A
You
know
ibm
is
spinning
off
their
their
managed
services
unit
into
its
own
whole
business,
and
you
know
we
look
at
managed
services
in
a
way
you
know
and
and
ibm
looks
at
managed
services
in
kind
of
a
different
way,
and
I'm
curious
how
you
think
that
move
is
going
to
impact
us
in
any
way
shape
or
form,
or
you
know
how
the
view
of
how
we
see
things
differently
and
interacting
with
that.
New
new
company
will
be
experience
wise
for
us.
B
B
B
B
We
should
talk
there
too,
so
gts
or
global
technology
services
at
ibm
has
long
been
a
business
that
has
been
driven
around
really
managing
data
centers,
so
they
have
been
able
to
offload
and
and
there's
a
ton
of
ton
of
their
customers
who
rely
on
them
to
take
ownership
really
of
their
data
center,
manage
a
workload
within
a
gts
owned
data
center
and
they'll
do
both,
but
it's
very
much
data
center
driven.
So
when
they
say
manage
services,
it's
heavily
about
the
data
center.
A
B
Involved
with
gts
for
a
long
time
now,
there's
a
couple
of
of
specifics
right
to
dive
into
that
announcement.
A
little
bit
so
gts
was
kind
of
the
big
business
unit
at
at
ibm.
A
couple
of
those
portions
of
that
will
stay
with
ibm,
so
tss.
I
think
it's
technical
support
services
that
will
stay
red
hat
has
had
a
long-standing
relationship
with
tss
because
they
provide
things
like
maintenance.
They
have.
B
They
predominantly
drive
things
with.
When
I
had
power
systems
power
systems,
you
could
purchase
rel
through
ibm
on
your
power
system
when
you
purchase
the
server
right,
because
we
had
that
partnership
with
with
ibm
tss
provided
kind
of
the
lead
on
delivering
that
to
a
customer.
So
technical
support
services
was
heavily
involved
in
ibm
systems
for
when
red
hat
products
came
in
with
your
ibm
system,
ess
was
very
involved
and
that
will
remain
with
ibm
so
that
sort
of
linkage
doesn't
get
broken.
B
No
change,
yeah,
no
change,
yeah
and-
and
I
think,
as
far
as
the
managed
services
around
gts
like
managing
your
data
center.
In
fairness,
we
have
been
working
with
them
as
a
partner
for
a
long
time.
Even
since
the
acquisition
right
we're
just
we're
just
over
a
year
into
the
acquisition
closure
and
we
still
work
with
them
as
a
partner,
so
my
view
on
that
is,
and-
and
it's
been
interesting-
I
work
with
gbs
global
business
services
over
at
ibm
and
gts
and
there's
linkages
there.
B
Gbs
will
deliver
to
customers
leveraging
the
capabilities
of
gts.
So
this
this
sort
of
partnership
model
of
how
we
work
together,
has
been
in
place
forever.
I
think
having
them
be.
A
new
company,
quite
honestly,
is
just
like
having
a
new
partner.
It's
not
really
going
to
change.
In
my
opinion,
I
got
we'll
continue
to
work
with
them
as
a
partner
like
we
work
with
a
lot
of
other
partners
in
the
industry.
So
I
it
didn't.
It
didn't
really
change.
B
When
the
acquisition
went
through
how
we
work
with
gts,
we
worked
with
them
as
a
partner.
I
think
that'll
continue.
So
I
I
think
it's
a.
I
think
it's
an
interesting
move
from
ibm
to
do
this.
I
think
it
allows
gts
to
focus
on
what
what
they
do.
It
allows
ibm
to
focus
on
their
gbs
services
business
so,
but
from
our
perspective,
at
red
hat
and
the
day-to-day
work
that
I
do
and
my
linkages
with
gts
and
gbs
and
ibm,
it
doesn't
really
change.
Yeah.
A
And
I
think
that
that
goes
to
our
model
right,
like
of
how
we
help
people
right
like
how
we
do
our
business
is,
you
know
very
open
and
standardized
and
very
kind
of
just
you
know
like
this,
isn't
going
to
change
anything.
You
know
it's
much
like
the
ibm
acquisition
yeah
a
couple
knobs
and
dials
got
switched,
but
you
know
that's
it
right
like
it.
A
There
wasn't
a
huge
sea
change,
but
it
made
a
tremendous
impact
right
like
we
can
see
already
the
impact
that
the
ibm
acquisition
is
having
with
you
know
our
every
literally.
Every
deal
we've
closed.
You
know
when
you
just
read
the
news,
but
the
the
the
coolest
thing
to
me
about
this
is
that
it
shows
a
renewed
focus
on
what
we're
doing
day
to
day
here
at
red
hat.
Right
like
that,
I
think
is:
what's
coolest
to
me
about
the
announcement
so.
C
B
I
think
that's
one
of
the
things
as
you
listen
through,
and
I
think
red
hat
you
know,
even
from
the
day
that
the
acquisition
was
announced
that
hybrid
cloud
kind
of
what
what
ibm
was
looking
for
from
red
hat,
to
really
strive
toward
that
hybrid
cloud.
This
provides
this.
This
is
even
amplified
now
with
this
announcement,
and
I
think
you
can
see
that
in
all
the
all
the
news
feeds
and
what
arvind
has
been
stating.
A
A
So
containers
are,
you
know
a
first-class
citizen
in
the
linux
kernel
kind
of
deal
and
you
know
we're
starting
to
see
them
become
part
of
a
like
packaging
ecosystem
of
some
sort.
How
do
you
see
containers
becoming
like
packages
in
the
future,
like
in
the
real
nine
ten
days?
He's
right
like?
How
do
you
see
that
kind
of
container
motion
impacting
future
releases?
And
potentially
you
know
like
package
management
in
general.
B
I
mean,
I
think,
the
I
think
the
modularity
right.
If
you
look
at
the
application
space,
the
modularity
and
the
technology
of
containers
has
been
in
linux
for
ages
right.
I
think
I
think
what
the
con
the
container
craze
so
to
speak,
right
of,
what's
going
on
right
now,
is
showing
people
the
power
of
what
it
can
do
for
applications,
not
only
simplification
of
of
how
you
deploy
an
application,
but
the
the
consistency
a
lot
of
the
customers.
B
I
talked
to
they're
like
listen,
I'm
not
so
worried
about
breaking
down
my
my
applications
into
microservices.
I
get
that,
but
what
I
really
love
about
the
container
aspect
that
they
they
tell
me
is
that,
like
I
can
package
it
once
I
send
that
out
to
all
of
the
lines
of
business.
I
know
that's
how
they're
gonna
run
it
when
I
need
to
change
it,
I
send
them
a
new
one
right
and
they
blow
the
other
one
up
and
they
roll
it
out.
B
So
that
level
of
consistency
is
very
important
and
we're
seeing
a
lot
of
there
is
the
the
packaging
value,
and
then
there
is
the
kind
of
capability
value
and
both
of
those
are
important,
I
think
at
the
application
layer
and
at
the
microservices
layer
that
is
driving
the
ecosystem.
Today.
I
think
there
is
more
to
learn
about
what
we
will
do
going
forward
right,
how
that
modularity
value
and
that
consistency
capability
starts
to
move
into
other
areas.
It's
certainly
something
that
that
we
talk
about
and
we're
watching
and-
and
we
don't.
B
You
know,
coming
back
to
a
bit
about
the
application
streams
right
application
streams,
breaks
up
that
monolithic
deployment
into
being
able
to
pull
different,
different
major
versions
of
your
user
space
package.
I
think
moving
forward
right,
watching
how
we
can
continue
to
build
upon
kind
of
that.
The
magic
of
that
modularity
is
is
something
that
we're
very
interested
in.
A
Yeah,
I
I
you
know,
I
work
in
the
openshift
unit,
so
I
deal
with
containers
all
the
time
and
I
keep
reminding
people
that
you
know
if
it
weren't
for
system
d,
if
it
weren't
for
the
linux
kernel
like
we
wouldn't
be
in
this
position
that
we're
in
right
now
and
it's
it's
it's
very
refreshing
to
see
like
people
talking
about
cis
calls
like
when
I
talk
to
them
about
security
right
like
yeah.
That's
really
cool
right
like
we're,
we're
getting
it
now
right
like
we.
A
We
have
now
reached
this
point
where
you
know
the
linux
kernel
is
becoming
something
we
all
understand
and
something
we
all
have
to
figure
out.
You
know
how
do
I
keep
these
things
from
happening
to
the
kernel
on
my
hypervisor
on
my
virtualization
or
orchestration
system
for
containers,
the
whole
nine
yards,
so
you
know
go
ahead.
Sorry.
B
No,
no,
no
because
you're
you're,
the
point
you're
making
right
now
is
really
really
important,
because
I
think
we
are
pivoting
in
the
container
dynamic.
That's
being
talked
about
in
the
industry
from
like
you
know
the
magic
of
containers
and
you
don't
have
to
worry
about
anything
else.
Just
get
your
container
deployed
anywhere.
B
B
Operating
system
gets
deployed
is
much
more
complicated
even
than
it
was
in
your
vm
space.
So
the
points
that
you're
making
in
that
level
of
maturity
that
is
being
realized
is,
is
actually
very
important
for
us,
because
we
we
want
to
make
sure
that
that,
as
you
said,
the
stability
and
the
ecosystem
that
we
deliver
with
rel.
And
now
we
translate
into
rel
core
os
on
behalf
of
openshift
that
that
value
translates
over.
But
the
operating
system
becomes
perhaps
less
visible
in
a
container-driven
world,
but
it
is
perhaps
more
important
and
how.
C
B
A
Yeah
so
we've
you
know
in
my
career
we've
gone
from
hey,
I
need
a
node
running.
You
know,
docker
too
hey.
I
need
a
fleet
of
nodes
running
like
containers
help
me
you
know
so
yeah.
It's
it's
interesting
to
see
when
people
are
like.
Okay,
I
just
want
containers
everywhere.
I
don't
I
don't
care
about
the
os.
Well,
I
was
like
well
wait
a
minute.
A
Are
you
sure
about
that?
Because
if
you
do
that,
if
you
do
a
system
where
it's
like
the
os
is
different
everywhere,
how
do
you
secure
those
workloads
uniformly?
How
do
you
apply?
You
know
pod
security
policies
and
system
security
policies
in
a
uniform
way
across
that
entire
fleet
of
all
these
devices,
and
I
think
that
goes
back
to
the
edge
as
well.
Right,
like
you,
have
to
have
some
standard
foundation
to
build
upon
and
and
rel
being
that
standard
linux.
Being
that
standard
is,
is
you
know
where
we
are
in
the
world?
A
I
feel
like
rel?
Is
you
know
the
the
top
performing
or
you
know
whatever
the
right
phrase?
Sorry,
legal
and
marketing.
The
right
phrase
is
for
rel
and
it's
you
know
position
in
the
market.
It's
it's
amazing
to
me
to
see
how
quickly
people
have
pivoted
back
to
like.
Oh
wait,
a
minute
that
kernel
does
matter.
Oh
wait!
A
A
minute
that
net
operating
system
is
going
to
impact
my
business
operations
right
like
or
my
you
know,
technical
operations
based
upon
you
know
life
cycle
management
of
those
systems,
because
you
know
kubernetes
deploys
every
quarter
right,
like
you've
got
to
manage
that
and
an
operating
system.
On
top
of
that,
that's
really
hard
right,
like
in
and
a
lot
of
people
do
go
out
to
a
service
and
you
can
get
openshift
dedicated
now,
just
like
you
can.
You
know
like
eks
xks,
all
the
other.
A
A
B
B
I
mean
that
pivot's
kind
of
kind
of
a
mindset,
and
if
you
want,
if
you
want
to
be
able
to
land
there,
you
kind
of
got
to
start
thinking
that
way
from
the
beginning,
to
your
point
on
on
linux,
so
in
in
2018,
linux
surpassed
windows
as
the
most
deployed
operating
system
in
the
world
and-
and
then
you
know,
rel
of
course
has
a
really
great
position
in
the
market
for
for
the
paid
linux
space.
But
the
point
that
that
makes
about
you
know
the
linux
deployment
at
large.
B
Is
that
that's
what
applications
are
being
built
on?
That's
what
ai
is
built
on.
That's
what
machine
learning,
that's
what
the
frameworks
are
being
built
and
that
the
tools
are
being
built.
So
there
is
clearly
a
path
to
say:
linux
is
the
place
to
start
your
development
because
that's
where
the
workloads
are
being
built,
that's
how
they're
being
deployed
so
right
from
day
one
having
that
linux
development
spot
is
is
critically
important,
because
no
one
wants
to
rewrite
and
to
your
point,
no
one
wants
to
no
one
wants.
B
When
you
have
to
ask
for
a
change
right,
you
you
don't
want
to
have
to
go
back
and
ask
microsoft
to
make
a
change
for
you
in
your
windows,
so
I
think
there's
there's
kind
of
a
baseline
decision
that
gets
made
that
linux
linux
is
where
it's
at
right.
It's
where
the
innovation
is
being
done.
It's
what
applications
being
built
on
now
you
move
to
kind
of
kind
of
the
developer
aspect
of
it.
Of
how
much
do
you
prepare?
We
clearly
understand
that
simplicity
of
access
is
key
right
for
developer.
B
C
B
Guest
plane
get
started,
and
this
is
something
that
we
we
have
been.
We
have
been
focused
on
to
try
and
make
sure
that
we
we
move
into
so
we
for
several
years
now
and
actually,
hopefully
it's
not
a
secret
or
surprise
to
anyone.
We
have
been
really
focused
on
making
sure
that
we
have
rel
developer
subs
right.
They.
C
B
Available
for
free
they're
focused
on
you
know,
making
sure
individual
users
can
get
access
and
for
with
with
simplicity,
to
starting
to
do
their
development
on
rel,
so
that
then,
when
it
lands
they,
they
know
it
can
land
in
a
production
of
deployment
etc.
So
we
want
to
make
sure
that
we
are
offering
that
simple
access
that
no
cost
access
to
folks
and
driving
that
forward,
I
think
there
is
there-
is
real.
B
There
is
real
merit
in
being
able
to
plan
ahead
for
the
success
of
what
you
want
to
do
in
deployments,
because
at
some
point
the
developer
and
the
line
of
business
meet
the
operations
team
right
and
how
do
you?
How
do
you
kind
of
bridge
that-
and
I
think
it's
a
it's
a
bit
of
a
reach
over
the
fence
from
both
sides?
I.
C
B
B
Yeah
and
and
and
doing
audits
on
the
security
and
the
compliance
and
all
of
that,
so
we
want
to
be
able
to
to
be
there
to
provide
a
you
know:
simple
access,
self-supported
development
only
subscription
easy
to
access,
and-
and
in
addition
right
I
mean
clearly
the
fedora-
the
fedora
community
is
providing
a
ton
of
focus
on
that
as
well
and
provides
a
whole
nother
space
for
folks
to
participate
in.
So
I
think,
between
fedora
and
then
coming
into
the
dev
subs,
we're
looking
to
try
and
make
that
easier
for
folks,
yeah.
A
C
A
Right
like
how
it
started
in
fedor
and
was
like
oh
my
gosh,
this
is
going
to
change
system
administration
for
lots
of
people.
This
is
going
to
be
great
to
now
it's
in
rel
and
like
it's
actually
changing
system
administration
for
people
and
the
data
center
and
far
and
wide
it's
pretty
cool
like
to
see
it
happen.
B
C
A
B
B
A
B
Folks,
we
have
rel
here
what
we've
done
fairly
recently
well
in
in
2019
was
we
announced
centos
stream,
which
sits
in
the
middle
right,
so
that
sits
between
the
fedora
upstream
and
rel
and
provides
a
a
bit
of
a
faster
iteration
loop
for
folks
who
are
looking
to
see
what's
coming
next
and
develop
on
top
of
rel,
but
get
visibility
to
that
early?
So
I
think,
there's
you
know.
B
A
Yeah
yeah
yeah.
No,
I
have
a
friend
on
the
fedora
team
who
I'm
constantly
like
this
is
so
cool.
When
can
when
is
this
landing
in
rel?
You
know
it's
it's!
It's
really
neat
and
you
know
fedora
drives
this
channel
right
like
we're
using
fedora
right
now
to
stream
the
the
actual
stream
like
it's
coming
out
of
a
fedora
box.
So
it's
it's
a
great
operating
system.
I
really
love
it
and
you
know
it
just
gets
better
with
time.
A
B
B
So
there's
there's
all
of
that
bit
the
thing
that
I
find
mostly
about
an
operating
system
that
that
to
me
it
makes
it
absolutely
not.
A
commodity
is
many
of
the
things
we
talked
about,
chris
around
around
being
that
kind
of
leveler
to
get
access
to
innovation,
to
move
to
the
edge
when,
when
someone
needs
to
move
to
the
edge
for
those
deployments
to
deploy
an
application
at
the
edge
or
a
container
at
the
edge.
All
of
that
means
that
the
choice
you
make
in
your
operating
system
is
a
very
strategic
decision.
Yeah
right.
B
It's
gonna
because
it's
strategic
both
for
what
I
deploy
today
for
what
I'll
deploy
next
year,
three
years
from
now,
how
secure
it'll
be
how
stable,
it'll
be
and
the
minute
it's
a
strategic
decision.
It's
not
a
commodity
right
and
that's
the
piece
that
that
I
I
hold
to
that.
Like
you
know,
hopefully
it's
simple:
hopefully
the
thing
just
just
works
and
you
don't
have
to
be
playing
with
it
every
day
and
fiddling
with
it
every
day,
but
that's
doesn't
that
does
not
a
commodity
make
right.
A
I
don't
I
don't
maintain
my
corn
supply.
No,
I
just
buy
it
and
consume
it
right,
like
you
know,
like
that's
a
commodity
right
like
the
the
idea
that,
like
oh
yeah,
the
os
doesn't
matter,
I
think
it's
just
like
okay,
fine,
if
the
os
doesn't
matter,
then
what
are
you
running
on
top
of
it?
That
does
matter
right,
like.
A
And
how
are
you
going
to
run
that
three
years
from
now
right
like
because
what
you
put
into
production
today
might
be
there
five
years
from
now,
you
don't
know
what
business
decisions
who
would
have
thought
kovid,
you
know
at
the
beginning
of
last
year,
would
have
changed
everything
that's
changed
today.
You
don't
know
what
your
code
is
going
to
do
five
years
from
now,
you
don't
know
where
it's
going
to
be
landing,
which
kind
of
ties
into
something
we
talked
about.
A
Yesterday
on
the
the
new
rail
show
we
have
here
on
the
channel
the
new
release
cycle
for
red
hat
enterprise-
linux
right,
like
I'm,
excited
about
it
because,
like
I
can
actually
open
up
a
calendar
and
plan.
My
upgrades
like
what
drove
us
to
that
decision,
was
it
literally
so
that
our
architects
out
there
could
open
up
a
calendar
and
plan
their
upgrades.
A
B
Came
in
and
they
said,
listen,
you
know
your
your
seven
and
eight
schedule
right.
I
didn't
know
what
was
coming.
I
didn't
know
when
to
plan
for
my
updates.
I
was
waiting
to
hear
from
you
guys,
so
we
came
in
with
a
with
a
you
know,
very
structured
way
so
that
they
could
plan.
But
that
was
absolutely
a
customer
request
and
the
feedback
from
customers
has
been
great
right
to
your
point.
Now
they
can
plan
they
can
predict.
B
I
can
tell
you:
it
takes
a
bit
of
navigation
in
the
ecosystem,
because
you
know
now
we're
working
with
all
our
partners,
whether
they
be
chip
partners,
whether
they
be
server
partners.
We
have
to
work
with
all
of
them
in
order
to,
but
we
have
put
a
stake
in
the
ground
to
what
we
are
doing
and
now
it's
a
matter
of
figuring
out
how
we
partner
and
pair
and
and
give
and
take
around
that.
But
you
know
the
feedback
has
been
great
incredibly
value
to
customers
yeah.
B
I'm
sorry,
the
value
of
an
operating
system
like
what's
next
make
sure
that
our
partnerships
remain
relevant.
That
is
number
one.
So
things
like
this
kind
of
consistent
deployment,
that's
important
for
us,
because
now
we're
partnering
with
the
public
clouds
we'll
be
partnering.
We
partner
with
nvidia
we
partner
with
all
of
these
partners
that
are
all
over
the
place,
and
we
have
to
make
sure
that
we
have
a
framework
in
place
that
allows
us
to
to
partner
with
the
next
startup.
That's
going
to
come
down
the
pipeline,
or
you
know,
kind
of
the.
B
Exactly
exactly
yeah,
so
how
do
we
stay
relevant
as
that
that
whole
world
of
of
isps
and
hardware
deployments,
and
all
of
that
start
continues?
I
think
the
second
piece
ties
to
the
ties
to
how
do
we
continue
to
drive
operational
efficiency
within
the
within
the
operating
system?
So
we
announced
insights,
I'm
sure
they
talked
about
the
inclusion.
C
B
We
pulled
in
insights
capabilities
into
every
subscription
available
right.
So
if
you
have
a
supported
sub
for
rel,
you
have
access
to
insights,
but
it
is
coming
back
to
that
managed
service
piece
right
that
you
talked
about
earlier.
It
is
our
way
of
providing
an
as
a
service
capability
that
takes
red
hat
knowledge,
expertise,
not
only
what
we
knew
yesterday,
but
what
we
will
know
next
month
and
what
we'll
know
in
three
months.
It
provides
us
a
way
to
provide
that
expertise
into
your
data
center
as
part
of
your
operating
system
subscription.
B
So
if
we
start
to
see
an
issue
bubble
up
with,
you
know
when,
when
this
config
runs
in
this
way,
with
this
application,
we
start
to
see
that
bubble
up.
We
can
proactively
tell
you
if
you're
linked
up
to
insights,
listen,
we've
seen
this
cause
trouble
for
others
right.
Take
a
look
at
this.
That
type
of
relationship
that
is
personalized
throughout
the
length
of
the
sub
to
me
is
super.
Exciting
insights
is
great
to
me.
A
B
A
We'll
turn
it
on.
You
know
we'll
test.
It
we'll
see
what
it
does
for
us,
but
they
happen
to
turn
it
on
one
of
their
database
servers
right
just
to
get
you
know,
sampling
and
that
database
server
has
had
problems
with
restarts
for
months
and
they've
been
working
with
the
database
vendor
for
months
to
try
and
figure
out
the
problem
they
turned
on
insights
the
next
morning.
They
got
their
report
hey
by
the
way.
This
kernel
has
a
problem
with
this
version.
A
B
B
Will
get
better
right
as
you
move
forward
in
that
subscription
length,
and
so
that
to
me
is
huge
value,
and
then
you
start
to
link
that
up
to
other
things
like
ansible
playbooks
that
are
built
to
remediate
those
issues.
Insights
gives
you
awareness,
you
decide
how
to
how
to
implement
the
remediation,
but
you
pull
that
into
things
like
insights.
It's
super
powerful,
yeah
and
we've
done
even
things
like
the
systems
roles
which
they
probably
talked
about
right.
We
actually
took
ansible
and
put
put
some
playbooks
in
for
system
roles
directly
into
the
operating
system,
so.
B
With
things
like
build
a
podman
scopio
right?
That's
one
step
forward.
It
gets
you
ready
for
when
you
need
to
move
into
orchestration
and
kubernetes
with
things
like
openshift,
so
I
think
there
is
a
there
is.
You
know
we
got
to
maintain
a
partnership
set
and
a
relationships
and
an
ecosystem
that
is
really
relevant
today,
but
there's
a
lot
of
work.
We
need
to
do
to
make
sure
that
that
continues
going
forward,
because
the
world
is
changing.
B
A
Mean
it's
going
to
happen
right,
like
I
mean
it's,
it's
inevitable
right
like
we're,
going
to
start
doing
very
specific,
like
nvidia
just
released
like
I
thought
they
call
it.
The
dpu
data
processing
unit
where
the
chip
is
on
the
actual
network
device.
It's
like!
Oh
that's,
mind-blowing,
right,
like
there's
going
to
be
more
and
more
situations
like
this,
where
the
compute
layer
becomes
different,
and
it's
like
a
subset
right
like
we
now
we
have
in
you
know
we
have
security
chips
inside
our
computers.
A
B
I
and
I
view
operating
system
and
what
we're
trying
to
do
in
rel
is
actually
exactly
the
opposite:
we're
trying
to
provide
a
level
of
standardization
to
make
sure
that
you
can
access
all
the
innovation,
and
I
think
that
ties
exactly
I
actually
was.
I
was
talking
to
someone
actually
last
week
on
this.
I
really
think
it
is
a
bit
of
a
lesson
too,
that
is
mirrored
in
what
we
see
in
the
open
source
communities
right.
You
have
all
of
these
projects
going
on.
B
They
could
all
be
doing
amazing
innovation,
but
if
they
all
went
in
different
directions
and
didn't
have
like
interfaces
to
make
sure
that
they
could
work
and
build
upon
one
another
and
have
standardization
of
the
boundaries
like
oci
compliance
as
an
example.
Without
those
kinds
of
standardization,
the
innovation
starts
to
go
off
in
different
directions
and
becomes
very
hard
to
implement.
So
there
is
a
layer
to
this
standardization
that
is
actually
improving
us
accessibility
to
innovation.
B
B
A
Yeah
it
and
it
was
the
whole
devops
movement.
I
think
too,
that,
like
oh
we're,
gonna
standardize
and
that's
gonna
help
us
move
faster,
but
wait
if
we
standardize
that's
gonna,
wait
what
right
like
no
like
going
fast,
actually
improves
speed
and
technology.
We've
proven.
I
know
like
changing
things
like
app
streams.
I
think,
is
the
perfect
example
of
this
right,
like
we
understand
that
you're
gonna
need
to
have
you
know:
postgres
9,
6,
10
and
12
all
in
this
life
cycle
of
rail
8.
A
right
like
we
get
it,
you
know
you're
and
you'll
want
13
and
you
want
14.,
and
you
know
that
might
be
on
rail
8.
That
might
be
unreal
9,
but
it's
going
to
be
there
for
you
in
the
future
and
having
that
there
having
that
standard
foundation
which
you
can
secure
and
manage,
and
standardize
across
your
entire
fleet
of
servers
and
hosts,
because
there's
metal
somewhere
is
a
very,
very
big
deal
to
me.
Yeah.
C
A
And
that
entry
level
stuff
that
we're
doing
to
help
people
dive
deeper
is
is
what
this
channel
is
all
about
right
like
so
we
take
those
tools
that
are
built
into
rel
and
kind
of
help.
People
understand
like
where
does
that
get
started
right,
like
in
the
level
up
hour,
show
we
talk
about
pod
man
and
spokeo
and
build,
and
you
know
how
we
build
up
to
that.
A
Kubernetes
stack
and
you
know,
we've
been
going
through
it
for
a
few
weeks
and
pod
man's
been
a
huge
part
of
that
journey,
and
it's
just
so
cool
to
see
like
our
commitment
to
containers
in
the
os,
and
it's
like
okay,
yes,
you
can
still
do
it
with
just
rel.
You
know
you
can
install
and
manage
it
through
cockpit.
If
you
want
right,
like
you,
don't
have
to
go
full-blown,
you
know
kubernetes
orchestrator.
If
you
just
need
to
run
a
few
containers,
you
could
still
do
that
with
rel.
B
Helps
you
get
started
right
and
start
to
pave
that
way
as
you
move
forward
and
and
that
that's
a
key
role.
I
think
that
we
have
to
play
here
and
I
think
what
it's
helping.
Hopefully
people
see
we
are
much
tighter
aligned
across
the
portfolio
because
of
this
right.
The
linkages
that
we
have
in
rel,
with
the
with
openshift
with
ansible,
how
we
pull
all
of
that
together
is
much
tighter
and
and
being
done
on
behalf
of
the
value
we
can
deliver.
You
know
collectively,
as
red
hat
to
a
customer.
A
Right-
and
I
think
you
know,
your
point
is
spot
on-
I
see
it
in
my
daily
life
right
like
every
week.
I
talk
to
somebody
in
the
ansible
team
and
somebody
in
the
rail
team.
You
know
every
product,
it
feels
like.
I
talked
to
somebody
on
that
team
every
week
and
that's
not
because
of
the
show
or
the
tv
channel
it's
because
of
actual
like
work
work
right
like
so
we're
all
working
together
on
making
this,
you
know
cloud
or
whatever
data
center
experience,
you're
going
through
a
better
experience.
A
A
B
C
B
Now,
when
you
look
at
the
the
market
right,
people
throw
out
the
term
hybrid
cloud
16
ways
to
sunday.
I
think
one
of
the
things
that
that
ties
to
the
point
you
just
made
about
making
technology
more
cohesive
is,
you
know,
hybrid,
hybrid
cloud
used
to
be
a
simple
term
of
I
have
on-prem.
I
have
off-prep,
I
am
now
hybrid.
I
think
now,
as
a
lot
of
the
technologies
we
talked
through
are
really
about
how
the
term
hybrid
or
the
just
pure
definition
of
hybrid
is
that
their
hybrid
is
across.
B
Really
your
entire
stack
at
this
point
right,
you
could
be
hybrid
at
the
architecture
level,
your
hybrid
across
which
public
clouds
you
use
your
hybrid
across
vms
and
bare
metal
and
containerization
you're
hybrid
across
edge.
Now,
in
linkage
with
what
I'm
running
in
my
data
center
hybrid,
is
across
all
the
spots,
so
it
is
not
about.
It
is
not
just
about
you
know,
on-prem
and
off-prem
anymore.
B
I
think
what
we're
trying
to
focus
on
as
a
portfolio
is:
how
do
we
bridge
all
of
those
layers
of
hybrid
and
whatever
next
layer
of
hybrid
is
going
to
come
down?
The
pipeline
right,
but
how
do
we
provide
some
access
to
all
of
those
hybrid
and
some
simplicity
with
how
to
run
it
and
how
to
deploy
it
and
how
to
manage
it
at
scale?
B
So
that's
really
that
to
me
is
where
our
focus
is,
and
it's
and
rel
has
a
core
role
to
play
in
that,
not
just
in
what
we
can
allow
folks
to
do
at
an
operating
system
level
in
bare
metal
or
vms
or
single
containers,
or
you
know,
small
containers.
But
how
do
we
then
bridge
that
technology
in
that
ecosystem
into
the
rest
of
the
portfolio?
B
So
I'm
super
excited
to
be
at
kind
of
the
the
the
heart
of
this
glue
right
that
we
try
and
deliver
and
and
and
this
kind
of
burgeoning
world
of
hybrid.
I
I
think
the
hybrid
cloud
term
is
one
of
those,
those
moving
moving
targets
that
we're
all
going
to
be
chasing,
but
that's
the
exciting
part
of
it
to
me.
Yeah.
A
Like
we
one
of
the
last
jobs
I
had
before
joining
red
hat,
it
was
like
oh
we're
all
in
on
aws,
I'm
like
wait,
wait.
Our
entire
network
is
managed
by
something
in
cisco's
cloud,
we're
not
all
in
on
aws
right.
We,
like
those
network
people,
have
to
manage
something
completely
different
than
aws.
We
have
to
help
them
right,
like
so
like
the
the
idea
that
you're
all
in
in
any
one
place,
I
think
the
only
place
you
could
really
do
that
is
in
your
own
data
center.
A
B
It
may
change
it
may
change
tomorrow.
It
may
change
in
a
week
right.
So
so
it's
really
about
how.
How
how
are
you
ready
to
be
able
to
change
with
it
right
and
and
based
upon
the
needs
and
and
evolve?
Can
you
evolve,
and
I
tell
you
nothing
has
shown
us
that
more
than
than
everything
everyone
has
been
through
with
kovid
right,
it
has
shown
us
all
the
the
unprecedented
change
that
we
all
may
have
to
be
dealing
with.
A
Well,
stephanie,
thank
you.
So
much
for
joining
us
today
really
appreciate
your
time.
It
was
a
wonderful,
wonderful
experience.
I
want
to
remind
folks
in
two
weeks
we'll
be
back
with
satish.
Our
vp
of
managed
services
here
at
red
hat,
so
that'll
be
an
interesting
conversation
to
follow
on,
after
our
conversation
about
managed
services
and
then
coming
up
immediately
after
this
is
devnation
with
talk
about
istio,
I
think
kubernetes,
istio
and
telepresence,
so
that'll
be
super
fun.
So
please
stay
tuned
and
thank
you
again.
Stephanie
for
joining
us.