RPM Repositories

Triggering RPM Metadata Updates

When enabled, the metadata calculation is triggered automatically by some actions, and can also be invoked manually by others. Either way, the metadata produced is served to YUM clients.

Automatic

RPM metadata is automatically calculated:

1. When deploying/removing/copying/moving an RPM file.
2. When performing content import (both system and repository imports).

Manual

You can manually invoke RPM metadata calculation:

1. By selecting the local repository in the Tree Browser and clickingRecalculate Indexin theActionsmenu.
2. Via Artifactory'sREST-API.

Indexing the File List

Thefilelists.xmlmetadata 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 indexingfilelists.xml, set theEnable File List Indexingcheckbox.

Note that thefilelists.xmlmetadata 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 thefilelists.xmlfile 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.

Configuration

To create an RPM local repository, selectRPMas thePackage Typewhen you create the repository.

Local Repositories

To enable automatic RPM metadata calculation on a local RPM repository, in theRPM Settingssection of theBasicsettings screen, setAuto-calculate RPM Metadata.

REPO_ROOT/$ARTIFACT_NAME/$ARTIFACT_VERSION/$ARCHITECTURE/FILE_NAME - or - rpm-local/foo/1.0/x64/foo-1.0-x64.rpmm

Remote Repositories

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 ispoint 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:

1. In theAdminmodule underRepositories | Remote,click "New" to create a new remote repository.
2. Set theRepository Keyvalue, and specify the URL to the remote repository in theURLfield as displayed below.
   
3. Click "Save & Finish"
4. Back in theArtifactsmodule, in theTree Browser,select the repository. Note that in the Tree Browser, the repository name is appended with "-cache".
5. ClickSet Me Upand copy the value of thebaseurltag.
   
   
   
6. Next,create the/etc/yum.repos.d/targetCentos.repofile andpaste the following configuration into it:

[targetCentos] name=targetCentos baseurl=http://localhost:8081/artifactory/targetCentos/ enabled=1 gpgcheck=0

Virtual Repositories

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 avirtual repository, set thePackage Typeto beRPM,and select the underlying local and remote RPM repositories to include in theBasicsettingstab.

To allow deploying packages to this repository, set theDefault Deployment Repository.

Signing RPM Metadata

Artifactory supports using a GPG key to sign RPM metadata for authentication by the YUM client.

To generate a pair of GPG keys and upload them to Artifactory, please refer toGPG Signing.

Installing RPM Packages Using Yum

After configuring therpm-localrepository in Artifactory, you need to configure your local machine to install software packages from it by executing the following steps:

1. Edit theartifactory.repofile with root privileges

   sudo vi /etc/yum.repos.d/artifactory.repo

2. Pastethe following configurationinto theartifactory.repofile:

   [Artifactory] name=Artifactory baseurl=http://localhost:8081/artifactory/rpm-local/ enabled=1 gpgcheck=0

Now, every RPM file deployed to the root of therpm-localrepository can be installed using:

yum install 

Deploying RPM Packages

Once you have configured your local machine to install RPM packages from your RPM local repository, you may also deploy RPM packages to the same repositoryusing the UIor using theREST API.

Through the REST API you also have the option todeploy by checksumordeploying from an archive.

For example, to deploy an RPM package into a repository calledrpm-localyou could use the following:

curl -u: -XPUT http://localhost:8080/artifactory/rpm-local/ -T 

where PATH_TO_METADATA_ROOT specifies the path from the repository root to the deploy folder.

Deploying RPM Modules to Your Local Repository

You can deploy RPM modules to therepodatafolder using themodules.yamlfile which contains all the desired modules and then proceed to trigger a repository index to update therepomd.xmland other metadata files with the modules information.

1. You can perform the upload directly in the JFrog Platform UI or using the following command.

   curl -u : -XPUT"http://localhost:8081/artifactory/rpm-local/>/modules.yaml -T "

2. Trigger the reindex by running theCalculate YUM Repository Metadata API.

YUM Groups

百胜集团是一组收集的RPM包衣服ether 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 tosame 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.

Artifactory supports attaching aYUM Group fileto the YUM calculation essentially mimicking thecreaterepo -gcommand.

A group file can also be created by running the following command:

sudo yum-groups-manager -n "My Group" --id=mygroup --save=mygroups.xml --mandatory yum glibc rpm

Attaching a YUM Group

The process of attaching YUM group metadata to a local repository is simple:

1. 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 theyum-groups-managercommand fromyum-utils.
2. Deploy the created group file to therepodatafolder.
   Artifactory will automatically perform the following steps:
   • Create the corresponding.gzfile 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.gzfile) to therepomd.xmlfile.
3. Make sure the group file names are listed in theYUM Group File Namesfield 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:

Setting Group Properties

YUM group properties can be set in the/etc/yum.configfile as follows:

Yum Authentication

Proxy Server Settings

If your organization uses a proxy server as an intermediary for Internet access, specify theproxysettings in/etc/yum.conf.If the proxy server also requires authentication, you also need to specify theproxy_username, andproxy_passwordsettings.

proxy= proxy_username= proxy_password=pass

If you use the yum plugin (yum-rhn-plugin) to access the ULN, specify theenableProxyandhttpProxysettings in/etc/sysconfig/rhn/up2date.In addition, If the proxy server requires authentication, you also need to specify theenableProxyAuth,proxyUser, andproxyPasswordsettings as shown below.

enableProxy=1 httpProxy= enableProxyAuth=1 proxyUser= proxyPassword=

SSL Setting

YUM supports SSL from version 3.2.27.

To secure a repository with SSL, execute the following steps:

• Generate a private key and certificate usingOpenSSL.

• Define your protected repository in a.repofile as follows:

  [protected] name = SSL protected repository baseurl= enabled=1 gpgcheck=1 gpgKey= sslverify=1 sslclientcert= sslclientkey=

  where:
  gpgkeyis 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.
  I此选项设置,百胜将自动而作t the key from the specific URL. You will be prompted before the key is installed unless theassumeyesoption is set.

[main] cachedir=/var/cache/yum/$basearch/$releasever keepcache=0 debuglevel=2 logfile=/var/log/yum.log exactarch=1 obsoletes=1 gpgcheck=1 plugins=1 installonly_limit=3 [comments abridged]

You can view all the metadata that annotates an RPM by choosing it in Artifactory's tree browser and selecting theRPM Infotab:

Metadata Fields as Properties

The corresponding RPM metadata fields are automatically added as properties of an RPM artifact in YUM repositories accessed through Artifactory:

• rpm.metadata.name

• rpm.metadata.arch

• rpm.metadata.version

• rpm.metadata.release

• rpm.metadata.epoch

• rpm.metadata.group

• rpm.metadata.vendor

• rpm.metadata.summary

Properties can be used for searching and other functions. For more details please refer toProperties.

Watch the Screencast

Watch this short screencast to learn how easy it is to host RPMs in Artifactory.