Actions
Story #3761
closed
As a user, I want to run crane on a remote server with published Docker content
Status:
CLOSED - WONTFIX
Priority:
Normal
Assignee:
-
Start date:
Due date:
% Done:
0%
Estimated time:
Platform Release:
Target Release - Docker:
Groomed:
No
Sprint Candidate:
No
Tags:
Pulp 2
Sprint:
Quarter:
Description
Motivation¶
Pulp supports to distribute content to remote servers using rsync
distributors. For e.g. RPM and ISO repositories, the published content
is sufficient to be able to serve repositories on the remote
server. The same should be possible for Docker content (requiring
Crane on the remote server to provide the Docker Registry API)
Problem¶
The files published by Pulp's Docker web distributor have two distinct users:
1. Apache httpd (or other web server) for serving static content
2. Redirect files for Crane
In contrast to other rsync distributors, the Docker rsync distributor
does not distribute the output of the web distributor. Instead it only
publishes the content (i.e. no redirect files) to support the CDN use
case.
Implementation options¶
- Enhance rsync distributor to create redirect files
Essentially, this requires the rsync publisher to do the same steps
as the web publisher
As the layout of the rsynced file tree should not change (i.e. no
`app` path), the redirect file should be at the same location as in
the 'master' tree of the web publisher (i.e. JSON file at the root
of the published tree). - Add a second rsync distributor that acts as a post-distributor of
the web publisher.
This would add a more 'conventional' rsync distributor.
Actions
.