Actions
Story #5307
closedStory #3821: As a user, I can migrate from Pulp 2 to Pulp 3
As a user, I can migrate repositories from Pulp2 to Pulp3
Start date:
Due date:
% Done:
100%
Estimated time:
(Total: 0:00 h)
Platform Release:
Groomed:
No
Sprint Candidate:
No
Tags:
Sprint:
Quarter:
Description
It's an epic to migrate repositories and everything related to them (importers, distributors).
Simple case(when everything is migrated, no details in the Migration Plan):
- create a repo
- create a remote (plugin's responsibility)
- migrate content
- create a repo version
- -create content guards (plugin's responsibility)-
- create publications/distributions (plugin's responsibility)
Complicated case (very similar, just ensure not to migrate eveything) :
- repo (only mentioned in a MP)
- remote (plugin) (only mentioned in a MP)
- migrate content
- repo versions (in a specific order mentioned in a MP)
- -create content guards (plugin)-
- create publications/distributions (plugin) (only mentioned in a MP)
Updated by ttereshc about 5 years ago
- Blocks Story #5337: As a user, I can fully migrate on_demand content added
Updated by ttereshc about 5 years ago
- Blocks deleted (Story #5337: As a user, I can fully migrate on_demand content)
Updated by ttereshc almost 5 years ago
- Project changed from Pulp to Migration Plugin
Updated by ttereshc over 4 years ago
- Status changed from NEW to CLOSED - CURRENTRELEASE
- Sprint/Milestone set to 0.1.0
Actions