zlmmirror - Mirrors bundles and catalogs of software, in whole or in part, from remote ZENworks Linux Management, YaST Online Updates, Novell Updates, YUM, and Red Hat Network servers, to your local ZENworks Linux Management server or to a local directory. For detailed information about mirroring Dell Update Packages to your ZENworks server, see Mirroring Software in the ZENworks 7.3 Linux Management Administration Guide.
zlmmirror [command] [options] [arguments]
This command reads the information necessary to connect to the local and remote server from an XML configuration file. Detailed information on creating zlmmirror configuration files is included in the ZENworks 7.3 Linux Management Administration Guide.
zlmmirror enables you to connect to a remote server and copy software catalogs, bundles, or packages from the remote server to your server using a few simple commands. Software can be mirrored from the following servers:
ZENworks Linux Management
Dell Update Packages (DUPs)
YaST Online Updates
Red Hat* Network
Red Carpet Enterprise or ZENworks 6.x Linux Management
Novell Updates
YUM
Novell, Dell, SUSE, and Red Hat each maintain servers of their respective types, enabling you to simply mirror the catalogs and bundles you are interested in without maintaining or updating these repositories. Mirroring is the preferred method of obtaining the majority of the software you distribute to managed devices.
During use, zlmmirror connects to the remote server, the local server, and to the zlman program, authenticating itself each time. It should be run on the same system as zlman and the rest of the ZENworks Linux Management server, and requires root privileges.
All of the commands below accept the option flags listed in the Global Options section. In addition, they accept individual options as listed with each command.
These commands are used to create, convert, and validate zlmmirror configuration files.
Converts the specified rcmirror.conf configuration file to the new XML format.
Creates a new, empty configuration file showing all possible fields.
Checks the configuration file for errors, and display the parsed configuration information.
These commands allow you to view the catalogs, bundles, and packages on the remote server.
Lists the packages available in the specified bundle. Accepts the following option flags:
Lists the bundles available in the specified catalog. Accepts the following option flags:
Lists the packages available in the specified catalog. Accepts the following option flags:
Lists the bundles available on the remote server. Accepts the following option flags:
Lists the catalogs available on the remote server. Accepts the following option flags:
Lists the packages available on the remote server. Accepts the following option flags:
The mirror command is used to perform the actual mirroring operation contained in zlmmirror.xml.
Performs a mirroring operation. Accepts the following option flags:
Displays a help message.
Logs messages to a file. If no log file is specified, the default (/var/opt/novell/log/zenworks/zlmmirror.log) is used.
Displays verbose output.
Prints zlmmirror version information and exits.
Remote server connection timeout (seconds).
The default configuration file.
You must create a different XML configuration for each remote server you mirror. A template XML file can be created using the conf-generate command. See the ZENworks Linux Management Administration Guide for detailed instructions on mirroring.
The following is a description of the sections contained in the zlmmirror XML configuration file. You must provide details about the remote server containing the software you want to mirror, and the local server, which is your ZLM server receiving the mirrored software, as well as information on the catalogs, bundles, and packages you want mirrored.
The remote server is specified according to the following:
Base - Path to the server you want to mirror, in the following format depending on Type:
ZLM: https://server
DELL: http://ftp.dell.com
RCE: https://server/path
YaST: http(s)://server/path or ftp://server/path
RHN: http(s)://server/path
NU: https://nu.novell.com/repo
YUM: YUM respositories for SUSE such as http://poincare.suse.de/testrepo/
Type - Type of server you want to mirror:
ZLM: ZENworks 7 Linux Management
DELL: Dell Update Package FTP Server
RCE: Red Carpet Enterprise, or ZENworks 6.x Linux Management
YaST: YaST Online Updates
RHN: Red Hat Network
NU: Novell Updates
YUM: Yellow Dog Updater, Modified
User - Name to use when connecting to the remote server. If no user is specified, zlmmirror reads the identity from the following location depending on Type:
ZLM: /etc/opt/novell/zenworks/zmd/deviceid on SLES 9 and OES, and /etc/zmd/deviceid on SLES 10 and SLED 10
RCE: /etc/ximian/mcookie
YaST: /etc/sysconfig/onlineupdate
NU: /etc/opt/novell/zenworks/zmd/deviceid on SLES 9 and OES, and /etc/zmd/deviceid on SLES 10 and SLED 10
YUM: Does not require any authentication.
When connecting to an RHN server or a Dell Server, leave this element empty.
Password - Password to use when connecting to the remote server. If no password is specified, zlmmirror reads the password from the following location depending on Type:
ZLM: /etc/opt/novell/zenworks/zmd/secret on SLES 9 and OES, /etc/zmd/secret on SLES 10 and SLED 10
RCE: /etc/ximian/partnernet
YaST: /etc/sysconfig/onlineupdate
NU: /etc/opt/novell/zenworks/zmd/secret on SLES 9 and OES, /etc/zmd/secret on SLES 10 and SLED 10
YUM: Does not require any authentication
When connecting to an RHN server or a Dell Server, leave this element empty.
Proxy - The Proxy configuration element is optional and is used with an Internet Proxy. You can add the Proxy element anywhere in the RemoteServer section. If the Internet proxy requires authentication, the format looks like the following example:
<Proxy>http://username:password@server:port</Proxy>
If the Internet proxy does not require authentication, the format looks like the following example:
<Proxy>https://server:port</Proxy>
SystemID - To mirror from the RHN server, you must add the SystemID configuration element in the zlmmirror configuration file. You can use the systemid file that has a valid authentication to the RHN server. You need to provide the complete path of the systemid file that is located on the ZENworks Server. The format looks like the following example:
<SystemID> /etc/opt/novell/zenworks/zlmmirror-example-rhn-conf.xml</SystemID>
The local server is specified according to the following:
Base - If the Type attribute is ZLM, leave this field empty. If the Type attribute is STATIC, enter the path to the local directory where you want the packages copied, in the following format: /path/on/filesystem.
Type - Type of mirroring you want to perform:
ZLM: Mirrors catalogs and bundles directly to your ZENworks Linux Management server. After mirroring, mirrored catalogs and bundles are displayed in the ZENworks Control Center.
You cannot perform ZLM mirroring on Secondary Servers.
STATIC: Mirrors packages to the file system of your ZENworks Linux Management server, but does not add them to ZENworks.
You can perform only static mirroring on Secondary Servers.
User - Name to use when connecting to your ZENworks Linux Management (local) server. The Administrator user should be specified if you want to use the default administrator account.
Password - Password for the account provided in User. If you are using the Administrator account, this is the password you specified during the server installation.
Each bundle and package you want to mirror must be contained in a catalog on the remote server, so Catalog is the only item necessary to mirror a catalog, bundle, or package. A configuration file can have multiple Catalog elements, and each catalog you want to mirror must have its own entry.
Local Name - Name of the catalog you want the mirrored software placed in. If no Local Name is specified, the catalog name from the source server is used. The local name for the catalog should not be same as that reserved for the <catalogname>-patches folder.
Folder - Specifies the eDir folder (such as /folder1/folder2) where bundles and catalogs are created and updated. If not specified, the catalogs and bundles are created and updated in the /zlmmirror folder.
Target - Restricts the mirroring operation on the catalog to packages and patches that support the specified target platforms. If the target is not specified, packages for all platforms are mirrored. This element can be specified multiple times, and can contain either a target name or a regular expression string for matching target names. For example, to include targets beginning with sles such as sles-9-i586, use the regular expression <Target>sles.*</Target>.
ExcludeTarget - Same as Target, except packages and patches supporting the specified target platforms are excluded. ExcludeTarget is performed after Target, so platforms appearing in a Target and ExcludeTarget are ultimately excluded. For example, to exclude targets that end with i586 such as sles-9-i586, use the regular expression <ExcludeTarget>.*i586</ExcludeTarget>.
Bundle - Restricts the mirroring operation on the catalog to the specified bundles. If the bundle is not specified, all bundles are mirrored. This option is valid only for ZLM, NU, and YaST source servers. It can be specified multiple times, and can contain either a bundle name or a regular expression string for matching bundle names. See the note below about regular expressions for more information.
LocalBundleName - Renames the bundle name locally.This is applicable only for the RCE, NU, and RHN services in which a catalog has only one bundle on the remote server. If you specify <LocalBundleName>, you must not specify the <Bundle> tag. This tag is not applicable when you mirror OES from the RCE service with more than one bundle per catalog.
ExcludeBundle - Same as Bundle, except packages and patches contained in the specified bundle or bundles are excluded. This option is valid only for ZLM, NU, and YaST source servers, can be specified multiple times, and can contain either a bundle name or a regular expression string for matching bundle names. ExcludeBundle is performed after Bundle, so bundles appearing in a Bundle and ExcludeBundle are ultimately excluded. See the note below about regular expressions for more information.
Package - Restricts the mirroring operation on the catalog to the specified packages. If the package is not specified, all packages are mirrored. This option can be specified multiple times, and can contain either a package name or a regular expression string for matching package names. This option is not supported for patch bundles. Filtering of packages in a patch bundle is not supported for RCE, YaST, and NU type of remote servers. See the note below about regular expressions for more information.
ExcludePackage - Same as Package, except specified packages are excluded. This option can be specified multiple times, and can contain either a package name or a regular expression string for matching package names. This option is not supported for YOU patches. ExcludePackage is performed after Package, so packages appearing in a Package and ExcludePackage are ultimately excluded. See the note below about regular expressions for more information.
Category: Restricts the mirroring operation on the catalog to the specified categories of patch bundles. If the category is not specified, all patch bundles are mirrored. Valid values are recommended, optional, and security. This tag is applicable only for the RCE type servers and NU type servers of SLES 10, SLED 10, and OES 2.
ServicePackGroups - Accepts Boolean values (true or false) only. By default <ServicePackGroups> is set to true, and it automatically creates bundle groups. This option is supported for YOU patches only.
AutoDeploy - Mirroring the packages to existing bundle creates a newer version of the bundle and deploys it on the server. If AutoDeploy is set to false, then the mirroring operation restricts the deployment of the newer bundle. Accepts only the boolean values (true or false). By default, the option is set to true.
CreateMonolithicBundle - Automatically creates monolithic package bundles consisting of only latest package rpms. It creates a separate monolithic bundle for each Service Pack release, and a separate monolithic bundle with the updates after the latest Service Pack release. It accepts Boolean values (true or false) only. By default the option is set to true. This option is supported for YOU patches only.
FilterPatchRPM - Restricts the mirroring operation of the YOU patch bundles to filter all the packages of the .patch.rpm type. This option creates an equivalent RPM package bundle in the local server. Accepts only the Boolean values (true or false). By default, the option is set to false. This option is supported only for the YOU patches.
NOTE:The use of regular expressions (regexes) has changed in ZENworks 7.3 Linux Management. ZENworks Linux Management does not use wildcard character matching. In ZENworks Linux Management 6.6.x, you can use a wildcard expression string instead of a regular expression string. In ZENworks 7.3 Linux Management, you should use <Bundle>patch-.*</Bundle> to mirror all bundles with the name starting with “patch-”. ZENworks Linux Management supports all the Java regular expressions. For more information on the Java regular expressions, see the Java documentation.
Copyright 2005-2010, Novell, Inc.. All rights reserved.
rug (1) Novell, zlman (1) Novell, zmd (8) Novell, zlm-debug (1) Novell, zrmservice (1) Novell
To report problems with this software or its documentation, visit Novell Bugzilla.