Project

Profile

Help

Story #5337

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 fully migrate on_demand content

Added by ttereshc over 1 year ago. Updated 8 months ago.

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

100%

Estimated time:
Platform Release:
Groomed:
Yes
Sprint Candidate:
No
Tags:
Sprint:
Sprint 60
Quarter:

Description

Add model to pre-migrate "lazy catalog" from pulp2

Pulp2LazyCatalog
  - importer_id
  - unit_id
  - content_type
  - url
  - checksum
  - checksum_algorithm

Expand the content migration pipeline to create ContentArtifacts and RemoteArtifatcs.

Since it's possible to migrate content only. Ensure that on_demand content is taken care of only when Remote is migrated/available. Otherwise, only downloaded content should be migrated.


Related issues

Blocks Migration Plugin - Story #5342: As a user, I can migrate repository into a set of repository versionsCLOSED - CURRENTRELEASE

<a title="Actions" class="icon-only icon-actions js-contextmenu" href="#">Actions</a>
Blocked by Migration Plugin - Story #5340: As a user, I can migrate Pulp 2 repository and importer to Pulp 3CLOSED - CURRENTRELEASE

<a title="Actions" class="icon-only icon-actions js-contextmenu" href="#">Actions</a>

Associated revisions

Revision b7ce0218 View on GitHub
Added by ttereshc about 1 year ago

Migrate on_demand content

Create RemoteArtifact for each of the lazy catalog entry.

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

Revision b7ce0218 View on GitHub
Added by ttereshc about 1 year ago

Migrate on_demand content

Create RemoteArtifact for each of the lazy catalog entry.

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

Revision b7ce0218 View on GitHub
Added by ttereshc about 1 year ago

Migrate on_demand content

Create RemoteArtifact for each of the lazy catalog entry.

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

History

#1 Updated by ttereshc over 1 year ago

  • Parent task set to #3822

#2 Updated by ttereshc over 1 year ago

  • Blocked by Story #5307: As a user, I can migrate repositories from Pulp2 to Pulp3 added

#3 Updated by ttereshc over 1 year ago

  • Blocks Story #5342: As a user, I can migrate repository into a set of repository versions added

#4 Updated by ttereshc over 1 year ago

  • Blocked by Story #5340: As a user, I can migrate Pulp 2 repository and importer to Pulp 3 added

#5 Updated by ttereshc over 1 year ago

  • Blocked by deleted (Story #5307: As a user, I can migrate repositories from Pulp2 to Pulp3)

#6 Updated by ttereshc about 1 year ago

  • Status changed from NEW to ASSIGNED
  • Assignee set to ttereshc

#7 Updated by ttereshc about 1 year ago

  • Groomed changed from No to Yes
  • Sprint set to Sprint 59

#8 Updated by ttereshc about 1 year ago

  • Status changed from ASSIGNED to POST

#9 Updated by rchan about 1 year ago

  • Sprint changed from Sprint 59 to Sprint 60

#10 Updated by ttereshc about 1 year ago

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

Applied in changeset commit:pulp-2to3-migrate|b7ce02189045f29bbab0a78ce1df6439bf709188.

#11 Updated by bmbouter 12 months ago

  • Sprint/Milestone set to 3.0.0

#12 Updated by bmbouter 12 months ago

  • Status changed from MODIFIED to CLOSED - CURRENTRELEASE

#13 Updated by ttereshc 11 months ago

  • Status changed from CLOSED - CURRENTRELEASE to MODIFIED

#14 Updated by ttereshc 8 months ago

  • Status changed from MODIFIED to CLOSED - CURRENTRELEASE
  • Sprint/Milestone set to 0.1.0

Please register to edit this issue

Also available in: Atom PDF