Project

Profile

Help

Story #3822

closed

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

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

Added by dkliban@redhat.com over 5 years ago. Updated almost 4 years ago.

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

100%

Estimated time:
(Total: 0:00 h)
Platform Release:
Groomed:
No
Sprint Candidate:
No
Tags:
Katello
Sprint:
Quarter:

Description

Description

Pulp 3 will provide a tool called pulp-2to3-migrate. This tool is going to be a Pulp 3 plugin. This tool is going to be modular. Some functionality will come from the core, but specific implementation for each content type will be provided by the plugins.

Users of this tool will be required to write a Migration Plan which is a JSON document that describes which content, repositories, importers, and distributors get migrated from Pulp 2 to Pulp 3. Users will be able to use Pulp 2 to generate a Migration plan for migrating everything.

Features

Pulp 2 will provide a REST API that returns a default Migration Plan.

This Migration Plan will migrate all content, all repositories, all importers, and all distributors.

Pulp 3 will provide a REST API that will accept two parameters: Migration Plan and concurrency.

This API will dispatch one more tasks to perform the migration. The default concurrency will be (Pulp 3 worker count) - 1. The concurrency will determine the number of tasks that will be dispatched in parallel. The tasking system will limit one migration "operation" at a time, although many tasks may run concurrently for that operation.

Content Migration implementation details

For each content unit discovered during migration of content, the following will be performed:

  • create a hard link in /var/lib/pulp/artifacts/ directory
  • create Artifact in the database
  • create Content in the database
  • record progress by storing references for pulp 2 and pulp 3 content unit

Sub-issues 4 (0 open4 closed)

Story #3810: As a user, I can migrate ISO content units from Pulp 2 into Pulp 3 as File ContentCLOSED - CURRENTRELEASEttereshc

Actions
Task #4205: bootstrap pulp-2to3-migrate django appCLOSED - COMPLETEttereshc

Actions
Story #5337: As a user, I can fully migrate on_demand contentCLOSED - CURRENTRELEASEttereshc

Actions
Story #5363: As a user, I can migrate docker content units from Pulp 2 into Pulp 3CLOSED - CURRENTRELEASEipanova@redhat.com

Actions

Also available in: Atom PDF