Metadata calculation cleans up RPM metadata that already existed as a result of manual deployment or import. This includes RPM metadata stored as SQLite database files.
Indexing the File List
The filelists.xml metadata file of an RPM repository contains a list of all the files in each package hosted in the repository. When the repository contains many packages, reindexing this file as a result of interactions with the YUM client can be resource intensive causing a degradation of performance. Therefore, from version 5.4, reindexing this file is initially disabled when an RPM repository is created. To enable indexing filelists.xml, set the Enable File List Indexing checkbox.
Note that the filelists.xml metadata file for a virtual repository may not be complete (i.e. it may not actually list all the files it aggregates) if any of the repositories it aggregates do not have file listing enabled. Note that if indexing of the filelists.xml file is disabled, it is not possible to search for a file using the YUM client to determine which package wrote the queried file to the filesystem.
To create an RPM local repository, select RPM as the Package Type when you create the repository.
To enable automatic RPM metadata calculation on a local RPM repository, in the RPM Settings section of the Basic settings screen, set Auto-calculate RPM Metadata.
RPM Metadata Folder Depth
Informs Artifactory under which level of directory to search for RPMs and save the repodata directory.
By default this value is 0 and refers to the repository's root folder. In this case, Artifactory searches the entire repository for RPMs and saves the repodata directory at $REPO-KEY/repodata.
Using a different depth is useful in cases where generating metadata for a repository separates its artifacts by name, version and architecture. This will allow you to create multiple RPM repositories under the same Artifactory RPM repository.
For example: If the repository layout is similar to that shown below and you want to generate RPM metadata for every artifact divided by name, set the Depth to 1 and the repodata directory is saved at REPO_ROOT/ARTIFACT_NAME/repodata :
- or -
When changing the configured depth of existing repository, packages indexed in the old depth might need to be re-indexed or moved to a new depth to be available in the new configured depth, and YUM clients might need to change their configuration to point to the new depth.depth.
Auto-calculate RPM Metadata
When set, RPM metadata calculation is automatically triggered by the actions described above.
Enable File List Indexing
When set, RPM metadata calculation will also include indexing the filelists.xml metadata file.
RPM Group File Names
A comma-separated list of YUM group files associated with your RPM packages.
Note that at each level (depth), the repodata directory in your repository may contain a different group file name, however each repodata directory may contain only 1 group metadata file (multiple groups should be listed as different tags inside the XML file. For more details, please refer to the YUM Documentation).
Metadata calculation is asynchronous and does not happen immediately when triggered, whether automatically or manually.
Artifactory invokes the actual calculation only after a certain "quiet period", so the creation of metadata normally occurs only 1-2 minutes after the calculation was triggered.
Artifactory remote repositories support RPMs out-of-the-box, and there no need for any special configuration needed in order to work with RPMs in a remote repository.
All you need to do is point your YUM client at the remote repository, and you are ready to use YUM with Artifactory.
To define a remote repository to proxy an RPM remote repository, follow the steps below:
In the Admin module under Repositories | Remote, click "New" to create a new remote repository.
Set the Repository Key value, and specify the URL to the remote repository in the URL field as displayed below.
Click "Save & Finish"
Back in the Artifacts module, in theTree Browser, select the repository. Note that in the Tree Browser, the repository name is appended with "-cache".
Click Set Me Up and copy the value of the baseurl tag.
Next, create the /etc/yum.repos.d/targetCentos.repo file and paste the following configuration into it:
A Virtual Repository defined in Artifactory aggregates packages from both local and remote repositories. This allows you to access both locally hosted RPM packages and remote proxied RPM repositories from a single URL defined for the virtual repository. To define a virtual YUM repository, create a virtual repository, set the Package Type to be RPM, and select the underlying local and remote RPM repositories to include in the Basic settingstab.
where PATH_TO_METADATA_ROOT specifies the path from the repository root to the deploy folder.
A YUM group is a set of RPM packages collected together for a specific purpose. For example, you might collect a set of "Development Tools” together as a YUM group.
A group is specified by adding a group XML file to same directory as the RPM packages included in it. The group file contains the metadata of the group including pointers to all the RPM files that make up the group.
The process of attaching YUM group metadata to a local repository is simple:
Create an XML file in the groups format used by YUM. You can either just type it out manually using any text editor, or run the yum-groups-manager command from yum-utils.
Deploy the created group file to the repodata folder. Artifactory will automatically perform the following steps:
Create the corresponding .gz file and deploy it next to the deployed group XML file.
Invoke a YUM calculation on the local repository.
Attach the group information (both the XML and the .gz file) to the repomd.xml file.
Make sure the group file names are listed in the YUM Group File Names field under the Basic tab of the repository configuration. This tells Artifactory which files should be attached as repository group information.
YUM Group Commands
The following table lists some useful YUM group commands:
yum groupinstall <Group ID>
Install the YUM group. The group must be deployed to the root of the YUM local repository.
yum groupremove <Group ID>
Remove the RPM group
yum groupupdate <Group ID>
Update the RPM group. The group must be deployed to the root of the YUM local repository.
yum groupinfo <Group ID>
List the RPM packages within the group.
yum grouplist | more
List the YUM groups
Setting Group Properties
YUM group properties can be set in the /etc/yum.config file as follows:
0 or 1
Determines YUM's behavior if two or more repositories offer package groups with the same name.
If set to1 then the group packages of the last matching repository will be used.
If set to 0 then the groups from all matching repositories will be merged together as one large group.
0 or 1
Determines YUM's behavior when the groupremove command is run.
If set to 0 (default) then all packages in the group will be removed.
If set to 1 then only those packages in the group that aren't required by another package will be removed.
0 or 1
Determines whether YUM will allow the use of conditionals packages.
If set to 0 then conditionals are not allowed
If set to 1 (default) package conditionals are allowed.
optional, default, mandatory
Tells YUM which type of packages in groups will be installed when groupinstall is called. Default is: default, mandatory
Proxy Server Settings
If your organization uses a proxy server as an intermediary for Internet access, specify the proxy settings in /etc/yum.conf. If the proxy server also requires authentication, you also need to specify the proxy_username, and proxy_password settings.
proxy=<proxy server url>
If you use the yum plugin (yum-rhn-plugin) to access the ULN, specify the enableProxy and httpProxy settings in /etc/sysconfig/rhn/up2date. In addition, If the proxy server requires authentication, you also need to specify the enableProxyAuth, proxyUser, and proxyPassword settings as shown below.
httpProxy=<proxy server url>
YUM supports SSL from version 3.2.27.
To secure a repository with SSL, execute the following steps:
Generate a private key and certificate using
Define your protected repository in a .repo file as follows:
name = SSL protected repository
baseurl=<secure repo url>
gpgKey=<URL to public key>
sslclientcert=<path to .cert file>
sslclientkey=<path to .key file>
where: gpgkey is a URL pointing to the ASCII-armored GPG key file for the repository . This option is used if YUM needs a public key to verify a package and the required key has not been imported into the RPM database. If this option is set, YUM will automatically import the key from the specific URL. You will be prompted before the key is installed unless the assumeyes option is set.
Using Yum Variables
You can use and reference the following built-in variables in yum commands and in all YUM configuration files (i.e. /etc/yum.conf and all .repo files in the /etc/yum.repos.d/ directory):
This is replaced with the package's version, as listed in distroverpkg. This defaults to the version of the redhat-release package.
This is replaced with your system's architecture, as listed by os.uname() in Python.
This is replaced with your base architecture. For example, if $arch=i686 then $basearch=i386
The following code block is an example of how your /etc/yum.conf file might look: