Project

Profile

Help

Task #4205

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

bootstrap pulp-2to3-migrate django app

Added by dkliban@redhat.com 11 months ago. Updated 6 months ago.

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

0%

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

Description

The migration tool is going to be modular.

The core of it going to live in a new 'pulp-2to3-migrate' repository. This repo should contain a Django app called 'pulp-2to3-migrate'.

The ISO plugin for it is going to be in it's own repository called 'pulp-2to3-migrate-iso'. This repo will contain a package by the same name. This package is going to provide an entry point for 'pulp_2to3_migrate.iso'.

Requirements

  • run on a machine where Pulp3 is installed
  • Pulp 3 environment (Django 2.x, Python 3.6+)
  • use DynaConf to manage Django settings
  • shared FS to access Pulp 2 storage (for in-place migration)
  • can be interrupted/re-run multiple times and continue migration

Associated revisions

Revision 50acb758 View on GitHub
Added by ttereshc 6 months ago

Bootstrap pulp-2to3-migrate tool

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

Revision 50acb758 View on GitHub
Added by ttereshc 6 months ago

Bootstrap pulp-2to3-migrate tool

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

History

#1 Updated by dkliban@redhat.com 11 months ago

  • Parent task set to #3822

#2 Updated by bmbouter 11 months ago

  • Groomed changed from No to Yes
  • Tags Pulp 3 added

This looks good to me. Also when making this I recommend using cookiecutter, which is what I used to bootstrap the streamer.

#3 Updated by jortel@redhat.com 11 months ago

  • Sprint set to Sprint 46

#4 Updated by rchan 10 months ago

  • Sprint changed from Sprint 46 to Sprint 47

#5 Updated by rchan 9 months ago

  • Sprint changed from Sprint 47 to Sprint 48

#6 Updated by jortel@redhat.com 8 months ago

Why should the tool be a django app?

#7 Updated by dkliban@redhat.com 8 months ago

This tool is going to need to use a database to keep track of state. Django provides an ORM we are familiar with. It also provides a framework for adding CLI commands. This will NOT be a web app.

#8 Updated by rchan 8 months ago

  • Sprint changed from Sprint 48 to Sprint 49

#9 Updated by rchan 8 months ago

  • Sprint changed from Sprint 49 to Sprint 50

#10 Updated by ttereshc 7 months ago

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

#11 Updated by ttereshc 7 months ago

  • Subject changed from bootstrap pulp-3-migrate django app to bootstrap pulp-2to3-migrate django app
  • Description updated (diff)

#12 Updated by ttereshc 7 months ago

  • Description updated (diff)

#13 Updated by ttereshc 7 months ago

  • Description updated (diff)

#14 Updated by ttereshc 7 months ago

  • Description updated (diff)

#15 Updated by ttereshc 7 months ago

  • Description updated (diff)

#16 Updated by rchan 7 months ago

  • Sprint changed from Sprint 50 to Sprint 51

#18 Updated by rchan 6 months ago

  • Sprint changed from Sprint 51 to Sprint 52

#19 Updated by ttereshc 6 months ago

  • Status changed from POST to MODIFIED

#20 Updated by daviddavis 6 months ago

  • Sprint/Milestone set to 3.0

#21 Updated by bmbouter 6 months ago

  • Tags deleted (Pulp 3)

Please register to edit this issue

Also available in: Atom PDF