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

Tue Jun 25 18:04:11 UTC 2019

On Thu, Jun 20, 2019 at 8:22 AM Brian Bouterse <bbouters at redhat.com> wrote:

>
>
> On Thu, Jun 20, 2019 at 7:54 AM Dennis Kliban <dkliban at redhat.com> wrote:
>
>> On Wed, Jun 19, 2019 at 2:10 PM Eric Helms <ehelms at redhat.com> wrote:
>>
>>> Thanks for these updates.
>>>
>>> On Wed, Jun 19, 2019, 1:59 PM Tatiana Tereshchenko <ttereshc at redhat.com>
>>> wrote:
>>>
>>>> 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.
>>>>
>>>
>>> In the copy case, will Pulp 3 migrations prevent a user from potentially
>>> filling their disk up and ending up in a broken state?
>>>
>>>
>> Definitely. Pulp will check the type of filesystem the user has. If it
>> supports hardlinks it will check that there is some sane amount of space
>> available. If it doesn't support hard links it will check that there is at
>> least as much free space as space already used by /var/lib/pulp. Pulp will
>> notify the user if there is not enough space.
>>
> This sounds good. I want to point out that Pulp2 could still be writing to
> the filesystem while the migration plan is applied by Pulp3 causing the
> initial "we're good" check to possibly later fail. I'm ok w/ that I just
> wanted to point out this case and that we are not planning to handle it.
>
> I'm also contemplating what would happen if we don't support migrations on
> filesystems that don't support hardlinks. To my knowledge, and from the
> feedback recently about what filesystems our users use in the community
> survey, all of them support hardlinks. Does it make any sense to wait to
> develop the "copy fallback" when we know a user will need it? Does anyone
> know that we will need to migrate on filesystems without hard links?
>

A POSIX-compliant filesystem, which includes hard link support, is a very
common & reasonable requirement for any application to have.

However, we have never formalized that requirement.

And I rarely see it introduced at upgrade time.

I'm personally on the fence about this. I'm learning towards erroring out
than having to worry about implementing & testing "copy fallback".

-Mike

>>
>>
>>>>   - 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
>>>>>
>>>> _______________________________________________
>>>> Pulp-list mailing list
>>>> Pulp-list at redhat.com
>>>> https://www.redhat.com/mailman/listinfo/pulp-list
>>>
>>> _______________________________________________
>>> Pulp-list mailing list
>>> Pulp-list at redhat.com
>>> https://www.redhat.com/mailman/listinfo/pulp-list
>>
>> _______________________________________________
>> Pulp-dev mailing list
>> Pulp-dev at redhat.com
>> https://www.redhat.com/mailman/listinfo/pulp-dev
>>
> _______________________________________________
> Pulp-dev mailing list
> Pulp-dev at redhat.com
> https://www.redhat.com/mailman/listinfo/pulp-dev
>

-- 

Mike DePaulo

He / Him / His

Service Reliability Engineer, Pulp

Red Hat <https://www.redhat.com/>

IM: mikedep333

GPG: 51745404
<https://www.redhat.com/>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://listman.redhat.com/archives/pulp-dev/attachments/20190625/6168a48a/attachment.htm>