Actions
Story #2127
closedAs a user I can update an RPM repository with an rsync distributor using ``pulp-admin``.
Status:
CLOSED - WONTFIX
Priority:
Normal
Assignee:
-
Sprint/Milestone:
-
Start date:
Due date:
% Done:
0%
Estimated time:
Platform Release:
Groomed:
No
Sprint Candidate:
No
Tags:
Pulp 2
Sprint:
Quarter:
Description
``pulp-admin rpm repo update`` provides the following new options for updating 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``. If an rsync distributor already exists for the repository, the distributor config is updated.
Actions