Overview

Deploying RPM packages on Linux servers involves the following steps. Each step cited below includes a reference to detailed instructions for the specific step.

RPM deployment process

Step

Instructions

Upload the RPM Packages to the SA Library.

Importing software packages

Define the Software policy.

Creating software policies and software templates

Add RPM packages to the software policy, and then configure the installation and upgrade options for the RPM packages in the policy.

Setting installation and update options for a RPM

Auto-Update Policy options provide additional upgrade efficiency. You can set up RPMs in your software policies to automatically update the policy whenever new RPMs are imported.

Automatically updating RPMs in a software policy

Attach the software policy containing the RPMs to the managed servers.

Attaching software policies to servers or device groups

Remediate the servers to implement the attached policies and maintain the RPM updates on the servers.

Remediating and installing software

To install the RPMs on a managed server, remediate the server with a software policy attached that contains the RPMs.

The RPM will become managed by the policy when the policy is remediated.

If the RPM was already installed on the managed server, then it will be adopted by the policy during the remediation process.

Adopted RPMs are treated the same as RPMs that were deployed by SA.

Installing and updating RPM packages using a software policy

To upgrade the RPMs that are already installed on a managed server, remediate the server with the software policy containing the newer RPMs.

Upgrade options for an RPM

To uninstall an RPM, you can:

Detach the policy containing the RPM from the server, and then remediate the server.

If an RPM resides in more than one attached software policy on a server, the RPM will only be uninstalled if all the software policies containing the RPM are detached from the server before the server is remediated.

If a software policy with adopted RPMs is detached and remediated, then these adopted RPMs will be uninstalled the exactly same way as RPMs that were deployed by SA.

Remove the RPM from the policy while keeping the policy attached to the server, and then remediate the server.

Detaching a software policy from the managed server

Reminders:

  • Upgrading a server’s RPM only occurs during remediation:
    • Attaching or detaching a software policy from a server does not—by itself—install, update or uninstall the RPM.
    • Updating the software policy with a newer RPM does not—by itself—install or upgrade the server.
  • To upgrade the RPMs on a managed server, the server must have a software policy attached that contains the updated RPM, and then the server must be remediated.
  • Once a server is remediated with a software policy attached that contains an RPM, the RPM on that server will thereafter be managed by that policy.
  • If an RPM was already installed on the managed server, and then you remediate a server with a software policy attached that contains that RPM, the pre-installed RPM will be adopted by the attached policy during the remediation process.