►
Description
A show that features the people and technology that make Red Hat Enterprise Linux into the the world’s leading enterprise Linux platform.
A
Good
morning,
good
afternoon,
good
evening,
wherever
you're
hailing
from
welcome
to
another
episode
of
red
hat
enterprise,
linux
presents
here
on
openshift
tv.
Today
we
are
talking
about
subscription
management.
We
brought
in
a
special
guest,
but
I'm
gonna
hand
it
over
to
the
one
and
only
scott
mcbryan
to
do
his
spiel
and
intro
our
guests
scott.
How
are
you
doing
today.
B
Doing
great
thanks
chris,
so
today
we
have
with
us.
I
think
someone
who
has
the
designation
of
being
one
of
the
most
loved
and
hated
red
hatters
at
red
hat.
This
is
senior
principal
product
manager,
rich
dorito,
rich.
Welcome
to
the
show.
Why
don't
you
tell
us
a
little
bit
about
what
you
do
at
red
hat.
C
Yeah
so
hello,
everyone,
I'm
rich
dorito,
I'm
one
of
the
product
managers
on
the
subscription
management
experience
team
at
red
hat.
My
team
works
primarily
on
most
almost
all
of
the
subscription
tooling
that
most
of
you
see
so
subscription
manager
subscription
watch,
cost
management,
red
hat
subscription
management,
all
of
those
things
kind
of
fall
into
our
purview.
B
So
rich,
when
people
complain
about
red
hat
products
being
hard
to
get
subscription
management
is
often
the
blame,
and
I
don't
think
that
that's
a
fair
wrap,
especially
because
we've
done
a
lot
of
stuff
like
created
the
developer
subscription,
which
provides
a
free
to
acquire
a
single
subscription
that
provides
access
to
a
whole
bevy
of
red
hat
products,
including
rel
and
others.
C
Yeah,
so
those
that's
actually
really
good
to
talk
about.
So
one
of
the
things
that
we've
been
working
on
over
here
on
the
red
hat
side
has
been
one
making
it
just
very
easy
for
you
to
get
through
the
front
door
of
the
redhead
experience
right
and
the
developer
programs
are
are
one
major
part
of
that
right.
C
We
want
to
make
it
easy
for
folks
for
those
development
use
cases
to
get
access
to
to
red
hat
enterprise
linux,
as
well
as
the
various
other
things
that
layer
on
top
of
it
from
a
subscription
management
point
of
view,
we've
been
focused
a
lot
on
making
sure
that
our
tooling
fits
the
personas
of
the
people
who
are
using
them.
So
when
we
think
about
subscription
management.
Historically,
we've
we've
built
a
set
of
tooling
that
required
folks
to
understand
a
lot
of
domain
expertise.
C
That's
very
specific,
the
red
hat
like
if
I'm
a
systems
administrator.
Do
I
really
care
about
a
pool
id.
Do
I
really
care
about
a
sku?
That's
that's,
not
language
that
I'm
accustomed
to
speaking
in
right.
I'm
accustomed
to
hearing
hey,
I
need
to
add
three
more
web
servers
to
this
particular
cluster
right,
so
my
team
has
been
focused
on
separating
that
complexity
from
the
operations
personnel.
C
Who
are
you
care
about
things
like
managing
servers,
managing
apps
managing
workloads,
while
also
understanding
that,
yes
in
the
corporate
setting,
we
do
need
to
keep
track
of
how
much
we're
deploying
in
the
past
we've
kind
of
merged
those
two
capabilities
into
one
set
of
tool
trying
to
satisfy
the
people
who
count
the
beans
and
the
people
who
manage
the
systems
and
we
weren't
really
good
at
satisfying
either.
So
now
we're
taking
more
of
an
approach
if
we
want
to
start
separating
those
two
personas
treat
them
independently.
C
As
far
as
some
best
practices
around
subscription
management.
There
are
a
few
things
I
do
like
to
like
to
point
out.
First
and
foremost
is
whether
you're
using
satellite
or
whether
you're
using
red
hat
subscription
management.
One
of
the
things
I
like
to
point
folks
to
is
what
we
call
activation
keys.
Activation
keys
are
a
means
to
kind
of
predefine
how
you
want
to
set
up
a
system
when
it's
registered
right.
It'll
cover
certain
things
like
which
repositories
do
you
want
to
enable
by
default?
C
I'll,
also
cover
things
like
what
subscription
you
want
to
attach
and
we'll
talk
about
what
we're
doing
around
subscription
attachment
in
a
minute,
but
the
activation
keys
are
one
of
those
functionalities
to
make
it
easy
for
you
to
build
automation,
workflows
on
top
of
our
subscription
management
tooling,
and
not
have
to
do
things
like
embed
passwords
into
scripts
and
stuff,
like
that,
no
one
really
wants
to
do
that.
The
other
major
recommendation
that
I
would
point
out
is
from
an
automation
perspective.
C
So
if
you
want
to
register
systems,
if
you
want
to,
you,
know,
tear
systems
down,
even
if
you
want
to
do
really
advanced
stuff,
like
grab
information
about
entitlements
and
do
your
own
kind
of
custom
reporting,
I
would
point
you
towards
the
red
hat:
subscription
management,
ansible
module,
because
that's
that's
our
primary
means
of
interacting
with
the
subscription
services
and
that's
maintained
by
our
team.
B
Cool,
so
you
brought
up
something
that
I
kind
of
wanted
to
dive
a
little
bit
deeper
on.
You
talked
about
separating
the
purchasing
from
the
consumption
and
utilization
and
one
of
the
things
that
I've
I've
heard
like
a
billion
times
over
the
years
is
that
it's
really
hard
when
you're
doing
purchasing,
because
essentially,
once
a
year,
you
renew
your
contract
with
red
hat,
which
is
what
then
renews
your
subscriptions
for
the
next
so
often,
and
during
that
time
you
essentially
need
to
decide
in
the
upcoming
year
or,
if
you're
doing
an
out
year
deal.
C
Yep,
so
so
one
of
the
things-
and
if
I
was
kind
of
to
put
it
in
very
short
terms
like
if
I
was
trapped
in
the
elevator
and
someone
was
like
what
do
you
do
for
a
living-
and
I
gotta
tell
it
to
him
and
in
five
seconds
or
so
my
response
would
be.
I
make
it
easy
for
people
to
give
red
hat
money
right,
like
that's.
That's
my
job
right
now
and
with
that
and
what
that
means
kind
of
crosses
two
major
areas
for
us
right.
C
The
first
one
is
making
it
so
that
you
can
acquire
redhead
technologies
through
whatever
modality.
That
makes
sense
right.
Historically,
red
hat
has
been
a
company
that
sold
you
know
yearly
subscriptions
or
three
year
or
five
year
subscriptions
now,
as
the
world
is
becoming
more
more.
I
hate
to
use
the
word
agile,
but
as
the
world
has
different
needs,
fluid
one
gear,
yeah
fluid
right
one-year
subscriptions
may
not
necessarily
be
the
best
way
to
purchase
red
hat
technologies
right.
So
you
see
this
a
bit
in
the
public
cloud.
C
C
Even
you
know
we're
working
with
the
openshift
team,
we're
working
with
the
ansible
team
as
well
right,
because
the
business
folks
are
always
trying
to
tweak
their
models
to
best
satisfy
the
customer
need,
and
my
team's
responsibility
is
to
make
sure
that
as
they
do,
that
we
have
the
correct
tools
in
place
to
ensure
that
you
can
count
that
stuff
right.
If
you
want
to
buy
by
the
hour,
that's
great,
but
at
some
point
you're
going
to
want
to
know,
does
it
make
sense
to
now
buy
by
the
year
or
vice
versa.
C
C
Yep
we
have
actually,
we
have
released
three
products,
we
were
busy,
but
yes,
so
for
our
yearly
subscription
customers,
we
released
in
summit
2020
a
capability
called
subscription
watch.
That
is
a
sas
based
dashboard.
It
lives
at
cloud.redhead.com.
C
It
runs
on
the
same
platform
as
red
hat
insights
as
well
as
red
hat
openshift
cluster
manager.
The
purpose
of
subscription
watch
is
to
provide
that
holistic
account
wide
view
of
where
you're
running
those
red
hat
technologies.
So
you
know
you
think
about
the
average.
You
know
moderate
to
large
size
customer
you
got
stuff
all
over
the
place
right.
You
got
some
stuff
on
premise.
You
might
got
some
stuff
on
the
public
cloud.
C
Maybe
I
prefer
one
public
cloud
provider
to
the
other.
What
kind
of
rel
is?
Is
it
physical
or
is
it
virtual
and
I
can
slice
and
dice
that
inventory,
based
upon
all
the
things
that
make
up
a
red
hat
subscription
stuff,
like
you
know,
what's
the
usage
type,
is
it
a
development
usage
or
is
it
a
you
know,
production,
usage
or
sla
right
is
the
standard
support
or
premium
support,
and
this
capability
right.
C
And
and
that
capability
is
available
to
all
red
hat
customers,
it
is
a
value
of
the
red
hat
subscription.
It's
not
a
thing
that
you
have
to
purchase.
You
know
as
an
additional
ad
on
subscription.
Today
we
support
rel
and
openshift
in
subscription
watch
and
we
are
diligently
working
to
expand
our
coverage
of
the
entire
red
hat
portfolio.
B
I
went
ahead
and
pulled
up
my
own
subscription
watch,
which
is
not
very
interesting,
so
we
have
about
well,
it
was
three
thousand
or
so
subscriptions
that
we
use
for
demos
and
other
stuff.
Those
are
all
for
renewal,
so
that's
now
almost
eight
thousand
subscriptions
and
then
three
thousand
are
gonna
drop
off
that
list.
So
my
top
bar
right
here
is
kind
of
all
my
subscriptions
lumped
together
and
down
here.
They,
the
much
smaller
than
it
used
to
be
line,
is
my
day-to-day
usage
over
time.
C
So
you
can
actually
pull
up
the
drop
down
on
the
right
hand,
side
where
it
says
daily,
and
you
can
actually
take
that
back
almost
a
year
and
that'll
show
you
kind
of
some
of
your
usage
over
time,
so
yeah,
so
we're
required
to,
I
believe,
hold
this
data
for
four
years.
C
So
when
it
comes
time,
let's
you
know
start
to
make
those
purchasing
decisions
like
how
much
rail
are
we
going
to
need
next
year.
While
we
can't
truly
forecast
it,
we
can
give
you
what
you've
used
in
the
past
and
that
may
be
depending
on
how
your
organization
deploys.
It
may
be
indicative
of
what
you
might
need
in
the
future.
B
Yeah
and
for
me,
like
my
boxes,
exist
for
all
of
30
minutes
at
a
time
and
then
essentially
I
strip
the
the
entitlement
from
them
and
throw
it
away
and
then
reuse
it
for
the
next
box
that
comes
in
for
30
minutes.
So
that's
why
we
just
kind
of
see
this
little
alum
you
can
see
in
december.
There
was
a
hump
there,
because
that
was
me
not
removing
subscriptions,
as
I
was
out
on
pgo.
C
So
one
of
the
things
that
I
do
want
to
point
out
with
subscription
watch
that
we
we
are
introducing
across
multiple
cloud
providers
as
we
are
introducing
what
we
call
high
precision
reporting.
C
So
today,
if
you
look
at
subscription
watch
what
you're
seeing
is
a
daily
snapshot
of
your
inventory
that
we
evaluate
once
a
day
right.
So
one
of
the
the
challenges
that
you
have
with
a
daily
snapshot
is
that
there
are
lots
of
folks
who
have
workloads
that
live
and
die
inside
of
a
24-hour
period
right
and
some
in
some
use
cases
those
may
be
purchased
by
the
hour
from
the
cloud
provider.
In
some
use
cases
they
may
use
a
yearly
subscription
for
them
in
either
case
anything
that
happens.
C
Inside
of
the
day
we
historically
weren't
able
to
visualize
inside
a
subscription
watch.
We
introduced
a
high
precision
reporting
capability.
It's
currently
available
for
amazon,
we're
going
to
be
releasing
it
soon
for
other
cloud
providers
like
azure
and
google.
But
what
that
gives
you
basically
is
gives
you
the
ability
to
configure
an
authentication
credential
so
an
arn
in
the
case
of
amazon,
and
that
allows
us
to
walk
through
the
amazon
api
and
we'll
actually
have
precise,
start
and
stop
times
of
your
instances.
C
So
we
can
actually
visualize
down
to
basically
the
nanosecond
when
those
images
come
or
instances
come
online
and
go
offline.
So
that's
again
we're
trying
to
give
you
that
level
of
precision.
So
you
understand
your
usage,
because
in
many
cases
we
are
going
to
have
to
make
purchasing
decisions
based
upon
that.
In
some
cases
it
may
make
sense
to
purchase
from
the
cloud
provider
other
cases
it
may
make
sense
to
purchase
from
red
hat.
My
job
is
to
give
customers
the
the
information
that
empowers
those
decisions.
A
Cool,
so
we
got
a
question
in
chat
or
two
questions
probably
have
the
same
answer
kind
of
deal
one.
This
is
from
detcon
kudo.
One
of
the
big
problems
I
have
is
free
form,
provisioning
of
rel,
for
ci
cd
workers
and
for
developer
use
where
the
machines
may
not
be
persistent
more
than
a
day
at
a
time,
most
of
that
ci
cd
infrastructure
can't
configure
subscription
manager.
So
how
do
we
deal
with
this
break
in
the
experience?
Right,
like
still
need
rail
in
the
pipeline,
but
not
long
term.
C
So
the
so
the
way
the
way
we've
addressed
it
is
kind
of
two-fold
right.
I
mean
at
its
very
simplest
right
before
I
go
into
the
next
piece
of
technology.
It
basically
boils
down
to.
We
have
the
capability,
so
you
don't
have
to
attach
subscriptions
anymore
period.
Okay,
we
call
that
capability,
simple
content,
access
right,
and
this
goes
to
kind
of
what
I
was
talking
about
earlier
about.
C
We
want
to
put
a
separation
between
the
folks
who
need
to
care
about
subscriptions
and
the
folks
who
don't
right
and
then
the
ci
cd
pipeline,
I
probably
don't
need
to
care
about
subscriptions.
I
also
don't
want
to
take
the
time
and
expense
to
to
actually
go
through
the
process
of
assigning
subscriptions
right.
So
so
sca
is
really
designed
to
to
address
that
right.
So
the
experience
we
are
we
are
targeting
is
a
register
and
run
experience.
C
So
if
you
own
rel,
you
should
be
able
to
register
a
rail
system
run
a
rail
system
entitlement
should
not
get
in
your
way.
That's
what
sca
allows
you
to
do
so
doing
things
like
building
ci
cd
pipelines
becomes
simpler
because
we
don't
have
to
do
a
title
entitlement
attachment
as
part
of
that
process
as
a
interesting
side
effect
is
because
we're
not
doing
all
the
entitlement
logic.
When
we
register
a
system
registration
happens
on
average.
This
is
environmental
dependent,
but
registration
happens
five
to
10x,
faster
okay,
so
those
are
those
are
major
improvements
right.
C
C
Yeah
so
simple
content
access
is
currently
available
for
our
satellite
customers.
Satellite
customers,
who
are
on
version
6.5
and
above,
can
leverage
simple
content
access
for
our
non-satellite
customers.
We're
looking
to
release
that
early
this
spring,
we
do
have
a
limited
availability
release.
So
if
you're
interested
right
now
reach
out
to
your
account
team-
and
we
can
get
you
hooked
up
with
that-
that
technology.
B
Yeah
and
for
not
using
simple
content
access,
you
know
when
I
provision
boxes,
they
get
provisioned,
there's
a
essentially
a
subscription
manager
register
with
activation
key.
B
It
assigns
their
their
channels
of
content
and
then
what
I'd
like
to
have
happen
is
when
the
system
gets
destroyed.
B
I
would
love
for
it
to
be
able
to
do
a
subscription
manager
unregister,
but
for
whatever
reason,
my
provider
doesn't
give
a
free
teardown
of
the
instance
of
scriptability,
so
that
one
that
one
causes
me
to
have
many
sad
days
as
I
go
through
and
clean
everything
up.
B
C
B
Yeah,
no,
so
we
did
but
there's
been
a
whole
bunch
of
changes
to
the
publicly
facing
api
for
red
hat
subscription
manager,
and
so
it
has
changed,
and
my
script
was
the
old
one
as
well,
and
I
just
need
to
go
through
and
update.
It
take
care
of
it
one
day,
my
my
ever
less
ever
growing
list
of
to
do's
will
just
continue
to
get
longer.
A
C
So
planned
yes,
eta,
we're
still
working
that
out,
but
yeah.
We
want
to
basically
we're
kind
of
working
from
a
little
bit
of
a
deficit
here
to
be
completely
transparent,
like
my
team's,
relatively
new
at
red
hat,
so
we
got
to
catch
up
on
all
the
ways
that
red
hat
sells
all
the
things
and
we've
kind
of
been
doing
them
in
a
priority
order
of
what
are
the
most
common
ways
that
people
procure
our
products,
so
we've
been
tackling
yearly
subscriptions
and
rel
and
openshift
and
ansible
more
traditional
models.
C
B
Rich
also
has
a
couple
of
doggos
that
are
his
co-workers
now.
A
I
mean
my
dog:
is
the
commerce
township
red
hat
office
employee
of
the
month
every
month
it
never
fails.
B
So
rich,
if
we
could
change
gears
a
little
bit
better,
a
little
bit,
what
tools
do
you
think
red
hat
customers
would
be
surprised
to
know
exist
that
your
team
has
been
working
on.
C
So,
besides
sca,
which
I
I
kind
of
feel
like
I'm
going
to
shamelessly
plug
it
just
because
I'm
never
going
to
pass
an
opportunity
to
subscription
watch
is
the
other
one
right
subscription
watch
is
that
cloud-based
dashboard
and
then
the
third
tool
in
our
portfolio
and
I'm
going
to
really
hurt
this
dog.
A
A
C
But
the
the
third
capability
that
my
team
offers
is
the
capability
for
openshift
called
cost
management
and
enables
our
customers
to
see
kind
of
vertically.
C
How
much
does
an
openshift
application
cost
them
running
on
a
public
cloud
right
and
we
do
have
that
capability
available
for
both
amazon
and
azure,
so
again,
just
kind
of
look
across
red
hat's
entire
portfolio,
no
matter
where
you
land
in
that
portfolio,
my
team's
going
to
be
delivering
or
have
delivered
a
set
of
capabilities
to
help.
You
understand
subscription
management
which,
when
you
really
think
about
it
at
its
core
subscription
management,
is
really
just
a
proxy
for
cost
management.
C
Right
and
cost
management
for
openshift
is
probably
the
big
thing.
I
would.
I
would
point
to
folks
and
we're
like
that's
a
thing
that
we
have
and
that's
included
with
an
openshift
subscription.
So
if
you
have
openshift,
that's
not
an
additional
add-on,
you
have
to
buy.
We
generally
like
to
bundle
things
on
the
red
hat
side,
but
that's
a
capability
that
we
have
that's
that's
available
and
then
the
last
thing
I
talk
about.
It's
not
really
a
product,
but
it's
just
the
capability
in
red
hat
enterprise.
C
Linux,
I
think,
is
very
much
worth
taking
care
of
taking
a
look
at
is
a
capability
called
system.
Purpose
right
and
system
purpose
is
it's
the
technology
we
introduced
around
the
rel,
a
timeline
because
in
rel
eight
we
simplified
the
the
actual
content
of
rel
eight,
so
we
needed
some
metadata
to
help
us
understand.
How
are
you
using
that
system?
This
is
the
rail
servers,
the
rail
workstation.
C
The
reason
why
that's
important
is
because,
when
I
kind
of
put
all
these
things
together
right,
simple
content
access,
it's
all
about
the
ops
guys
right,
I'm
gonna
make
it
simple
for
them
to
just
use
our
stuff
register.
The
box
build
the
server,
build
the
workload
you
don't
have
to
know
about.
Subs
subscription
watch
that
target
targets,
those
buying
personas
right
people
who,
at
some
point,
got
to
pay
a
bill
right.
They
do
need
to
understand.
C
You
know
how
much
of
it
have
we
deployed.
Where
have
we
deployed
it
and
in
the
case
of
things
like
you
know,
our
virtual
data
center
subscriptions
how
many
hypervisors
are
using
our
stuff,
but
there's
a
missing
link
between
those
two
two
personas
right,
many
red
hat
subscriptions,
are
purchased
based
upon
like
sla,
you
pay
a
little
bit
more
for
premium
than
you
do
for
standard.
C
Well,
how
can
subscription
watch
count
with
systems
are
premium
and
standard?
That's
not
a
thing.
I
can
query
from
the
system.
Inherently,
it's
not
a
system
fact
right,
it's
not
a
rpm,
so
I
need
to
ask
you,
as
the
systems
administrator
tag,
these
systems
up
right
and
if
you
tag
those
systems
properly,
that
information
matriculates
into
subscription
watch
and
that's
what
helps
power.
Those
those
rich
charts
that
we
show
and
system
purpose,
just
like
all
of
our
other
subscription
stuff,
is
exposed
via
the
red
hat
subscription.
Ansible.
B
It's
also
something
that
can
be
set
at
install
time
through
kickstart
or
through
the
graphical
installer
and
then
just
to
provide
a
little
bit
more
historical
depth
there.
If
you
don't
mind,
it
used
to
be
the
case
that
when
you
registered
a
subscription,
we
would
choose
a
subscription
out
of
the
subscription
pool
to
assign
that
box,
but
there
was
no
method
of
being
like.
B
Oh,
this
is
a
you
know,
self-support
subscription
that
should
be
assigned
to
this
box
because
it's
a
short-lived
dev
box
that
we
don't
really
need
to
register
and
you
know,
call
red
hat
support
services
or
get
24x7
365
fossil
the
sun
support
on,
and
we
didn't
really
have
a
method
for
being
like
this
dev
box.
How
do
I
make
sure
that
I
get
a
self
support
right?
One
of
those
lower
cost
subscriptions
tied
to
it
and
system
purpose
allows
that
to
happen.
B
So
it
looks
at
what
you
provide
as
your
system
purpose
and
then,
if
you
allow
it
to
it'll,
make
an
automatic
decision
based
off
of
that
to
try
and
align
the
subscription
type
that
gets
assigned
to
that
box
to
match
the
system
purpose.
So
if
you
say
that
it's
a
dev
or
test
box
and
there's
one
other
criteria,
skipping
me
rich
self-support.
C
So
yeah,
so
your
your
matrix
with
system
purpose
is
role,
usage
and
sla.
Basically,
what's
the
workload
who
do
you
plan
on
calling?
How
do
you
want
us
to
support
you
and
then,
lastly,
like?
When
do
you
plan
on
calling
all
right?
Those
are
kind
of
the
three
things
about
three
or
four
things
about
a
subscription
that
are
not
system,
facts
that
if
you
tell
us,
we
are
able
to
make
better
decisions
around
what
subscription
you
get.
So
you
tell
me
this
box
is
running
rel
and
requires
premium.
C
Then
we're
going
to
go,
look
for
real
subscriptions
that
have
premium
and
we're
going
to
prefer
them.
We'll
fall
back
and
use
a
standard
support
subscription
on
a
premium
system,
but
we'd
only
do
that
if
and
only
if,
you
don't-
you
know,
have
any
premium
and
then
we'll
tell
you
we'll
be
like
hey.
We
we
put
a
standard
on
this
box.
It
doesn't
match
your
preference,
but
you
know
we
had
to
do
that.
To
give
you
content.
B
Right
and
it
in
the
status
from
subscription
manager
and
we'll
take
a
look
at
this
in
that
demo
section
a
little
bit.
It
actually
identifies
what
the
system
purpose
been
said,
as
well
as
what
subscription
has
been
assigned,
plus
whether
there's
a
mismatch
between
those,
but
that
that
was
one
of
the
first
things
that
we
did
a
couple
years
ago
to
try
and
allow
people
to
tell
us
so
that
we
could
make
better
decisions
when
assigning
upon
registration.
What
subscription
went
with
their
box.
B
So
rich,
what's
something
you
see,
people
do
with
subscription
management
all
the
time
that
you
wish
they'd
do
differently.
C
Oh
man,
so
what
do
I
see
them
do
with
subscription
manager
that
I
wish
they'd
do
differently?
Stop
yelling
at
me
about
it.
C
Right,
okay,
so,
but
but
seriously,
I
think
the
the
big
thing
that
I
I
I
see,
which
is
a
pattern
which
I
want
to
call
an
anti-pattern,
is
that
I've
seen
folks
like
to
unregister
systems
and
re-register
them
a
lot
right.
Like
that's
a
thing.
I've
seen
in
common
workflows
like
I've,
seen
people
do
this
with
like
puppet
I've.
C
Seen
people
do
it
with
other
automation
tools,
but
they'll
do
something
like
some
kind
of
like
health
check
like
if
this
system
can't
access
this
particular
repo
or
what
have
you
instead
of
just
like,
enabling
that
repo
they
would
unregister
the
system
and
register,
because
it's
almost
kind
of
like
a
registered
system
is
in
fact
the
desired
state
right.
So
I've
seen
that
I
think
the
other
thing
that
I've
seen,
which
I
kind
of
see
less
of
now,
just
because
folks
do
kind
of
understand.
C
More
of
the
subscription
tools
is,
I
used
to
see
a
lot
of
folks
who
would
have
who
would
have
either
different
types
of
subscriptions,
and
they
would
do
like
weird
things
with
activation
keys,
where
they
would
attach
different
types
of
subscriptions
to
activation
keys
right
and
then
that's
that's
a
little
bit
of
a
challenge
in
the
subscription
tools
because
effectively,
if
you
think
of
an
activation
key,
it's
a
registration
token.
It
gets
you
through
the
front
door.
It
sets
up
a
whole
bunch
of
stuff.
C
So
if
you
think
about
it
in
the
unix
model,
you
kind
of
want
these
things
to
be
like
single
purpose,
because
you
can
use
more
than
one
right,
which
is
a
pro
tip
that
a
lot
of
people
don't
know.
You
can
actually
use
more
than
one
activation
key
at
registration
time.
But
what
we'll
see
is
what
I
would
see
is.
I
would
have
folks
they
would
lob
everything
in
right
have
openshift
subscriptions
and
rel
subscriptions,
and
they
have
it
all
mixed
up
and
jumbled
on
the
keys.
C
And
then
one
of
the
challenges
is
when
you
do
all
that
you
get
non-deterministic
behavior
right
and
that's
one
of
the
things.
That
was
an
area
where
we
had
friction
with
subscription
management,
so
assuming
that
you're
not
going
to
move
over
to
simple
content
access,
which
you
really
should
I
mean
like,
I
buy
you,
a
coffee
or
a
drink
of
your
choosing.
Please
use
simple
content
access,
but
if
you
don't
take
a
look
at
your
activation
keys,
your
activation
keys
should
generally
be
fairly
single
purpose.
You
should
have
an
activation
key
to
assign
subscriptions.
C
You
should
have
an
activation
key
to
maybe
enable
repositories
that
way
as
you
introduce
new
workloads.
You
don't
have
this
linear
increase
in
the
number
of
activation
keys
that
you're
managing
you
can
just
mix
and
match
them
as
you
need.
So
those
are
kind
of
some
things
that
I
see
people
do
in
the
subscription
management
space
that
are
that
are
kind
of
anti-patterns
that
we
kind
of
want
to
get
away
from.
C
B
So,
holding
aside
simple
content
access
for
a
second,
what
you
were
suggesting
for
activation
key
layout
is:
do
one
that's
like
rel,
which
includes
base
os
and
app
spring
repos,
a
second
activation
key
for
ansible,
two,
nine
repo,
a
third
activation
key
for
aj
add-on,
repos
and
then,
depending
on
whether
your
boxes
that
you're
registering
need
those
things.
You
just
apply
a
combination
of
those
activation
keys
to
the
box
as
it
needs
it.
C
So
then
we
we,
we
have
a
doc
that
kind
of
covers
what
happens
when
there's
conflicts
and
activation
keys,
because,
obviously
because
you
can
set
the
same
settings
on
more
than
one
key,
we
do
have
to
have
some
conflict
resolution,
so
that
is.
That
is
something
that
is
documented.
C
So
let's
say,
for
instance,
if
I
using
your
example,
scott,
I
had
a
rel
key
ansible
key
and
an
h,
a
key
right
and
on
the
rel
key,
I
say
enable
base
os
an
app
screen,
but
then
on
the
ansible
key,
I
say
disable
base
os
in
app
stream,
which
one
wins
and
that's
something
you
need
to
be
aware
of.
Obviously,
because
you
want
to
make
sure
you
have
the
effect
that
you
desire.
A
short
version
is
the
key
that
is
to
the
right
most
on
the
command
line.
A
B
So
richard
been
around
a
long
time,
I
almost
always
ask
this
question
of
guests,
and
I
know
that
you
don't
work
for
a
rel
anymore
or
ever,
but
what's
something
that
you
see,
people
do
with
rel
that
you
wish
they'd
do
differently.
C
C
Have
you
known
a
really
strong
affinity
and
I
would
see
folks
not
patch
their
systems
and
there's
a
multitude
of
reasons,
but
ultimately,
almost
all
of
them
come
down
to
a
perception
of
risk
right
and
then,
when
I
would
work
with
customers
on
the
satellite
side
right
they're,
like
I
can't
patch,
why
not
and
then
almost
they
give
a
thousand
one
reasons,
but
all
of
them,
when
you
boil
them
down
to
their
essence,
they
were
about
risk
right
and
there
are
a
number
of
ways.
You
know
you
can
go
and
address
risk
right.
C
You
can
address
risk
with
things
like
satellite
which
allow
you
to
curate
the
content,
so
you
can
limit
when
and
which
updates
are
available
to
systems
right.
You
can
mitigate
risk
with
tools
like
ansible,
so
you
can
do
things
like
rolling
updates,
or
you
know,
ways
to
do
automation
and
testing
against
the
system
to
make
sure
it's
in
a
healthy
state
post
patching
right.
C
There
are
things
that
rel
offers
like
many
of
rel's
life
cycle
products
like
eus
and
e4s,
and
some
of
the
other
lifecycle
streams
that
give
you
an
even
slower
than
rel
release
cadence
for
those
critical
workloads
that
require
it
now,
which
one
of
those
you
use.
That's
going
to
vary
by
the
organization
right.
Many
organizations
use
more
than
one,
but
you
gotta
use
them.
You
gotta
catch
right
because
the
longer
you
defer
patching
it's
like
credit
card
debt
right,
the
longer
you
defer
it.
C
C
A
No,
I
mean
like
there's,
there's
folks
asking
about
like
satellite
and
ocp.
I
don't
think
there's
any
integration
is
coming
there.
Subwatch
seems
to
not
work
for
us
on
osd,
so
it's
a
little
nebulous
to
me.
Is
there
anything
coming
on
that
front,
rich.
C
Yeah,
so
for
for
osd
and
ok
we're
still
in
development
of
those
capabilities
for
sub-launch.
So
right
now,
subs
watch
really
covers
just
the
traditional
yearly
openshift
subscriptions
awesome.
B
So,
like
many
other
people,
I
used
to
yell
at
rich
a
lot
and
then
I
discovered
something
I
installed:
bash
completion
in
my
standard,
build
environment
and
all
of
a
sudden,
a
lot
of
my
complaints
about
subscription
manager
just
vanished
because,
like
I,
I
was
an
idiot.
A
B
I
mean
it
has
a
fairly
complex
lexicon
on
the
command
line,
and
I
I
don't
know
that
it's
really
easy
to
remember
all
the
options,
but.
C
B
It's
true
and
that's
quotable
as
well
all
right,
so
I
have
this
box,
it's
a
just,
a
small
vm
and
you
can
see
when
I
pulled
the
status.
It's
giving
me
a
system
purpose
mismatch,
because
I
set
the
type
of
usage
as
development
test,
but
it
has
a
self-support.
B
And
we
could
go
in
and
adjust
what
these
are,
if
we
so
desire
to
kind
of
do
away
with
that
error
message,
so
you
can
make
changes
to
your
system,
purpose
on
running
systems
and
that's
it'll
be
fine,
but
I'm
gonna
go
ahead
and
unregister
this
box
as
much
as
rich
hates
people
on
registering
finally
registered
boxes.
C
It's
expensive,
that's
all
it's
true!
When
you,
when
you
register
a
box,
we
have
to
create
at
least
two,
if
not
more
x.509
certificates
that
identify
that
system,
uniquely
globally
across
every
system,
red
hat,
knows
about
and
we
have
to
provide
the
x.509
certificates
for
you
to
access
content.
Obviously
anything
with
crypto
takes
a
little
bit
of
time,
so
we
don't
want
people
doing
that
in
you
know
in
high
frequency,
if
they
could
avoid
it.
B
Well,
and-
and
that's
one
of
the
other,
I
think
complaints
that
you
likely
get
a
lot
is
how
long
it
takes
to
do
things
like
registrations
and
that
that
would
be
a
great
reason
why
it's
taking
so
long
so
because
certificate
generation
is
something
that
just
takes
what
it's
gonna
take.
C
B
All
right,
so
I
went
ahead
and
re-registered
it
just
using
my
user
credentials
instead
of
using
the
activation
key,
because
I
want
to
also
take
a
look
at
attaching
repos
to
it
as
well
rich.
Do
you
have
a
preferred
way
that
I
should
go
about
doing
that
or
should
I
just
fumble
my
way
through
it.
C
B
Right
so
when
it's
registered
and
I
need
to
take
a
look
at
what
repositories
are
available
for
it,
so
we're
gonna
do
subscription
manager,
repo.
B
Repos,
but
we
have
a
lot
of
repos
available,
so
I'm
going
to
run
it
once
and
I'm
going
to
rerun
it
again
with
some
gripping
to
pull
out
the
pieces.
I
know
I
need
because
I
know
that
I
need
this
box
registered
to
the
oh.
Well,
there
you
go
all
right,
so
let
me
attach
a
subscription
first.
C
A
B
A
B
C
So
you
don't
have
to
explicitly
provide
auto
anymore.
I
believe
we,
I
believe
we
default,
that
we've
been
doing
that
for
about
a
year
or
so
now,
cool.
C
C
Yeah
we've
been
looking
at
simplifying
some
of
the
sub
commands,
because
some
of
them
are
equivalent
like
subscribe
and
attach
are
actually
equivalent.
Sub
commands
subscribe
is
actually
the
old
one
attaches
the
newish
one,
but
we
weren't
able
to
get
that
change
into
rail
eight.
So
we
obviously
can't
take
it
out
in
the
middle
of
the
the
release
so
you'll
see
in
real
nine.
C
The
number
of
subscription
manager
commands
are
probably
gonna
be
about
three
or
four
fewer
sub
commands,
because
some
of
them
are
duplicates
that
we
just
can't
drop
unless
it's
a
major
release
stream.
C
So
I
do
want
to
give
a
shameless
plug
here
for
the
repo
override
command
since
tab
completion
shows
it
up.
So
scott.
You
were
talking
about
things
that
I
see
people
do
with
subscription
manager
that
I
rather
did
not
do.
The
big
one
is
editing,
redhead.repos
right,
sc,
yum.repose.d,
redhead.repo,.
C
With
those
well
it's
ours,
we
treat
it
treat
it
like.
It's
a
managed
file
that
you
don't
own.
However,
there
are
times
where
you
may
need
to
edit
that
file
right,
the
common
one
that
I
see
is
I
have
like
customers
who
use
the
apple
repository
right
and
the
apple
repository.
C
Sometimes
you
may
need
to
set
up
like
young
priorities
so
that
a
package
in
apple
doesn't
conflict
with
something
that
red
hat
provides.
Well,
you
do
that
by
updating
the
yum
stanza,
but
if
you
edit,
redhead.repos
the
next
time
you
run
subscription
manager
refresh
you
lose
your
update.
C
A
A
A
C
There
are
some
times
when
you
when
you
do
need
to
do
that.
So
one
of
the
kind
of
intrinsic
behaviors
of
red
hat
subscription
tools
is
that
if
you
instantiate
a
container
on
top
of
a
rail
box,
the
container
by
default
gets
access
to
its
host
repositories.
So
you
don't
have
to
register
containers
explicitly.
C
However,
there
are
times
where
you
may
want
to
register
a
container
explicitly
one
if
you
want
to
register
it
to
something
other
than
the
same
subscription
as
the
host.
If
you
want
to
register
it
to
something
different
like
a
satellite
server,
you
may
want
to
do
that.
So
in
those
cases
they're
not
common,
but
in
those
cases
it
may
make
sense
to
delete
that
that
directory.
So
it's
not
always
an
anti-pattern.
I
won't
say
it
as
a
universal.
Don't
do
it,
but
it's
more
of
a
advanced
user
feature
there.
You
go
okay,.
B
All
right,
rich,
I
want
to
adjust
my
system
purpose
so
that
I'm
not
erroring
out
anymore.
C
Whoa
whoa
whoa
whoa
whoa
whoa.
What
are
we
doing?
Editing
files
by
hand,
we
give
you
commands
for
this,
there's
command.
What's
this
purpose?
That's
why?
Yes
purpose
cis
purpose,
shell,
which
will
show
you
your
current
system,
purpose
attributes
today
I
learned.
A
C
I
mean
you
can
edit
the
file,
but
it's
you
didn't
have
to
call
subscription
manager
refresh
after
you
do
it.
So
it's
actually
more
difficult,
I
guess
so
which
of
the
three
values
you
want
to
set.
C
C
C
C
And
I
can't
remember
if
this
is
case
sensitive
or
not.
I,
like
my
heart,
tells
me
it's
not
case
sensitive,
but
you
know
we'll
find
out
unix
it's
unix.
After
all,
so
you
know
it
should
be
case
sensitive
right.
B
B
C
Right
so
for
sure,
so
in
subscription
manager,
we're
actually
moving
cis
purpose
to
be
a
sub
command
of
subscription
manager,
so
it'll
be
subscription
manager,
cis
purpose,
but
the
cis
purpose
command
will
still
exist
for
the
entirety
of
the
the
rel8
life
cycle,
but
in
real
nine
it'll
be
subscription
manager
assist
purpose.
Just
so
we
can
unify
all
the
subscription
stuff
under
one
command.
B
Are
you
guys
planning
on
in
real
life
obsoleting
some
of
those
commands
that
are
duplicative
of
each
other
like
register
and
subscribe
yeah?
That's
subscribing!
Thank
you,
okay,
cool!
So
that's
a
little
bit
on
using
subscription
manager.
Anything
else
I
should
show
as
well
rich.
C
Now
you
got
the
you
got
the
big
things
right
I
mean.
The
key
things
with
subscription
manager
to
remember
is
that
activation
keys
are
awesome,
so
set
those
up,
because
that
allows
you
to
automate
all
this
stuff
activation
keys
can
set
which
subscription
you
want
to
attach
it.
Can
they
can
set
system
purpose
attributes?
So
if
you
didn't
set
them
during
rail
installation
time,
you
can
also
set
them
on
an
activation
key,
and
then
you
can
also
cover
which
repositories
you
want
to
enable
by
default.
C
So
for
a
rail
system
we
enable
by
default
base
os
and
app
stream
for
rel8
or
just
you
know,
like
rel,
seven
server
rpms
for
earlier
versions,
because
obviously
those
are
universally
needed.
But
if
you
wanted
to
always
enable
like
the
ansible,
rpms
repo
or
you
know
some
other-
you
know
code
ready
builder
or
what
have
you
you
can
use
an
activation
key
to
do
that
universally
to
save
you.
You
know
that
that
round
trip
of
a
another
subscription
manager
call.
A
C
B
B
Having
had
to
like
come
in
every
few
days,
while
on
pto
and
delete
boxes,
because
man-
I
I
cannot
emphasize
enough
how
much
I
I
want
a
like
post,
provisioning
or
pre-tear
down
script
to
like
unregister
something
yeah,
but
there's
a
reason
why.
I
just
keep
like
doubling
and
tripling
the
number
of
subs
that
I
register
every
year
to
try
and
like
gain
more
time
between.
C
Cloud
provider
type
use
cases
you
hit
terminate
in
the
amazon
console,
nothing
comes
back
through
and
cleans
it
up.
One
of
the
things
that
I
that
I
I
might
want
to
talk
to
you
about
scott,
because
it
seems
like
a
reasonable
rfe.
C
I
wouldn't
be
opposed
to
having
logic
like
in
satellite
in
the
customer
portal
to
where,
like
the
admin
can
say,
stale
profiles
over
in
number
of
days
just
purge
them
out,
because
that's
what
people
are
doing
with
api
scripts
today
anyway
right.
So
why
don't
we
just
make
it
a
a
proper
first
class.
You
know
feature.
A
B
C
No
it
just
I
mean
you
really
sit
down
and
think
about
it.
Right,
like
fundamentally
like
I
used
to
be
a
cis
admin,
many
folks
on
the
call
or
sis
admins
as
well
like
dude.
We
got
enough
to
do
right,
like
that's.
That's
literally
what
everyone's
saying
it's
like
dude!
We
got
enough
to
do,
and
you
know
my
responsibility
is
to
make
sure
that
you
know
it's
easy
to
use
red
hat
stuff,
because
if
it's
not
quite
frankly,
you'll
just
not
use
red
hat
stuff
right.
C
So,
yes,
making
it
easy
for
you
to
do
business
with
us,
keep
track
of
your
stuff
clean
up
your
your
expired
systems,
because
that
helps
me
too.
You
got
to
remember
those
old
profiles
that
stay
around.
We
still
count
them
in
subscription
as
if
there
were
live
systems
right.
So
it's
it's.
I
have
a
vested
interest
in
this,
so
this
isn't
all
altruism
here,
okay,
but
I
have
a
vested
interest
in
making
sure
you
maintain
a
clean
inventory
because
it
impacts
my
ability
to
represent
how
much
of
our
stuff
you're
using.
B
Well,
rich,
I
want
to
thank
you
for
coming
on
today
and
talking
to
us
about
subscription
manager.
It's
always
great
when
I
learn
new
stuff
and
certainly
felt
that
way
today,
with
with
you
so
chris
do
we
have
any
other
questions
before
we
roll
out.
C
It's
really
good
question,
my
disconnected
folks.
I
love
them
they're,
my
favorite,
like
honestly
again,
I
used
to
be
a
satellite
pm,
so
I
love
disconnected
customers
yeah,
but
disconnected
systems
are
inherently
almost
generally
not
registered
to
red
hat's
hosted
portal
just
because
they're
in
secured
air
gap
networks
that
can't
communicate
out
so
usually
what
most
folks
will
do
in
the
disconnected
network
is
they
will
build
some
kind
of
means
of
getting
content
into
that
disconnected
network.
C
Some
folks
use
satellite
for
this
as
an
area
where
satellite
excels,
but
not
everybody,
uses
satellite
use
other
tools
as
well,
but
they
will
patch
that
system
in
that
disconnected
environment,
basically
bring
the
content
in
instead
of
allowing
that
system
to
communicate
out
in
a
kind
of
larger
picture.
C
One
of
the
things
that
you
know
my
team
is
responsible
for
is
making
sure
that,
even
if
you
are
a
disconnected
customer,
you
still
should
be
able
to
understand
how
much
red
hat
stuff
am
I
using
so
many
of
our
tools
and
you'll
see
this
in
satellite.
C
Specifically,
many
of
our
tools
allow
you
to
take
an
inventory
of
those
disconnected
environments
and
dump
that
to
disk
right
sanitize.
It
take
out
host
names
and
and
ip
addresses,
because
for
subscription
reasons
we
don't
care
what
your
host
names
are
but
be
able
to
get
that
minimalized
metadata
export
and
be
able
to
upload
that
to
subscription
watch.
So
we
can
represent
you're
using
as
much
rail
when
you're,
using
that
much
open
shift
and
do
so
in
a
manner
that
honors
your
privacy
concerns.
A
C
So
yeah
I
mean
all
of
the
all
the
red
hat
stuff,
whether
it's
our
hosted
portal
cloud.reddit.com
or
our
ship
software
like
satellite.
They
all
have
robust
apis.
So
if
you
need
to
do
some
kind
of
complex
automation
or
integration,
that
capability
is
there.
I
would
say
that
for
most
things,
especially
if
you're
using
a
satellite,
there
are
a
number
of
scripts
and
ansible
playbooks
and
roles
that
we
maintain
in
the
community
in
the
red
hat
satellite
github
organization.
C
A
Cool
all
right,
I
don't
know
how
to
say
this
username
but
lunix
p.
Please
feel
free
to
email
me
to
continue
the
conversation
c
short
at
redhat.com.
A
And
then
adding
it
to
subscription
manager
and
so
forth,
then
enabling
certain
repos,
so
it
seems
like
this
could
be
done
a
cleaner
way.
But
I
don't
know.
C
So
cc
me
on
that
email:
oh
yeah,
yeah,
yeah
yeah,
because
I
know
me
and
richard
redhat.com,
I
got
a
cool
email
address.
Yeah
me
and
dan
have
been
working
with
dan's.
My
other
pm
counterpart
we've
been
working
with
the
the
the
openshift
folks
around
making
sure
it's
super
easy
to
get
real
content
into
openshift
containers.
So
if
there's
any
confluence
between
what
you're
working
on
in
this,
we
might
be
able
to
help.
B
Well,
and
the
other
thing
that
you
should
probably
check
out
is
whether
the
existing
built
red
hat
universal
base,
image
or
ubi
has
the
rowell
components
that
you're
looking
for,
because
if
you
pick
something
like
the
multi
multi-service
image
or
the
just
normal
image,
not
the
minimal
you're
able
to
get
access
to
repo
content
for
more
software
to
stick
in
there
and
it
doesn't
require
registration
or
anything,
because
it's
just
using
repositories
that
are
exposed
on
red
hat's
container
registry.
B
So
that
might
be
an
alternate
way
rather
than
trying
to
subscribe.
Your
container
and
download
repos
and
other
stuff
to
it.
Check
out
red
hat
ubi.
A
B
All
right,
well
thanks
everybody
for
watching
today
and
if
you're
watching
delayed
thanks
for
tuning
in
later
and
rich,
as
always
a
pleasure
to
to
speak
with
you,
thanks
for
for
coming
and
seeing
us
today,.