Story #5003
closed
Story #3821: As a user, I can migrate from Pulp 2 to Pulp 3
As a user, I can use the REST API to dispatch a Pulp 2 to 3 migration task.
Status:
CLOSED - CURRENTRELEASE
Description
The Django app in the pulp-2to3-migrate[0] repo needs to provide a view that handles requests at /pulp/api/v3/migrate_pulp2/.
This view should accept 2 parameters: dry_run (boolean) and migration_plan (JSON object). Both of the parameters should be used to dispatch a task called "migrate_from_pulp2". This task should sleep for 1 second and then exit.
[0] https://github.com/pulp/pulp-2to3-migrate
- Groomed changed from No to Yes
- Sprint Candidate changed from No to Yes
I'm not sure why it needs to sleep and exit, however it's a detail and can be discussed/decided at implementation stage.
This is a no-op task for right now. The sleep statement is just for fun :)
- Status changed from NEW to ASSIGNED
- Assignee set to ttereshc
- Status changed from ASSIGNED to NEW
- Assignee deleted (
ttereshc)
- Status changed from NEW to ASSIGNED
- Assignee set to ttereshc
- Status changed from ASSIGNED to MODIFIED
- % Done changed from 0 to 100
Applied in changeset commit:pulp-2to3-migrate|c1829f92abc460551f2b03ced08942599d431332.
- Related to Test #5265: Test - As a user, I can use the REST API to dispatch a Pulp 2 to 3 migration task. added
- Status changed from MODIFIED to CLOSED - CURRENTRELEASE
- Project changed from Pulp to Migration Plugin
- Category deleted (
25)
- Sprint/Milestone deleted (
3.0.0)
- Status changed from CLOSED - CURRENTRELEASE to MODIFIED
- Status changed from MODIFIED to CLOSED - CURRENTRELEASE
- Sprint/Milestone set to 0.1.0
Also available in: Atom
PDF
.
Add model and dispatch a basic task for the migration tool
closes #5003 https://pulp.plan.io/issues/5003