Ensuring Approved Packages Are Installed Across System Profiles Using the Drift Service
How to validate that approved packages are installed across system profiles and generate reports
Red Hat Customer Content Services
Making open source more inclusive
Red Hat is committed to replacing problematic language in our code, documentation, and web properties. We are beginning with these four terms: master, slave, blacklist, and whitelist. Because of the enormity of this endeavor, these changes will be implemented gradually over several upcoming releases. For more details, see our CTO Chris Wright’s message.
Providing feedback on Red Hat documentation
We appreciate your feedback on our documentation. To provide feedback, highlight text in a document and add comments.
- You are logged in to the Red Hat Customer Portal.
- In the Red Hat Customer Portal, the document is in the Multi-page HTML viewing format.
To provide your feedback, perform the following steps:
Click the Feedback button in the top-right corner of the document to see existing feedback.Note
The feedback feature is enabled only in the Multi-page HTML format.
- Highlight the section of the document where you want to provide feedback.
Click the Add Feedback pop-up that appears near the highlighted text.
A text box appears in the feedback section on the right side of the page.
Enter your feedback in the text box and click Submit.
A documentation issue is created.
- To view the issue, click the issue link in the feedback view.
Chapter 1. Overview
As an IT operator, use Insights for Red Hat Enterprise Linux to ensure approved security tools and RPM packages are installed on each system:
- Access the drift service.
- Add systems manually within the drift service.
- Filter system configuration data by installed packages.
- Export the filtered data to a CSV file for analysis.
Chapter 2. Accessing the drift service
The drift service is part of Insights for Red Hat Enterprise Linux. Access this service via Red Hat Hybrid Cloud Console.
Navigate to the Red Hat Enterprise Linux > Drift > Comparison page where the Comparison screen opens.
Cick Add to comparison. The Add to comparison screen opens, where you can add systems or baselines to compare.
- On the Systems tab, you can add any systems you want to compare. This screen also lists any baselines that already exist in your Insights for RHEL inventory.
On the Baselines tab, you can create baselines. This screen also lists any baselines that already exist in your inventory.
- Click Submit to add your systems or baselines for comparison.
Once you add them, you can start comparing the facts of systems and baselines in your Insights for RHEL inventory.
Chapter 3. Adding systems manually to comparisons
Within the drift service, you can add systems registered in your Insights for RHEL inventory.
- Navigate to the Red Hat Enterprise Linux > Drift > Comparison page where the Comparison screen opens.
- Click Add to comparison.
- Select the systems to compare from the list. Alternatively, enter the system name in the search box to find by name, and then select the system.
- Click Submit.
- At any time, you can add more systems by clicking the Add to comparison button near the top of the Comparison screen.
- Similarly, you can remove a particular system under comparison by clicking the X symbol on the upper-right corner of the individual system name.
- You can remove all systems under comparison by clicking the options menu ( ) located at the top.
- Click Clear all comparisons to start again.
Chapter 4. Filtering system facts by installed packages
To filter the system facts by installed packages:
Enter the required package name in the search box at the top, or enter
installed_packagesto view the list of all packages installed.
- In the View drop-down list, ensure you are viewing the result for all comparison states, by selecting the check boxes for Same, Different, and Incomplete data.
For all installed packages, the Insights for RHEL service lists installed packages and their versions, indicating whether they are the same, or different, and where information is missing across systems.
Facts are filtered by installed RPM packages for which you can see a subset of the list. Note that for package `deltarpm` there is no difference in its version between the two systems. However, packages `rpm`, `rpm-build-libs`, `rpm-libs`, and `rpm-python` show differences. Also, data is missing for some of the other packages. This is a discrepancy as systems were not consistently upgraded with approved packages.
Chapter 5. Exporting system comparison output
You can export a comma-separated-values (CSV) file of the system profiles you previously filtered. The report captures, by installed packages, where RPM versions are the same, different, and where information is missing.
The exported CSV report preserves all your current selections on the system comparison output, including any filters applied. That is, it follows the WYSIWYG (What You See Is What You Get) paradigm. Therefore, you may need to expand any nested fact categories (
installed_packages, for example) to be exported in the report.
- At the top of the system comparison output screen for two or more systems, click the Export to CSV button .
- Click Export to CSV.
Save the CSV file to the location of your choice so that you can analyze discrepancies in installed RPM packages.