Project

Profile

Help

Actions
Send by e-mail Copy link

Task #6516

closed

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

Added by dalley about 4 years ago. Updated about 3 years ago.

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

100%

Estimated time:
Platform Release:
Groomed:
No
Sprint Candidate:
No
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.

Actions
Copy link
 #1

Updated by ttereshc about 4 years ago

  • Tracker changed from Issue to Task
  • % Done set to 0
Actions
Copy link
 #2

Updated by ttereshc almost 4 years ago

  • Sprint/Milestone set to 0.2.0
Actions
Copy link
 #3

Updated by ttereshc almost 4 years ago

  • Priority changed from Normal to Low
Actions
Copy link
 #4

Updated by ipanova@redhat.com almost 4 years 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

Actions
Copy link
 #5

Updated by ttereshc over 3 years ago

  • Priority changed from Low to Normal
  • Sprint set to Sprint 78
Actions
Copy link
 #6

Updated by rchan over 3 years ago

  • Sprint changed from Sprint 78 to Sprint 79
Actions
Copy link
 #7

Updated by ttereshc over 3 years ago

  • Sprint/Milestone deleted (0.2.0)
Actions
Copy link
 #8

Updated by rchan over 3 years ago

  • Sprint changed from Sprint 79 to Sprint 80
Actions
Copy link
 #9

Updated by rchan over 3 years ago

  • Sprint changed from Sprint 80 to Sprint 81
Actions
Copy link
 #10

Updated by rchan over 3 years ago

  • Sprint changed from Sprint 81 to Sprint 82
Actions
Copy link
 #11

Updated by dalley over 3 years ago

  • Status changed from NEW to ASSIGNED
  • Assignee set to dalley
Actions
Copy link
 #12

Updated by rchan over 3 years ago

  • Sprint changed from Sprint 82 to Sprint 83
Actions
Copy link
 #13

Updated by rchan over 3 years ago

  • Sprint changed from Sprint 83 to Sprint 84
Actions
Copy link
 #14

Updated by rchan over 3 years ago

  • Sprint changed from Sprint 84 to Sprint 85
Actions
Copy link
 #15

Updated by rchan over 3 years ago

  • Sprint changed from Sprint 85 to Sprint 86
Actions
Copy link
 #16

Updated by rchan over 3 years ago

  • Sprint changed from Sprint 86 to Sprint 87
Actions
Copy link
 #17

Updated by rchan over 3 years ago

  • Sprint changed from Sprint 87 to Sprint 88
Actions
Copy link
 #18

Updated by dalley over 3 years ago

  • Status changed from ASSIGNED to POST

Added by dalley over 3 years ago

Revision e243fcc2 | View on GitHub

Automatically produce a "complex" migration plan from simple ones

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

Added by dalley over 3 years ago

Revision e243fcc2 | View on GitHub

Automatically produce a "complex" migration plan from simple ones

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

Added by dalley over 3 years ago

Revision e243fcc2 | View on GitHub

Automatically produce a "complex" migration plan from simple ones

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

Actions
Copy link
 #19

Updated by dalley over 3 years ago

  • Status changed from POST to MODIFIED
  • % Done changed from 0 to 100
Actions
Copy link
 #20

Updated by ttereshc over 3 years ago

  • Sprint/Milestone set to 0.7.0
Actions
Copy link
 #21

Updated by pulpbot about 3 years ago

  • Status changed from MODIFIED to CLOSED - CURRENTRELEASE
Actions
Send by e-mail Copy link

Also available in: Atom PDF