Story #3822
Updated by dkliban@redhat.com about 6 years ago
Pulp 2 needs to provide a tool called 'pulp-3-migrate'. 'pulp-3-migrate' is going to be a django app with a sqllite database. This tool is going to be modular. Some functionality will come from the core, but specific implementation for each content type will be provided by the plugins. 'pulp-3-migrate content' command is going to that can migrate content units from Pulp 2 to Pulp 3. It will have two modes of operation: local The tool should take the following settings: Pulp 3's REST API URL Pulp 3 username and remote. It will record progress in the database so it can know where password Content types to resume on subsequent runs. migrate. For The tool should generate a database with a table for each content unit discovered during 'pulp-3-migrate content', the following will be performed: Local mode: * create type migrated. The table needs to contain a hard link in /var/lib/pulp/artifacts/ directory * create Artifact in reference for the database * create Content content unit in the database * record progress by storing references for pulp Pulp 2 and pulp 3 content unit Remote mode: * create an Artifact using REST API * create a Content using REST API * record progress by storing references reference for pulp 2 and pulp 3 the content unit in Pulp 3.
.