►
Description
A show that features the people and technology that make Red Hat® Enterprise Linux® into the world’s leading enterprise Linux platform.
A
Good
morning,
good
afternoon
good
evening
and
welcome
to
another
episode
of
red
hat
enterprise,
linux
presents
I'm
chris
short
executive
producer
of
open
shift
tv,
and
I
would
like
to
hand
it
off
to
the
one
and
only
rel
experienced
person
to
the
stars,
scott
mcbryan,
who
actually
is
supporting
the
red
hat
enterprises
on
next
label.
Today,.
B
Thanks
thanks
a
lot
chris,
so
today,
we're
joined
by
two
guests.
First
is
terry
bowling,
who
is
the
senior
product
manager
for
rail,
upgrade
migration
and
management
experiences
and
I'll
give
him
a
second
in
a
minute
to
well
that
was
misnomer
I'll.
Give
him
a
minute
in
just
a
moment
to
introduce
himself
and
also
with
us
today
is
jerome
young,
who
is
a
senior
architect
for
red
hat
consulting
and
today
we're
going
to
be
talking
about
migrating
from
one
linux,
to
red
hat
enterprise,
linux
or
other
linux's
to
red
hat
enterprise
linux.
B
So,
let's
start
with
terry
and
then
we'll
move
on
to
jerome
and
just
do
a
little
bit
of
introductions
about
yourself
and
and
what
you
do.
C
Sure
thanks
scott
yeah,
so
I've
been
with
red
hat
gosh
how
many
years
going
on
nine.
I
think
so.
I'm
in
the
rel
product
management
team
focused
on
a
variety
of
things,
including
installations,
migrations
in
place
upgrades
as
well
as
other
management
experiences.
So
I
was
a
sis
admin
for
many
years.
C
So
when
I
talk
to
other
sis
admins,
I
feel
like
I'm
with
my
people
and
I
feel
like
I
really
relate
to
those
people
and
the
types
of
work
that
they
have
to
do
and
the
kind
of
problems
that
they
run
into
and
their
challenges.
So
usually,
when
I
I
talk
to
those
types
of
customers
and
those
types
of
people,
I
I
feel
like.
I
can
really
feel
and
own
their
issues
that
they
experience
thanks.
D
Good
good,
I
guess
I'll
give
my
little
intro,
I'm
jerome
young,
I'm
an
architect
with
red
hat.
I've
been
here
for
about
nine
years
as
terry
as
just
about
as
long
as
terry
has,
and
I
actually
work
a
lot
with
customers
actually
to
do.
Architecture,
planning
and
even
implementation
of
you
know
either
moving
from
a
another
linux
or
even
upgrading
linux
at
scale.
So,
if
you're
in
a
large
enterprise,
how
do
you
do
that
in
a
very
large
way?
Actually
take
some
planning?
D
And
you
know
some
execution
so
been
through
a
lot
of
a
lot
of
things
with
customers
and
can
talk
to
a
lot
of
experiences
out
there
in
the
field.
B
I'm
excited
to
have
you
both
today,
so
we're
talking
about
converting
from
other
linuxes
to
red
hat
enterprise
linux.
So
what
are
the
reasons
that
you
guys
see
people
converting
from
other
linuxes
to
red
hat
enterprise,
linux.
D
That's
good
yeah.
I
could
definitely
go
first.
I
think
one
of
the
key
reasons
is
definitely
support
being
one
of
the
key
reasons
for
a
lot
of
larger
enterprise
customers,
but
also
having
expertise
there.
While
you
you,
sometimes
you're,
running
the
free
linux,
and
that's
that's
great
well,
you
can
save
sometimes
you're
running
a
version
of
linux
and
you
don't
have
the
support
there
to
actually
get
you
over
problems
when
they
happen.
D
So,
if
you're
writing
something,
especially
that's
business,
critical
that
problem
could
actually
cost
you
serious
money
or
serious
downtime,
where
a
lot
of
folks
have
a
mindset
when
they're
at
home,
something
goes
down
at
home.
It
causes
some
inconvenience,
but
when
you
run
out
of
business
that
definitely
causes
a
real
problem.
So
I
think
support
is
definitely
the
big
reason
why
folks
move
to
red
hat.
C
Yeah
and
I'll
add
to
that
jerome
we
have
a
lot
of
customers
that
find
themselves
in
a
situation
where
they
themselves
are
a
business
and
they
have
their
own
customers
and
they
have
to
answer
to
their
own
customers,
so
they
have
to
answer
to
their
their
customers
regarding
things
like
security
supply
chain
and
especially
when
those
customers
have
their
own
end,
customers,
where
they're,
maybe
managing
customer
data
customer
personal
information,
this
whole
concept
of
a
secure
supply
chain
and
a
known
provenance
of
origin.
Where
did
these
open
source
bits
come?
How
were
they
built?
C
Are
there
any
points
in
the
process
along
the
way
where
a
malicious
person
could
insert
something
bad
and
with
recent
security
concerns
in
the
public
media
today?
That
is
a
growing
topic,
so
we
have
a
lot
of
customers
coming
to
us
and
say:
look
we
built
our
business
around
centos.
It's
been
great,
however,
to
get
this
next
customer
account,
they
are
requiring
us
to
maybe
have
government
certifications
like
the
system
must
be
run
in
fips
mode.
C
You
know,
there's
still
some
things
that
don't
quite
pass
the
muster
when
you're,
maybe
trying
to
land
a
big
government
contract
or
something
like
that
where
they,
they
simply
have
strict
requirements
that
they
must
adhere
to.
So
as
wonderful
as
the
open
source
community
is
there's
certain
business
problems
that
you
know
you.
It
just
requires
a
business
investing
in
the
people
to
follow
the
process
and
make
that
happen.
So
that's
another
real
value
that
we're
hearing
from
customers
is.
They
simply
have
to
convert
to
something
that
meets
those
security
requirements.
B
And
perry
just
to
follow
up
on
that.
You
said
that
especially
public
sector
folks
certifications.
Just
this
week
we
achieved
both
crowning
criteria
and
fips
140-2
for
rel
8.1
and
so
rebuilds
like
centos.
C
Even
though
it
might
be
built
from
the
same
source
code
or
close
to
the
same
source
code,
those
certifications
it's
about
a
process,
it's
about
a
build
pipeline
and
knowing
that
you
can
control
and
lock
down
access
to
that.
And
when
you
have
a
open
public
community,
it's
really
hard
for
those
same
public
communities
to
achieve
that
same
level
of
control
and
and
quite
honestly,
it
requires
money.
Investing
in
the
certification
process,
which
is
quite
expensive.
C
So
red
hat
spends
a
lot
of
money
with
third-party
certification
organizations
to
validate
that
and
there's
just
a
lot
to
it
that
centos
and
I'm
not
aware
of
any
other
any
other
linux
distribution
that
has
managed
to
obtain
these
certifications
without
some
type
of
enterprise
company
behind
it.
B
C
Great
question
so
currently
the
the
tooling
that
we
have
been
working
on.
We
call
it
convert
tyrell
and
it
focuses
on
those
rel
derivative
distributions,
so
those
would
include
distros
like
centos
or
centos,
depending
on
your
preference
of
pronunciation,
so
centos
oracle.
Linux
is
also
a
derivative.
C
Scientific
linux
would
be
one,
but
they
transition
to
centos
or
centos
proper
a
couple
of
years
ago.
I
believe
so
those
are
pretty
much
the
distributions
we're
looking
at,
so
it
doesn't
really
apply
to
even
fedora,
because
that's
a
little
bit
too
forward
thinking.
So,
even
though
it's
it's
part
of
the
same
ecosystem
family,
it's
a
little
bit
too
far
upstream
or
upriver
for
the
the
tooling
to
effectively
convert
to
rel.
So
I
think
I
covered
everything.
Did
I
miss
anything?
Jerome?
No,.
B
And
are
there
any
specific
versions
that
are
supported
in
versions
that
are
not
supported.
C
Yeah,
the
tooling
that
we're
focused
on
right
now
is
primarily
focused
on
converting
centos,
seven
and
eight
to
rel,
eight
red
hat
enterprise,
linux,
a
and
so
seven
and
eight
the
tooling
actually
works
with
six
and
we've
had
a
lot
of
success
with
that,
especially
with
our
consulting
agency.
They've
they've
been
the
ones
working
with
customers
the
most
with
it
I'll.
Let
jerome
comment
on
that
in
a
moment,
but
we're
we're
we're
considering
we're
thinking
about.
C
What's,
in
the
best
interest
of
our
customers
and
helping
customers
convert
centos
6
to
row
6,
given
that
it's
that
end
of
life
cycle
it,
it
raises
a
lot
of
questions
of.
Is
this
the
best
behavior
that
we
should
be
doing
so
we're
kind
of
treating
that
as
a
support,
exception
scenario.
So
we're
not
planning
on
that
being
broadly
supported,
the
tooling
in
the
community
works.
C
If
you
have
a
simple
centos
6,
it
will
convert
it
to
rel
six,
but
it's
it's
very
basic
and
minimal
and
we're
not
necessarily
recommending
that
unless
you're
also
planning
on
doing
a
rel
six
to
rel7
upgrade
because
getting
yourself
to
a
supportable
found
platform
that
has
a
life
cycle
remaining
where
you're
getting
security
you're
at
it,
that's
really
the
best
recommended
practice.
So
that's
what
we're
focused
on
so
really
centos,
six
since
or
centos
seven
and
eight
to
rel7
and
eight
jerome.
Do
you
want
to
mention
anything
about.
D
Yes,
I'd
say
definitely
trying
to
get
folks
onto
a
supported
platform
is
really
kind
of
the
key,
and
so
since
rel
six
is
now
end
of
life.
For
the
most
part,
it's
also
comes
with
its
own
challenges,
because
well,
six
has
some
age
behind
it,
and
so
you
know
working
on
the
consulting
side.
What
we've
seen
there
are
some
old
either
cis
admin
things
that
have
been
done.
D
That
can
cause
some
things
to
not
miss
a
not
work,
but
we've
found
ways
around
them
to
kind
of
make
that
work,
but
it
does
take
some
work
at
times
to
get
that
going
because
you
have
these
unexpected
challenges
just
because
of
the
age
of
rel,
six
and
oftentimes.
These
systems
have
been
around
for
a
very
long
time
and
changed
many
hands.
B
D
The
oracle
linux
is
one
and
centos.
Those
are
the
main
two
we've
seen
centos.
You
know.
Seven
is
a
big
one
and
oracle
linux
before
six
and
seven
are
the
big
two
right
now
that
we're
seeing.
B
Awesome
and
in
the
towards
the
end
of
the
the
show
today
we're
gonna
convert
a
centos
linux,
eight
box
to
a
relate
box
and
it's
a
you
know:
10
commands
or
something
you
got
to
put
some
stuff
into
place,
and
so
it's
possible
to
do
a
your
your
own
conversion.
B
But
what
kind
of
scale
do
you
see?
People
converting
jerome,
yeah.
D
So
usually
it's
it
can
go.
You
know
from
a
handful
of
systems,
basically
usually
critical
systems
that
either
folks
don't
have
the
ability
to
re.
You
know
reset
up
like
it's
been
configured
and
nobody
really
knows
how
to
reconfigure
them
or
it
can
go
to
thousands
of
systems
where
something
like
a
hadoop
cluster,
for
instance.
If
those
are
on
centos,
that's
something
you
would
convert,
but
also
hey.
All
of
our
footprint
has
just
been
a
centos,
and
now
we
want
to
convert
them
to
a
supported
platform.
D
B
And
I
know
that
we're
going
to
talk
in
a
bit
about
kind
of
best
practices
and
things
like
that
yeah,
I'm
sure
I
will
have
questions
there
about
like
testing
and
do
you
do
it
in
phases,
and
so
I
I
will
ask
you,
those
at
the
appropriate
timeout.
C
Okay,
so
the
way
it
works
is
we
have
this
utility
called
convert
tyrell
and
it's
it's.
It's
still
in
a
quasi-supported
state.
It's
it
was
developed
in
partnership
with
consulting
and
engineering,
and
so
we're
still
in
the
process
of
making
it
a
final,
broadly
supported
utility.
But
it
is
accessible
to
anyone
today
and
we're
very,
very
close
to
declaring
criteria
on
support
and
so
that
we
can
simply
say
it's
supported,
go
ahead
and
use
it
we'll
support
the
results
and
so
the
way
the
utility
works.
C
Is
you
download
this
utility
and
when
you
run
it,
you
provide
it
as
certain
parameters.
It's
it's
going
to
want,
ideally
a
subscription.
C
We
can
talk
about
those
offerings
in
a
moment,
but
the
best
way
that
the
tool
runs
is
when
it
can
access
red
hat
to
download
the
latest
versions
of
packages,
because
you're
always
better
to
go
and
upgrade
where
the
packages
need
to
update
themselves
rather
than
a
package
downgrade,
and
I
can
talk
more
details
about
that
in
a
moment
as
well.
But
so
you
provide
your
credentials
or
not
authentication
key
but
registration
key
and
so
that
it
can
access
your
subscription
and
it
examines
your
system
there's
a
few
files.
C
It
needs
to
to
change
and
manipulate
because
we
have
oh
gosh.
I
am
drawing
a
blank
today:
the
pim
files,
the
the
authentic
certificates.
C
C
You
know
validate
themselves
with
the
signing
key
and
everything,
and
so
it's
going
to
examine
the
packages
on
the
system
make
a
few
changes
around
red
hat
subscription
manager,
the
red
hat,
release
files.
Things
like
that,
and
it's
going
to
examine
your
your
your
repositories
and
look
for
like
any
repos
that
you
might
have
configured
that
we
have
concerns
about
like
might
cause
you
problems
or
possibly
disable
some.
C
It's
going
to
make
sure
that
the
newer
red
hat
repos
are
configured
and
then
it's
literally
kind
of
like
a
patching
cycle
takes
about
the
same
amount
of
time.
So
it's
very
similar
to
you
know
doing
a
young
update
to
update
to
a
minor
release
where
it's
going
to
replace
every
package
on
the
system
and
it
literally
just
downloads
all
the
packages
and
and
then
does
the
basically
like
a
package.
Reinstall
there's
a
few
other
things
under
the
hood
that
it
does.
B
Okay,
so
jeroen
there's
an
old
adage
that
if
you
fail
to
plan
you
plan
to
fail,
so
if
somebody
is
considering
doing
a
conversion,
what
type
of
stuff
should
they
be
prepping
in
advance
of
that
before
they
actually
execute
on
it.
D
So,
let's
try
in
our
dev
environment
to
test
this
out,
build
the
workflows
and
then
go
to
production
and
then,
as
we
all
know,
everything
in
production
does
not
look
exactly
like
dev,
but
one
key,
mitigating
piece.
There
is
actually
having
some
type
of
backup
either
a
vmware
snapshot
if
it's
vmware
or
any
virtualization
snapshot
really
or
using
a
tool
like
boom.
If
it's
a
physical
machine,
so
you
can
actually
restore
the
machine
if
possible.
D
If
things
do
go
wrong,
but
I
think
that's
kind
of
the
key
thing,
but
really
kind
of
following
a
process
of
starting
in
dev
testing
it
out,
building
your
workflows
there
and
then
basically
strategizing
how
you're
going
to
build
in
production
and,
of
course,
having
that
backup.
As
part
of
that
workflow,
I
think,
is
the
key.
There.
B
Okay
and
when
they,
when
you're
preparing,
do
you
need
to
do
anything
like
build
out
what
packages
you
have
installed
or
third-party
packages
that
might
be
there
like
when
you're
doing
that,
prep
work?
What
are
the
things
you
need
to
be
keenly
aware
of.
D
Yeah
definitely
any
third
party
repositories
or
those
packages
and
making
sure
and
some
of
these
things
you'll
find
out
as
you're
kind
of
doing
things
in
dev
to
see.
If
some
of
these
third
parties,
the
packages
have
issues
or
are
not
even
the
version
that
ships
are
red
hat,
so
some
of
those
may
be
overwriting
versions
of
the
centos
package,
that's
there
and
then
addressing
those
issues
as
well
where
oftentimes,
especially
when
you're
in
the
centos
space.
Folks
really
just
aren't
thinking
about
it.
D
They'll
just
write
over
packages
that
centos
ships
and
not
think
much
about
it.
But
if
you're
going
to
go
to
the
supported
model,
you
want
to
make
sure
you're
using
the
packages
that
are
shipped
by
red
hat
for
those
packages.
B
Yeah
for
sure
I
worked
in
a
development
shop
for
a
while
and
one
of
the
guys
needed
to
get
a
an
updated
or
he
wanted
to
install
image
magic
on
a
box.
And
he
pulled
down
the
tar
archive
and
did
like
a
make,
make
install
yeah
yeah
and
it
like
overrode,
a
bunch
of
libraries
and
I'm
like.
E
D
Yeah
yeah
so
yeah
and
that's
kind
of
the
best
case
scenario
really
using
rpms,
but
just
kind
of
watching
out,
for
you
know,
like
that
scenario
there,
where
somebody
has
a
tar
and
it
just
writes
over
files
and
so
a
lot
of
times
you
can
kind
of
catch.
Those,
though
in
the
dev
process,
as
when
you
do
the
conversion
either
things
will
work
or
either
things
won't
work.
B
Yeah
and
I've
actually
been
looking
at
doing
an
article
for
the
enable
sysadmin
community
about
always
having
plan
b
right
because
there's
so
many
times
where
you're
like
troubleshooting
and
you're
like
editing
a
file
and
then
turns
out.
That's
not
the
thing,
but
now
you've
got
a
changed
file
and
you
can't
remember
what
changes
you
made
to
it,
because
you
didn't
account
for
that
in
your
plan
b.
So
your
your
plan
b
is
make
a
bootable,
backup
or
or
a
backup
that
can
restore
completely
the
state
of
the
system.
Exactly.
D
Guess,
that's
it
yeah
and
I'd
say
it's.
The
the
harder
piece
is
definitely
when
you're
dealing
with
physical
systems
versus
virtual
virtual
gives
you
that
kind
of
ease
on
the
end
just
have
to
worry
about.
Is
there
storage
for
it
where
physical,
if
it
does
mess
up,
there's
a
lot
more
pain
so
having
that
backup
is
very
critical.
B
And
if
I
was
scheduling
kind
of
a
maintenance
window
to
do
to
do
the
work,
you
know
terry
talked
about
how
it's
a
rather
quick
process,
but
while
the
process
itself
might
be
quick,
maybe
you
gotta
execute
that
back
out
plan
right.
So.
E
B
Type
of
of
maintenance
window
should
I
probably
look
at.
D
Yeah,
so
I
usually
try
to
say
always
make
your
maintenance
big
enough
for
the
worst
case
scenario.
So
you
know
for
a
system
mainly
like
maybe
two
to
three
hours,
even
though
you
will
probably
not
come
close
to
that.
If,
for
some
reason,
the
the
back
out
process,
you
may
even
take
some
time
the
physical
system
that
that
might
even
grow
a
bit
more
because
that
you
know
that's
going
to
be
a
case
by
case
and
that's
something.
We
would
have
more
of
a
good
idea
when
you're
doing
things
in
devs.
D
B
Awesome
yeah,
so
this
is
a
question
for
both
of
you.
What
are
some
kind
of
issues
that
you've
run
across
several
times,
or
particular
points
of
contention?
That
people
should
be
aware
of.
C
C
What
we
know
we
need
to
take
care
of
these
are
some
of
the
known
issues
that
I
want
to
make
sure
everyone's
aware
of,
and
I
don't
want
to
scare
anyone
off.
This
is
especially
the
the
conversation
that
just
took
place,
we're
being
ultra
conservative.
C
We
we
want
to
be
safe
with
our
customer
systems,
because
we
don't
want
to
see
anyone
in
a
bad
position,
so
I
don't
want
to
sound
all
doom
and
gloom,
but
at
the
same
time,
let's
do
our
due
diligence
and-
and
let's
be
careful
so
some
of
the
known
issues
that
we
have
is
the
tooling
currently
has
a
bug
dealing
with
uefi
hardware
systems.
So
it
works
great
with
bios
legacy.
Bios
type
systems
there's
an
own
bug
that
we're
working
on.
C
We
should
have
a
resolution
for
it
pretty
quickly,
but
the
breadth
of
testing
before
we
really
release
that
you
know
there's
a
lot
of
different
versions
of
uefi
different
hardware
platforms.
So
there's
a
lot
of
testing
to
cover.
So
that's,
why
might
seem
a
little
simple
to
fix?
But
when
you
think
about
all
the
testing
we
need
to
do
it
takes
us
a
little
bit
longer
before
we
have
that
confidence
level.
C
So
if
you
are
using
uefi
based
systems
hold
off
just
a
little
bit
longer
and
and
we'll
have
that
working
for
you.
We
already
talked
about
the
third-party
repository
content,
but
I'll
just
mention
that
again,
anytime
you're,
using
third-party
software,
red
hat,
does
not
necessarily
know
about
that
or
know
what
you're
using.
C
We
know
some
of
the
the
big
companies
netbackup
many
of
our
customers
are
using
some
of
the
other
symantec
prop
products,
and
you
know
oracle
databases,
but
you
know
there's
a
level
of
collaboration
that
has
to
happen
between
partners
and
we
can't
always
force
other
companies
to
test
and
evaluate
and
provide
guidance
to
their
customers.
So
we
can't
always
answer
every
question,
so
we
always
urge
customers
know
what
is
on
your
system,
which,
hopefully
you
already
do
if
you're
managing
your
environment.
Well,
our
best
run.
C
Customers
can
usually
tell
us
exactly
what
is
on
every
system.
So
that's
a
very
good
skill
to
develop
and
so
just
have
a
conversation
with
those
third
parties
and
make
sure
that
there's
no
compatibility
concerns
honestly.
We've
not
really
seen
any
third
party
compatibility
concerns
because
centos
did
a
really
good
job
of
at
least
being
binary
compatible
compatible
for
the
most
part.
So
we're
not
aware
of
any
known
issues,
we're
just
being
super
conservative
and
cautious.
C
C
Also,
we
commonly
see
this
with
network
and
storage
interfaces,
because
the
third
party,
maybe
malinox,
intel
hp,
you
name
it
any
of
the
big
oem
brands
they
might
have
like
their
latest
and
greatest
drivers
available
with
the
latest
functionality
that
hasn't
quite
landed
in
the
upstream
kernel
yet
or
flowed
into
the
rel
ecosystem.
Yet
it's
all
stuff
that
will
eventually
land
but
sometimes
there's
a
timing
mismatch,
and
so
sometimes
those
can
be
just
an
unknown.
C
C
I
think
it
is
so
basically
that's
a
source,
a
service
rather
that
you
run
on
your
system
and
it
uses
the
the
compiler
on
your
system
and
nvidia
has
done
this
for
many
years
where
they
they
basically
provide
the
source
code
for
a
shim
that
gets
basically
compiled
on
the
fly,
and
so
this
dkms
service
will
detect
that
oh
you're,
installing
a
new
kernel,
I
better
rebuild
this
shim
and
usually
it
does
a
great
job,
but
there's
a
risk
there,
because
it's
not
something
that
we
can.
C
You
know
if
you've
installed
a
different
version
of
the
gcc
compiler
or
using
some
other
third-party
c
compiler.
We
don't
know
that
we
don't
know
what
exact
combination,
so
there's
no
possible
way
for
us
to
to
know
or
tell
that.
So
our
recommendation
is
if
you're,
using
third-party
kernel
modules
or
the
latest
k
mods
from
a
vendor
or
if
you're,
using
dkms,
don't
use
this
tool.
C
That
system
may
not
be
a
good
candidate
for
conversion,
especially
if
you're
using
any
community
repos
like
I
know,
there's
a
community
zfs
kernel
module
for
centos,
and
that
would
be
a
great
example
of
there's
a
whole
lot
of
unknown
there.
It
might
work
it
might
not.
I
don't
know,
but
that's
not
something,
that's
supported.
So
that's
those
systems
wouldn't
be
good
candidates,
so
don't
use
this
tool
for
those.
C
We
are
looking
at
a
future
scoping
of
working
with
some
of
our
partners
like
nvidia,
intel,
melanox
and
others,
so
that
we
can
support
some
of
those
known
use
cases,
but
we're
just
not
there.
Yet
antivirus
is
another
unknown.
We
know
it.
Oftentimes
use,
30
third-party
k.
Mods
also
antivirus
has
this
unique
ability
to
identify
what
it
thinks
as
suspicious
activity,
and
so
we
have
concerns
of
what
it's
going
to
think
is
happening
if
it
sees
the
convert
to
rel
utility
taking
place.
C
So
that's
an
unknown
that
we
recommend
testing
that
on
a
system
first.
So
if
you're
using
antivirus
software,
I'm
not
saying
you
can't
proceed,
it's
just
we're,
not
testing
that
yet
so
we
encourage
you
to
test
it
thoroughly
and
evaluate
that
and
make
sure
that
it's
working
and
we'd
love
to
work
with
you,
if
you're
a
customer
or
community
user.
That's
going
to
test
that
we'd
love
to
talk
to
you
about
it
and
work
through
that
with
you,
because
any
findings
that
you
discover
in
your
own
testing.
C
We
plan
to
test
on
that
in
the
future.
So
if,
if
you're
already
doing
that,
we'd
love
to
take
that
information
and
then
incorporate
that
into
the
future
testing
when
we
do
get
around
to
it,
the
other
big
one
is
clustering.
If
you
have
a
system
that
is
clustered
it's
important
enough
to
need
high
availability
that
deserves
an
extra
step
of
caution
right,
because
you've
already
deemed
that
environment
very
important.
C
So
right
now
we
have
that
out
of
scope,
that
our
goal
is
simply
to
detect
clustering
is
in
place
and
have
the
utility
simply
stop.
So
we
don't
consider
those
as
good
systems
for
conversion
at
this
time.
It
might
be
something
that
we
can
look
at
more
in
the
future,
but
currently
our
recommendation
for
clusters
is
a
true
migration
to
other
systems
rather
than
in
place.
Conversion
yeah.
D
Oh
no
and
I
think,
actually
tara
kind
of
hit
on
on
most
of
the
points,
and
especially
with
the
the
kernel
module
pieces,
and
that's
where
I
was
talking
about
the
pre,
the
implementation
and
then
the
post
piece
of
like
the
workflow,
that's
something
that
would
become
part
of
the
post
piece
of
the
workflow
of
okay.
We've
done
the
conversion.
We
know
this
piece
needs
some
fixing
up
and
that's
what
becomes
part
of
that
is.
Okay.
Now
the
fix-up
process
for
the
nvidia
drivers,
for
instance.
B
E
B
Drivers
so
when
we
say
that
they're
not
supported
or
that
you
want
to
be
extra
cautious
about
them,
we're
recommending
that,
because
we
just
want
to
make
sure
that,
if
you're
using
them
that
you
they're
still
going
to
be
unsupported,
even
though
your
goal
of
coming
to
rel
may
be
to
gain
more
support
right.
C
Yeah-
and
a
lot
of
this
is
it's-
it's
wording
is
hard
right,
so
there's
some
of
this
stuff
where
it's
it
might
work
fine,
but
we're
not
testing
it.
Yet.
Therefore,
we
can't,
we
can't
really
say
it's
supported
because
we're
not
able
to
test
certain
scenarios
and
ultimately,
though,
the
way
this
works
is,
if
you
get
a
system
that
successfully
converts
to
rel,
that
system
will
be
supported.
C
C
It's
just
we're
not
able
to
test
all
these
things
use
caution.
If
your
system
breaks,
because
you
did
one
of
these
things,
we
guided
against
it's.
C
Going
to
affect
the
level
of
support
you
get
if
that
makes
sense,.
B
Right
so
like,
if
the
tool
stops,
because
it
sees
that
I
have
some
clustering
packages
installed,
and
I
do
something
super
horky
and
force
it
to
continue
anyway,
and
then
it
comes
up.
You
know
boots
after
the
conversion,
and
my
cluster
doesn't
work
anymore
or
my
database
doesn't
work
anymore.
That's
a
place
where
you
would
not
consider
it
a
fully
supported
system,
because
you
very
obviously
transgressed
against
the
the
guidance
that
we
are
providing
on
usage
in
the
tool.
C
Yeah
and
so
our
response
to
something
like
that
might
be,
you
know
simply
back,
you
know,
take
copies
of
your
cluster
configuration
uninstall,
the
cluster
software
reinstall
it
and
and
then
reapply
those
configurations.
That
would
probably
be
the
level
of
guidance
that
you
would
get.
C
So
it's
it's
not
like
you're,
going
to
be
totally
turned
away
and
left
defend
for
yourself.
But
there's
you
know
it's
it's
not
something
that
we
can
guarantee.
We
can
fix
an
existing
broken
system.
It
might
be
some
level
of
you
need
to
rebuild
this
environment
or
at
least
rebuild
part
of
it.
B
Right
and-
and
I
think
that's
the
other
point
I
wanted
to
make-
is
that
we're
disclosing
that
there
are
factors
of
risk
and
if
you
know
that
the
risk
exists,
you
can
determine
what
level
of
of
effort
you
want
to
put
against
mitigating
that
risk,
and
so,
if
the
thing
is
that
we
just
kind
of
give
up
and
we
restore
to
our
known
good
state
backup
there
you
go.
That's
that's
the
mitigation
of
said,
risk
good
and
then
terry.
We
talked
earlier
about
how
fedora
is
not
a
good
convert
real
candidate.
C
Sorry,
I
I
have
a
habit
of
always
muting
myself
yeah,
so
that
is
a
great
question,
scott,
so
cintos
stream.
We
are
not
currently
testing
that
we're
very,
very
interested.
We
want
to
see
centos
stream
be
as
successful
as
possible
and
we
want
to
enable
our
customers
to
use
centos
stream
and
when
needed,
convert
to
a
supported
platform.
There's
some
unknown
questions
there
right
now.
There's
I'm
gonna
go
a
little
bit
low
level
for
a
moment
and
so
bear
with
me.
C
But
when
you
install
rpm
packages,
one
of
the
things
it
does
is
it
runs
these
little
rpm
scriptlets
and
those
rpm
scriptlets
literally,
can
be
like
shell
scripts
or
even
python
scripts
that
are
embedded
in
the
package
and
those
scripts
are
not
item
potent
like
they
don't
check.
If
the
system
is
in
this
state.
So,
for
example,
a
known
rpm
scriptlet
problem
is
I'm
going
to
install
the
apache
web
server.
C
They
just
say:
do
something
and
there's
no
intelligence
to
know
that
that
account
already
exists,
so
don't
do
it
and
also
there's
no
reversing.
So
when
you
install
an
rpm
package,
usually
the
package
maintainer
will
provide
uninstall
scriptlets
to
undo
or
reverse
everything
that
was
already
done
in,
and
so
when
you,
when
you
upgrade
usually
open
source
packages
rpm
packages,
those
maintainers
are
always
thinking
to
the
future,
moving
forward
for
upgrades
and
very
rarely
do
they
think
of
the
opposite.
What
happens
if
I
need
to
downgrade
this
package?
C
So
we
already
have
a
known
issue
with
that
with.
If
you
want
to
do
an
rpm
downgrade
or
a
yum
downgrade,
that's
already
got
a
lot
of
known
issues.
Sometimes
it
works
beautifully,
but
we
have
known
issues
especially
any
time.
The
kernel
or
g-lib
c
is
involved.
Where
a
customer
might
say
you
know
what
I
just
upgraded
to
7.9
we're
experiencing
a
problem.
We
don't
know
if
it's
with
the
os
upgrade
or
if
it's
with
my
application
or
something
else,
we
need
to
do
a
root
cause
analysis.
C
So,
in
the
meantime,
we
need
to
revert
it
back
to
the
previous
state,
and
so,
if
they
upgraded
maybe
from
7.7
to
7.9,
maybe
they
skipped
a
minor
release
in
between
doing
that.
Downgrade
could
impose
problems
so
already
with
simple
straight
supported
raw
minor
releases.
We
do
not
recommend
doing
a
downgrade,
so
the
concern
with
centos
stream
is.
C
We
see
problems
and
we
decide
no
we're
going
to
remove
it
or
defer
it
to
later
or
or
something
I
don't
know,
and
so,
if
you
try
to
convert
a
centaur
stream
system
to
a
supported,
rel
miner
release,
we
don't
know
what
kind
of
rpm
downgrade
package
scenarios
we
might
run
into
again.
This
is
us
being
super
conservative
because
we
provide
enterprise
stable
linux.
That
means
we
don't
get
crazy.
Experimental,
fedora
and
cintastream
are
good
ecosystems
to
be
a
little
bit
more
and
experimental.
C
But
when
we
say
enterprise
linux
is
supported,
we
really
mean
it,
and
so
it's
not
that
we
want
to
discourage
innovation.
It's
we
need
to
make
sure
our
customers
is
safe,
are
safe
rather,
and-
and
so
that's
the
concern
there
with
centos
stream.
B
All
right-
and
I
saw
that
there
was
a
question
in
chat
about
rel
subscriptions,
so
I
would
say
that
if
you
so,
the
question
is,
if
I
don't
have
a
rel
subscription,
can
I
test
convert
to
rail,
particularly
with
vms?
B
I
would
suggest
that
maybe
the
developer
for
individual
subscription
might
be
a
good
match
to
that
use
case,
or
you
can
also
get
an
evaluation
subscription
where
you
get.
I
think
it's
30
or
90
days
of
a
rel
lives
if
you
want
to
use
it
for
evaluation
and
testing.
So
there
are
ways
that
you
can
get
a
a
rel
subscription
to
to
try
out
doing
this
conversion.
D
Yeah,
like
I
said
I'll,
add
to
that
you
can
also
use
a
custom
repositories
as
well,
so
you
don't
have
to
connect
through
rhsm
and
I
believe
we
have
in
our
link
on
how
to
do
that.
So,
if
you
do
need,
if
you
need
to
use
a
local
iso
or
get
rel
through
a
web
server,
we
have
some
instructions
and
our
knowledge-based
article
on
convert
to
rail.
That
spell
that
out.
B
Yeah
and
I'll
actually
be
using
an
iso
and
the
repos
on
the
iso
today
in
the
in
the
demo.
So
terry
you
one
last
thing.
One
like
you
know,
story
time
with
with
scott,
so
I
was
working
on
a
doing
applying,
updates
to
a
whole
bunch
of
systems
and
after
I
had
applied
updates
to
this
one
box
that
was
running
an
enterprise
database.
B
I
couldn't
get
the
enterprise
database
to
start
up
its
storage,
drivery
stuff
and
after,
like
just
thrashing
against
the
machine
troubleshooting
it
we
finally
got
it
back
up
and
working,
and
it
turns
out
that
the
cause
of
the
problem
was
in
short,
I'll
put
this
for
us
to
face.
In
the
channel
too
in
the
rpm
uninstall
scriptlet
there
was,
or
actually
it's
a
rpm
that's
remove.
B
There
was
an
rm
command
that
basically
said
rm
lib
modules
and
then
had
a
uniam-r
encapsulated
command
and
then
the
path
to
the
driver
that
had
been
built
against
that
kernel,
except
I
had
booted
into
the
newer
update
kernel
and
that
script
or
that
that
rpm
would
build
one
and
replace
it,
and
I
didn't
need
to
replace
anymore,
because
I
had
rebooted
the
machine
when
I
ran
the
rpm
command
to
remove
it.
B
C
B
Yeah,
and-
and
this
is
a
place
where
I
have
never
once
had-
someone
complain
to
me
that
we
finished
the
maintenance
earlier
than
the
maintenance
window
never
once,
but
this
was
a
situation
where
we
went
over
the
maintenance
window
and
there
was
much
anger
even
though
it
was
the
weekend
and
the
system
wasn't
actually
in
use.
But
there
was
anger
that
we
had
crossed
over
the
threshold
of
our
maintenance
window.
B
As
we
were
trying
to
diagnose,
troubleshoot
and
repair
this
box
that
that
had
gotten
medical,
so
yeah
it
happens.
Everybody
has
stories
all
right,
so
I'd
like
to
switch
gears
and
and
do
demonstration,
but
before
I
do
that,
I
want
to
give
both
terry
and
jerome
any
an
opportunity
to
have
any
last
parting
thoughts
before
I
switch
gears
and
they
make
fun
of
my
terrible
typing.
B
Oh,
and
so
what
I'm
going
to
be
using
is
the
short
I
think
you
already
pasted
it
in
the
chat,
the
I'll
grab
it
again,
red.
A
B
K
bass
article
on
how
to
execute
convert
to
rail,
so
I
will
just
be
using
that
as
my
guideline,
but
one
of
the
things
that
that
it
starts
off
with
is
excuse
me.
B
It
doesn't
tell
you
how
to
prepare
your
environment
to
to
ins,
to
get
access
to
the
rel
software.
So
first
thing
is:
I'm
just
going
to
go
ahead
and
install
this
convert
to
rail
rpm.
A
B
Okay,
so
here
we're
installing
off
of
github.
I
already
have
it
installed
in
the
box,
which
is
yay.
You
can
also
download
and
find
this
from
the
red
hat
knowledge
base
article
and
then
there's
a
short
link
that
that
takes
you
there,
I
think,
short,
has
already
posted
in
the
chat
as
well.
B
B
B
B
All
right
so
there
it
is,
there's
the
app
stream
directory,
which
should
go
with
the
rel8,
app
stream,
repo
that
I've
created
and
the
base
os
one.
So
I'm
just
gonna
real
quick.
Do
a
yum
recognized
if
I
wrote
correctly.
B
Yeah
so
there's
appstream
there's
base
os
and
I
think
we're
good
ish.
B
B
B
Well,
this
the
box,
that
is
my
hypervisor,
has
been
a
little
bit
squidgy
of
late.
B
Rail
eight
f
string,
and
I
did
I
see
that
yeah
and
I
want
to
enable
extra
verbose
logging
as
I'm
doing
this.
So
let
me
just.
B
B
So
I
can
get
it
back
right
because
I
always
have
a
backup
plan
and
so
we're
going
to
go
ahead
and
say
yes
and
it's
going
to
basically
verify
all
the
packages
that
I
have
you
see
it's
calling
the
command
rpm
va
there
and
what
it's
looking
for
is
packages
where
I
may
have
changed
configuration
files,
or
maybe
there
are
files
that
have
changed.
That
would
actually
be
something
that
would
detect
the
situation
jerome
mentioned
earlier,
where
somebody
has
overwritten
the
libraries
or
something
with
oh,
oh.
B
B
B
All
right
well,
so
it
was
on
its
way
to
converting
it.
Does
the
rpm
va
and
then
it
figures
out
what
packages
it
needs
to
replace
and
then
stops
and
goes
okay,
we're
about
to
we're
about
to
cross
the
threshold
of
un
unmangling.
You
can't
you
can't
go.
E
B
And
we'll
ask
if
you
want
to
do
it
and
if
you
say
yes,
then
it'll
start
downgrading
or
replacing
the
command.
The
rpms
with
the
new
ones
and.
A
B
A
A
B
A
B
C
So
this
is
this:
is
the
rail
web
console
which
I'm
a
super
big
fan
of?
I
have
this
running
on
my
my
hypervisor,
which
is
actually
a
roll
7
hypervisor,
because
I've
not
yet
gotten
around
to
upgrading
it
actually.
C
I
need
to
just
buy
a
new
box
and
spend
some
money
and
then
do
a
nice
clean
rail
8
on
it.
So
anyway,
I'll
go
into
virtual
machines.
Here's
my
little
virtual
machine
that
I
use
for
centos,
torel,
8.3,
so
I'll
go
ahead
and
run
that.
C
And
while
it's
starting
up-
and
so,
oh
goodness
so
I
had
to
search
my
history,
so
here's
a
little
playbook
that
I
was
testing,
and
so
the
first
thing
I
do
is
I
validate.
Is
this
really
centos
or
oracle
linux?
And
then
I
check?
C
Is
it
the
latest
version,
because
I'm
still
of
the
mine,
let's
make
sure
I'm
starting
from
the
latest
version
possible,
because
I
don't
want
to
combine
a
conversion
with
a
minor
release
all
at
the
same
time,
let's,
let's
like
separate
that
out
so
I'll,
just
update
to
the
latest
centos
first
and
then
I'll.
Do
the
conversion?
C
So
it's
actually
pulling
packages
over
the
internet
because
I'm
also
of
the
mine-
and
we
might
make
this
a
support
criteria
as
well,
if
you're
installing
against,
if,
if
you're
going
to
convert
using
the
dvd
iso,
which
doesn't
get
updated,
but
yet
the
system
is
using
the
latest
errata
updates
pulled
over
the
internet.
You
potentially
face
another
package
downgrade,
so
I
don't
like
using
the
dvd
unless
I'm
going
to
convert
like
a
7.8
system
to
wait.
What's
my
numbering
7.8
to
7.9,
so
that
I
know
I'm
getting,
the
migration
is
using
the
latest
packages.
C
I
don't
like
package
downgrades
anyway,
so
that's
that's
what
I'm
doing
here,
but
I'll
copy
and
paste
the
commands,
because
you
don't
get
to
see
it
run,
I'm
using
the
auto
answer
flag.
So
you
don't
get
all
this
to
see
all
the
commands
around
that
scott
was
pointing
to
so.
Let's
see,
can
I
log
in
now?
Yes,
I
am
in
so.
A
A
C
C
A
C
A
You
know
what
we
had
like,
I
said,
or
earlier
we
had
a
wonderful
little
level
up
hour
this
morning,
where.
C
B
So
this
is
the
the
point
of
no
return
right.
So
when
we
answer
yes
to
this
question,
we're
actually
going
to
start
swapping
the
packages
out.
So
if
your
box
dies
unexpectedly
at
this
point
where
it's
swapping
packages
out
you'll,
not
know
what
state
it's
in
or
if
it
has
some
kind
of
wonky
error
during
this
stage
that
can
cause
you
an
uncertain
state.
So
that's
here's
your
last
chance
to
back
out
of
this
process
before
moving
forward.
C
Tells
you
this
is
the
point
of
no
return,
and
it's
not
saying
that
yet,
but.
C
We
are
we're
talking
probably
weeks.
We
will
be
providing
a
signed
version
of
this
package
from
an
official
redhat.com
download
page,
so
that.
C
It
from
github
cool,
so
basically
it's
identifying
some
pot
packages
that
will
be
excluded.
C
B
So
yes,
and
no-
and
this
is
one
of
the
bug
still
arguments-
I've
been
having
one
of
the
devs
on
the
team,
so
it
actually
downloads
some
things
like
the
centos
release
package
and
scrolls
it
away
somewhere
and
there's
like
three
or
four
other
things
that
go
along
with
that.
B
C
Yes,
which
screen
do
you
see
right
now.
B
C
C
B
No,
it's
not,
but
I
I
am
now
late
for
a
meeting
that
got
dropped
on
my
schedule.
Five
minutes
ago,
oh.
A
B
A
C
C
C
C
C
C
C
B
E
A
B
And
just
one
note,
terry:
one
of
the
reasons
why
we
want
to
use
subscription
manager
is
because
I'm
guessing
this
is
a
rel
or
a
centos
83
box,
and
if
you've
been
updating
it
and
then
you
can
you
add
the
iso
for
convert
to
rel
to
use
your
centos
linux.
83
box
is
further
ahead
than
the
iso
that
was
initially
released
with
83
right,
you've,
applied,
updates
and
other
stuff,
and
so
that's
where
you're,
in
the
situation,
where
you'd
have
to
downgrade
a
bunch
of
packages.
C
E
C
Of
using
a
subscription
that
I'll
show
you
once
it
starts
doing,
its
thing
is
included
with
the
individual
developer
subscription.
Here's
we
go.
B
But
prior
to
that,
it's
it's
talking
about
the
packages
being
removed,
that's
where
it
scrolls
them
away
in
this
other
location.
So
if
you
say
no,
you
still
have
to
kind
of
un
undo
some
things
to
get
it
back
to
right
to
rightness.
C
B
A
C
So
it's
really
cool
insights.
Red
hat
insights
comes
with
free
developer
subscription,
so
another
benefit
to
this,
especially
for
your
home
lab.
The
individual
developer
subscription
is
good
for
up
to
16
instances.
That's
a
pretty
awesome
home
lab.
I
don't
have
that
many
devices
in
my
office
that
in
my
home
lab
that
can
use
all
of
these
up,
and
let's
see
I
forget
where
it
is,
I
want
to
go.
Wait,
that's
another
site.
Isn't
it
is
it
insights,
cloud,
dot,
red
hat.
C
So
I'm
going
to
go
to
the
insights
dashboard
and
we
see
all
of
these
cool
things,
so
I'm
going
to
go
to
inventory
first,
oh,
I
haven't
registered
it
to
insights.
I
need
to
wait
on
it
to
finish
so.
I'd
have
to
actually
type
in
the
command
insights
client
register
before
it
shows
up,
but
it
would
eventually
show
up-
and
I
would
see
it
here,
so
I
don't
have
anything
yet
subscription
watch.
C
Basically,
you
can
see
a
nice
inventory
of
all
the
subscriptions
that
you
have
in
use
so
yeah.
I
guess
this
isn't
telling
us
a
whole
lot
yet,
but
once
I
register
this
system
to
insights,
I'm
going
to
get
all
of
these
cool
tools
advisor
vulnerability.
You
know
if
there's
another
name,
brand
security
vulnerability
that
is
circulating.
The
media,
like
I'm,
going
to
be
able
to
see
which
of
my
systems
are
vulnerable,
I'm
going
to
be
able
to
download
remediation
scripts
as
either
shell
scripts
or
ansible
playbooks,
so
that
I
can
take
care
of
that.
C
B
So
terry,
maybe
regging
with
insights,
would
be
a
an
option
for
your
convertible.
C
B
Yeah
so,
and
also
at
this
point,
if
it
completely
derails
you're,
probably
in
the
state
where
you
need
to
restore
from
back
up
right.
A
D
C
C
A
B
C
B
It's
important
to
note
that
we
had
john
spinks
on
the
program.
Maybe
a
month
ago,.
C
E
C
I
just
have
a
couple
vms
that
I
use
often
I
call
them
my
utility
vms
and
when
I
come
to
the
dashboard,
I
see
this
nice
interface
that
it's
telling
me.
I
have
zero
critical
issues
that
are
affecting
my
systems
that
are
registered
two
important
three
moderate.
So
let's
go
ahead
and
click
on
important
and
let's
see
what
they
say.
A
C
Point
yeah,
my
centos
system
isn't
registered.
Centos
cannot
register
to
insights.
A
C
It
can
never
benefit
from
any
of
this
stuff,
but
what's
nice
is
it.
C
C
B
C
C
B
Yeah,
and
it
could
also
be
that
you
pulled
a
pulled-
a
package
from
another
repo
that
obsolete.
B
C
B
That's
one
of
the
things
that
you
can
do
now
is
you
can
kind
of
accept
the
accept
the
advice
and
basically
remove
it
from
the
list
it's
in
the
dot
dot.
If
I
remember
correctly,.
B
C
E
C
B
Well,
we'll
get
right
on
rendering
your
box
unusable.
Yes,.
C
B
We
can
call
it
good
and
go
after
this.
If
you
don't
survive
it,
it
needs
to
be
restored
from
back
up.
If
you
do
survive,
reboot
and
you'll
notice,
the
red
hat
kernel
is
in
place.
If
you
do
a,
you
know,
check
out
the
red
hat
release
file
it'll
tell
you
they're
on
red
hat
enterprise
linux,
and
at
that
point
you
would
because
terry
converted
with
subscription
manager,
it'll
register
and
then,
if
you
wanted
to
also
register
to
insights,
that
would
be
a
post
reboot
task
to
do.