[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]

Re: [Pulp-list] Pulp 2 to 3 Migration meeting on Thursday June 14th

Migrations are not additive (in theory, they can be - if Pulp 2 had only additive changes since last migration).
Each time you run a migration the tool will make sure that the result (Pulp3 content/repositories) reflects what is specified in the Migration Plan.
So after any migration, Pulp3 should always mirror Pulp 2 for the plugins which are specified in the Migration Plan.

I'll add somewhere explicitly that content and various resources can be removed or added during migration.

Thanks for asking,

On Thu, Jun 13, 2019 at 11:29 PM Eric Helms <ehelms redhat com> wrote:
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 redhat com> wrote:
The logs from the meeting can be viewed here[0].
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 [1] is updated with the suggested changes to the Migration Plan structure, you can see it in the examples for use cases on lines 188+.

On Wed, Jun 12, 2019 at 8:56 PM Tatiana Tereshchenko <ttereshc redhat com> wrote:
An IRC meeting will be held on Thursday June 14rg at 10am Eastern[0]. 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+ [1]
  - 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 [1] before the meeting.

Pulp-list mailing list
Pulp-list redhat com

[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]