►
From YouTube: The Level Up Hour (E26): Let's talk subscriptions
Description
Over the last 26 episodes, we've had several questions about subscriptions and licensing for Red Hat Enterprise Linux, OpenShift, and the Level Up Program, so we invited some experts! Gordon Tillmore and Rich Jerrido join us to help answer your questions and discuss common topics around the value of a Red Hat subscription.
Follow us:
Langdon White https://twitter.com/1angdon
Chris Short https://twitter.com/ChrisShort
Rich Jerrido https://twitter.com/SideAngleSide
What is the Level Up Hour?
Every Wednesday at 9am ET we stream live demos on how Red Hat Enterprise Linux (RHEL) users and admins can benefit their organizations and improve their careers by learning how to use containers, Kubernetes, and Red Hat OpenShift.
Learn more at:
https://red.ht/leveluphour
http://red.ht/3ayHlHI
How to participate in the The Level Up Hour:
Watch on YouTube every Wednesday at 9amET
Chat with us on Discord https://discord.gg/5VMVGJt
Check out our GitHub repo https://github.com/level-up-hour/
About OpenShift:
Red Hat OpenShift is an open source container application platform based on the Kubernetes container orchestrator for enterprise application development and deployment.
https://www.openshift.com/
https://github.com/openshift/
#RedHat #OpenShift #tluh
A
A
Good
morning,
good
afternoon,
good
evening,
wherever
you're
hailing
from
welcome
to
another
edition
of
the
level
up
hour,
I
am
chris
short
executive
producer
of
openshift
tv
and
I
am
joined
by
three
of
my
favorite
red
hatters.
But
I'd
like
to
hand
it
off
to
the
one
and
only
the
illustrious
langdon
white
langdon.
Please
take
it
away.
Hi.
B
Everybody
hope
everything
is
going
well
for
you.
I
know
I
am
sufficient
or
significantly
lacking
in
coffee,
but
you
know
we
are.
We
are
starting
to
get
a
little
more
functional,
so
that's
a
good
thing
also
had
a
couple
few
days
off,
so
you
know
we
may
be
starting
a
little
slowly
today,
but
that's
probably
good
for
the
topic
at
hand.
So
today
we're
gonna
be
talking
about
subscriptions
and
I
would
like
to
let's
let's
hit
the
slides
first
and
then
go
and
do
intros.
A
B
C
So
if
you
think
about
the
breadth
of
things
that
we
cover,
we
cover
everything
from
subscription
manager
to
the
customer
portal
to
the
subscription
experience
and
satellite
subscription
watch
at
cloud.redhat.com,
as
well
as
we
work
with
the
various
product
teams
like
the
openshift
team
or
the
ansible
team
around
how
to
integrate
their
tools
and
improve
their
subscription
experience.
I've
been
at
red
hat,
roughly
10
years,
actually
10
and
a
half
years.
C
At
this
point,
I've
been
in
a
number
of
roles,
so
I
do
subscriptions
now
and
I
used
to
be
a
pm
for
satellite
used
to
do
technical
marketing
for
satellite
and
was
the
solutions
architect
in
the
sales
organization.
Prior
to
that,
so
I
kind
of
been
around
the
block
and
thanks
for
having
me
here
today,
awesome.
B
D
A
D
Yeah
so
product
marketing,
I
am
in
our
cloud
platforms,
business
unit.
I
have
been
at
red
hat
for
a
long
time,
17
years
in
various
roles
and
one
of
the
things
that
I'm
responsible
for
is
our
level
up
program
and
working
closely
with
these
guys
with
with
the
level
up
hour
here.
So
that's
why
it's
like
the
you
know.
The
project
has
become
a
reality
to
a
certain
degree
here
this
morning,
where
I'm
glad
to
be
on
front
and
center
with
you
guys
so
yeah.
B
B
B
Yeah
yeah
exactly
because
I'm
only
five
foot
ten,
you
know
and
then
so
everybody
around
me
is
like
six.
Two
plus
you
know
when
you
hang
out
with
the
czech
guys-
and
I
know
chris
is
pretty
tall
as
well.
So
why
don't
we?
Okay
now
we're
gonna
hit
the
slides,
we're
gonna,
introduce
the
topic
and
for
my
slate
maya
culpa,
we'll
we'll
talk
about
that
in
a
second,
and
here
are
the.
A
B
B
C
B
D
B
Yeah
yeah
yeah
all
right,
so
you
can
also
find
us
on
our
discord.
The
link
is
there
and
I'm
sure
chris
will
drop
it
in
with
the
bot
and
you
can
come
and
chat
with
us
there.
We
have
a
couple
different
channels,
but,
generally
speaking,
you
know
the
general
channel
is
more
than
enough,
and
you
know
if
you
have
any
specific
questions,
I'm
often
hanging
out
there
and
then
here
is
information
about
the
show.
B
And
then
so
today,
we're
going
to
talk
about
subscriptions
and
specifically
basically,
we
really
want
to
take
questions
from
the
audience.
However,
we
also
want
to
talk
about
kind
of
like
what
it
means
to
can.
I
have
a
subscription
what
happens
with
things
like
ubi
and
then
things
like
there's
also
this
new
training
subscription
that
we
might
talk
about
a
little
bit.
B
B
B
B
B
Like
you
know,
one
of
the
things
that
helps
when
you're
trying
to
use
a
piece
of
software
is
understanding
like
the
philosophy
behind
it,
and
so,
if
you
understand
the
philosophy
behind
the
software
like
what
its
goals
are,
it
can
often
make
using
the
software
simpler
and
easier,
and
so,
if
you
kind
of
give
us
a
little
bit
of
like
what's
the
driving
force
behind
like
the
subscription
engine,
I
don't
want
to
say
subscription
management
because
I
don't
want
to
imply
like
that
particular
product.
You
know
what
is
what's
kind
of.
B
C
Yeah,
so
the
so
the
best
way
to
look
at
it
and
my
team
we're
relatively
like
a
newly
formed
team.
So
one
of
the
things
that
that
I
have
the
charter
to
do,
along
with
the
rest
of
the
folks
on
our
team,
is
to
kind
of
unify
the
experience
right
prior
to
probably
about
early
2018
red
hat
subscription
experience
was
very
disjointed
and
fragmented
right.
So
we
have
a
lot
of
honestly
places
of
friction
in
the
experience
where
we
need
to
address.
C
But
when
my
team
formed,
we
kind
of
had
this
this,
like
long
like
discussion
of
like
what
is
a
subscription,
if
you
had
to
define
what
a
subscription
is
to
a
person,
that's
either
inside
or
outside
of
red
hat,
what
is
it?
And
basically,
we
look
at
a
subscription
as
being
comprised
of
five
things,
five
basic
like
core
things.
First
and
foremost,
what
do
you
get
right?
Most
red
hat
subscriptions,
give
you
access
to
some
form
of
content
right,
usually
bits
to
install
rail
fix,
install
openshift,
but
not
always
right.
C
We
got
like
training
subscriptions,
we
got
learning
subscriptions,
but
generally
you
get
access
to
something.
That's
the
first
thing.
Second
thing
that
describes
a
description.
A
subscription
is
how
long
you
get
access
to
it
for
right,
the
term.
How
long
does
it
last
usually
a
year,
sometimes
three
sometimes
shorter,
just
depends
and
then
the
next
three
things
that
make
up
what
a
subscription
are
are
really
just
a
bunch
of
use
cases
right.
Who
do
you
call
for
support?
Do
you
call
red
hat
for
support,
or
do
you
call
an
obm?
C
When
do
you
call
us
for
support
24x7
or
5x12,
or
not
at
all?
So
we
have
some
subscriptions.
You
can't
call
for
support
and
then
also
what
type
of
support
do
you
get
when
you
call
us
right
a
lot
of
times
most
folks
want
production
support,
but
we
also
have
development
level
support
where
we'll
give
you
assistance
with
design
and
every
red
hat
subscription
is
basically
combinatory
combinations
of
those
five
things
right.
C
If
you
change
any
one
of
those
things,
it
also
changes
things
like
pricing,
because
we
sell
those
things
at
different
metrics
right,
you
pay
more
for
premium
versus
standard.
So
that's
what
a
subscription
is.
So
then,
the
the
goal
of
the
subscription
tooling
is
to
help
folks
understand
how
much
of
each
type
do
they
have
deployed.
Where
do
they
have
them
deployed
at
and
are
they
above
or
below
the
capacity
of
what
they've
purchased?
C
C
You
know
at
what
point
do
I
have
to
pay
red
hat
money?
How
much
do
I
have
to
pay
them
right?
Those
are
kind
of
the
two
like
core
goals
of
subscription
management.
Now
we
also
have
to
take
the
existing
systems.
We
have
today
and
turn
them
around
and
kind
of
start
and
get
them
to
march
in
that
direction,
and
that's
that's
going
to
take
us
some
time
right,
but
we
do
have
a
lot
of
new
capabilities
that
are
available
today
that
help.
B
So
I
have
actually
like
I
have
that
in
a
sense,
quasi-exact
experience
right.
I
primarily
spent
most
of
my
career
as
like
a
developer
and
our
company.
Whatever
organization
that
was
you
know
whether
I
was
consulting
to
them
or
working
for
them
would
have
a
subscription
to
something
right.
So,
for
example,
they
have
you
know
a
red
hat
subscription.
B
However,
as
a
developer,
I
don't,
generally
speaking,
have
the
ability
to
go
after
the
content,
myself
right
and
as
a
result,
I
have
to
kind
of
go
through
a
middleman.
You
know
of,
like
a
you
know,
some
admin
type
person
or
whatever
to
access
the
content
that's
available
to
the
company.
The
problem
is
it's
much
like
ftp
by
email.
If
you
want
a
super
throwback,
oh
gosh,
that's
old!
You
have
to
know
what
to
ask
for
right
so
kind
of
what
I'm
curious
about
is
like
that
sounds.
B
I
really
like
the
distinction
of
kind
of
the
permanent
person
versus
the
kind
of
operator
person.
What
about
kind
of
the
developer
person?
Do
you
have
a
plan
or
a
thought
around
where
developers
would
be
able
to
access
subscription
content
that
is
available
to
my
company?
So
I
don't
mean
like
a
developer
subscription
I
mean,
like
you,
know,
an
actual
company
one
or
at
least
a
way
for
me
to
know
like
have
a
a
catalog
that's
available
to
me.
That
is
pre-approved
or
something
like
that.
C
There
is
hey,
I'm
an
independent
developer
and
I
want
access
to
the
bits
because
I
like
your
ecosystem-
and
I
want
to
learn
your
stuff,
because
maybe
I
want
to
build
a
career
on
top
of
your
technology
right.
The
way
we
make
it
so
that
person
access
subscription
services
might
be
a
little
different
than
the
way
you
know
the
large
fortune,
500
company,
that
has
you
know,
5
000
developers
needs
to
access
our
subscription
services
right.
C
C
Right
red
hat
believes
that
it
is
in
you
know
the
best
interest
of
our
relationship
with
our
customers
to
make
it
easy
for
you
to
use
rel
for
development
style,
use
cases
well,
rel
and
other
red
hat
products,
but
leading
with
rel.
So
you'll
see
you
know
new
red
hat
programs
in
the
near
future.
That
will
address
those
types
of
use
cases
so
that,
if
you
know
again,
if
we
go
back
to
like
what's
a
subscription
right,
there
are
subscriptions
that
you
pay
for,
for
a
certain
reason
right.
C
C
Maybe
we
can
make
those
subscriptions
more
more
freely
available
inside
of
the
large
enterprises
and
be
able
to
do
that
so
that
not
every
developer
in
the
company
has
to
go
to
a
portal
and
sign
up
right.
We
want
to
make
it
so
that
you
getting
access
to
that
software
is
a
function
of
your
relationship
and
that's
handled
at
the
account
or
organization
level
versus
you
know.
C
C
B
Know
yeah
yeah
yeah.
I
know
exactly
what
you
mean.
I
think
I
think
that's
actually.
I
think
you
kind
of
keep
touching
on
another
point
that
I
think
a
lot
of
people
find
confusing
or
don't
it's
not
really
that
they
find
it
confusing.
Is
that
I
think
they
don't
realize
it
is
that
your
subscription
is
almost
more
about
your
support
model
rather
than
it
is
about
kind
of
access
to
bits
like
in
a
sense
that
you
for
the
vast
majority
of
the
subscriptions
right.
B
The
kind
of
baseline
is
just
kind
of
access
to
the
bits
for
that
thing
and
when
I
say
just
to
be
clear
when
I
say
access
to
the
bits
right,
what
we
mean
is
like
binary
bits,
in
other
words,
things
I
can
download
and
run
right,
but
it's
kind
of
a
slang
term,
and
so,
when
you,
when
you're
kind
of
you
know
kind
of
like
all
of
them,
have
access
to
the
software
itself,
you
know
in
a
particular
class.
So
if
you
buy
an
openshift
subscription,
you
get
access
to
that
software.
B
C
It's
the
big
things
that
change,
probably
the
most
often
that
most
people
would
care
about.
Is
the
support
level
right,
I'll,
say,
support
stuff,
because
support
stuff
is
basically
three
different
variables
right.
There
is
the.
When
do
you
call
for
support?
Who
do
you
call
for
support
and
what
do
they
help
you
with
when
you
call
right?
Those
are
kind
of
the
three
things
that
go
in
the
support
bucket
and
depending
on
your
organization,
you
may
need
different
combinations
of
those.
Sometimes
the
bits
do
in
fact
change
right.
There
is
not
a
one.
C
Size
fits
all,
for
instance,
for
like
rel
content
for
some
of
the
other
products
like
like
openshift
or
rev
or
like
satellite.
They
do
have
a
one
size
fits
content
model
where
all
of
their
subscriptions
get
the
same
stuff,
but
in
in
rel
there
are
scenarios
where
there
are
either
add-ons
for
rel,
so
things
like
high
availability
or
the
resilient
storage,
and
things
like
that.
Those
are
add-ons
that
you
would
pay
additional
additional
cost
for
and
even
inside
of
rel.
C
There
are
other
things
like
we
have
like
extended
maintenance
streams
for
rel,
where,
if
you
need
to
stay
on
a
minor
release
for
a
longer
period
of
time,
that's
something
that
you
can
either
purchase
separately
or
you
can
kind
of
like
uplift
to
a
bigger
subscription
which
includes
that.
So
it
is,
the
content
does
change
from
time
to
time.
So
it
isn't
always
just
support
that
changes.
What
subscription
you
buy,
but
it
is
that's,
probably
the
big
one.
I'd
say
like
of
all
the
things
that
changes
most.
It's
usually
support.
C
B
This
is
more
like
you
know,
I'm
trying
to
build
out
this
environment.
You
know,
am
I
kind
of
approaching
it
the
right
way
and,
in
my
experience,
I've
only
kind
of
messed
around
with
that
with
really
in
the
rel
kind
of
world,
but
is
that
is
that
kind
of
more
uniform
or
is
that?
Is
it
still
mostly
rel?
Is
it
things
like
you
know?
Can
I
call
up
and
talk
about
containers
with
somebody
at
redneck.
C
B
C
So
the
definition
of
development
support
I'll
tell
you
right
now,
I
don't
like
the
terminology.
We
use
right,
it's
overloaded
terminology,
yeah
right,
but
putting
that
aside,
it
is.
It
is
a
great
program.
I
think
the
best
analogy
that
I
would
probably
draw
like
an
outside
red
hat
analogy
was
developer.
Support
is
very
much
like
an
msdn
subscription
from
microsoft
right
it's
it's
not
what
it's
not
the
subscription
you're
going
to
pick
up
the
phone
and
call
when
you
got
a
production
down
situation
right.
That's
that's!
Not!
C
C
Those
are
the
kind
of
questions
that
are
included
in
and
development
support,
which
is
which
is
awesome
honestly,
because
it
means
that
you
have
a
a
matrix
of
support
all
the
way
from
the
inception
of
your
application,
and
then
you
know,
as
that
application
grows
matures
if
it
ever
goes
into
production,
you
can
put
it
on
a
system
that
has
production
support
and
you
get
that.
You
know
that
runtime
brick
fix
support.
B
You
know
how
that's
that's
exactly
exactly.
My
point
is
right.
We
have
hundreds
of
pieces
of
software,
maybe
thousands
of
pieces
of
software
in
just
rel
right
and
there's
no
way
I
as
a
developer,
even
an
architect
can
necessarily
say
this
is
the
direction
that
system
d.
You
know
home
d
is
going
over
time,
so
you
know.
Is
there
somebody?
B
I
can
call
that's
an
expert
so
that
I
know
if
I,
if
I
kind
of
invest
in
this
part
of
the
api,
will
it
be
there
for
the
long
term
and
yeah
and
that
it
sounds
like
that
is
something
that
we
offer.
I
also
wanted
to
give
the
caveat
that
you
know
I
haven't
been
a
microsoft
developer
in
many
many
many
years,
so
all
of
that
could
have
changed.
It
was
just
kind
of
my
experience.
You
know
a
long
time
ago.
Sorry
to
cut
you
off
a
little
bit.
There.
C
B
C
The
only
thing
I
was
going
to
add
is
depending
upon
which
product
that
we
have
at
red
hat
some
products
all
for
development
support,
some
don't
right,
so
rel
offers
it
the
middleware
products
offer
it.
I
believe
openshift
currently
does
not.
I
think
I
think
that's
a
correct
statement,
and
I
think
part
of
that
is
just
because
most
people
are
doing
developmental
things
on
top
of
openshift
right,
not
the
people
who
would
need
development
level.
Support
for
openshift
itself
would
be
like
a
partner
who's.
C
Integrating,
maybe
like
someone
was
building
like
a
container
scanning
app
like
those
are
the
kind
of
folks
who
would
generally
need
development
level
support
for
for
something
like
openshift.
So
that's.
That
is
something
just
when
you
kind
of
go
down
that
route
of
development
that,
depending
on
the
product
you
may
want
to,
you
know,
talk
to
either
an
account
team
or
a
red
hat
or
just
to
understand
if
development
supports
available,
but
for
most
of
the
the
portfolio
it
is.
B
Right,
well,
I
mean
so
for
the
vast
majority
of
software
kind
of
near
open
shift,
you're
really
running
rel
right
in
the
sense
that
you
know
you're
running
a
container
which
is
actually
doing
your
thing,
and
that
container
has
you
know
rel
content.
It's
not
really
open
shift
content
per
se
right,
and
so
you
know
that
would
be
yeah
exactly
your
point,
which
I
think
is
interesting.
I
wanted
to
digress
for
a
minute.
You
know
I
felt
like
there
was
a
good
transition
there,
but
maybe
I'm
crazy.
B
D
A
couple
different
things:
first
off
I
I
have
to
admire
the
fact
that
rich
invoked
shadow
man
with
shadow
man,
mind.
If
you
know
we
went
down
this
path.
I
kind
of
like
thinking
of
that,
but
anyway,
yeah
so
level
up
is,
is
really
the
the
goal
of
level
up
is
to
reach
out
to
all
of
our
our
linux
aficionados
our
rel
aficionados
and
gurus
out
there
and
try
to
quote
unquote
level
up
their
their
domain,
expertise
right
or
their
skill
sets
and
give
them
a
path
to
get
to
kubernetes
right.
D
Which
we
we
have
some
prescribed
training
for
which
we
can
talk
about
or
the
actual
openshift
subscriptions
right.
So
we
we're
we're
doing
both
right,
so
we've
got
outreach
where,
in
essence,
on
the
subscription
front,
what
we're
saying
is
look
we
want
you
to
kind
of
put
your
toe
in
the
water
with
openshift
and
with
supported
openshift
at
that
we
want
to
give
you
a
subscription.
If
you
meet,
you
know
certain
basic
criteria
and
the
criteria
is
fairly
fairly
bait.
D
Look
basic
is
the
word
right,
so
I
mean
if
you've
got
active
rel
in
your
organization,
and
I
think
the
cutoff
is
five
active
rail
subscriptions
and
you
don't
have
openshift.
Well
guess
what
you
can.
You
can
get
a
full
year
support
for
10
quarters
of
openshift
to
try
it
out
so
level
up
your
your
organizational
agility
so
to
speak.
If
I'm
quoting
the
marketing
speak
here
right,
but
lagged
into
your
point
about
training.
D
D
D
D
D
Twenty
seven
hundred
dollars
it
won't
get
fifty
percent
off
so
log
in
with
your
rhcsa
account
number
and
you're
good
to
go.
It'll
appear
in
your
shopping,
cart
at
50
off
and
there's
also
to
to
tail
on
to
that
a
new
new
ish
red
hat
credential
certification
for
kubernetes
that
was
launched,
let's
say
august
september
somewhere
in
there,
but
it
is
red,
hat
certified
specialist
in
containers
and
kubernetes.
So
it's
got
a
longish
name,
but
we've
got
that
as
50
percent.
D
D
It's
true,
but
it
this
one's
50
off
too
right,
so
the
whole
goal.
I
mean
you
guys
know
this
better
than
I
do
right.
I
mean
when
you
look
at
kind
of
foundational
kubernetes.
What
is
kubernetes?
What
is
kubernetes
it's
distributed
linux
right,
so
we
want
to
give.
We
want
to
give
people
a
path
to
move
from
a
to
b,
and
that's
that's
what
we're
hopefully
doing
with
this
level
up
program
and
some
of
these
educational
offerings.
B
B
Openshift
is
a
convenient,
useful
bundle
of
kubernetes
and
a
bunch
of
other
stuff
right,
it's
not
fundamentally
different,
and
so,
if
you,
if
you
want
to
understand
kubernetes,
you
know
taking
that
course
is
going
to
teach
you
how
to
understand
kubernetes-
and
you
know,
and
maybe
the
variations
that
are
around
what
you
know
the
open
short
open.
I
can't
talk
now
open
shift
distribution
of
that
tool
chain,
but
it's
not
like
a
big
change
in
the
tool
chain,
and
so
I
think
that
was
a.
B
B
A
D
And
just
to
be
clear
with
that,
just
just
so
you
guys
know
so
you
know
we
were
joking
earlier
about
marine
once
in
our
hcsa,
always
orange
csa
and
frankly,
that's
the
same
with
our
hce
rhca.
All
of
our
search
right,
but
the
whole
basis
is
if
you,
if
you've
gotten
your
certification
in
the
last
three
years,
you
are
current
and
apparently
that
shows
up
on
certification,
central
and
other
places.
You
can
check
and
you
can
see
if
that's
the
case,
if
it's
beyond
that
three-year
period,
it's
non-current
not.
D
Lost
it,
it
never
expires.
It
never
goes
away
right,
it's
just
current
versus
non-current
and
you
can
always
re-up
it
and
in
fact
you
know
as
part
of
level
up.
Another
offer
is
hey
if
you're
a
non-current
rh
csa,
and
you
want
to
re-up
it
and
test
on
the
latest
and
greatest
and
take
the
the
rhcsa
exam
you
you
can
do
that.
That's
another
50
off
that
they're
giving
folks.
So
I
think
normally
it's
400
bucks.
D
A
A
D
I
think
it
is
which
I
believe
is
for
a
while
that
was
free
of
charge,
and
I
think,
if
you
do
a
google
search
on
d0101,
it
still
might
be.
There
are
what
I
can
tell
you
without
tipping
my
hand
too
much
there.
There
are
plans
to
do
exactly
what
miranda
is
talking
about.
Okay,
yeah
and
another
note
on
that
front
too.
This
certification
exam,
I'm
I'm
speaking
of
this
with
the
long
name
right,
red
hat,
certified
specialist
in
kubernetes
and
containers.
D
That
you
don't
need
to
be
an
rh
csa.
To
take
that,
so
I
mean
you
can
jump
into
that
right
now,
it's
400
hours.
I
think,
if
you
want
to
take
it
and
bam,
you
are
red
hat
certified,
so
you
can
take
it
from
your
computer.
You
obviously
don't
have
to
go
to
a
red
hat
training
facility
to
do
it
with
with
code
which.
B
D
Perfect
segue,
and
just
just
to
close
out
on
my
thinking
on
this
you
I
mentioned
the
50
off
the
course.
The
d0180
there's
not
obviously
a
whole
lot
of
in-person
training
going
on
in
the
world
right
now.
Hopefully
that
changes
soon
as
we
all
get
shots
in
our
arms
right,
but
so
so
gls
landing
to
your
point.
They
they
really
have
been
ramping
up
their
their
online
efforts,
and
this
this
particular
offer
here
it
court.
It
relates
to
that.
D
So
the
two
formats
that
you
can
get
this
50
off
in
are
are
what
they
call
online
education.
I
believe
it
is
where
literally
you
get
all
of
the
course
curriculum
and
you
get
all
of
the
video
feeds
and
webinars
and
labs
and
other
things
and
you've
got
90
days
to
take
it
right.
So
you've
got
a
fair
amount
of
time
to
take
it,
and
then
the
the
other
format
you
can
take
is
what
they
call
video
classroom,
which
is
literally
a
video
of
the
four
day
class,
just
kind
of
asynchronous
right.
B
So
we
did
have
a
question
on
the
chat:
that's
probably
a
little
bit
more
for
rich,
but
my
guess
is
you're
not
going
to
know
the
answer
to
this,
but
it
basically,
the
question
was
one
of
the
challenges
that
the
audience
member
had
was
when
they
kind
of
call
in
for
support.
They
seem
to
get
routed
to
weird
time
zones.
A
B
Yes,
good
point
and
so
and
as
a
result
doesn't
have
as
kind
of
timely
a
response
as
they
would
prefer.
I'm
just
curious
is
that
like
do
you
know,
if
there's
is
there
regions
of
excellence
as
it
were
around
support,
because
knowing
how
red
hat
engineering
works?
That
wouldn't
surprise
me
like
we
have.
C
So
it's
it's
kind
of
a
little
bit
of
all
of
that
right.
So
one
of
the
things
that
support
and
engineering
try
to
partner
on
really
well
is
making
sure
that,
within
a
particular
meta
region,
right
so
think
of
north
america,
latin
america,
europe,
middle
east
and
africa
and
aipac,
we
try
to
have
support
personnel
as
well
as
qe
personnel,
as
well
as
engineering
personnel
kind
of
all
co-located
right.
So
if
a
customer
calls
in
with
a
critical
issue,
we
can
kind
of
go
soup,
the
nuts
you
know
in
that
time
zone.
C
We
try
that
as
best
as
possible
that
isn't
universally
held,
because
some
of
our
products
are
incredibly
specialized.
Think
of
things
like
our
identity
products
right.
They
are
some
incredibly
complex
products,
but
that's
something
that
support
and
engineering
try
to
aim
for.
So
that's
what
will
happen
a
lot
of
times.
Is
that
they'll
they'll
route,
your
support
case
to
to
to
the
area
that
has
the
most
amount
of
expertise.
If
it's
something
like
rel,
we
have
rail
covered
in
every
time
zone
across
the
planet
right.
C
If
it's
a
a
newer
product
or
a
more
specialized
product,
they
may
have
expertise
in
a
certain
region,
so
they
may
send
that
ticket
there
first,
even
though
that
might
be
outside
of
the
time
zone
of
the
person
who
opened
the
case.
It
is,
I
wouldn't
say
it's
hit
or
miss,
because
that
kind
of
sounds
bad,
but
it
does
vary
by
product.
B
A
Now
anyways,
so
just
a
real,
quick
technical
note,
it
looks
like
discord
like
there's
some
issues
with
the
chat
aggregation.
So
I
wanted
to
mention
this
pinhead
over
in
discord.
Chat
says:
there
is
a
time
zone
field
you
should
make
sure
is
set
for
you
jp
dade,
so
make
sure
that
that
time
zone
field
is
actually
set
for
us
eastern
time
double
check
next
time
you
call
in
or
just
call
in
or
email
in
and
oh
it
is
okay.
Great,
that's
weird.
B
Yeah
well
or
it's
tourist's
point,
if
you're
asking
about
like
we
can
only
have
you
know
so
much
expertise
in
any
given
location
right.
So,
if
you're
asking
some
deep
dark
question
about
how
you
know
aj
proxy
works
under
you
know
this
kind
of
particular
unusual
condition:
you're
gonna
get
to
the
expert
which
may
or
may
not
be
your
time
zone
versus.
You
know
a
more
generalized
question,
like
you
know
the
things
I
would
ask
you
know
which
is
going
to
be
able
to
answer
by.
B
You
know
a
grammar
school
kid
so
yeah,
so
that
was
kind
of
I
like.
I
said.
I
thought
it
was
a
interesting
question,
so
I
wanted
to
kind
of
bring
it
up.
The
other
thing-
and
this
is
a
little
bit
to
gordon
somebody
else-
mentions
in
the
chat
as
well-
that
their
company
actually
offers
a
you
know
a
bonus
for
getting
to
certification
on.
They
actually
specifically
talk
about
aws,
but
I
was
just
kind
of
curious.
B
D
I
you
know,
I
can't
speak
to
a
specific
instance,
but
you
hear
it.
You
know,
anecdotally,
all
the
time
right
where
our
partners
and
our
even
customers,
whatever
else
I
mean
the
most
successful
ones,
are
the
ones
who
have
this
domain
expertise
in
place.
So
I
know
that
I
want
to
say
it
was
accenture
who
had
a
similar
program
in
place.
D
Don't
quote
me
on
that,
but
there's
I
know
I've
seen
several
instances
where
it's
exactly
that
right,
so
borrowing
this
aws
model,
but
but
for
red
hat,
where
it's
like,
hey
look,
let's
get
our
guys
up
skilled
to
do
that.
You
know
once
you
hit
this
threshold,
we'll
give
you
bonus
x.
Once
you
get
this
threshold
bonus
y
there's
something
out
there
called
red
hat
learning
subscriptions
right
and
they
even
offer
like
a
seven
day
free
trial
on
this.
It
literally
just
opens
up
the
entire
curriculum
to
an
individual
right.
D
Now
you
can
get
enterprise
licenses
too.
I
think,
but
I
want
to
say
it
runs
like
six
thousand
dollars
for
the
basic
and
another
thousand
dollars
on
top
of
that,
for
the
more
advanced
which
gives
you
even
so,
seven
thousand
dollars
gives
you
access
to
all
of
our
certifications
exams,
for
instance
right,
so
you
have
in
essence
red
hat
training
in
a
box
right
there,
your
year-long
subscription,
you
know
rich,
was
talking
about
different
types
of
subscriptions
earlier.
D
B
And
I
think
that
also
just
launched
like
a
recently
a
not
a
like,
like
they
just
reorganized
the
program.
So
if
you
have
looked
at
it
in
the
past,
I
think
it
also
very
recently
changed.
So
you
know
it'd
be
worthwhile
checking
it
out
again,
like
I
think
I
remember
seeing
the
like.
You
know,
announcement
or
whatever,
like
within
the
last
month
or
two.
D
D
C
C
I
I
need
something
new
like
I
want
to
do
the
next
big
thing
and
in
my
head,
I'm
looking
around
I'm
like
well
like
what
I
want
to
get
certified
on,
like
what
investment
do
I
want
to
make
in
myself-
and
I
was
like
you
know
what,
if
I
get
my
rhce
that'll
that'll,
definitely
help.
If
I
want
to
go
work
for
red
hat
right
and
then
I
was
like,
if
I
get
the
rhca,
that
definitely
will
help
right
right.
C
So
yes,
I
I
mean
I,
I
went
ahead
and
I
made
that
investment,
self-studied
and-
and
you
know,
still
took
advantage
of
getting
all
five
little
certification
courses,
the
five
that
you
need
for
rel,
and
then
it
was
kind
of
funny
that,
like
like
three
weeks
after
I
got
my
rhca
now
granted
your
mileage
may
vary.
But
three
weeks
after
getting
my
rhca,
my
solutions,
architect
was
like
hey.
You
wanna
go
work
for
red
hat,
so
so
I
got
an
immediate
return
on
investment
on.
C
On
that
investment
I
made
in
those
those
training
courses,
but
you
know,
given
that
the
the
learning
subscription
you
know
gives
you
access
to
all
the
all
the
training
right
which,
at
the
time
I
had
to
go,
spend
money
out
of
pocket.
Take
my
own
like
pto,
to
go
and
actually
sit
in
the
class
and
get
trained.
C
Now
I
can
you
know
if
I
had
a
learning
subscription,
I
could
do
that
from
home
right
after
hours,
you
pair
that,
with
like
the
the
zero
cost
developer
subscription,
which
gives
you
access
to
the
bits
right,
you
can
build
your
home
lab,
you
can
work
on
stuff
in
a
real
environment.
So
there's
there's
a
whole
bunch
of
goodness
that
that
that
you
get
that'll
help
further.
Your
career
learning
subscription
is
one
of
them
and
I
like,
like
I
said
I
wish
it
was
there
10
years
ago,
yeah.
D
Funny
side
note
on
that:
it's
it!
You
know
back
10
years
ago,
12
years
ago.
That's
when
I
was
still
with
this
gls
marketing
and
we
rolled
out
rhca
red
hat,
certified
architect
and
the
program
we
put
in
place
was
something
called
race
to
rhca,
and
so
we
we
wanted.
We
had
all
these
grand
plans
right
and
we
wanted
to
offer
like
one
of
the
first
rhcas,
like
a
corvette
for
a
year
with
with
a
shadow
man,
logo
and
an
rhca
logo
on
the
front,
and
we
had
all
this
stuff
lined
up.
D
A
Yeah,
so
that
being
said,
this
some-
I
forget
the
name,
but
someone
brought
up
in
chat,
something
that
cncf
does,
and
I
only
know
this
because
I'm
a
cncf
ambassador
and
they
allow
for
multiple
retakes
right.
So,
if
someone's
paying
400
to
take
this
exam
and
they
you
know
bomb
it
for
whatever
reason
bad
night
sleep
or
whatever,
they
have
to
pay
another
400
to
take
it
again,
and
I'm
wondering
if
that's
something
I
could
feed
back
into
the
gls
pipeline
to
be
like
hey.
B
B
D
B
B
Yeah
I
just
it's
funny.
I
haven't
taken
very
many
certification
exams
like
that,
but
when
I
was
doing
the
practice
test
for
one
my,
I
was
having
a
hard
time
with
it.
My
wife
just
kept
saying
you
need
to
learn
to
think
inside
the
box
like
and
what
I
specifically
remember
is
that,
like
I
was
answering
questions
the
way
this
technology
worked
in
the
real
world,
not
the
way
it
was
intended
to
work.
So
there
were
bugs
right.
B
I
had
been
using
this
stuff
a
long
time
and
I
knew
where
the
bugs
were,
and
so
I
automatically
kind
of
you
know
pivoted
around
those
bugs
because
you
had
to
do
workarounds
or
whatever,
and
so
I
would
get
the
questions
wrong
on
the
exams
because
I
was
taking
into
account
the
bugs.
So,
yes,
I
have
a
little.
I've
always
had
a
bit
of
a
challenge
with
certification
exams.
So,
but
who
knows?
I
wanted
to
go
back
a
little
bit
to
subscriptions
and
specifically
mention
rich.
B
C
So
subscription
watch
is
a
new
application
that
my
team
maintains
that
provides
basically
fleet
wide
visibility
into
the
usage
of
a
product.
So
one
of
the
one
of
the
big
things
that
we've
we've
run
into,
especially
with
our
larger
customers,
is
they're
like
how
much
am
I
using?
Where
am
I
using
it
at
right
and
if
you
think
of
tools
like
red
hat
satellite,
which
a
lot
of
our
large
customers
use
those
tools
operate
more
or
less
autonomously
from
the
custom
report
right?
C
So
if,
if
we
go
back
to
kind
of
what
I
said
before
about
how
we
want
to
address
those
personas
right,
I
want
to
be
able
to
send
a
person
who
doesn't
know
the
intricacies
of
how
the
technology
works.
I
want
to
be
able
to
send
them
to
a
portal
and
say
this
is
a
dotted
green
line.
That
shows
you
what
you
own
and
here's
a
chart
that
shows
you
what
you've
used.
Are
you
above
that
line,
or
are
you
below
that
line?
C
That's
what
subscription
watch
does
so
today
it
exists
for
red
hat
enterprise
linux
and
for
openshift
we're
in
the
process
of
expanding
it
out
for
the
rest
of
the
portfolio.
So
if
you're
an
openshift
customer
you
go
to,
you
know
oc
ocm,
you
manage
your
openshift
clusters.
You
have
to
do
nothing
for
your
subscription
experience.
Just
use
openshift
right.
We
own
ocm.
We
own
subscription
watch,
we
just
paired
the
two
together.
C
So
instead
of
having
to
do
things
like,
oh,
I
got
to
go
and
title
this
system
or
I
got
to
go
and
title
this
cluster
just
use
the
software
we'll
visualize,
how
much
you're
using
inside
of
subscription
watch
and
you
go
look
at
that
dotted
green
line.
If
you're
above
that
line,
you
might
want
to
have
the
conversation
with
your
account
team
you're
below
that
line.
You're
good
right.
C
We
built
integrations
into
other
products
like
our
customer
portal
as
well
as
satellite,
so
that
those
tools
can
now
send
their
inventory
up
to
subscription
watch.
So
if
I'm
a
you
know
large
customer,
I
finally
have
the
ability
to
say
or
see
here's
how
much
rel
I'm
using
here's.
The
type
of
realm
I'm
using
is
a
physical
virtual.
Is
it
running
on
the
public
cloud
on
which
public
cloud
is
it
running?
I
now
have
a
dashboard
that
gives
me
that,
and
we
show
that
to
you
over
time.
C
I
think
we're
required
to
hold
two
or
three
years
of
data.
So
now
you
can
actually
look
at
well.
How
has
my
usage
changed
over
time
right?
Am
I
going
up
into
the
right,
or
am
I
going
you
know
down
into
the
right
like
those
are
the
kinds
of
questions
that
you
know
empower
many
of
the
transactions
that
we
have
with
you
like,
when
your
account
team's,
like
hey,
it's
time,
to
do
a
renewal?
How
much
rail
you
got!
C
That's
another
technology
that
we
built
really
to
to
make
life
easy
for
the
operator
right.
So
those
two
technologies
live
somewhat
in
an
ecosystem
together,
like
you,
don't
have
to
use
them
together,
but
they
work
really
well
together,
because
what
simple
content
access
does
is
it
makes
it
easy
for
the
operator
to
just
operate
register
the
system
install
the
bits
you
don't
have
to
worry
about.
Attaching
entitlements,
that's
awesome
so,
but
we
still
need
to
show
people
how
much
you're
using
and
that's
what
subscription
watch
does.
B
B
C
C
Right,
go
fix,
stuff
and
don't
don't
come
out
until
you
got
something?
That's
awesome
right
right,
so
so
we
did
so
and
we
we
went
off
and
we
built
subscription
watch
and
we,
you
know,
we
built
simple
content
access
and
we
made
those
capabilities
available
to
the
to
the
field.
Subscription
watch
itself
lives
on
the
same
platform
and
infrastructure
as
insights
right.
So
my
team's
goal
again
is
to
basically
we
joke
about
it,
but
we
say
we
make
subscription
management
subscription
non-management
right
like.
C
If
I
do
my
job
right,
you
shouldn't
know
I
exist,
and
what
that
means
is
that
we
want
to
integrate
into
the
tools
that
you're
already
using.
So
if
you're
using
red
hat
insights,
you
are
using
subscription
watch,
we
just
pull
all
that
information
out
of
the
insights
database
automatically
right.
Actually,
we
don't
pull
the
information
out.
It's
actually
the
share
same
database.
We
just
look
at
it
differently.
So
from
a
technological
perspective,
don't
think
of
subscription
watch
as
being
another
piece
of
software.
C
You
now
have
to
build
into
your
operational
processes
and
have
to
learn
how
to
use
think
of
it,
as
as
I'm
using
other
red
hat
stuff,
it
will
show
up
in
subscription,
watch
and
really.
Your
goal
is
to
log
into
subscription
watch
from
time
to
time,
and
does
it
look
right?
Does
it
not
look
great
and
even
that
we're
going
to
make
that
go
away
because
we're
building
out
some
comprehensive
notifications?
So
we
can
just
fire
you
a
notification.
C
B
B
Just
so
I
can
give
some
feedback,
and
so
I
use
the
developer
sub
to
get
access
to
rel,
for
example,
and
I
know
for
me
something
a
subscription
watch
would
actually
be
super
handy
because,
because
I
churn
vms
with
rel,
so
fast
a
lot
of
the
time
that
kind
of
getting
a
sense
of
like
you
know.
Why
am
I
getting
this
error
right?
If
there's
a
quick
and
easy
way
to
say?
Oh,
it's
because
you
know
you're
using
300
subscriptions
and
you
only
have
access
to
10..
B
That's
a
that's
a
good
piece
of
data.
You
know,
so
that's
a
you
kind
of
getting
a
sense
of
that.
Overall,
you
know,
consumption
even
even
kind
of
as
a
single
person
right
is
actually
really
useful,
because
it's
very
hard
to
wrap
your
head
around
where
all
that
stuff
is
allocated
at
any
given
time,
at
least
for
me,
I
don't
know-
maybe
I'm
just
slow
it's
it's
actually.
C
It's
it's
a
use
case
that,
like
one
of
my
like
very
next
products
like
if
I
look
at
my
wrote,
matt
post
summit,
because
you
know
how
red
hat
works
right
there-
everything
you
do
up
till
summit
yeah
the
month
after
summit
for
you
to
catch
your
breath
and
then
you
basically
start
preparing
for
the
next
summit
right.
But
what
one
of
the
products
that's
really
high
on
my
roadmap
is
the
developer
products
right.
C
I
want
to
make
sure
that,
because
they're
so
critical
to
red
hat's
future
that
we
represent
those
in
subscription
watch
and
one
of
the
things
like
from
a
use
case
perspective.
A
big
pain.
Point
of
our
subscription
tools,
as
they
have
historically
existed,
has
been
dealing
with
high
churn
environments
right
because
historically,
you've
had
to
register
a
system
entitle
the
system
and
then
keep
track
of
those
entitlements
over
time.
C
C
C
So
so
yeah,
so
this
sort
of
so
the
big
thing
from
from
my
perspective
is
I
want
to
make
it
so
that
the
penalty
for
getting
it
wrong
is
next
to
nothing
right.
So
if
I'm
assistable
and
I
forget
to
delete
a
system
out
of
inventory,
so
what
right
like
at
the
end
of
the
day,
so
what
right?
I
want
to
visualize
to
you
that
you
haven't
done
it,
but
I'm
also
not
going
to
penalize
you
for
not
having
done
it
right
right.
C
So
the
first
thing-
and
this
is
especially
for
the
developer
program
right-
that's
going
to
be
a
important
capability-
is
that
new
subscription
experience
we
deliver
via
simple
content
access.
It's
only
available
to
sat
customers
today,
we
plan
to
release
it
at
summit
for
our
customer
portal
customers
for
our
non-satellite
customers.
Okay.
So
what
that
means
is
that
as
a
developer,
you
go
to
developers.reddit.com
you
sign
up
for
the
developer
program.
You
get
your
16
entitlements
of
rel
go
ahead
and
deploy
the
systems
they'll
show
up
in
subscription.
C
C
Without
simple
content,
access,
we'll
tell
you,
hey,
dude,
you're
out
of
entitlements,
you
got
to
go,
find,
go,
find
the
one
that
needs
to
give
up
an
entitlement
and
you're
like
dude.
This
sucks
I'd
rather
go
use.
Something
else
right.
That's
usually
the
response
that
you
get
right.
Most
people
don't
go
spelunking
for
entitlements.
Most
people
are
like
this
is
friction
I'll,
just
go
use
something
else.
C
Whereas
when
simple
content
access
is
turned
on,
go
ahead
register
that
17th
system,
we
still
give
it
access
to
content
the
next
morning
you
log
into
subscription
watch
you'll
see
you
have
17
systems
consuming
content
and
you
can
sort
them
by
which
one
was
the
last.
You
know
one
that
checked
in
what
have
you?
The
great
thing
that
we
do
in
subscription
watch
is
we
do
auto
call
out
old
systems.
So
let's
say
you
did
you
know
you
did
delete
a
system.
You
threw
away
the
vm,
but
you
didn't
properly
unregister
it.
C
C
C
I
can't
wait
for
summit
to
get
here
honestly
because,
like
our
satellite
customers
have
had
simple
content
access
since
last
summit
and
they
love
it
yeah
right,
they
absolutely
love
it
because
again
it
lets
operators
operate
right,
like
you,
don't
have
to
have
a
phd
in
red
hat
subs
to
build
a
freaking
rail
server
right
right.
That's
that's!
That's
it!
Right,
like
I
have
a
phd
in
red
subs
because
I'm
financially
compensated
to
have
that
phd
right,
but
most
people
aren't
so
so
that's
that's
really
my
goal.
My
goal
is
register
and
run
connect.
C
The
box
enable
the
repos
you
need
if
you
need
anything
beyond
the
you
know,
defaults
and
just
install
the
bits
right.
Let
us
worry
about
visualizing
how
many
subscriptions
and
skus
and
entitlements
and
stuff
that
you're
using
because
we
know
all
the
dark
art
to
count
all
that
stuff
and
that
shouldn't
be
a
blocker
for
you
using
the
technology.
B
Yeah
yeah,
I
I
100
agree.
I
wanted
a
sidebar
just
a
little
bit
because
someone
in
the
chat
brought
up
that
if
you
do
buy
the
learning
subscription
you
get
two
retakes,
I
think
per
exam
is
the
way
they
describe
it.
Okay,
obviously
I'm
reading
something
in
the
twitch
chat.
So
you
know
your
mileage
may
vary.
You
know,
go
check
it
yourself,
but
it
does
sound
like
that.
There
are
retakes
built
into
the
subscription
or
the
learning
subscription
there.
You.
A
B
Yeah,
don't
laugh
at
it,
it's
required
so
serious
it.
Actually,
it
is
kind
of
like
a
subscription.
In
fact,
the
more
shows
you
come
to
the
more
points
you
get,
and
so
you
know,
if
you
ever
use,
slashdot
or
reddit,
you
know
which,
basically,
you
can't
work
in
tech
and
not
have
done
those
things
you
know
so
up
voting
down
voting.
B
You
know
the
idea
is
that
people
are
interested
in
collecting
points,
and
so
we
decided
to
distribute
points
for
the
show,
and
currently
our
leaders
are
narendev
with
4
400
points
and
netherlands
hackam,
as
we've
decided
to
pronounce.
That
is
at
4300
points.
Sorry,
I
was
looking
in
another
window
for
the
the
cut
and
paste
for
today's
show,
which
should
be
that
it's
also
on
the
screen
in
case.
You
see
it
there,
but
it
I
just
put
it
into
the
chat.
B
Hopefully
that's
getting
really
streamed
around
and
then
we
have
noah
friction
with
3
500
points,
joe
fuzz,
with
2300
points.
Detective
conan
kudo,
who
I
didn't
see
today
with
900
points,
but
who's
been
a
pretty
new,
strong,
new,
regular
and
bacon
fork.
Who's
also
been
a
strong
new
regular,
but
I
also
didn't
see
in
the
chat
today.
B
I
have
to
be
careful
about
the
pronunciation,
but
other
than
that
it
is
a
very
good
name,
so
yeah.
So
thanks
so
much
as
always
for
coming
collecting
points.
I
I
reiterate
that
we
are
so
close
to
being
able
to
make
them
more
than
just
intrinsic
value
points,
and
you
know
we
will
hopefully
be
able
to
continue
that
imminently
and
yeah.
So
there's
the
points
for
today.
I
threw
the
way
to
get
the
points
for
today's
show
in
the
chat.
B
So
please
see
that
there
or
it's
on
the
screen
right
now.
Basically,
you
just
go
to
that
form
and
fill
it
in
with
this
particular
code.
I
will
reiterate,
because
this
is
also
getting
closer.
You
may
see
these
codes
elsewhere
on
the
kind
of
red
hat
properties.
I
don't
really
want
to
say
the
internet,
but,
and
so
you,
if
you
see
those
codes
elsewhere,
you
can
also
submit
those
codes.
If
you
submit
an
issue
on
the
repo
or
you
submit
a
pr
or
you
know
basically
there's
a
whole
activities.
B
Page
excuse
me,
you
know
you
can
there's
other
ways
to
earn
points.
Besides
attending
the
show,
you
can
also
go
and
watch
past
shows
and
submit
points
for
those,
so
that
was
the
internet
points
which
we
always
like
to
hit
and
we
try
to
hit
within
the
literal
level
up
hour.
But
chris.
What
was
the
question
that
you
found.
A
C
Grab
grab
a
glass
of
your
favorite
beverage
and
and
and
let
uncle
richie
take
you
on
a
trip
back
into
the
subscription
wayback
machine,
so
gosh
we're
gonna
start
all
right.
So
all
right,
yeah,
I'm
I'm
going
to
do
this
so
long.
Long
time
ago,
in
a
red
hat
far
far
away,
we
used
to
offer
red
hat
subscriptions
based
solely
on
physical
systems.
Right
like
we're
talking
in
the
world
pre-virtualization
right.
So
you
go
buy
your
old
like
dell
poweredge
2650,
you
bought
a
rail
sub
off.
C
You
went
right
and
back
then
subscription
management
was
really
not
a
thing
because
it
was
just
simple.
Math
you
counted
pieces
of
hardware.
Hermes
is
a
hardware.
You
had
that's
how
many
subs
you
purchased
super
easy.
You
didn't
need
a
phd
in
subscription
management.
Ged
and
subscription
management
was
about
all
you
needed
at
that
time.
Right
then,
virtualization
happened
right
and
folks
were
like
well,
hey,
wait
a
minute
like
yeah.
While
I
can
take
those
subscriptions
I
purchased
for
that
dell
2650
and
use
them
on
my
virtual
machine.
C
C
Let's
introduce
virtual
style
subscriptions
and
those
are
subscriptions
that
were
purchased
based
on
a
hypervisor
right,
so
you
you
bought
it
for
a
hypervisor
and
in
addition
to
providing
access
to
the
hypervisor,
you
got
a
certain
number
of
guests
on
top
of
it
right
and
back
in
the
day,
this
was
1,
4
or
unlimited
right.
Yes,
there
were
some
yeah,
I'm
I'm
pre-dating
you.
This
is
like.
I
said
this
is
like
old,
red
hat
yeah
yeah.
This
was
back
before
shadow
man,
possibly
even
had
a
shadow
like
this
is
old
stuff.
C
So
then,
as
virtualization
became
more
common
and
more
prevalent
right,
we
we
kind
of
matured
those
subscriptions,
and
now
we
move
to
what
we
have
today.
What
we
call
the
virtual
data
center
style
subscription,
which
is
you
purchase
it
for
a
two
socket
two
sockets
at
a
time
you
can
stack
them
to
use
it
for
four
socket
boxes
and
they
still
include
an
unlimited
number
of
virtual
machines.
C
So
we
have
what
we
call
convertible
subscriptions
you'll
also
hear
them
call
either
or
subscriptions,
which
will
cover
either
a
two
socket
system
or
two
virtual
machines
or
cloud
instances
right
and
those
subscriptions
are
portable.
They
can
be
used
on
premise
and
in
the
in
the
public
cloud.
So
that's
the
really
the
major
difference
between
the
two.
So
if
we
go
back
to
you
know
the
five
things
that
make
up
a
red
hat
subscription
right.
C
C
C
D
C
C
Well,
two
socket
rail
subscriptions
probably
needs
to
come
in
premium
standard,
self-support
right,
so
that's
times
three
already
right
right,
then
I
need
a
one-year
version,
a
two-year
version,
a
three-year
version,
a
four-year
version,
a
five-year
version,
crap
right,
15,
right,
right,
okay,
I
need
to
offer
some
to
be
sold
and
supported
by
red
hat,
some
to
be
sold
and
supported
by
the
oems
double
that
number
right.
So
you
could
see
like
just
bring
in
a
singular
subscription
to
the
market.
C
A
single
offering
to
the
market
will
sometimes
lead
to
50
60,
100,
new
skus
being
created
right
and
that
complexity
has
historically
matriculated
through
all
of
the
tooling
all
the
way
down
to
the
poor
operator
who's.
Like
do
I
attach
rh003
or
rh004
right
right
again.
That's
that's!
That's
why
it's
complex
right!
It's
complex
because,
as
we
change
those
five
things
that
make
up
a
subscription,
it
permea
makes
the
permutations
of
subscriptions.
We
have
to
create.
C
My
job
is
to
insulate
the
operator
from
all
of
that
madness,
because
it's
madness
like
I
I'm
not
even
going
to
try
to
defend
it,
it's
madness
right!
So
for
me,
I
want
to
make
it
so
that
log
into
a
tool
like
subscription
watch
and
be
able
to
see
the
types
of
rail
you're
using
like
in
subscription
watch.
C
We
will
visualize
the
difference
between
rel
running
on
a
physical
system
versus
a
number
of
virtual
machines
that
are
on
a
hypervisor
like
we
will
show
you
that
differently,
because
it
does
matter,
it
doesn't
matter
from
like
what
repo
do
I
access?
They
all
are
rel.
You
have
access
to
rel,
repos
doesn't
matter
if
that
aspect,
but
it
does
matter
at
the
you
know.
C
A
C
A
C
C
Virtualization
came
along
and
honestly
complicated
a
lot
of
the
things
around
subscription
management,
and
we
made
attempts
over
the
years
to
try
to
bring
some
sanity
to
the
the
very
dynamic
world
of
virtualization
and
understanding
what
people
are
using
and
the
tools
kind
of
became
complex
in
a
process.
They
didn't
really
become
complex
by
design.
C
If
you're
in
a
developer
program
to
me
you're
a
paying
customer
right,
you
might
not
be
paying
me
in
cash
but
you're,
paying
me
your
time,
you're,
paying
me
an
adoption,
you're
paying
me
and
all
those
other
things
that
still
matter
to
red
hat
right.
So
if
our
tools
are
providing
friction
to
you,
that's
bad
right.
So
we
we
now
have
to
evolve
the
tools
to
solve
the
goal
of
helping
people
understand
what
they're,
using
where
they're
using
it
and
how
much
of
it
that
they're,
using
while
also
not
getting
in
their
way
right.
B
Well,
I
think
the
other
thing
too,
that
people
forget
about
with
subscription
manager
right
is
that
red
hat
was
actually
a
very
early
adopter
of
the
subscription
concept
for
software
and,
as
a
result
right
they
built
a
very
early
implementation
and,
like
all
legacy
software,
the
reason
we
call
it
legacy
software,
even
if
it's
six
weeks
old,
is
because,
for
some
reason
we
don't.
You
know
the
architecture
of
the
design
of
it.
B
Whatever
is
hard
to
adapt
to
the
changes
in
business
or
technology
or
whatever
it
is
that
you
need
to
adapt
it
to
and
subscription
manager
is
going
to
suffer
from
that,
but
it
also
suffers
from
a
secondary
type
of
legacy.
Right
is
that
there's
a
whole
mess
of
business
processes
that
go
around
it
right?
So,
as
a
result,
you
can't
it's
not
just
evolving
the
software
over
time,
but
it's
also
evolving
the
business
processes
and
honoring.
You
know
you
were
talking
about
five-year
skus,
you
know,
I
don't
even
know
there
might
even
be
longer
ones.
B
I
don't
even
know
that
you
know
so
that
you
have
to
honor
all
those
old
ones
in
the
new
software
as
well.
So
you
can't
just
rip
and
replace
your
subscription
management
like
you
could
like.
You
could
actually
do
with
like
your
web
server
right,
which
you
you
know.
If
you
decide
you
want
to
get
away
from,
you
know,
apache
and
move
to
nginx.
That's
in
a
lot
of
ways
a
lot
easier
to
do,
because
you
don't
have
to
evolve
business
processes
around
it
right.
B
C
Yeah
I
mean
my
team.
We
spend
a
lot
of
time
working
with
the
the
back
office
people
who
bring
the
offerings
to
market
right
and
we
help
them
through
that
process
right
because,
like
our
front
end
and
back
end
weren't
connected
for
a
while,
so
there
were,
there
were
scenarios
where,
like
they,
there
were
people
who
would
build
offerings
that
just
like
fundamentally
didn't
work
with
our
subscription
tools.
C
Right
and
we
didn't
have.
You
know
the
processes
and
the
checks
and
balances
in
place
to
ensure
that.
So
now,
that's
what
I
mean
like
my
team,
like
in
the
history
of
red
hat
right,
that's
a
20
plus
year
old
company
right,
my
team's
been
around
for
two
right
and
in
those
two
years
you
know,
we've
we've
taken
a
an
advisory
level
approach
to
a
lot
of
the
back
office
functions
at
red
hat
like
hey.
This
is
how
this
is
going
to
interact
with.
C
C
So
maybe
we
need
to
build
a
tool
to
count
it
right,
because
that's
because,
like
the
business
is
going
to
evolve
right,
like
today,
red
hat
sells
most
of
their
stuff
through
you
know
yearly
subscriptions,
but
that
isn't
universally
true,
because
I
can
go
through
the
various
cloud
providers
and
purchase
red
hat
stuff
by
the
hour
right
or
you
know,
business
models
may
change
to
something
else
in
the
future
and
we
have
to
make
sure
that
we
have
the
the
tooling
and
stuff
in
place.
So
it
is
kind
of
this
in
the
end.
C
Experience
that
we're
really
looking
at
from
the
from
the
point
where
you
know
some
vp
is
like.
I
want
to
sell
something
to
the
point
where
you
know
I
have
to
express
to
you
know
the
person
who
bought
the
thing.
How
many
of
the
thing
are
they
using
like?
That's
that's
an
entire
like
life
cycle
that
we
now
look
at
holistically,
whereas
in
the
past
we
looked
at
it
very
separately,
like
skus
were
done
over
here
and
product
and
engineering
was
done
over
here
and
you
know,
reporting
was
done
honestly.
C
We
pushed
that
down
to
sales
sales
figured
out,
and
that
was
how
things
were
done
and
that's
you
know,
that's
not
something.
That's
going
to
be
scalable.
So
now
like
we're
working
with
you
know
the
openshift
bu
I
mean
I,
I
think
we
we're
basically
indentured
to
them
all
the
time,
but
and
that's
just
because
they're
they're
off
they're
offering
all
kinds
of
new
stuff
that
needs
to
be
counted.
C
So
we
work
with
them
very
heavily
to
understand
like
here's,
how
this
thing's
going
to
go
to
market
here's,
how
it's
packaged,
here's,
how
it's
sold!
Here's,
how
it's
metric,
here's,
how
it's
metered
so
that
you
know
on
day
zero
when
that
new
product
goes
out
of
the
door.
We
want
to
be
able
to
say
yes,
mr
customer,
it's
super
easy
to
set
up
and
use
and
you'll
be
able
to
understand
how
much
of
it
you're
using
on
day
one
right
and
that's
that's!
That's
the
goal.
C
C
You
should
be
able
to
instantiate
that
red
hat
product
without
friction
be
able
to
see
how
much
of
that
red
hat
product
you're
using
and
be
able
to
see
that
over
time,
and
if
I
can
do
that,
along
with
the
rest
of
the
product
managers
and
business
analysts
on
my
team,
then
we've
had
a
home
run
and
honestly,
if
we
do
that,
you'll
probably
never
see
me
on
this
call
again
because
I
won't
exist.
People
will
be
like
rich
who,
but
that's
that's
my
goal.
A
B
Don't
think
you
should
gloss
over
the
fact
of
the
having
the
kind
of
bird's
eye
view
of
all
that
that
you
mentioned
right,
so
it's
not
only
frictionless
access
and
getting
it
connected
and
getting
it
engaged
and
stuff.
But
it's
also
that
bird's
eye
view
of
what
am
I
using
is
also
hugely
important
and
difficult
to
to
present.
C
I
mean
we
have.
We
have
customers,
and
I
mean
I've.
I've
worked
with
some
of
red
hat's
biggest
customers
where
just
getting
the
count
of
things
that
they
are
running
is
a
multi-month
process.
Oh
yeah,
right,
yeah
like
and
I'm
just
I'm
just
sitting
there.
Thinking
like
it's
something
that
has
to
be
done,
yeah,
but
does
it
gotta
take
months?
I
think.
B
C
So
so
I
mean
it's,
it's
a
it's
a
real,
it's
a
real
challenge
right.
So
what
I'm
trying
to
do
is
I'm
trying
to
make
it
so
that
one
shorten
that
amount
of
time
right
if
I
can
make
that
as
close
to
real
time
as
possible,
that's
better
one,
because
it
helps
out
our
sales
organization.
Yes,
we
have
one
of
those.
C
I
have
to
care
about
them,
but
it
also
helps
out
the
customer
right
because
at
some
point
some
forces
admin
is
going
to
be
told,
go
count
the
things
right
and-
and
that's
it's
like
really
so
in
addition
to
patching
these
servers
building
these
servers
dealing
with
the
compliance
people
down
my
neck.
I
also
need
to
go
grab
inventory.
Oh
okay,
great!
That's
going
to
suck
right!
So
if
I
could
take
out
that
one
particular
pain
point
which
is
a
particularly
large
one
for
some
of
our
biggest
customers,
that's
I
mean
that's.
A
C
D
Oh
just
in
30
seconds
or
less
just
to
reiterate
what
I
said,
which
is
look
guys
if
you're
interested
in
level
up
open
shift
subscriptions,
you've
got
five
active
rail,
subs
or
more,
and
it
is
five.
I
double
checked
and
no
open
shift.
You
know
go
to
that
landing
page
that
we
talked
about.
I
think.
First,
you
probably
posted
it
there
you
go.
Thank
you
and.
D
C
So
if
you
had
a
legit
bug,
just
open
up
a
legit
bug,
my
team
gets
them.
If
you
have
feedback,
that's
not
necessarily
bug
related
email
me
directly,
I'm
rich
at
redhat.com.
It
took
me
ten
years
to
get
that
one.
Yes,
hey
wait
for
a
guy
to
leave
to
get
that
one,
but
yeah,
I'm
rich
at
redhat.com
email
me
directly
and
I'll,
probably
loop
in
other
people
on
our
team.
C
You
know
I'm
very
in
enthused
to
get
field
feedback
because
it
does
very
much
shape
our
our
tooling
and
shapes
kind
of
our
opinion
on
where
we
want
to
go
so
yeah.
If
you
got
a
bug,
just
open
up
a
little
classic
bug
in
bugzilla,
but
if
it's
other
feedback,
just
email
me
and
we'll
go
from
there
awesome
thanks.
B
A
D
B
B
A
Angle
side,
if
you
want
to
like
dive
into
anything
that
rich
has
said
today,
right
like
he
might
just
tell
you,
be
like
ooh,
send
me
an
email,
but
you
know
it
could
be
that
complex.
We
can't
handle
it
on
twitter,
so
yeah,
just
if
you
need
to
reach
out
and
didn't
get
your
question
answered.
I
apologize.
That's
my
fault
email
us.
We
can
get
it
answered.
So
thank
you
all
for
joining
us
today,
rich.
Thank
you.
So
much
for
joining
us
really
appreciate
your
help.
Gordon
thank
you
as
well.