►
Description
Being a Systems Administrator brings with it a lot of responsibility. Wouldn’t it be helpful if there was a tool that could help you manage your Linux servers at scale? Oh wait! There is. Join Eric and Matthew Yee as they discuss Red Hat Satellite and how it can help manage your infrastructure.
A
Hello
and
welcome
to
redhead
enterprise
presents
this
is
episode
number
25
introduction
to
satellite.
Thank
you
all
so
much
for
joining
us
today.
I'm
really
excited.
We've
got
a
lot
of
a
lot
of
great
things
to
talk
about
on
the
show
today,
so
time
appropriate
greetings
to
all
of
you
as
usual
in
the
chat.
This
is
the
best
way
to
to
talk
with
the
host
talk
with
our
guest.
Ask
your
questions
and
and
be
part
of
the
show.
A
So
if
you
are
not
on
our
discord,
there's
a
discord
server
as
well
and
we'll
share
all
those
links
throughout
the
the
show
and
they'll
be
in
the
show
notes
afterwards.
But
before
we
get
too
deep
into
today's
topic,
I
do
have
an
announcement
I'm
really
excited
about.
I
would
like
to
introduce
our
new
recurring
co-host,
brian
smith,
how
you
doing
today,
brian
good.
A
B
Sounds
good
yeah
so
right
now,
I'm
a
product
manager
in
the
rel
business
unit
focused
on
automation
and
management.
So
what
that
means
is
I'm
working
with
technologies
like
rail
system
roles
and
web
consoles
stuff,
like
that
I've
moved
into
this
position
back
in
april
and
before
that
I
was
with
red
hat
as
a
tam,
a
technical
account
manager
for
for
about
three
years.
So
so
that's
my
background
before
before
that
I
worked
as
a
sysadmin
for
many
many
years.
So
yeah
excited
to
be
here.
B
A
Yeah,
I'm
glad
to
have
you
as
a
co-host.
There's,
there's
always
a
lot
to
love
to
keep
track
of
between
the
chat,
the
stream,
the
conversation,
the
interview,
so
I
for
one
am
very
thankful
to
have
you
and-
and
as
I
recall,
you
are
not
not
new
to
this
particular
youtube
channel.
As
I,
as
I
recall
a
couple
years
ago,
your
your
wonderful
narration
skills
were
put
to
good
use
for
the
rel
8.0
beta.
There
was
a
bunch
of
videos.
B
A
Yeah
and
shameless
plug
for
brian,
if
you
follow
our
blog
brian,
has
been
a
machine
publishing,
probably
what
close
to
eight,
if
not
a
dozen
blogs
around
system
roles
right
now.
So,
if
you're
looking
to
automate
your
builds,
if
you're
looking
to
standardize
your
environment
system
roles
are
a
great
way
to
do.
That,
and
brian,
I
think,
has
the
monopoly
on
system
role,
blog
content
right
now,.
A
Yeah,
that's
actually
on
the
roadmap
for
early
next
year,
but
yeah.
We
definitely
do
they
are
incredibly
powerful
and
in
fact,
kind
of
is
a
good
segue
into
today's
topic,
because
system
roles,
ansible
things
like
tools
like
this-
have
come
a
very
long
way
since
my
days
as
a
systems
administrator
and
one
of
the
other
tools
that
that
we
we've
actually
not
covered
in
25
episodes
on
the
or,
I
should
say
in
24
episodes.
We
have
not.
A
We've
only
mentioned
this
product
in
passing,
but
that
is
red
hat
satellite
and
I
could
think
of
no
one
better
to
come
on
the
show
and
and
talk
about
satellite
than
our
own
matthew
yee.
He
is
a
technical
marketing
manager
here
at
red
hat.
He
works
on
my
team
and
he
was
with
me
a
couple
of
weeks
ago,
as
we
talked
about
rel
8.5
looks
like
we're
having
some
streaming
issues
so
give
me
just
a
second
and
I'll,
bring
matt
on
to
introduce
himself
and
we'll
see
hey
matt.
A
A
C
C
B
C
So,
from
the
the
point
of
view
of
a
systems
administrator,
a
lot
of
us
have
had
this
problem,
but
sometimes
when
you
do
a
yum
or
dnf
update
what
happens
if
the
firewall
hasn't
been
opened
or
if
there's
no
proxy
configured,
you
can't
update
your
system.
There
are
lots
of
ways
to
work
around
it.
The
recommended
way
of
doing
it
at
red
hat
is
red,
hat
satellite.
C
You
can
also
provision
machines
and
you
can
also
take
advantage
of
some
of
our
hosted
services
like
insights
at
red,
hat
console.redhat.com
and
just
a
little
plug
here.
For
those
that
don't
know,
insights
will
do
stuff.
Like
look
for
security
vulnerabilities.
What
else
will
it
do
it
will?
Let
you
know
how
to
fix
it?
It
will
provide
an
answerable
playbook
so
that
you
can
do
a
push
button
remediation
on
those
vulnerabilities
that
it
finds.
C
B
C
This
is
all
then
managed
through
the
foreman
project.
We've
got
candlepin
that
allows
you
to
manage
subscriptions
and
there's
a
whole
bunch
of
stuff
out
there.
So
where,
where
red
hat
offers
value
here
is
we
provide
we,
we
combine
all
of
these
projects
and
we
make
sure
that
they
all
work
together
well
and
yeah.
Just
ensure
that
you
have
the
tools
that
you
need
to
manage.
Your
hosts
sounds.
B
A
C
B
Yeah,
that's
been
my
experience
as
well,
and
working
with
a
lot
of
customers
over
the
years
is,
if
you
follow
the
documentation
for
upgrading
satellite
things
will
go
pretty
smoothly.
If
you
try
to
just
wing
it
and-
and
you
know
figure
it
out
on
your
own,
your
results
might
vary.
So
I
would
like
matthew
said.
I
definitely
recommend
you
know,
review
the
documentation.
B
C
C
There's
a
couple
of
reasons
for
that.
This
is
to
prepare
all
of
our
current
customers
for
a
future
update
to
satellite
7.0,
and
so
a
lot
of
the
I
would
say,
if,
like
in
terms
of
doing
an
upgrade
the
most
time
consuming
part
of
that
upgrade.
We're
asking
you
to
do
that
right
now,
with
6.10,
we've
included
a
bunch
of
migration,
slash
upgrade
tooling
in
six.
C
That
includes
a
bunch
of
upgrade
tooling
and
in
the
upgrade
manual
we'll
tell
you
how
to
use
that
upgrade
tooling
to
migrate
your
pulp
2
content
into
pulp
3.,
without
going
too
deep
into
it.
The
upgrade
process
is
now
or
at
least
the
migration
process,
from
pulp
2
to
pulse
3
is
show
I'm
going
to
use
this
term
anyway,
but
it's
item
potent
so
you
can
run
it
as
many
times
as
you
want.
You
can
stop
the
operation
and
re-run
the
operation.
C
It's
designed
to
make
the
upgrade
process
as
painless
as
possible.
So
because
it's
a
very
time
consuming
process.
We
want
you
to
be
able
to
complete
it
on
your
own
time.
Whenever
is
convenient
and
once
the
migration
is
done,
the
upgrade
is
very
timely.
We're
estimating
it'll
take
like
20
minutes
for
you
to
run
after
you've
upgraded
the
pulp
back
in
anyway.
A
You
mentioned:
go
ahead
to
stop
and
restart
this
this
this
upgrade
process.
So
is
that
something
that
when
I
leave
the
office
at
six
o'clock,
I
can
kick
this
off
as
I'm
walking
out
the
door
and
if
it's
not
done
say
by
the
the
next
morning,
when
I
get
into
the
office
around
eight
or
9
a.m,
I
can
stop
it
that
way.
My
my
satellite
server
isn't
isn't.
Is
it
hung
up
during
the
day
when
we're
trying
to
work
with
our
different
environments
or.
C
Or
even
it's
it's
actually
better
than
that.
So
let's
say
you
ignored
my
advice.
Just
now
to
run
the
preparation
script,
your
migration
will
actually
fail.
So
what
you
can
then
do
is
you
can
go
back
and
run
the
migration
or
the
preparation
script
like
I
asked
you
to
and
then
you
can
kick
off
the
migration
all
over
again
and
it
should
complete
properly
that's
what
it's
really
used
for.
A
C
So
the
one
one
of
the
reasons
why
we've
made
the
upgrade
process
like
this
is
because,
because
it
takes
a
long
time,
it's
hard
to
predict
how
long
it's
going
to
take.
We
have
a
command
that
will
do
an
analysis
on
your
pulp,
2
back
end
and
give
you
an
estimate,
but
we
don't
know
for
sure
how
long
it's
going
to
take.
C
So,
let's
say
we
estimated
three
hours,
but
it
really
took
one
hour
and
then
in
between
that
two
hours
there
were
some
synchronization
updates
that
were
done,
you're
going
to
want
to
run
that
upgrade
script,
one
more
time
before
you
actually
do
the
switch
over
to
6.10.
That's
that's
another
reason
why
you
would
do
that.
C
C
A
C
A
C
C
For
those
people
who
don't
know
satellite
six
at
least
the
six
branch
runs
on
red
hat
enterprise
linux.
Seven,
we
don't
have
support
for
rel
eight.
Yet
that
is
coming
with
satellite
7.0,
which
is
the
next
release.
You
guys
may
be
wondering
well,
why
is
that
the
flat
out?
The
real
reason?
Is
we
don't
have
time
we
need
to
check
it
and
there
were
higher
priorities
that
we
needed
to
work
on
to
dump
into
satellite
6.10,
which
is
why
we
currently
don't
have
support
for
8.0
of
rel.
Yet.
C
C
I've
added
the
app
stream
repo
and
the
base
os
repo
once
you've
done,
that
you're
going
to
want
to
synchronize
them,
so
the
default
synchronization
mode
for
red
hat
satellite
is
to
not
download
the
yum
packages
that
you'll
that
you'll
associate
with
the
repository
yeah.
This
is
the
one
I
wanted
to
show
what
the
default
synchronization
mode
is
going
to
pull
down
all
of
the
metadata
associated
with
those
yum
packages
and
there's
a
reason
for
that.
C
A
So
sorry
go
ahead
yeah.
So
I
remember
when,
when
I
used
satellite
way
back
in
like
the
5.4
days
that
you
didn't
really
have
an
option,
you
just
you
subscribed
to
a
repository
and
you
had
to
pull
down
like,
in
this
case
all
21
21
000
packages
and,
like
you
said
that
takes
a
lot
of
bandwidth
a
lot
of
disk
space.
A
A
Yeah
and
that
helps
especially
with
a
disconnected
environment.
Maybe
it's
not
something:
that's
air
gapped,
but
if
it's,
if
it's
disconnected
or
it
has
you
only
want
to
open
up
that
that
firewall
ports
say
when
you're
when
you're
refreshing,
your
your
patching
cycle
or
something
that's
a
great
way
to
to
to
handle
that.
But
as
far
as
most
businesses
are
concerned
and
and
my
own
satellite
server
here
at
home,
I
don't
need
21
000
packages
sitting
on
my
satellite
server
chances.
A
A
So
it's
got
that
that
map
of
dependencies
and
all
that
kind
of
thing
and
then,
when
I
go
to
to
trigger
an
update
from
satellite
or
when
I
go
and
install
a
one-off
package
from
one
of
my
satellite
registered
clients,
it's
nice
to
know
that,
then,
that
client
is
talking
to
the
satellite
server.
Satellite
is
talking
to
our
to
red
hat
cdn
and
it
pulls
down
exactly
the
packages
and
exactly
the
repo,
the
the
dependencies
that
I
need
and
so
you're
you're
talking
about.
C
B
A
Did
did
either
of
you
ever
ever
have
like
a
a
repo
sync
spreadsheet.
I
I
when
I
was
running
satellite,
I
literally
had
a
spreadsheet
that
was
like
color
coded
based
on
okay
between
between
2
a.m
and
3
a.m.
We're
going
to
sync
like
red,
hat,
satellite
or
red
hat
rel5
packages,
and
then
between
three
and
four
in
the
morning,
we're
going
to
sync
sync
real
six
packages.
A
I
mean
we
literally
had
to
spreadsheet,
and
it
was
so
tough
back
back
in
those
days
that
we
actually
worked
with
the
the
backup
teams
to
make
sure
that
we
were
doing
a
that.
We
weren't
going
to
step
on
when
they
were
using,
like
the
storage
area
network,
just
to
make
sure
that
satellite
and
backups
and
all
these
other
things
and
and
it
was
all
spreadsheet
driven
it
was.
It
was
miserable.
C
B
C
A
C
Yeah
now
for
for
our
viewers,
you
might
be
saying:
well,
that's
not
a
big
deal.
Why
would
why?
Wouldn't
I
want
to
sync
all
of
these
down
and
that's
an
entirely
reasonable
statement,
but
for
large
organizations
when
you
start,
including
all
the
extra
stuff
and
by
extra
stuff
I
mean,
like
I,
don't
know,
ansible
jboss
all
that
stuff.
It
starts
to
get
big,
pretty
quick
and
that's
not
even
including
custom
content
that
you
want
to
add
to
satellite.
C
C
So
I'm
going
to
show
you
here.
I
got
one
for
rel7,
one
of
the
first
things
you're
going
to
do
after
you've
pulled
your
content
down
is
you're
going
to
want
to
create
an
activation
key
and
what
you
end
up
doing
is
with
this
act.
This
is
your
activation
key
right
here.
I
feel
comfortable
showing
this
to
everybody,
because
if
you
ran
it
right
now,
it
wouldn't
do
anything
because
you're
not
connected
to
my
satellite
anyway.
C
I
am,
as
you
can
see,
this
is
in
ec2
one
of
the
first
things
I
need
to
do
here
and
you
you
will
probably
not
to
do
that.
You
will
probably
not
need
to
do
this
in
your
own
environment,
but
I'm
going
to
remove
the
red
hat,
update
infrastructure,
client
or
rui
as
we
refer
to
it,
because
I
don't
want
my
host
updating
from
rui.
I
want
to
actually
update
from
satellite,
so
one
more
time
just
to
just
to
be
clear.
C
C
C
C
C
A
I
usually
lead
with
a
yum
clean
all
just
out
of
sheer
paranoia.
It
seems
like
it
seems
like
when
you're
doing
any
kind
of
maintenance
window
that
it
seems
like
there's
always
some
some
metadata.
That's
that's
expired
and
or
some
dependency
that
hasn't
been
sorted
out.
So
if
you
do
a
young
clean
all
and
then
do
a
yum
update,
it
pulls
all
that
stuff,
fresh
and
and
I'd
I'd
encourage
that
even
more
because
you
are
switching
repositories
and
not
just
not
just
repos
but
you're
you're
completely
changing
where
that
content's
coming
from.
C
C
C
C
C
A
A
I
usually
hate
when,
when
shows
do
this,
but
we're
as
you
can
see,
with
with
some
of
the
new
content,
some
of
the
new
guests
and
having
a
a
new,
a
new
host
and
a
new
co-host
shows
undergoing
a
lot
of
changes,
we're
growing
it
we're
we're
so
tell
a
friend.
If
you
don't
have
any
friends
go
out
on
twitter.
All
of
your
all
of
your
friends.
Are
there.
A
A
B
C
I
there's
I
mean
you
certainly.
Can
I
don't
know
if
it's
bad,
but
at
the
same
time,
if
you
really
wanted
to-
and
let's
say
you
are
a
very
controlling
sysadmin-
we
give
you
the
choice
to
create
a
subset
of
all
of
those
repos,
in
other
words,
a
subset
of
that
content,
so
that
you
can
associate
that
with
a
an
activation
key.
So
just
to
reiterate,
content
views
are
for
creating
sub
access
subsets
to
your
content,
so
that
not
all
of
it
is
given
to
everybody.
B
Yeah
and
another
another
way
I've
talked
about
this
before
too
is
it's.
It's
freezing
that
content
at
a
point
in
time.
Right
so
like
a
situation
you
want
to
avoid.
Let's
say
you
have
like
three
environments,
you
know
dev
test
and
prod
in
your
environment
and
you're
gonna
go
ahead
and
patch.
You
know
you're
gonna
update
dev
today,
okay
and
then
two
weeks
later,
you
know
now
I
wanna
update
test
well,
if
you're,
not
using
satellite
and
not
using
content
views
in
those
two
weeks
that
have
passed
there
might
be
additional
updates.
B
You've
got
you're
getting
now
in
your
test
environment
from
rel
that
we've
released
in
those
two
weeks.
Okay,
let's
say
two
weeks
later:
now
you
go
to
update
prod
and
again,
if
you're,
not
using
satellite,
you
just
do
a
yum
update.
It's
going
to
pull
the
latest
content,
there
could
have
been
a
minor
release.
It
could
have
gone
from
8.4
to
8.5
in
those
two
weeks
of
the
past
and
now
you're,
installing
rel,
8.5
and
prod
and
you've
never
tested
that
out
in
your
dev
and
test
environment.
B
So
with
the
content
you
you
can
you
take
that
you
make
a
content
view,
it's
that
point
in
time
snapshot
and
then
you
update
all
three
environments,
dev
test
and
product
from
that
same
content
view
and
they
get
the
exact
same
access
to
content
and
so
you're
you're.
Not
having
that
situation
where
prod
is
getting
later
content
than
the
endeavor
test.
B
Then,
and
one
of
one
other
cool
feature
I'll,
throw
with
content
views
that
I
that
I
really
like
is
you
can
exclude
content
too
so
say
you
know
like
the
emacs
package,
for
example,
you
know
you
could
exclude
that
from
your
content
view,
and
so
your
you
know,
your
users
can
install
that.
So,
if
there's
certain
packages
you
want
to
exclude
out
of
there.
A
C
Can
you
guys
see
that
yeah
cool
okay,
so
both
hosts,
should
be
showing
up
now
as
they
both
are?
So
that's
my
rel
eight
host
and
my
rel
seven
host
a
note
about
this.
You
may
recall
earlier
I
did
a
cat,
etsy
red
hat
release
and
it
showed
red
hat
8.4
while
now
showing
8.5,
because
I've
done
a
reboot
and
or
an
update
and
a
reboot.
C
A
C
A
C
B
Yeah
we
have,
we
have
documentation
that
talks
a
lot
about
that.
It's
called
inner,
satellite,
sync
or
iss.
I
don't
know
if
that's
a
play
on
the
whole
space
and
satellite
thing,
but
anyways
yeah
enter
satellite
sync,
it's
it's
documented.
How
to
how
to
do.
You
know,
export
the
content
and
put
it
in
there
on
your
on
your
disconnected
satellite
server.
C
C
B
C
C
C
C
C
C
So
remote
execution
is
really
handy.
You
can
basically
do
anything
and
apply
it
to
any
number
of
hosts.
So
let's
say
you
had
100
hosts,
you
could
remote
execute
against
all
hundred
of
them,
which
means
that
you
can
also
run
commands
like
yum,
install
or
dnf
install
some
kind
of
package
and
install
that
on
your
host.
C
A
And
I
think
the
power
of
satellite
comes
in
from
a
lot
of
the
different
tools
that
the
red
hat
has
been
has
been
expanding
on
between
system
roles,
image
builder
satellite-
I
mean
I
if,
if
you,
if
you
look
at
a
green
field
infrastructure
nowadays,
it
would
be
so
easy
to
create
all
the
stuff
using
infrastructure's
code,
golden
images
and
just
lay
all
this
stuff
out.
Science
set
up
a
set
of
different
roles
and
profiles
and
satellite
have
have
your
content
views,
which
we
didn't
go
too
deep
into
on
this
episode.
A
But
having
all
those
things
you
could,
you
could
literally
tear
down
your
entire
infrastructure
and,
with
the
click
of
a
button
rebuild
it
from
basically,
nothing
just
use
image
builder
to
create
a
template.
Have
that
have
that
image
builder
image
tie
into
your
satellite
system
so
when,
when
it
first
boots
your
your
system
registers
with
insights
and
with
satellite
and
then
you
can
use
you
can
use
remote
execution,
you
can
use
scheduled
jobs.
You
can
use
different
profiles
to
using
profiles
as
a
generic
term
to
define
that
this
is
going
to
be
a
database
server.
A
So
my
database
users
need
to
have
access
to
it.
It
needs
these.
It
needs
these,
these
additional
repositories
for
this
database
and
basically
just
sitting
back
as
as
an
operator
instead
of
as
a
systems
administrator,
I
don't
have
to
go
in
and
do
this
on
500
servers
anymore.
Instead,
it
really
is
a
step
closer
to
that
that
dream
of
having
infrastructures
code
and
having
an
infrastructure
that
is
the
same
across
every
platform
across
every
infrastructure
base,
whether
that's
virtual
bare
metal
cloud
or
some
kind
of
hybrid
of
of
all
the
above.
B
And
eric
another,
just
on
that
train
of
thought.
We
also
know
how
the
satellite
ansible
collection,
that's
supported,
and
you
can.
You
can
use
that
to
you
know,
write
code
to
implement
your
satellite,
so
you
know
automate
the
installation
and
configuration
of
you
know
of
of
your
satellite
resources,
either
repositories.
C
A
A
A
C
C
C
A
Brian,
what
do
you
think
before
I
hand
it
over
to
brian?
I
wanted
to
add
just
one
quick
comment
on
that.
One
of
the
things
that
I
kind
of
heard
in
between
the
lines
of
what
you're
saying
was
with
something
like
podman
and
containers
there
there
there
seems
to
be
a
threshold
somewhere,
and
it
comes
up
a
lot
quicker
than
you
think.
Where
just
managing
pod
man
containers
by
hand
starts
to
get
it
out
of
hand.
A
It
starts
to
become
untenable,
and
that's
that's
when
you
start
thinking
about
something
like
an
orchestrator,
something
like
red,
hat,
openshift
or
just
straight
kubernetes.
So
well,
while
running
three
or
four
containers
may
be
great,
while
even
running
a
dozen
containers
on
a
single
note
or
a
couple
of
different
notes,
may
work
to
begin
with.
It's
one
of
those
things
that
can
quickly
get
out
of
hand,
especially
with
something
as
small
and
as
prolific
as
as
a
container
so
using
something
like
satellite
in
an
existing
infrastructure
would
definitely
definitely
help.
A
I
look
at
it
as
almost
a
spectrum
of
not
everyone's
going
to
use.
Containers
at
all.
Some
people
will
have
three
or
four
and
that's
enough
for
them.
Other
people
start
out
using
a
couple
and
then,
within
a
couple
of
quarters,
they
realize
that
we
have
a
thousand
containers,
no
way
to
schedule
any
of
them.
We
need
an
orchestrator
so
that
that's
kind
of
what
I
heard
as
you
were
talking
matt.
C
C
B
Yeah,
I
think
I
think
you
guys
covered
it
really.
Well,
I
mean
the
key
takeaway.
Is
you
know
if
you,
if
you
want
to
run
just
just
rel,
we
have
that
covered.
If
you
want
to
run
some
containers,
you
know
we
have
podman
and
if
you
want
to
do
a
lot
of
containers,
we
have
open
shifts.
So
no
matter
where
you're
at
you
know
with
with,
if
you
want
to
use
containers,
don't
want
to
use
containers.
You
know
we
have
solutions
to
help
you
out
with
that.
A
Well,
it's
that
we
are
at
the
top
of
the
hour,
and
I
wanted
to
first
off.
Thank
you,
matt,
very
much
for
for
coming
on
to
two
episodes
in
a
row
and
talking
about
talking
about
satellite.
I
know
that
this
was
long
overdue,
25
episodes
before
we
even
mentioned
before
we
even
demoed
satellite.
I
know
we've
mentioned
it
in
passing,
but
thank
you
so
much
for
coming
on,
back-to-back
episodes
and
and
demoing
different
pieces
of
satellite.
A
In
fact,
if,
if
you
watch
this
episode,
please
post
in
the
comments
we've
been
toying
with
the
idea
of
doing
a
satellite
like
mini
series
and
just
kind
of
touching
on
some
of
the
different
major
categories
of
of
satellite.
So
if
you'd
be
interested
in
a
satellite,
focused
mini
series
put
it
in
the
comments,
put
it
in
our
discord
server
and
then
I
would
be
remiss
if
I
didn't
promote
our
next
episode
and
in
two
weeks
join
brian
smith
and
father
linux
himself.
A
That's
his
twitter
handle
scott
mccarty.
He
is
another
he's
one
of
the
product
manager
or
product
managers.
Here
at
red
hat,
we
are
going
to
talk
about
all
things
containers,
so
we're
going
to
talk
about
podman.
I
there
was
a
question
about
there's,
there's
a
question
about
logging
with
with
podman,
so
come
back
in
two
weeks
same
time,
same
channels
and
we'll
we'll
promote
that.
A
So
we
we
haven't
decided
which
one,
whether
that's
that's
minecraft
or
something
else,
but
definitely
something.
I'm
looking
forward
to
it'll,
be
a
great
conversation
and
scott
is,
is
a
lot
of
fun
so
tune
back
in
in
two
weeks
and
we'll
have
that
episode.
Brian.
Any
any
closing
thoughts
before
we
get
out
of
here.
A
Well,
I've
I've
already
gotten
a
vote
in
chat
that
the
penguin
whisperer
would
like
a
satellite
mini
series.
So
if
the
penguin
whisperer
says
says
we
should
have
a
satellite
mini
series,
we
probably
should
but
we'll
look
at
doing
that
sometime
next
year,
but
until
then
thank
you
all
so
much
for
joining
us
be
sure
to
like
and
subscribe
this
video
and
our
channel
join
us
every
two
weeks
and
definitely
follow
us
on
twitter
at
redhat
rel,
and
you
can
follow
satellite
at
red
hat
satellite
both
on
twitter,
brian
matt.
Thank
you
guys.