Project

Profile

Help

Story #5549

closed

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

As a user, I can migrate content only

Added by ttereshc almost 5 years ago. Updated about 4 years ago.

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

0%

Estimated time:
Platform Release:
Groomed:
No
Sprint Candidate:
No
Tags:
Sprint:
Quarter:

Description

Currently the migration plugin supports migration of repositories and content.
Some users might need to migrate content only and later create repositories by themselves.

To support this use case, repository/importers/distributors/on_demand content migration and pre-migration steps should be skipped. Only downloaded content should be migrated.

If a migration plan doesn't contain repositories section for a plugin, it means that only content should be migrated.

Actions #1

Updated by dalley almost 5 years ago

  • Status changed from NEW to ASSIGNED
Actions #2

Updated by dalley over 4 years ago

  • Assignee set to dalley
Actions #3

Updated by dalley over 4 years ago

  • Status changed from ASSIGNED to NEW
  • Assignee deleted (dalley)
Actions #4

Updated by ttereshc over 4 years ago

  • Project changed from Pulp to Migration Plugin
Actions #5

Updated by ttereshc over 4 years ago

  • Description updated (diff)
  • Status changed from NEW to CLOSED - WONTFIX

So far no one expressed a need to migrate content only. Moreover, it would be possible only for downloaded content, since migrating on_demand content requires migration of importers.

In case, the is a desire to migrate content only, please re-open this story or file a new one.

Actions #6

Updated by bmbouter about 4 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