Creating a patch catalog for Debian or Ubuntu
The patch catalog is used to maintain and work with the patch repository through the TrueSight Server Automation Console. For both types of repositories, online and offline, you create a patch catalog through the TrueSight Server Automation console. Patches are added to the catalog as depot objects according to filters defined for the catalog.
This topic describes how to set up a patch catalog for Debian or Ubuntu, and includes the following sections:
- Step 1: Review prerequisites for the catalog
- Step 2: Create the patch catalog
- Editing the options
- Where to go from here
Step 1: Review prerequisites for the catalog
Review the following prerequisites for creating patch catalogs for Debian and Ubuntu.
- Ensure that security policies on the repository server do not block the download of the catalog.
Ensure that the system you will use for the patch repository is supported by TrueSight Server Automation.
Step 2: Create the patch catalog
- Right-click a folder in the Depot and select New > Patch catalog > Debian Linux Patch Catalog.
The New Patch Catalog dialog panel opens. This option applies to both Debian and Ubuntu. Provide information for the patch catalog as described in the following table:
Panel section
Description
General
Enter a Name for the patch catalog and a Description of its contents. Then, browse to the folder in which you want to store the catalog.
Catalog options
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.
- In the bottom right corner, select Job options. (You can also edit the catalog at a later time to set these options).
Provide information for the patch catalog options as described in the following table:
Tab
Description
Schedules
Job Run Notifications
Depot Object Options
Network URL Type for Payload Deployment
- (default) Copy to agent at staging: The TrueSight 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.
Max Deport Object Work Items to Process in Parallel
Maximum number of work items that can be performed in parallel.
Job Properties
Permissions
- Click Finish.
A Patch Catalog is stored in the appropriate Depot folder.
Editing the options
- In the Depot, right-click the Debian Linux Patch Catalog you just created.
- Select Open.
- Set or update any information for the patch catalog options.
- When finished, save the catalog.
Where to go from here