Project

Profile

Help

Story #6198

Story #6146: [Epic] As a user, I can migrate RPM plugin content and repositories

As a user, I can migrate distribution(kickstart) trees

Added by ttereshc about 1 month ago. Updated 10 days ago.

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

67%

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

Description

Background

Distribution trees are supported differently in Pulp 2 and in Pulp 3. Pulp 2 has only content for the main repo and no content for any subrepos. If Pulp 2 content is migrated as is, users in Pulp 3 will struggle to get subrepo content for migrated distribution trees.

Proposed solution

Migrate as much as possible from Pulp 2 to Pulp 3, so the repositories in Pulp 3 which contain a distribution tree are provisionable. To make it easy to update the migrated distribution tree, change/decrease the build timestamp in Pulp 3 for a distribution tree. On the next sync, a distribution tree will be fully synced, including subrepos.


Checklist


Subtasks

Task #6199: Create a Distribution model to communicate with pulp2MODIFIEDdkliban@redhat.com

Actions
Task #6200: Create a distribution tree detail model for pre-migrationMODIFIEDdkliban@redhat.com

Actions
Task #6201: Add ability to migrate distribution treesASSIGNEDdkliban@redhat.com

Actions

History

#1 Updated by ttereshc about 1 month ago

  • Checklist item Check that modifying a build timestamp doesn't affect provisioning added
  • Checklist item Complete subtasks added

#2 Updated by ttereshc about 1 month ago

  • Description updated (diff)

Please register to edit this issue

Also available in: Atom PDF