(upbeat music)
- In this video, we'll discuss the basics of patching
and software management with Red Hat Satellite
Satellite helps you define
and manage a standard operating environment, or SOE.
Building an SOE includes two key things.
Defining your builds, your workloads,
and your applications that run on Red Hat,
and figuring out how to best manage
and integrate those apps in your organization
by looking at the enterprise as a whole.
From the workloads to the people who manage them
to your patching methodologies.
That way when it's time to build out new servers,
you have the tools and the processes in place
to quickly create those environments.
In turn, this enables you to quickly respond
to security vulnerabilities such
as Heartbleed and Shellshock.
Once you have your SOE built, it's really easy
for you just to take and quickly patch those environments
and keep them up to date.
This in turn helps you comply
with your organization's security policies.
Security gets a lot easier when you know exactly
what's on your system and what systems need to be patched.
And finally, Satellite makes it really easy
to not only deploy Red Hat software
but pretty much any third party software.
Once you add a product into Satellite,
Satellite owns that content and keeps track of it.
Now we'll jump into our demo environment
and we'll show you how to patch existing systems
as well as how to create a custom product
and leverage that within Satellite.
We'll start by looking at the host
that we already have in our environment.
We'll then apply a patch to one host,
and then we'll look at how to apply patches to many hosts.
I'll start by going "Hosts", "Content Hosts".
When we see a list of content hosts,
notice in the "Installable Updates" column
that there's several different categories
of updates that are available.
We have security, bug fixes,
enhancements, and package updates.
We're gonna start by looking at the most important
which is your security updates.
I'm gonna click right on the host itself
where you can see more details about the host.
Then notice we have the same section in the upper right
under "Installable Errata."
I'll click on the security category
and it will show me a list of security errata
that are available.
To get more details, click on any errata that you like,
and it's going to show you all the information
such as your description, your solution,
and the packages that are affected.
I'll go back to the errata list
and you can select one or more
of the errata that you want to apply
and simply click Apply Selected.
Confirm that you want to apply it
and in a matter of moments your errata is applied
to your host.
That's really simple for one host,
but obviously you don't want to go in every host
one at a time like this,
so let's take a look at how you would apply an errata
to a group of hosts.
We go to "Content", "Errata",
and note under the "Content Host Counts" column
we have a list of how many hosts are applicable
as well as installable.
So if I click on this errata
I can see in the content host view
that it effects four of my five hosts.
I'll go back to the errata list
and to apply, simply select one or more errata
and then click Apply Errata.
Select the host that you want to apply it on
click Next, and Confirm.
Again in a matter of moments,
your errata is applied to your host
and to confirm this you can go to "Monitor",
"Tasks",
and you can see the details of where the errata
has been applied.
So hopefully you can see how this would be really easy
if you have something like Heartbleed or Shellshock.
You can quickly identify which hosts are affected
by the errata,
and apply them to those hosts.
Next let's look at a third party piece of software
and how we would create that within Satellite.
To add a custom piece of software into Satellite
we're going to use the EPEL repository.
We have a Knowledgebase entry on how
to do this within Satellite,
so essentially I'm just going
to follow the steps within this knowledge base.
I'm pointing it out for your reference,
I'm not going to follow it line by line.
Since the EPEL software package uses GPG,
the first thing we need to do
is add a content credential into Satellite.
Select "Content", "Content Credentials."
I don't currently have any created,
so I'm gonna click Create Content Credential.
We'll name this EPEL, it is a GPG key,
and the key itself
is located on the Fedora page.
I'll paste that key
right into the page, and click Save.
Next thing we're going to do is create a product.
So under "Content", "Products",
as you can see we already have a variety
of products that are listed here that are Red Hat products
but now we're going to create
our own third party custom product.
We'll again call this EPEL.
We'll point it at our EPEL GPG key,
and you can provide any description that you like.
Click Save, that's created our product as a category,
but we still need to create a repository
to associate this with.
So I'll click New Repository.
This is the EPEL_REPO.
It's yum software, I'm going to restrict
that to the x86 architecture.
In my "Upstream URL", I have open here in my browser.
And my GPG key is EPEL.
A lot of this other information is there
because depending on the piece of custom content
that you're adding, you may or you may not
need to provide those items.
I'm going to unclick Verify SSL
and then click Save.
So I've not provided any software, or uploaded any package,
but I did provide a URL where
that content can be synchronized.
So the next step is to sync the repository.
Select the box, and click Sync Now.
This will take a few minutes,
but thanks to the magic of video, it's been sped up for you.
(clock ticking)
As you can see we got a success message
which means we have synced the repository
from the non-Red Hat software
into our Satellite environment.
If I return to the products page, I can see the EPEL repo,
as well as "Success", and the content of that repository.
So that gets the software into Satellite,
how do we get that out to your hosts?
We do that using a concept that we call Content Views.
The Content View is a managed selection of content
that contains one or more repositories.
To create a Content View
we go to "Content", "Content Views",
as you can see we already have a couple of views
that have been created
but we'll create a new View that has our EPEL repository.
We'll call this EPEL.
I'm not going to select the Composite View
or the Auto Publish at this time.
I'll click Save.
And under Yum Content I'm going to add
the EPEL repo.
So that's the only thing that is contained
within this repository
I could absolutely add more content if I wanted.
Notice the Publish New Version button at the top.
If I wanted to go ahead
and publish this Content View
and make it available to hosts
that's how I would do it.
But I'm not gonna do it quite yet.
I'm going to return to the Content Views page
and I'm going to create a second view.
This time I'll create what's known
as a composite Content View.
I'm going to create a view
that has both the content from RHEL
as well as the content from EPEL.
That way when I send that Content View out to a host
it will get all the content from both
of these Content Views.
That's known as a composite view
and I will select the Auto Publish button.
That way when a Content View, either the RHEL
or the EPEL Content View is updated
it will automatically publish this Composite Content View.
So click Save.
I'm going to include EPEL and RHEL 7 Content Views
into my Composite Content View.
Again, I'm not going to publish the view at this time.
I'm going to return to my Content Views.
Notice that EPEL is not yet published
and RHEL+EPEL is also not yet published.
So if I return to my EPEL repository,
and I'll click Publish New Version
I can enter any sort of description that I want.
It already has version 1.0, so as I make changes
to this repository, it will increment the version number.
I'll click Save,
and this will start the process of publishing
and promoting the Content View.
(clock ticking)
So I successfully published version 1.0
of the EPEL repository into my library environment.
Satellite also has the concept of life cycle environments
so this currently in the library,
but as I move along and test this out,
I could move it into a Q and A type environment,
or a development environment, or a production environment,
and I can continually promote these different Content Views
into matching life cycle environments.
If I return back to the main Content Views page
I had published the EPEL repository
but note that the RHEL+EPEL also was successfully published.
That's because this Composite Content View
had auto publish enabled.
So that handles getting the content into Satellite,
adding the content to a Content View,
bu now let's make it available to our hosts.
We'll do that by going "Hosts", "Content Hosts."
Then I can select one of these hosts.
Then notice under the Content View
currently it's set to RHEL 7
I can edit that and change it to the RHEL+EPEL Content View
that we just created.
So that assigned the appropriate Content View
but to sync the packages
we go to "Packages", "Actions",
then select Update All Packages.
(clock ticking)
And that process applied all
of the packages from the RHEL Content View,
as well as from the EPEL Content View.
So you can see we've added a whole bunch
of new packages to this host, both Red Hat and non-Red Hat.
As a recap in this video, we started by patching
a single host, just adding one errata to that host.
We then showed how to go into the errata section,
find a particular errata, figure out what hosts
that errata applies to,
and apply that errata to all of the applicable hosts.
We then created a new product,
pointed at a repository for EPEL, synced that repository
of non-Red Hat software into Satellite,
created a Content View as well as a Composite Content View
to make that content available to hosts,
then we updated all the packages.
So this package now has both RHEL
as well as non-RHEL software managed through Satellite.
That concludes this section.
See you in the next video.