►
From YouTube: In the Clouds (E23) | Red Hat Enterprise Linux 9 preview
Description
Are you ready to learn how Red Hat Enterprise Linux 9 builds on the solid foundation of enterprise dependability, security, and stability established in Red Hat Enterprise Linux 8? In this episode of In the Clouds, Red Hat Vice President and GM for Linux Gunnar Hellekson and host Stu Miniman will be discussing what's in store with RHEL 9 and preview some of the upcoming simplified experience and new features designed to make Linux more secure, easy to manage in hybrid multicloud cloud environments, and easy to use on edge devices.
Want to learn more?
https://www.redhat.com/en/blog/whats-new-rhel-90-beta?sc_cid=7013a000002qG16AAE
Try Red Hat Enterprise Linux: https://www.redhat.com/en/technologies/linux-platforms/enterprise-linux?sc_cid=7013a000002qG16AAE
Follow us:
Stu Miniman https://twitter.com/stu
Gunnar Hellekson https://twitter.com/ghelleks
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 on redhat.com https://red.ht/3JBaOia
OpenShift on GitHub https://github.com/openshift/
#RedHat #OpenShift #HybridCloud
A
A
Welcome
to
in
the
clouds-
I
am
your
host
stu
miniman-
and
this
is
the
may-
is
the
whole
month
yesterday
was
star
wars
day
or
may.
The
fourth
beat
with
you
and
that
of
course
makes
today
revenge
of
the
fifth
so
needed
to
get
all
the
star
wars
puns
out
of
the
way,
because
at
red
hat,
yes,
we
do
celebrate
star
wars
day.
A
We
all
bring
our
whole
selves
there
and
I've
been
wearing
lots
of
star
wars
gear
all
week,
but
it
is
also
a
very
special
week
this
week
at
red
hat,
because
it
is
relweek
which
is
red,
hat
enterprise.
Linux,
I'm
sure
anybody
watching
this
knows,
and
tomorrow
actually
is
the
20th
anniversary
of
rel.
So
to
help
us
celebrate
that
and
talk
about
all
that's
new
and
what's
been
going
on
with
the
development
of
rel,
nine
really
happy
to
welcome
to
the
program.
A
A
Yeah
so
boy
I
mean
gunner
it
it
it's
funny.
So
you
know
you
haven't
quite
been
at
red
hat
for
20
years,
I've
only
been
at
red
hat
for
a
year
and
a
half,
but
I
remember
when
you
know
it's
funny,
it
was
you
know:
raz
2.1
came
out
of
it,
which
eventually
turned
into
rel.
20
years
ago
I
was
working
for
a
large
storage
company.
You
know
we
needed
enterprise
workloads
in
production
and
oh
my
gosh,
the
linux
2.4
kernel.
A
What
a
mess
we
had
pages
of
patches
that
customers
needed
to
use
to
be
able
to
support
it.
We
only
had
a
very
small
team
of
engineers
that
was
doing
that
testing
and
when
red
hat
kind
of
separated
itself
from
the
pack
and
said
here's
an
offering
that
can
work.
You
know
I
is
like
a
product
and
program
manager
told
our
field
like
hey.
A
B
It
has,
if
you
think,
about
what
and
it's
not
just
relevance
changed
right.
It's
the
it's.
The
entire
linux
landscape
has
changed.
We
went
from
being
kind
of
rough
up
stars
right,
everybody
recompiling
their
own
2.4
kernel.
I
know
that's
what
I
did
right
and
now
it
is.
Linux
is
like
water,
it's
it
is
everywhere.
It's
powering
everything!
It's
and
I'm
looking
at
my
desk
here,
it's
in
at
least
one
two,
three
four
six
devices
on
my
desk.
B
A
Yeah,
no,
no
gunner
you're!
So
right,
you
know.
One
of
the
things
I
used
to
say
is
an
analyst.
If
it
wasn't
for
linux,
we
probably
wouldn't
have
the
cloud,
and
maybe
people
said
stu-
we
probably
wouldn't
have
the
internet
of
today.
If
it
wasn't
for
linux,
we
don't
need
to
think
about
it.
When
I
do
you
know
a
search
on,
you
know
the
web
or
if
I
buy
a
product
on
the
web,
I
don't
think
about
the
fact
that
there's
linux
underneath
that.
A
So,
let's
let's
talk
about
rel
itself,
though
so
you
know
a
lot
has
changed.
You
talk
from
the
self-compiling
kernel
to
you
know
how
many
people
at
red
hat
here.
Have
you
know
a
shrink,
wrap
box
behind
them
to
talk
about
the
deployment
that
they
did
of
of.
You
know
rel,
and
you
know
red
hat
linux
before
that
to
today
the
the
development
of
what
you've
been
doing
in
real
nine.
It's
a
little
bit
different
than
what
we've
seen
in
the
past
yeah.
B
Yeah,
that's
right
so
so
excuse
me,
real
nine
will
be
the
first
release
that
we
have
done
using
the
centos
stream
mechanism.
So
actually
let
me
do.
I
should
do
a
history
lesson
right,
that's
how
we
started
okay,
so
you
mentioned
we
split
red
hat,
we
split
rel
or
sorry
when
we
split
red
hat
linux
into
fedora
and
red
hat
enterprise
linux.
B
We
did
that
in
order
to
basically
keep
kind
of
a
separation
of
concerns,
we
needed
a
place
to
go,
do
kind
of
disruptive
innovative
risk
taking
and
then
we
needed
a
place
or
you
know
to
do
the.
I
think
they
call
it
they
like
to
call
the
bleeding
edge
work
right
and
then
we
needed
a
place
where
we
could
do
the
hardening
and
the
stability
and
and
create
something
that
somebody
could
use
in
a
like
a
mission,
critical
enterprise
context.
B
Okay,
so
now
we've
got
fedora
over
here
and
we've
got
red
hat
enterprise
linux
over
here.
This
served
us
extremely
well
for
a
very
long
time,
and
so
recently
we
made
a
change,
though
we
added
a
intermediate
step,
because
what
we
found,
especially
with
things
moving
so
quickly,
we
needed
a
a
good
way
of
better
collaborating
with
our
partners,
who
they
needed
early
access
to
what
we
were
doing
and
but
couldn't
wait
until
we
had
fully
productized
it,
and
so
they
needed
something
they
needed
a
middle
step.
B
A
Yeah,
so
that
development
almost
a
little
bit
more
in
the
open,
because
it's
always
been
open
source
and
what's
done,
but
that
that
relationship
with
the
community
has
changed
a
little
one
of
the
other
things
gunner.
You
know
I
remember
back.
You
know,
I
believe
it
was
three
years
ago
when
rel
8
came
out.
B
B
A
A
Okay,
awesome
all
right
great,
thank
you
and
yeah,
no
good
to
see
people
in
the
chat
eric
the
it
guy
who
does
one
of
the
red
hat
live
streams?
Is
there
I
know
he's
been
doing
a
lot
of
the
internal
activity
for
real
week
this
time
and-
and
I
love
what
you
talked
about-
gunner,
because
when
the
the
kind
of
competing
challenges
that
enterprises
face
and
where
red
hat
sits
right
in
the
middle
is
number
one
is
there's
that
constant
change,
there's
so
much
coming
on.
A
You
know,
I
remember
seeing
it's
like
you
know:
what's
you
know
a
million
lines
of
code
change
every
month
in
the
linux
piece
and
on
the
other
hand
the
enterprise
says
like
hey?
I
can't
change
this
every
month,
every
quarter,
sometimes
I
can't
even
change
it
every
year.
So
how
do
you
keep
me
up?
Get
my
security
patches
yet
allow
me
to
have
longer
life
cycles
and,
of
course,
that's
what
red
hat's
been
doing
with
all
of
our
software
product
for
a
long
time.
A
B
Yeah,
so
the
so,
if
you
think
about
I'll,
just
hear
it
this
way,
I
like
to
think
about
real
having
kind
of
three
different
kinds
of
customers
right.
So
the
first
set
of
customers
is
those
hardware
providers
that
I
was
that
I
was
talking
about
and
they
need
to
be
able
to
have
a,
as
you
mentioned
like
having
have
a
stable
kernel
that
they
can
work
against
and
they
need
a
stable
kernel
that
they
can
write.
B
They
can
write
drivers
for
right
and
so
being
able
to
so,
and
I
feel
like
that's
a
we've
done
a
pretty
good
job
at
that
over
the
last
20
years.
We
made
that
pretty
simple
for
folks
for
people
writing
applications,
that's
the
second
kind
of
audience
for
the
operating
system.
For
people
writing
the
applications
we
have.
We
provide
a
stability
internally.
B
We
call
it
the
abi,
the
binary
interface
right,
so
we
have
a
stable
avi
and
with
rel
we
commit
that
when
we
do
a
new
major
version
that
major
versions
abi
will
be
stable
throughout
the
lifetime.
So
if
you've
written
an
application
for
rel
8.1,
it's
going
to
continue
working
all
the
way
through
the
eight
all
the
way
through
the
eighth
cycle.
B
So
that's
the
three
is
there's
a
third
audience,
and
I-
and
I
think
it's
ironic-
that
we
only
started
talking
about
this
third
audience
recently,
but
the
third
audience
are
the
people
who
are
actually
using
the
operating
system.
It's
we
spend
a
lot
of
time,
thinking
about
the
artworks,
a
lot
of
time,
thinking
about
the
application,
folks,
the
developers,
but
I
think
only
recently-
we've
really
spent
a
lot
of
time
focusing-
and
this
is
in
part
due
to
I
think
in
part.
B
This
is
part
of
our
own
attention,
but
I
think
also
this
is
a
statement
about
the
maturity
of
the
linux
market
in
general.
Is
we're
at
the
point
now,
where
we're
doing
things
like
shipping
web
consoles
gui
is
making
things
easier
to
use,
making
first
of
all
people
with
mouse
and
keyboards
right,
having
making
gui's
easier
to
use,
but
also
creating
systems
to
make
automation
of
linux
easier
right,
because
it's
been
a
long
time
since
most
of
our
customers
have
touched
a
server
with
a
mouse
and
a
keyboard
right.
B
People
still
do
it,
but
the
vast
majority
of
servers
out
there
are
being
managed
not
by
people
but
they're,
being
managed
by
machines
right.
It's
automation,
systems
like
ansible
and
so
forth,
and
so
when
we
talk
about
simplifying
a
lot
of
what,
what
we're
simplifying
is
we're
simplifying
the
act
of
managing
the
system
both
for
humans
through
things
like
web
consoles
and
guise,
and
things
like
this
and
also
simplifying
the
management
through
these
automation
systems
and
that's
through
investments
we've
made
in
something
we
call
system
roles
so
rel
system
roles
are.
B
If
you
use
the
system
roles
in
order
to
manage
your
system
perform
these
routine
tasks,
you're
insulated
from
a
lot
of
the
complexity
of
like
you
know.
So,
if
we
were
to,
for
example,
do
something
crazy
like
change
the
time
system
on
rel
right,
you
don't
have
to
go
back
and
redo
all
of
your
automation,
because
we
changed
the
time
system.
If
you're,
using
a
system
role,
the
system
rule
will
take
care
of
all
those
changes
and
insulate
you
from
all
those
changes,
and
so
anyway,
that
was
a
long
answer.
B
A
Yeah
and
kind
of
that
that
tees
up
that
those
underlying
systems,
so
you
know
my
my
background,
I'm
an
infrastructure
guy
and
you
know
I
remember
if
you
go
back,
you
know
about
10
years
ago
it
was
oh
we're
going
to
go
all
the
white
boxes,
everything's
going
to
be
commoditized.
The
cloud
should
look
at
as
this.
A
You
know
simple
plane
and
I
look
at
the
cloud
and
I
say
if
I
want
to
deploy
a
server
in
the
cloud,
I
think
there's
more
complexity
and
options
there
than
if
I
go
to
you
know.
Dell
hp
lenovo
choose
your
server
of
choice
in
my
data
center
there's
more
options
there.
I
know
a
lot
of
work's
gone
on
with
arm.
There's,
there's
new.
You
know,
hardware
architectures,
so
maybe
speak
a
little
bit
to
arm
and
some
of
the
other.
A
B
Yeah,
so
I
mean
this
is
one
of
the
core
missions
of
railroad
is
to
be
available
everywhere.
Customers
need
us
to
be
right,
and
so
we've
always
supported
multiple
micro
architectures,
so
the
x86
folks
and
power
and
z
and
so
forth,
and
just
in
january
we
announced
that
we
made
finally
made
generally
available
rel
for
arm.
B
So
now
arm
is
a
first
class
citizen,
just
like
all
the
other
micro
architectures-
and
this
was
I
mentioned
before-
that
the
this
kind
of
predictability
of
the
hardware
market
you
know
it
used
to
be.
You
could
set
your
clock,
you
know
every
18
months,
moore's
law,
right,
it's
okay,
things
are
going
to
double
every
18
months:
tick,
tock,
tick,
tock,
right
that
that
is
no
longer
the
case,
and
and
that's
due
to
lots
of
things
right.
B
We
know
we
have
new
and
exciting
micro
architectures
like
arm-
and
I
know
we
have
other
up
and
comers
coming.
You
know
so
risk
five
people
are
starting
to
talk
about
meaningfully
and
we've
got
also
the
introduction
of
accelerators
right,
so
there's
asics
and
fpgas
and
gpus,
and
so
as
you
it's
it's
interesting
watching
the
hardware
market
now,
because,
on
the
you
have
the
public
cloud
providers
who
the
fun
it's
a
commodity
market
right,
it's
a
the
economics
of
it
or
it's
a
commodity
market,
so
they
need
to
differentiate
their
offerings.
B
A
It's
one
of
those
the
customers
expect
it,
but
they
under
appreciate
the
amount
of
work
that
has
to
go
into
it.
I
had
mike
barrett
who
runs
product
management
for
openshift
on
two
shows
ago.
So,
a
month
ago,
talking
about
openshift,
4.10
and
when
it
came
to
you
know,
new
support
for
azure
stack
hub
and
the
question
I
posed
to
him
was
well
we've
had
you
know,
rel
and
openshift
running
on
azure
for
years,
isn't
azure
stack
hub?
A
Just
you
know
that
microsoft
instantiation
in
customers,
data
center
and
mike
was
like
well
yeah.
It
is,
but
at
the
operating
system
level
there
are
certain
bits
and
configurations
and
settings
that
change,
and
it's
like.
Oh
it's
where
you
know
the
marketing
and
the
engineering
reality.
You
know
yeah,
it
works,
but
the
devil's
in
the
detail.
We
know
and
that's
where
you
know
red
hat's
experience
working
across
all
those
environments
and
working
closely
with
the
isv
ecosystem
so
yeah.
I
guess
that
sets
up
for
the
discussion
of
you
know
this
hybrid
multi-cloud
world.
A
You
know
we
talk
about
whatever
you
know
term
customers
want
to
use.
The
reality
is
the
diversity
of
applications
and
infrastructure
that
they're
doing
is
even
more
diverse
today
and
will
continue
to
be
more
diverse
in
the
future.
So
you
know
what
does
that
mean?
You
know
what
what's
in
real
nine
and
what
are
the
things
that
that
your
team's
looking
at
to
you
know,
live
thrive
and
enable
you
know
our
customers
to
to
innovate
and
take
advantage
of.
What's
out
there.
B
Yeah
sure
so
so
kind
of
picking
up
on
some
of
the
breadcrumbs
I
just
left
behind
the
certainly
we're
gonna
continue
doing
the
things
that
all
the
braille
needs
to
do,
which
is
again
insulate
people
from
and
let
them
I
say
insulate.
I
say
insulate
them
from
the
complexity,
while
still
allowing
them
to
take
advantage
of
all
of
the
interesting
stuff
that
this
hardware
can
do.
B
That's
kind
of
job
number
one
and
job
number
two
is
to
number
one
create
that
stability
that
I
talked
about
for
the
applications,
but
also
you
know
it's
interesting.
If
you
look
at
the
rel's,
something
like
10
000
packages,
now
it's
it's,
this
conglomeration
of,
like
10,
000
upstream,
open
source
projects,
it's
crazy,
the
amount
of
software
that
it
is
right.
It's
a
no
longer
fits
on
a
dvd
right.
It's
that's
it's
that
big,
but
if
you
look
at
what
an
actual
like
what
is
an.
A
B
Basically,
they
can
trust
us
to
be
shipping
the
software
and
making
sure
that
it's
stable
and
that
we're
patching
bugs
and
things
like
this
and
so
having
taught
people
that
they
keep
asking
us
to
ship
more
stuff
right,
and
so
the
natural
progression
of
rel
is
just
to
keep
adding
more
packages
more
packages
and
more
packages.
That's
fine
as
far
as
it
goes,
and
it's
work
that
we're
happy
to
do.
B
B
In
this
way
we're
able
to
let
people
take
advantage
of
almost
like
rel
as
us
as
a
supply
chain
right
and
give
people
as
many
options
as
possible
without
sacrificing
those
the
stability
that
we've
got.
So
if
you
want
to
go
move
more
quickly
with
something
like
ruby
or
python,
or
something
like
that,
you
can
go
use
those
application
streams.
B
If
you
want
kind
of
a
10-year
promise
and
a
13-year
commitment
on
something
that
is
super
super
super
super
stable,
then
you
can,
then
you
have
that
option
as
well
and
so
yeah.
In
this
way
we're
rel
is
first
an
operating
system,
but
second,
it's
also
a
library
of
dependencies
that
that
people
can
use
in
their
own
in
their
own
shop.
A
Yeah,
it's
great
there's
some
good
residents
in
the
chat
about
the
the
arm.
Processor.
Eighth
doctor,
who
was
asking,
I
think,
he's
looking
for
you
know,
would
love
to
have
a
inexpensive
arm
platform
to
be
able
to
do
I'm
guessing.
You
know,
test
dev,
home,
lab
type
of
environment,
any
anything
you've
been
hearing
from
the
team
as
to
what
ways
to
do
that.
B
In
order
to
make
this
make
the
whole
operation
less
expensive
is.
This
is
a
good
plug
for
the
our
developer
program.
So,
with
the
red
hat
developer
program
developer
for
individuals,
we
call
it
inside
you
can
go
and
subs
you
can
go
sign
up
for
the
developer
program.
We
just
expanded
that
so
that
you
can.
B
B
This
subscription
was
is
designed
for
you,
so
if
you
want
to
run
your
own
home
lab,
if
you
want
to
run
your
own
mail
server
in
a
basement,
you
can
do
that
with
the
with
the
red
hat
developer
subscription
and
with
that
it
should
give
you
access
to.
You
know
you
can
use
whatever
arm
hardware
you
like
now.
I
should
say,
though,
that
the
arm
hardware,
that
we
support
right
now
is
we're
pretty
focused
on
the
server
ready
hardware.
B
It's
like.
Can
I
take
a
digression
on
the
weirdness
of
the
arm
of
the
arm?
You
can
say:
okay,
all
right
here,
we
go.
Okay
are
like
so
intel
amd.
The
x86
world
super
super
predictable
right.
You
have
one
company
that
is
basically
making
these
things
and
all
these
motherboards
look
the
same.
All
the
systems
look
more
or
less
the
same,
and
so
anyway,
so
relatively
predictable,
relatively
stable
arm
super
innovative,
moving
quickly
lots
of
different
providers,
and
so
you
have
all
different
systems
on
ship.
You
have
all
these
different
socs
floating
around.
B
Each
of
them
have
to
get
enabled
separately,
unlike
the
x86
ecosystem,
where,
if
we've
got
one
version
of
a
chip,
I
could
we
can
kind
of
enable
that
and
everything
more
or
less
works,
but
each
of
these
socs
have
to
get
enabled
separately
and
so
creating
and
encouraging
more
consistency
in
the
arm
ecosystem
is
something
that's
pretty
important
to
us.
So
the
arm
folks
have
set
up
a
program
for
this.
It's
called
the
system
ready
program
and
so
they're
our
system,
server,
ready
and
so
we're
rel
works
on
the
on
that
hardware.
B
B
We
are
we're
focused
on
the
arm
server
class
hardware
right
now,
and
especially
as
we
start
making
investments
in
edge,
we're
going
to
be
we're
going
to
be
working
our
way
down
that
that
list
of
programs
again
so
to
make
sure
that
we
can
take
advantage
of
all
the
interesting
stuff
that
the
the
arm
edge
hardware
is
doing.
We
have
there's
every
reason
to
believe
that
rel
has.
The
rel
can
go,
enable
those
use
cases
as
well.
A
B
Think
let
me
read
this:
I'm
sorry
we're
going
how
to
get
the
enterprise
time
ecosystem
vendors
through
these
desktop
packages
for
cs9
before
blind,
oh
yeah,
okay,
so
yeah
people
can
target
centos
stream.
People
can
certainly
target
sent
to
a
stream
nine.
I
think
the
this
is
a.
This
is
a
good
opportunity
to
talk
about
apple,
so
enterprise
extra
packages
for
enterprise-
linux,
I
think,
is
what
it
stands
for
apple.
We
just
call
it
apple,
so
this
is
a
kind
of
sidecar
project
that
allows
you
to.
B
People
can
build
packages
that
red
hat
won't
won't
ship.
You
can
build
those
separately
and
put
them
on
apple,
and
if
you
subscribe,
your
your
rels
rail
system
to
these
apple
repositories,
you
can
go
get
those
extra
packages,
so
it's
a
way
for
people
to
extend
the
rel
ecosystem
without
waiting
for
red
hat
to
ship
software.
So
if
you
think
about
how
the
development
of
rel
works,
we
started
fedora
and
then
we
move
into
centos
stream
and
things
cook
and
sent
to
a
stream
when
you're
looking
at
centos
stream.
B
Today,
you
are
looking
at
the
development
of
the
actual
rallies
or
red
hat
engineers
working
on
rel,
and
so,
if
you
are
targeting
a
package,
if
you're
targeting
an
application
for
something
like
real
nine,
you
can
follow
the
development
of
centos
stream
nine
and
know
that,
as
we
get
closer
and
closer
to
ga
you're
getting
closer
and
closer
to
what
rel
nine
is
eventually
gonna
ship
and
look
like
and
so
anyway,
which
is
to
say
if
now
we
have
now.
This
is
so.
B
The
question
is
about:
how
do
we
get
ecosystem
vendors
to
release
desktop
packages
in
cs9
before
real
nine?
This
is
exactly
what
we
would
like
people
to
be
doing.
So
if
you
are
building
desktop
applications
for
real
nine
and
if
and
you're
an
isv
who's
I'm
trying
to.
I
don't
want
to
pick
one
out
by
name
but
just
firefox.
Let's
say
just
as
an
example.
B
If
I'm
building
firefox-
and
I
want
to
target
it
for
real
nine,
you
should
be
able
to
build
your
firefox
against
centos
stream,
nine
and
if
you
are
following
sent
to
a
stream
nine
through
the
through
the
lifetime.
By
the
time
we
get
to
real
nine
ga
you'll
be
ready,
you'll
you'll
be-
and
this
is
exactly
what
the
centos
stream
system
was
designed
to
enable,
so
that
you
don't
have
to
wait
for
like
a
real
nine
alpha
or
a
real
line
beta
before
you
can
do
your
before.
You
can
do
your
work.
A
All
right,
one
of
the
other
topics
we
haven't
touched
on
yet
is
security.
So
is
there
anything
new
in
real
nine?
You
know
when
I
think
about
the
whole
space.
The
surface
area
of
attack
is
so
much
larger.
You
talk
about
the
diversity
of
hardware.
I'm
sure
has
challenges
going
to
the
public
cloud
going
to
the
edge
all
have
unique
issues.
We're
spending
a
lot
of
time
on
the
secure
supply
chain
is
red
hat
as
a
overall.
I've
got
some
people
on
my
team
working
on
that.
A
B
B
No,
with
every
release,
we
obviously
take
security
very
seriously.
It's
one
of
the
things
customers,
customers
expect
from
us
and
so
we're.
So
we
so
we
made
several
investments,
and
sometimes
I
could
talk
about
new
security
features
which
way
of
which
we
have
several,
but
maybe
one
of
the
most
important
things
we're
doing
is
actually
taking
things
out
in
order
to
make
a
new
maker
outline
more
secure.
So,
for
example,
you
should
see
us
deprecating,
outdated,
cryptograph,
cryptographic,
algorithms
right.
B
So
there
are
some
hashing
algorithms,
which
have
been
discouraged
for
for
years
now,
and
part
of
our
job
is
to
make
sure
that
we're
not
accidentally
using
any
of
those
discouraged
hashing
out
the
rooms,
because
we
don't
want
people
thinking
that
they're
secure
when
they're,
not
in
fact
secure
because
their
cryptography
is
broken.
So
we've
taken
some
of
the
some
of
them
we've
deprecated
some
additional
cryptographic.
Algorithms
you'll
see
us
rebuilding
on
openssl
three,
for
example,
you
know
lots
of
lots
of
individual
security.
B
Related
packages
have
obviously
been
updated
and
and
rebased
in
order
to
for
the
for
their
online
release,
one
of
them
one
of
my
favorite
projects.
Back
before
I
was
before
I
was
on
the
product
side
iral.
I
was
in
the
public
sector
for
red
hat.
I
was
working
with
the
federal
government
and
state
local
governments,
and
things
like
this,
and
one
of
my
favorite
projects
was
was
a
was
a
thing
called
scap
the
secure
content
automation
protocol.
B
So
this
is
a
way
of
describing
a
security
posture
and
ensuring
that
your
system
matches
that
security
posture.
So,
in
other
words,
if
you
have
a
set
of
rules
around
the
federal
desktop
computing
standards,
for
example,
you
could
put
those
rules
in
machine,
readable
form
and
then
run
run
a
program
on
your
system
and
the
system
would
self-report
like.
Yes,
I
comply
with
the
standard.
B
This
is
useful
for
both
an
individual
server,
but
also
useful
to
be
able
to
do
across
many
systems
at
the
same
time,
right
if
you've
got
a
whole
fleet
of
systems
that
need
to
be
hipaa
compliant
or
complying
with
like
pci
dss
or
what
have
you
and
so
with
rel.
We
actually
ship
with
guidance
on
things
like
hipaa
and
pc
pcids,
that's
built
in
so
so.
Each
of
your
real
systems
can
now
reach
your
real
nine
systems.
B
They
can
self-report
on
their
on
their
compliance
with
with
particular
standards,
so
I
always
enjoy.
I
always
enjoy
stuff
like
that.
We've
also
changed
several
defaults
because
one
of
the
most
important
things
with
security
is
making
sensible
choices
from
the
outside
and
so
we've
with
a
major
release
of
the
operating
system.
A
So
this
show
is
in
the
clouds
gunner.
How
about
you
know
what
what's
happening
in
the
public
cloud.
You
know
how
many
years
ago,
what
was
there,
the
you
know
just
enough
operating
system
movement.
You
know
I'm
not
going
to
need
to
think
about
it.
Heck.
You
know
red
hat
acquired
coreos,
whose
original
you
know
business
model
was
you
know
it's
gonna
be
just
like
chrome
automatic
update.
A
B
Yeah
yeah
yeah,
so
I
think
the
number
one,
especially
for
customers
who
already
have
an
infrastructure
right
they.
What
was
true
before
clouds
existed,
which
is
that
especially
when
you're
talking
about
an
operating
system,
consistency
and
you.
We
talked
about
simplicity
at
the
top
of
the
show,
the
simplicity
and
complexity
and
making
sure
that
your
operations
are
efficient
and
well
audited.
And
all
these
other
things.
These
are
all
still
important
and
that's
true,
whether
you're
managing
multiple
data
centers
or,
if
you're,
managing
data,
centers
and
cloud.
B
And
so.
But
when
I
talk
to
customers,
what
I
find
is
that
they
are
happiest
when
they
have
made
a
single
operating
system,
choice
that
they
can
then
exercise
on
on
all
the
different
clouds
and
all
the
different
infrastructures
that
they
that
they
need
to
run
and
by
the
way.
Nowadays,
it's
not
even
just
a
data
center
in
a
public
cloud.
It's
also
data
center
public
cloud
and
and
deployments
out
to
the
edge
right,
and
if
you
can
have
the
same
operating
system
that
is
able
to
host
applications
on
all
of
those
infrastructures.
B
Then
you've
got
a
chance
to.
You
only
have
to
train
your
operators
once
you
only
have
to
train
your
developers
once
everyone's
kind
of
swimming
in
the
same
pool.
So
that's
that's
kind
of
that's.
That's
kind
of
the
takeaway
number
one
now
that
said,
public
clouds
are
unique
in
the
sense
that
they
are
elastic
and
you
can
spin
things
up
and
shut
things
down
very
quickly,
and
so,
when
we
build
rel
for
the
public
clouds,
we
have
to
optimize
for
different
things.
B
First
of
all,
the
hardware
is
weirder
like
we
like,
we
talked
about
it's,
the
hardware
is
unique,
and
so
we
need
to
make
sure
we're
optimizing
for
for
the
novel
hardware-
that's
up
there,
but
we
also
need
to
optimize
for
things
like
boot
time
right
in
a
data
center
you're,
not
so
much
worried
about
boot
time
on
the
public
cloud.
You
are
extremely
worried
about
boot
time
right
because
that's
that
that
affects
the
responsiveness
and
the
response
time
of
your
applications.
B
I
think
you
mentioned
the
the
just
enough
os
there
was
that
there's
a
drive
to
also
make
things
significantly
smaller,
and
I
think
there
is-
and
so
minimization
is
certainly
a
theme
that
we're
working
on
for
for
for
rel
in
general
and
then
specifically
on
rail,
nine,
making
it
easier
to
make
rel
composable.
That
is
not
just
to
it
shouldn't
be.
The
easiest
thing
should
not
be
to
go:
install
all
10
000
packages
of
rail.
B
The
easiest
thing
should
be
to
use
tools
like
image
builder,
which
is
an
online
service
that
we've
got,
and
also
an
on-premise
application,
using
tools
like
image
builder,
to
let
people
compose
an
operating
system
that
they
need
for
that
specific
workload
on
that
specific
provider.
So
I
should
be
able
to
say
I'm
going
to
do
xyz
on
my
system.
B
I
need
dust
and
such
packages,
and
it
goes
here
on
amazon
or
goes
here
on
azure
and
so
making
integrating
the
deployment
of
an
operating
system
or
kind
of
a
gold
image
into
the
cloud
and
just
making
that
kind
of
a
natural,
a
natural
thing.
That's
that's
pretty
important
to
us
now
in
a
way
that
it
wasn't
before
yeah.
I
think
so.
It's
the
cloud
is
it
on
the
surface.
B
It
feels
extremely
different,
but
it
turns
out
that
a
lot
of
the
optimizations
and
a
lot
of
the
things
that
we're
doing
to
make
the
cloud
easier
easier
to
use
perform
better.
These
are
all
these
all
have
dividends
for
the
on-premise
work
as
well.
It
turns
out
that
it's
actually
not
so
different.
After
all,.
A
B
B
B
Right,
yeah,
and
so
so,
some
of
the,
but
some
of
the
things
are
the
same
right.
All
that
simplicity,
that
consistency
across
the
platforms
that
becomes
really
important.
The
way
that
you
manage
the
application
becomes
very
different
because,
like
in
the
iss,
if
you,
if
you're
gonna,
go
to
a
system
update
it
better
work
and
if
it
doesn't
work,
you
better
have
a
way
of
of
coming
back
and
recovering,
and
that's
true,
whether
in
a
space
station
or
you're
on
a
telephone
pole.
And
so
so.
B
Some
of
the
investments
that
we're
making
on
on
the
edge
is
yes
expanding
the
kind
of
hardware
that
we're
going
to
support
with
rel,
but
also
giving
people
the
tools
they
need
in
order
to
manage
both
their
linux
hosts
and
the
applications
that
are
right
on
top
and
do
so
in
a
kind
of
a
way
that
is
natural
for
the
for
the
edge
deployments.
And
so
you
using
technology
that
we
got
from
coreos
right,
which
you
mentioned
earlier.
B
So
we
have
to
make
concessions
for
that.
But
again,
just
like.
I
talked
about
for
public
cloud
all
this
stuff
that
I'm
talking
about
doing
for
the
edge.
I
have
every
expectation
that
people
are
going
to
be
able
to
take
advantage
of
all
this
back
in
their
own
data
centers
and
in
the
public
cloud
right,
because
people
care
about
bandwidth,
people,
care
about
latency
people,
care
about
atomic
updates
people
care
about
being
able
to
roll
back.
A
Yeah
and
gonna
retention
there's
a
note
that
came
in
the
chat
that
I'm
sure
you
can
speak
to,
because
it's
not
only
in
the
public
cloud,
but
even
in
the
data
center
oftentimes
the
default
is
well
there's
a
free
option
out
there.
I
know
if
I
go
build
an
ami.
You
know
in
amazon.
You
know
that
amazon
linux
looks
good
ubuntu's
there.
You
know,
I
I
need
to
scroll
down
a
little
bit
and
say:
oh
wait.
I
need
to
pay
for
this
rel.
So
I
usually
see
it
is
more
of
an
and
story.
B
A
Use
free
stuff
and
there's
there,
so
maybe
you
can
speak
to
how
how
customers
see
that
and
how
they
you
know
when
are
they
like
yeah?
No,
I
I
I
know
red
hat.
I
trust
red
hat.
You
know
those
sorts
of
the
utah.
We
talked
about
the
enterprise
life
cycle
before
so
they're.
All
things
that
pay
into
the
you
know
free
versus
paid
yeah.
B
No,
no
free
operating
systems
are
great.
We
have
several
of
them
inside
red
hat
right,
it's
the
and
there
is
no.
I
don't
see
it
as
a
as
a
as
a
tension
between
the
free
and
the
paid
it
is
like
you
said
it's
just
like.
There
are
different
use
cases.
People
need
different
stuff
if
you
need
to
take
an
application,
deploy
it
on
an
extremely
predictable
environment
and
have
it
behave
basically
the
same
for
like
13
15
years,
then
you
probably
need
a
paid
operating
system.
B
If
you
have
an
operating
system
where
you
have
an
application,
that's
constantly
changing
and
constantly
churning,
and
you
know,
you're
not
going
to
need
help
with
anything
and
you
don't
particularly
care
about
security,
and
you
don't
particularly
care
about
your
ecosystem
or
hardware
partner,
vendor
or
hardware
software
partners.
Cool
you
can
get,
you
know,
go
using
a
free
operating
system.
That's
fine!
The
free
operating
systems
play
an
important
role
in
the
ecosystem
and
they're
part
of
the
success
of
linux.
B
Overall
right,
just
like
the
paid
operating,
the
paid
linuxes
also
fulfill
an
important
role
in
the
ecosystem,
and
I
would
argue
that
one
cannot
exist
without
the
other,
like
all
of
us
are,
are
working
on.
You
know
we're
competing
in
the
market.
Things
like
this,
but
in
terms
of
the
linux
project,
overall,
of
making
all
of
this
technology
as
available
as
possible.
All
of
us
are
playing
an
important
role
in
that.
A
B
B
So,
for
me
he's
for
me
he
was
going
to
experience
it
in
the
same
order.
I
did
so
it's
going
to
be
it's
going
to
be
new
hope
right.
So
we
started,
we
started
four.
I
watched
the
first
10
minutes
of
normal
and
I
don't
remember
being
that
violent.
I
was
like
I
was
like
you
got
darth
vader,
throwing
people
all
over
the
place.
I
was
like.
I
don't
remember
this.
I
saw
this
when
I
was
three.
How
could
it
be
anyway?
A
Yeah,
I
I
dove
right
in.
I
did
it
the
same
way
I
watched
it.
I
had
my
kids.
We
watched
the
original
trilogy,
then
the
prequels-
and
you
know
they
were
old
enough
to
see
the
sequels
and
they
came
out
awesome.
So
hey
tomorrow,
congratulations,
20th
anniversary
of
rel,
that's
super
exciting
and
we
at
red
hat
next
week
have
summit,
so
you
and
I
will
both
be
in
boston,
any
any
quick,
shout
outs.
You
want
people
to.
B
Yeah,
obviously
so,
first
of
all,
the
onstage,
the
demos
are
always
a
fireworks
event.
Those
are
always
I'm
always
I'm
always
delighted
by
those
I'm
doing
a
session
on
the
future
of
the
operating
system
or
I'm
gonna
go
deeper
on
some
of
the
things
that
we
talked
about
today,
but
really
make
yourself
available
for
all
the
content
I
mean
there
is,
I
think,
there's
something
like
30
sessions
on
rel
and
all
that's
different,
all
those
different
flavors
and
aspects.
So
please
enjoy
a
an
avalanche
of
rail
information.
A
Yeah
and
and
for
those
that
aren't
coming
to
boston,
which
it
is
a
pretty
small
event,
if
you
just
go
to
redhat.com
summit,
you
can
still
sign
up
for
the
virtual
lots.
You
know
you've
got
access
to
all
the
content,
it's
free
to
register,
and
you
know
please
reach
out
to
us.
If
you
have
any
questions
so
all
right,
I
was
just
looking
to
see
if
there
are
any
questions
right
shantanu,
I
understand
you
know,
maybe
the
sequels.
A
We
shall
not
refer
to
them
as
there
I
was
just
seeing
if
there
was
any
other
specific
questions.
Yeah,
you
know
it's
there's
one
here
a
question
I'd
have
is
how
do
you
define
the
the
value
of
red
hat
subscriptions?
Let
me
put
it
up
on
the
screen
there,
for
you,
you
know,
is
it
relationship?
Is
it
maintenance?
Is
it
something
else?
I
I
guess
a
good
final
question
to
kind
of
you
know
why
rel
in
2022.
A
B
So
this
okay,
so
let
me
see
if
this
is
my
this
is
this-
should
be
rifle
training
for
me
and
everybody
that
works
for
me.
So,
let's
see
how
well
I
do
okay,
so
the
ultimate
the
value
of
the
value
of
rel
is
specifically
a
lot
of
people.
Think
about
it
as
okay.
It's
a
it's
a
hardened
set
of
bits
and
it's
a
phone
number
that
you
can
call,
and
that's
true.
That
is
certainly
that's
kind
of
that
may
be
the
core
of
the
subscription
value.
B
One
part
of
the
subscription
value,
though,
is,
is
the
extensive
relationship
we
have
with
other
partners
other
organizations
in
order
to
number
one
make
sure
that
security
vulnerabilities
are
fixed
promptly.
That
requires,
if
you
are
relying
simply
on
the
upstream
communities,
to
fix
your
security
problems.
What
you're
doing
is
forcing
yourself
to
upgrade
to
the
latest
version
in
order
to
follow
thing,
and
that
may
come
with
new
bugs
and
new
features
that
you
were
not
planning
on,
and
so
what?
B
One
of
the
things
that
you
get
with
a
rail
subscription
is
the
ability
to
separate
these
two
things,
so
you
can
have
security
fixes
without
being
forced
to
to
upgrade
right.
So
that's
that's
pretty
important
if
you're
interested
in
stability
and
not
being
surprised,
part
of
those
relationships
also
is
the
relations
we
have
with
the
hardware
and
the
software
vendors
to
ensure
that
new
hardware
that's
coming
out
can
be
supported
alongside
all
the
hardware
that
you've
already
got
to
ensure
that
your
application,
it
remains
stable
for
a
very
long
time.
B
B
B
Coming
up
coming
up
soon,
you're
going
to
see
us
adding
things
like
malware
detection,
you're
going
to
see
us
adding
things
like
cost
management
tools
to
help
you
kind
of
like
right
size,
your
your
public
cloud
spending.
All
these
tools
exist
in
console.redhat.com.
So
when
you
have
a
subscription,
you
have
a
red
hat.
Robot,
that's
gonna!
Be
there
to
tell
you
like
hey,
you
might
have
this
thing,
misconfigured
or
hey!
You
think
you
might
have
these
vulnerabilities
that
you
haven't
looked
at
having
those
kinds
of
coaching
or
advisory
opportunities.
B
A
A
If
you
have
topics
guests
that
you
think
we
should
be
watching,
you
know
feel
free
to
reach
out
I'm
just
at
stu
on
twitter,
I'm
stu
at
redhat.com
for
the
email
gunner
thanks
so
much
for
for
joining
us
and
you
know
be
sure
to
tune
in
next
week
for
red
hat
summit.
You
know,
live
and
virtually
from
boston.
So
until
next
time,
thank
you
for
joining
us
on
your
journey
in
the
clouds.