As a user I can create an RPM repository with an rsync distributor using ``pulp-admin``.
``pulp-admin rpm repo create`` provides the following new options for creating a repository:
--rsync-ssh-user - ssh user for remote server --rsync-ssh-identity-file - Absolute path to the private key that will be used as the identity file for ssh. The key has to be readable by user apache. --rsync-host - The hostname of the remote server. --rsync-root - Absolute path to the remote root directory where all the data (content and published content) lives. Remote equivalent to /var/lib/pulp. The repository’s relative url is appended to the root to determine the location of published repository. --rsync-content-units-only - If true, the distributor will publish content units only (e.g. /var/lib/pulp/content). The symlinks of a published repository will not be rsynced. --rsync-skip-repodata - If true, repodata will be omitted from the publish. --rsync-delete - If true, --delete is appended to the rsync command for symlinks and repodata so that any old files no longer present in the local published directory are removed from the remote server. --rsync-remote-units-path - the relative path from the root where unit files should live. Defaults to content/units.
When the user specifies a --rsync-ssh-user option, an ``rpm_rsync_distributor`` is added to the repository. The ``predistributor_id`` for the rsync distributor is ``yum_distributor``.
Updated by bmbouter over 3 years ago
- Status changed from NEW to CLOSED - WONTFIX
Pulp 2 is approaching maintenance mode, and this Pulp 2 ticket is not being actively worked on. As such, it is being closed as WONTFIX. Pulp 2 is still accepting contributions though, so if you want to contribute a fix for this ticket, please reopen or comment on it. If you don't have permissions to reopen this ticket, or you want to discuss an issue, please reach out via the developer mailing list.