Task #6516: Automatically produce a "complex" migration plan from "simple" migration plans - Migration Plugin - Pulp

Send by e-mail

Task #6516

Automatically produce a "complex" migration plan from "simple" migration plans

Added by dalley over 1 year ago. Updated 9 months ago.

Status:

CLOSED - CURRENTRELEASE

Priority:

Normal

Assignee:

dalley

Sprint/Milestone:

0.7.0

Start date:

Due date:

% Done:

100%

Estimated time:

Platform Release:

Groomed:

Sprint Candidate:

Tags:

Sprint:

Sprint 88

Quarter:

Description

The migration plugin code should only handle complex migration plans under the hood, as they are simpler to schedule work for. When a user creates a "simple" migration plan for a plugin, it should be transparently pre-processed such that the same codepaths are used as for the complex migration plans.

Associated revisions

Revision e243fcc2 View on GitHub
Added by dalley 9 months ago

Automatically produce a "complex" migration plan from simple ones

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

Revision e243fcc2 View on GitHub
Added by dalley 9 months ago

Automatically produce a "complex" migration plan from simple ones

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

Revision e243fcc2 View on GitHub
Added by dalley 9 months ago

Automatically produce a "complex" migration plan from simple ones

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

History

#1 Updated by ttereshc over 1 year ago

Tracker changed from Issue to Task
% Done set to 0

#2 Updated by ttereshc over 1 year ago

Sprint/Milestone set to 0.2.0

#3 Updated by ttereshc over 1 year ago

Priority changed from Normal to Low

#4 Updated by ipanova@redhat.com over 1 year ago

This will be a non user facing change. Simple migration plan will be translated into complex migration plan and used during the migration but to the user will still be returned simple plan