Story #3822
Updated by dkliban@redhat.com about 6 years ago
Pulp 2 will needs to provide a tool called *pulp-3-migrate*. This tool 'pulp-3-migrate'. 'pulp-3-migrate' is going to be a Django 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* 'pulp-3-migrate content' command is going to migrate content units from Pulp 2 to Pulp 3. It will have two modes of operation: local and remote. It will record progress in the database so it can know where to resume on subsequent runs. For each content unit discovered during *pulp-3-migrate content*, 'pulp-3-migrate content', the following will be performed: *Local mode:* Local mode: * create a hard link in /var/lib/pulp/artifacts/ directory * create Artifact in the database * create Content in the database * record progress by storing references for pulp 2 and pulp 3 content unit *Remote mode:* Remote mode: * create an Artifact using REST API * create a Content using REST API * record progress by storing references for pulp 2 and pulp 3 content unit
.