Project

Profile

Help

Story #6198

closed

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 almost 5 years ago. Updated over 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:
Sprint:
Quarter:

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.


Sub-issues 3 (0 open3 closed)

Task #6199: Create a Distribution model to communicate with pulp2CLOSED - CURRENTRELEASEdkliban@redhat.com

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

Actions
Task #6201: Add ability to migrate distribution treesCLOSED - CURRENTRELEASEdkliban@redhat.com

Actions

Also available in: Atom PDF