This is the 4th installment of a series of posts focusing on OpenSCAP. Previous posts in this series can be found below.
OpenSCAP Part 1: Introduction and Basic Usage for RHEL 7/CentOS 7/Fedora
OpenSCAP Part 2: SCAP Content for RHEL 7
OpenSCAP Part 3: Running Scans from the Command Line in RHEL 7
This time around we are going to work on integrating OpenSCAP functionality into
Red Hat Satellite 6.5 Installing SCAP Content on Satellite Server
SSH into your satellite server and run the command below as root.
# foreman-rake foreman_openscap:bulk_upload:default
By default only a few content files are added.
Installing Additional SCAP Content
This can be done via the UI (and possibly via the CLI, however I have not attempted this).
In this example I have already downloaded RHEL 8 content from
Log into the Satellite UI, and navigate to “
Hosts” > “ SCAP content”
Upload New SCAP Content”
And select Choose File to select a file from your local machine.
Red Hat Satellite consists of a number of running services. Restarting each service manually can be painful. Luckily you can use the commands below to easily restart all services.
Run the command below to view a list of all Satellite services that are started at boot.
# katello-service list
Redirecting to ‘foreman-maintain service’
Running Service List
List applicable services:
All services listed [OK]
Check Service Status
The command below will check the status of all Satellite services. The output is similar to running a systemctl status on all Satellite specific services. The output can be quite verbose.
# katello-service status
Use the command below to stop all Satellite services.
# katello-service stop
Use the command below to start all Satellite services.
# katello-service start
The command below will restart all Satellite services.
# katello-service restart
In this post I will review the process of creating
Content Views (CV), Composite Content Views (CCV), publishing each view, and creating lifecycles.
Note that in this post we are working with
Red Hat Satellite 6.4, in which there was a major overhaul of the WebUI. You may have noticed that all menus are now situated on in a pane on the left, rather than at the top of each page. Sync Plans
A sync plan is a constant, scheduled synchronization of updates of a Red Hat Satellite repository and the source repositories. I suggest syncing either daily or weekly in order to minimize the deltas between each sync. When you sync more often, the amount of change between syncs is less and therefore should complete faster than a monthly sync.
Note that this step assumes that you have already setup the correct repositories for RHEL and Red Hat OpenStack. A list of required repositories can be found in the
Red Hat OpenStack Director Installation and Usage Guide.
Content > Sync Plans
Here we create a daily sync plan for RHEL 7.
We now add RHEL 7 as the product.
Now we need to create a daily sync plan for Red Hat OpenStack.
Note: you might need to create a sync plan for Ceph as well. Ensure all plans sync at the same interval.
Create a Content View
Now we need to create our content views. We will create one for RHEL, and one for OSP. If you are using ceph, you will need to create a content view for it as well.