Project

Profile

Help

Task #5476

closed

Story #3821: As a user, I can migrate from Pulp 2 to Pulp 3

Let plugin migrate all its content models at once and not one by one

Added by ttereshc over 3 years ago. Updated over 2 years ago.

Status:
CLOSED - CURRENTRELEASE
Priority:
Normal
Assignee:
Sprint/Milestone:
Start date:
Due date:
% Done:

100%

Estimated time:
Platform Release:
Groomed:
Yes
Sprint Candidate:
Yes
Tags:
Sprint:
Sprint 60
Quarter:

Description

Plugins like Docker and RPM need to process multiple content types at once because they are related.

Currently the migration plugin pre-migrates and then migrates content type by type.
To give plugins more flexibility, the migration plugin should:
- separate pre-migration and migration for content
- pre-migrate all the content before triggering any plugin specific content migration
- introduce an interface which plugin will define and the migration plugin will use to trigger plugin specific content migration
- adjust ISO content migration to use this interface.

Actions #1

Updated by dkliban@redhat.com over 3 years ago

  • Groomed changed from No to Yes
  • Sprint Candidate changed from No to Yes
  • Sprint set to Sprint 59
Actions #2

Updated by dkliban@redhat.com over 3 years ago

  • Tags Pulp 2 to 3 Migrate added
Actions #3

Updated by ipanova@redhat.com over 3 years ago

  • Status changed from NEW to ASSIGNED
Actions #4

Updated by ttereshc over 3 years ago

  • Status changed from ASSIGNED to POST

Added by ttereshc over 3 years ago

Revision 745e81a7

Separate pre-migration and migration steps for content

Give plugins more control over migration flow. Introduce a migrator interface.

closes #5476 https://pulp.plan.io/issues/5476

Added by ttereshc over 3 years ago

Revision 745e81a7

Separate pre-migration and migration steps for content

Give plugins more control over migration flow. Introduce a migrator interface.

closes #5476 https://pulp.plan.io/issues/5476

Added by ttereshc over 3 years ago

Revision 745e81a7

Separate pre-migration and migration steps for content

Give plugins more control over migration flow. Introduce a migrator interface.

closes #5476 https://pulp.plan.io/issues/5476

Actions #5

Updated by rchan over 3 years ago

  • Sprint changed from Sprint 59 to Sprint 60
Actions #6

Updated by ttereshc over 3 years ago

  • Status changed from POST to MODIFIED
  • % Done changed from 0 to 100

Applied in changeset commit:pulp-2to3-migrate|745e81a7c620527b0b72c0f3f1c73a0fd69737b1.

Actions #7

Updated by ttereshc about 3 years ago

  • Project changed from Pulp to Migration Plugin
Actions #8

Updated by ttereshc almost 3 years ago

  • Status changed from MODIFIED to CLOSED - CURRENTRELEASE
  • Sprint/Milestone set to 0.1.0
Actions #9

Updated by bmbouter over 2 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

Also available in: Atom PDF