0.1.0 A release compatible with pulpcore 3.0, supports File and Container plugins 100% 57 issues (57 closed — 0 open) Related issues Issue #5479: Migration plugin suffers from reverse accessor clashes Actions Issue #5480: Migration plugin should allow storage_path to be set to null Actions Issue #5481: Migration plugin expects to migrate only FileContentUnit Actions Issue #5483: Include description in the pulp2repository creation Actions Issue #5485: Migration plugin should filter only those repo types that belong to the plugin that is being migrated Actions Issue #5546: migration plan creation expects 'plan' to be pre-serialized within bindings Actions Issue #5551: Importer config can't be null Actions Issue #5820: pulp-2to3-migration requires all supported Pulp 3 plugins to be installed Actions Issue #5899: migration plan fails with "local variable 'pulp2repo' referenced before assignment" Actions Issue #5957: pulp 2to3 migration only works if notes field is filled out with the type Actions Issue #5978: Migration of multiple plugins does not work Actions Issue #5980: Older repositories are not migrated if the newer ones have already been migrated Actions Issue #6049: On the pulp2 repositories api, distribution_hrefs and publication_hrefs are not serialized properly Actions Issue #6053: Add repository_href to pulp2repositories api Actions Issue #6056: migration plans require a 'pulp2_importer_repository_id' but importer must have a feed url Actions Issue #6058: re-migrating after deleting a pulp2 repo errors with: AttributeError: 'NoneType' object has no attribute 'publication_set' Actions Issue #6062: Migration doesn't handle repos that are removed and then re-created Actions Issue #6070: empty repositories should still be migrated if they are specified in the migration plan Actions Issue #6097: docker migration fails with 'NoneType' object has no attribute 'pulp2_repo_id' Actions Issue #6099: Docker migrator fails on a re-run Actions Issue #6103: Migrating large file repository leads to unmigrated units Actions Issue #6186: Mutable content that has changed since the last migration run is not migrated Actions Issue #6234: Do not pre-migrate schema1 docker tags when there are 2 tags with same name witin a repo Actions Task #4205: bootstrap pulp-2to3-migrate django app Actions Task #5081: Add ability to the migration tool to connect to mongodb from Pulp 3 environment Actions Task #5082: As a developer, pulplift can create a dev environment for migration tool Actions Task #5083: Add model for Pulp 2 data and dump Pulp 2 generic data using this model Actions Task #5306: Add models to pre-migrate pulp 2 data about repositories/importers/distributors Actions Task #5476: Let plugin migrate all its content models at once and not one by one Actions Task #5492: Add bindings for pulp2 -> pulp3 migration plugin Actions Task #5501: Configure towncrier for the migration plugin Actions Task #5632: Mark changed/removed Pulp 2 repositories/importers/distributors Actions Task #5633: Switch from CharField to TextField Actions Task #5837: Specify pulp2_distributor_repository_ids instead of distributor_ids Actions Task #5845: Update get_pulp3_repository_setup so repos are grouped by plugin type Actions Task #5849: Add an example of a migration plan Actions Task #5852: Add ability to pre-migrate importers and distributors independently from the repo they belong to Actions Task #5984: Make `pulp_importer_repo_id` optional Actions Task #6131: Clean up for RC release Actions Task #6145: Move README to readthedocs website Actions Story #3810: As a user, I can migrate ISO content units from Pulp 2 into Pulp 3 as File Content Actions Story #3822: As a user, I can migrate all content units of a specific type from Pulp 2 to Pulp 3 Actions Story #5003: As a user, I can use the REST API to dispatch a Pulp 2 to 3 migration task. Actions Story #5178: As a user, a Migration Plan is validated Actions Story #5229: As a user, I can see progress of Migration Plan execution Actions Story #5230: As a user, I have a default configuration for MongoDB connection Actions Story #5231: As a user, I can query Pulp 2->Pulp 3 mapping for migrated content Actions Story #5307: As a user, I can migrate repositories from Pulp2 to Pulp3 Actions Story #5319: As a user I have validated resources Migration plan refers to Actions Story #5337: As a user, I can fully migrate on_demand content Actions Story #5340: As a user, I can migrate Pulp 2 repository and importer to Pulp 3 Actions Story #5342: As a user, I can migrate repository into a set of repository versions Actions Story #5343: As a user, I can migrate Pulp 2 distributor into publication/distribution in Pulp 3 Actions Story #5363: As a user, I can migrate docker content units from Pulp 2 into Pulp 3 Actions Story #5450: As a user, a Migration Plan is respected Actions Story #5634: As a user, I can query Pulp 2->Pulp 3 mapping for migrated resources Actions
.
.
.