Patch catalog - Debian Catalog

The Debian Catalog tab defines a number of options including locations (such as the location of the source files and the repository), as well as filters and whether local copies of the files are created on the target server or downloaded directly during deployment.

Note

After a catalog option update, ensure you update the patch catalog for the catalog option update to take effect.

The following sections provide information about the Debian Catalog tab:

Catalog Mode

Select one of two options:

Source from Debian (Online Mode): Use this mode if the BMC 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 Only) location of existing metadata and payload files
Metadata files stored in this location are copied to the catalog automatically. Payload files are not copied to the catalog.

Repository Location (NSH Path)

NSH path of the patch repository
This location must be on a Linux platform (Red Hat, SUSE or Oracle Enterprise Linux). BMC recommends that this location have ample free space. Repositories typically contain many files, usually totaling gigabytes of data.
Note: (Online Mode) You can copy pre-existing Errata and RPMs manually into this directory. BMC Server Automation does not download duplicate files from the Red Hat Network site.

Note

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

Depot Object Options

Enter the following information:

Field

Description

Network URL Type for Payload Deployment

(default) Copy to agent at staging: The BMC Server Automation Application Server copies patch payloads to a staging directory on the target server during the Deploy Job staging phase.
Agent mounts source for direct use at deployment (no local copy): A Deploy Job instructs the agent on a target server to: mount the device specified in the URl and deploy patch payloads directly to the agent. The Deploy Job does not copy patch payloads to a staging area on the agent, so the job does not create any local copies of the patches on target servers.

Network URL for Payload Deployment

The value entered here depends on your selection in the Network URL Type for Payload Deployment box:

If you chose Copy to agent at staging, do not enter a value here. The value is autopopulated based on the repository location.
If you chose Agent mounts source for direct use at deployment (no local copy), enter the NFS-accessible path to the location of the payload.
If you specify the host in this path as an IPv6 address, enclose the IPv6 address in square brackets.

RBAC Policy

Browse to and select a predefined ACL Policy. Permissions defined by the ACL Policy are assigned to all Depot objects created in the catalog.

Download From Vendor (only for Online Mode)

If you are creating a patch catalog to analyze which patches are missing on your targets, it is recommended that you leave the Download from Vendor check box unchecked. This ensures that only the metadata of the patches are downloaded at the time of catalog creation. You can then download the required missing patches during remediation.

However, if you want to download all patches in the at the time of catalog creation, you can select the Download from Vendor check box.

Distributions Tree View

This distributions tree view allows you to to expand the nodes and select the Version, Base URL, Distribution, Component, and Architecture of patches that you want to add to the catalog. See the screenshot below for an example of the distribution tree view.

Page tree