Project

Profile

Help

Story #5363

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

Story #3822: As a user, I can migrate all content units of a specific type from Pulp 2 to Pulp 3

As a user, I can migrate docker content units from Pulp 2 into Pulp 3

Added by ipanova@redhat.com about 2 months ago. Updated 7 days ago.

Status:
MODIFIED
Priority:
Normal
Category:
-
Sprint/Milestone:
-
Start date:
Due date:
% Done:

100%

Platform Release:
Blocks Release:
Backwards Incompatible:
No
Groomed:
No
Sprint Candidate:
No
Tags:
QA Contact:
Complexity:
Smash Test:
Verified:
No
Verification Required:
No
Sprint:
Sprint 60

Description

Desired workflow for migrating docker content
h5. 1. Create a migration plan by POSTing to /pulp/api/v3/migration-plans/ the following JSON.

{  
    "plugins": [ 
       {
         "type": "docker",
       }
    ]
}
2. Run the migration plan

POST request to /pulp/api/v3/migration-plans/asdf-2345-ghjk-4567-adc/run/

Implementation details

Inherit from DeclarativeContentMigration and create pipeline for docker content migration.

As a result of this MP task docker blobs, manifests, manifest list and tags will be migrated

History

#1 Updated by ipanova@redhat.com about 2 months ago

  • Status changed from NEW to ASSIGNED
  • Assignee set to ipanova@redhat.com
  • Sprint set to Sprint 58

#2 Updated by rchan about 1 month ago

  • Sprint changed from Sprint 58 to Sprint 59

#3 Updated by rchan 19 days ago

  • Sprint changed from Sprint 59 to Sprint 60

#4 Updated by ipanova@redhat.com 14 days ago

  • Status changed from ASSIGNED to POST

#5 Updated by ipanova@redhat.com 7 days ago

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

Please register to edit this issue

Also available in: Atom PDF