[Pulp-dev] Pulp 2 to 3 Migration meeting on Wednesday June 19th

[Tatiana Tereshchenko]

The logs from the meeting can be viewed here[0].

We covered:
  - hard links approach for "migrating" files, good or bad; alternatives
    * current plan: Pulp 3's migration task will migrate content by either
creating a hard link in the Pulp 3 artifact storage location or by copying
it there if hard links are not supported. There will be a way to see how
much content has been migrated and how much is left.

  - protected repos migration
    * current plan: CertGuards witll be created and associated with
Distributions in Pulp3. The Migration Plan will provide the ability to
configure which repositories content protection is migrated for to Pulp 3.

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 L316,
L325.

[0]
https://pulpadmin.fedorapeople.org/triage/pulp-2to3-sig/2019/pulp-2to3-sig.2019-06-19-16.00.log.html
[1] https://etherpad.net/p/pulp-2to3-migration

On Tue, Jun 18, 2019 at 6:34 PM Tatiana Tereshchenko <ttereshc at redhat.com>
wrote:

> An IRC meeting will be held on Wednesday June 19th at 12pm Eastern[0]. The
> meeting will take place in #pulp-2to3-sig on Freenode IRC network.
>
> Tentative agenda:
>   - continue on use cases, see etherpad L18+
>     * especially distributors migration part
>     * verify that everything is covered by the current MP structure
>     * discuss any questions around use cases that can affect the MP
> structure
>  - hardlinks approach for "migrating" files, good or bad; alternatives
>
> Please put any questions or ideas into the etherpad [1] before the
> meeting.
>
> [0]
> https://www.worldtimebuddy.com/?qm=1&lid=100,4487042,3078610&h=100&date=2019-6-19&sln=16-17
> [1] https://etherpad.net/p/pulp-2to3-migration
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://listman.redhat.com/archives/pulp-dev/attachments/20190619/d1c55178/attachment.htm>