Comments inline. David
On Tue, Apr 18, 2017 at 2:42 PM, Dennis Kliban <[email protected]> wrote: > Do we want to provide a tool for migrating from Pulp 2 to 3? If yes, then > ... > > Would the tool be able to migrate repository definitions and require the > user to sync and upload content to restore /var/lib/pulp/content? > > Question: is the structure of /var/lib/pulp/content changing in Pulp 3? If not, that might simplify the migration process. > Would this tool support installing Pulp 3 along side Pulp 2 and performing > a migration of database and /var/lib/pulp/content? > > I think we should allow for at least part of the installation process to be performed while Pulp 2 is running. We had a very painful process I think it was with Pulp 2.8 where users had to take their katello installations offline for hours or sometimes days. We should try to avoid that as much as possible by allowing part of the install to run while Pulp is running. > Would this tool be able to accept a mongodump of Pulp 2 MongoDB and a path > to a copy of Pulp 2's /var/lib/pulp directory and use that information to > populate Pulp 3? > > > I would say: - For the mongo data, use whatever is set in pulp’s config but allow users to override it and specify a mongo connection or mongodump. - For the pulp filesystem content, use /var/lib/pulp but allow users to override this too. > > _______________________________________________ > Pulp-dev mailing list > [email protected] > https://www.redhat.com/mailman/listinfo/pulp-dev > >
_______________________________________________ Pulp-dev mailing list [email protected] https://www.redhat.com/mailman/listinfo/pulp-dev
