[Pulp-dev] [Pulp-list] Pulp 2 to 3 Migration meeting on Thursday June 14th
ehelms at redhat.com
Thu Jun 13 21:29:11 UTC 2019
Thanks for sending along and sharing. Will migrations be additive only? I
am not seeing any language to handle removal of content from Pulp 3. I am
thinking of the cases around my Pulp 2 content has changed since I last
attempted a Pulp 3 migration and I now have cruft in my Pulp 3 that does
not mirror my Pulp 2 before I have switched to Pulp 3.
On Thu, Jun 13, 2019 at 4:16 PM Tatiana Tereshchenko <ttereshc at redhat.com>
> The logs from the meeting can be viewed here.
> The agenda was quite ambitious, the first item was partially covered and
> discussion will continue next week.
> We covered:
> - content or no content migration
> - how to keep the MigrationPlan declarative and migrate various plugins
> at different times without unintentionally removing pulp3 content which has
> been fully migrated
> The etherpad  is updated with the suggested changes to the Migration
> Plan structure, you can see it in the examples for use cases on lines 188+.
>  https://etherpad.net/p/pulp-2to3-migration
> On Wed, Jun 12, 2019 at 8:56 PM Tatiana Tereshchenko <ttereshc at redhat.com>
>> An IRC meeting will be held on Thursday June 14rg at 10am Eastern. The
>> meeting will take place in #pulp-2to3-sig on Freenode IRC network.
>> Tentative agenda:
>> - go through use cases and see if we forgot anything, see etherpad
>> L184+ 
>> - verify that everything is covered by the current MP structure
>> - discuss questions around use cases that can affect the MP structure
>> - hard link approach for "migrating" files, good or bad; alternatives
>> Please put any questions or ideas into the etherpad  before the
>>  https://etherpad.net/p/pulp-2to3-migration
> Pulp-list mailing list
> Pulp-list at redhat.com
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Pulp-dev