Story #2102
closedEasier way to configure Crane to serve both V1 and V2
0%
Description
In order to configure Crane to serve both V1 and V2 content, one has to make a directory containing symlinks to both the 'v1' and 'v2' directories Pulp publishes to. Older versions of Crane did not follow the symlinks when watching for changes, so Pulp published directories had to be moved around as well.
It would be nice if Crane could serve both V1 and V2 without needing specific configuration.
Related issues
Updated by dkliban@redhat.com about 8 years ago
- Sprint Candidate changed from No to Yes
- Tags 2.11 added
Updated by amacdona@redhat.com about 8 years ago
- Blocked by Story #2099: As a user, I can sync v2 schema manifests added
Updated by mhrivnak about 8 years ago
- Tags deleted (
2.11)
I think I understand what you're asking for, but please chime in if I'm misinterpreting your request.
I think if you want crane to serve both v1 and v2 content direct from pulp, you can just make these two symlinks:
ln -s /var/lib/pulp/published/docker/v1/web /var/lib/crane/metadata/v1
ln -s /var/lib/pulp/published/docker/v2/web /var/lib/crane/metadata/v2
Then it will serve all of your published repos via v1 and v2.
Especially considering that v1 content is nearly extinct at this point, I'm not sure it's worth trying to do something to make that even easier. What do you think?
Updated by amacdona@redhat.com about 6 years ago
- Sprint Candidate changed from Yes to No
Updated by bmbouter over 5 years ago
- Status changed from NEW to CLOSED - WONTFIX
Updated by bmbouter over 5 years ago
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.