Story #5343
closed
Story #3821: As a user, I can migrate from Pulp 2 to Pulp 3
Story #5307: As a user, I can migrate repositories from Pulp2 to Pulp3
As a user, I can migrate Pulp 2 distributor into publication/distribution in Pulp 3
100%
Description
Based on pre-migrated data for distributors and repositories, create publications and distributors in Pulp 3.
It's plugin's responsibility, the core part of the migration plugin should introduce plugin API for this.
This step should happen after repo version creation.
See the Migration Plan schema in #5178 for the way to specify which Pulp2 distributors for which repos to use.
By default, when all repositories are migrated and no specification is present for distributors, plugin decides what happens, however it needs to be provided with all distributors for a repo at once.
Related issues
Updated by ttereshc over 3 years ago
- Blocked by Story #5342: As a user, I can migrate repository into a set of repository versions added
Updated by ipanova@redhat.com over 3 years ago
- Status changed from NEW to ASSIGNED
- Assignee set to ipanova@redhat.com
- Sprint set to Sprint 61
Updated by ipanova@redhat.com over 3 years ago
- Groomed changed from No to Yes
- Tags Pulp 2 to 3 Migrate added
Updated by ipanova@redhat.com over 3 years ago
- Status changed from ASSIGNED to POST
Added by ipanova@redhat.com over 3 years ago
Updated by ipanova@redhat.com over 3 years ago
- Status changed from POST to MODIFIED
- % Done changed from 0 to 100
Applied in changeset pulp-2to3-migration|a0d81795fb20d94981154efde41f0bc35754439d.
Updated by ttereshc almost 3 years ago
- Status changed from MODIFIED to CLOSED - CURRENTRELEASE
- Sprint/Milestone set to 0.1.0
Updated by bmbouter almost 3 years ago
- Tags deleted (
Pulp 2 to 3 Migrate)
We're removing the 'Pulp 2 to 3 Migrate' tag to allow membership of the Migration Plugin project in Redmine to be the controlling area https://pulp.plan.io/projects/migration
.
Migrate distributors.
closes #5343