Project

Profile

Help

Story #7779

As a user, a migration re-run is very fast, if there were no or very little changes in pulp 2

Added by ttereshc 3 months ago. Updated 2 months ago.

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

0%

Estimated time:
Platform Release:
Groomed:
No
Sprint Candidate:
No
Tags:
Katello
Sprint:
Quarter:

Description

Motivation

Users run the migration task multiple times upfront, so the switchover to Pulp 3 happens quickly, within few minutes. Switchover = stop pulp 2 services, run migration for the last time, start using pulp3.

Existing concerns and thoughts

  • Following the same code path as normal migration when no changes have been made in pulp 2 takes a noticeable amount of time. We might need to introduce some shortcuts for the case when nothing has been changed in pulp 2.
  • Same goes to the case when only very few changes have been made.
  • If everything possible is done and no shortcuts are available we might need to look at the performance of the longest steps or rethink the approach.

History

#1 Updated by ttereshc 2 months ago

Currently a re-run for a large-ish system (1K repos, 300K rpms) when nothing changed in pulp 2 is taking 13 mins.

#2 Updated by ttereshc 2 months ago

  • Tags Katello added

Please register to edit this issue

Also available in: Atom PDF