Creating a patch catalog for SuSE Linux - Documentation for TrueSight Server Automation 21.3

Define options such as locations (location of the source files, the repository, the signature file, and so on) as well as filters and whether local copies of the files are created on the target server or downloaded directly during deployment.

Catalog Mode

Select one of two options:

Source from Vendor (Online Mode): Use this mode if the TrueSight Server Automation Application Server is installed on a server with Internet access.
Source from Disk Repository (Offline Mode): Use this mode in a secured environment where download occurs on a server, with Internet access, outside of the environment.

Repository Options

Enter the following information:

Field	Description
Payload Source Location (NSH Path)	(Offline mode only) Location of the XML files generated by the downloader and the corresponding payload files Metadata files stored in this location are copied to the catalog automatically. Payload files are not copied to the catalog. To support sourcing of vendor-supplied media, run the BMC Patch Downloader utility using the `-createRepo` option. This option creates the repository with the necessary metadata file. Then identify the source location here.
Repository Location (NSH Path)	NSH path to the patch repository. This location can be on a Linux platform (Red Hat, SUSE or Oracle Enterprise Linux). However BMC strongly recommends that this location be on a SUSE platform, because some SUSE-specific patches need to be stored only on a SUSE repository server. Also, ensure that the repository server has ample free space. Repositories typically contain many files, usually totaling gigabytes of data.

Field

Description

Payload Source Location (NSH Path)

(Offline mode only) Location of the XML files generated by the downloader and the corresponding payload files
Metadata files stored in this location are copied to the catalog automatically. Payload files are not copied to the catalog.
To support sourcing of vendor-supplied media, run the BMC Patch Downloader utility using the -createRepo option. This option creates the repository with the necessary metadata file. Then identify the source location here.

Repository Location (NSH Path)

NSH path to the patch repository. This location can be on a Linux platform (Red Hat, SUSE or Oracle Enterprise Linux). However BMC strongly recommends that this location be on a SUSE platform, because some SUSE-specific patches need to be stored only on a SUSE repository server.

Also, ensure that the repository server has ample free space. Repositories typically contain many files, usually totaling gigabytes of data.

Important

When specifying a host within an NSH path, you can use either the host name of the IP address (IPv4 or IPv6).

Filters

Filters limit the amount of information brought into the catalog. Use this procedure to re-create the same filters defined in the configuration file used by the Patch Downloader utility. You can define a filter during catalog creation or later, when editing the catalog.

There is no upper limit to the number of filter combinations you can create, but you must create at least one. Only those RPMs that match the combinations that you define (and their dependent RPMs) are added to the catalog.

To begin, you click Add Filter (as shown in the following figure), and then you provide values for the following options:

OS Flavor: Select the combination operating system and architecture from the list provided.
OS: The operating system, based on your selection in the OS Flavor box, is supplied automatically in a read-only box.
Architecture: The architecture, based on your selected in the OS Flavor box, is supplied automatically in a read-only box.
OS Level: The operating system level of the files to be downloaded.

(Online Only) In Online mode, the SUSE filter XML file contains the following URLs for a combination of OS and Architecture: Online, Updates, and Pool. Depending on which updates need to be downloaded, select one or more of the following options:

Update: The latest updates for the specified OS level. If you select the Updates option, you must ensure that your target is at the OS level for which you require the updates. For example, if you select the Update option for SUSE Linux Enterprise 10 SP1, you must upgrade your target to SUSE Linux Enterprise 10 SP1 before applying the updates.
Online: Updates from the previous OS level to the specified OS level. You must use the Online option only when you want to bring your target from the existing OS level to the next OS level. For example, you must use the Online option if you want to bring your target from SUSE Linux Enterprise 10 SP2 to SUSE Linux Enterprise 10 SP3.
Pool: All the updates until the specified OS level. For an OS-Architecture combination, if you require the updates from an OS level to the next or the latest OS level, you must use the Pool option. For example, you must use the Pool option if you want to bring your target from SUSE Linux Enterprise 10 SP1 to SUSE Linux Enterprise 10 SP4.
Note: The Pool option includes the updates provided in the Online option, so selecting the Online option and the Pool option together is not required.

(Optional) On the Patch Global Configuration tab, you may also specify the SUSE override filters list file by performing the following steps:

Import the file into the Depot workspace
Point to this Depot path on the Patch Global Configuration tab.
The drop-down list for Service Packs in the SUSE Linux Catalog tab displays only the service packs specified in the SUSE filters list file.