<div dir="ltr"><div dir="ltr"><br></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Thu, Jun 20, 2019 at 7:54 AM Dennis Kliban <<a href="mailto:dkliban@redhat.com">dkliban@redhat.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr"><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Wed, Jun 19, 2019 at 2:10 PM Eric Helms <<a href="mailto:ehelms@redhat.com" target="_blank">ehelms@redhat.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="auto"><div>Thanks for these updates.<br><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Wed, Jun 19, 2019, 1:59 PM Tatiana Tereshchenko <<a href="mailto:ttereshc@redhat.com" target="_blank">ttereshc@redhat.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr"><div dir="ltr"><div>The logs from the meeting can be viewed here[0].</div><div><br></div><div></div><div>We covered:</div><div><span class="gmail-m_-8421617807850904047m_-736569525982438710gmail-m_6301835222378576649m_2445678411476290648gmail-m_3245281579523179355gmail-JtukPc"><span> - hard links approach for "migrating" files, good or bad; alternatives</span></span></div><div> * 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.</div></div></div></blockquote></div></div><div dir="auto"><br></div><div dir="auto">In the copy case, will Pulp 3 migrations prevent a user from potentially filling their disk up and ending up in a broken state? </div><div dir="auto"><br></div></div></blockquote><div><br></div><div>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.</div></div></div></blockquote><div>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.</div><div><br></div><div>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?<br></div><div><br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr"><div class="gmail_quote"><div><br></div><div><br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="auto"><div dir="auto"></div><div dir="auto"><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr"><div dir="ltr"><div><br></div><div> - protected repos migration</div><div> * 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.<br></div><div><br></div><div>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.</div><div><br></div><div>[0] <a href="https://pulpadmin.fedorapeople.org/triage/pulp-2to3-sig/2019/pulp-2to3-sig.2019-06-19-16.00.log.html" rel="noreferrer" target="_blank">https://pulpadmin.fedorapeople.org/triage/pulp-2to3-sig/2019/pulp-2to3-sig.2019-06-19-16.00.log.html</a></div><div>[1] <a href="https://etherpad.net/p/pulp-2to3-migration" rel="noreferrer noreferrer" target="_blank">https://etherpad.net/p/pulp-2to3-migration</a></div></div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Tue, Jun 18, 2019 at 6:34 PM Tatiana Tereshchenko <<a href="mailto:ttereshc@redhat.com" rel="noreferrer" target="_blank">ttereshc@redhat.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr"><div dir="ltr"><div dir="ltr"><div dir="ltr"><div>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. <br></div><div><br></div><div>Tentative agenda:</div><div><span class="gmail-m_-8421617807850904047m_-736569525982438710gmail-m_6301835222378576649m_2445678411476290648gmail-m_3245281579523179355gmail-JtukPc"><span> - continue on use cases, see etherpad L18+ <br></span></span></div><div><span class="gmail-m_-8421617807850904047m_-736569525982438710gmail-m_6301835222378576649m_2445678411476290648gmail-m_3245281579523179355gmail-JtukPc"><span> * especially distributors migration part <br></span></span></div><div><span class="gmail-m_-8421617807850904047m_-736569525982438710gmail-m_6301835222378576649m_2445678411476290648gmail-m_3245281579523179355gmail-JtukPc"><span> * verify that everything is covered by the current MP structure <br></span></span></div><div><span class="gmail-m_-8421617807850904047m_-736569525982438710gmail-m_6301835222378576649m_2445678411476290648gmail-m_3245281579523179355gmail-JtukPc"><span> * discuss any questions around use cases that can affect the MP structure</span></span></div><div><span class="gmail-m_-8421617807850904047m_-736569525982438710gmail-m_6301835222378576649m_2445678411476290648gmail-m_3245281579523179355gmail-JtukPc"><span> - hardlinks approach for "migrating" files, good or bad; alternatives</span></span></div><div><span class="gmail-m_-8421617807850904047m_-736569525982438710gmail-m_6301835222378576649m_2445678411476290648gmail-m_3245281579523179355gmail-m_-66137992526237004gmail-JtukPc"> </span><br></div><div>Please put any questions or ideas into the
etherpad [1] before the meeting. <br></div><div><br></div><div>[0] <a href="https://www.worldtimebuddy.com/?qm=1&lid=100,4487042,3078610&h=100&date=2019-6-19&sln=16-17" rel="noreferrer noreferrer" target="_blank">https://www.worldtimebuddy.com/?qm=1&lid=100,4487042,3078610&h=100&date=2019-6-19&sln=16-17</a></div><div>[1] <a href="https://etherpad.net/p/pulp-2to3-migration" rel="noreferrer noreferrer" target="_blank">https://etherpad.net/p/pulp-2to3-migration</a></div></div></div></div></div>
</blockquote></div>
_______________________________________________<br>
Pulp-list mailing list<br>
<a href="mailto:Pulp-list@redhat.com" rel="noreferrer" target="_blank">Pulp-list@redhat.com</a><br>
<a href="https://www.redhat.com/mailman/listinfo/pulp-list" rel="noreferrer noreferrer" target="_blank">https://www.redhat.com/mailman/listinfo/pulp-list</a></blockquote></div></div></div>
_______________________________________________<br>
Pulp-list mailing list<br>
<a href="mailto:Pulp-list@redhat.com" target="_blank">Pulp-list@redhat.com</a><br>
<a href="https://www.redhat.com/mailman/listinfo/pulp-list" rel="noreferrer" target="_blank">https://www.redhat.com/mailman/listinfo/pulp-list</a></blockquote></div></div>
_______________________________________________<br>
Pulp-dev mailing list<br>
<a href="mailto:Pulp-dev@redhat.com" target="_blank">Pulp-dev@redhat.com</a><br>
<a href="https://www.redhat.com/mailman/listinfo/pulp-dev" rel="noreferrer" target="_blank">https://www.redhat.com/mailman/listinfo/pulp-dev</a><br>
</blockquote></div></div>