https://pulp.plan.io/https://pulp.plan.io/favicon.ico2017-12-15T21:11:43ZPulpPulp - Story #3173: As a plugin author, I have documentation on how to implement a sync operation for my importerhttps://pulp.plan.io/issues/3173?journal_id=234072017-12-15T21:11:43Zdkliban@redhat.com
<ul><li><strong>Parent issue</strong> set to <i>#3209</i></li></ul> Pulp - Story #3173: As a plugin author, I have documentation on how to implement a sync operation for my importerhttps://pulp.plan.io/issues/3173?journal_id=235522017-12-19T22:28:22Zdkliban@redhat.com
<ul><li><strong>Description</strong> updated (<a title="View differences" href="/journals/23552/diff?detail_id=24009">diff</a>)</li></ul> Pulp - Story #3173: As a plugin author, I have documentation on how to implement a sync operation for my importerhttps://pulp.plan.io/issues/3173?journal_id=235552017-12-19T22:40:22Zdkliban@redhat.com
<ul><li><strong>Has duplicate</strong> <i><a class="issue tracker-1 status-12 priority-6 priority-default closed" href="/issues/3228">Issue #3228</a>: As an authenticated user, I can create a new repository version</i> added</li></ul> Pulp - Story #3173: As a plugin author, I have documentation on how to implement a sync operation for my importerhttps://pulp.plan.io/issues/3173?journal_id=235822017-12-21T17:10:28Zdaviddavis
<ul><li><strong>Status</strong> changed from <i>NEW</i> to <i>ASSIGNED</i></li><li><strong>Assignee</strong> set to <i>daviddavis</i></li></ul> Pulp - Story #3173: As a plugin author, I have documentation on how to implement a sync operation for my importerhttps://pulp.plan.io/issues/3173?journal_id=235832017-12-21T17:12:23Zdaviddavis
<ul></ul><p>A couple items:</p>
<ul>
<li>add_many and remove_many seem vague. I was thinking about something like add_content_units and remove_content_units.</li>
<li>Is the order of the actions (add, remove, then sync) correct? I thought we discussed sync, add, remove in the past.</li>
</ul> Pulp - Story #3173: As a plugin author, I have documentation on how to implement a sync operation for my importerhttps://pulp.plan.io/issues/3173?journal_id=235872017-12-21T18:12:34Zdaviddavis
<ul><li><strong>Blocks</strong> <i><a class="issue tracker-3 status-11 priority-6 priority-default closed child" href="/issues/3234">Story #3234</a>: As an authenticated user, I can create a new version by adding or removing content to the latest version.</i> added</li></ul> Pulp - Story #3173: As a plugin author, I have documentation on how to implement a sync operation for my importerhttps://pulp.plan.io/issues/3173?journal_id=235892017-12-21T18:19:02Zdaviddavis
<ul></ul><p>I talked a bit with @dkliban and it seems like the order should be sync, add, then remove. For instance, suppose I have a version that was synced that contains units A and B. If I want to sync again to get unit C but also remove unit B, then I can't actually remove B (because sync will just re-add it). I thinks users would be surprised if they called sync and remove B, only to find that B was still there because it was removed before sync and then sync re-added it.</p> Pulp - Story #3173: As a plugin author, I have documentation on how to implement a sync operation for my importerhttps://pulp.plan.io/issues/3173?journal_id=236212018-01-03T20:39:41Zbmbouterbmbouter@redhat.com
<ul></ul><p><a href="mailto:daviddavis@redhat.com" class="email">daviddavis@redhat.com</a> wrote:</p>
<blockquote>
<p>I talked a bit with @dkliban and it seems like the order should be sync, add, then remove.</p>
</blockquote>
<p>This makes sense to me. +1 to doing it in this way.</p> Pulp - Story #3173: As a plugin author, I have documentation on how to implement a sync operation for my importerhttps://pulp.plan.io/issues/3173?journal_id=236222018-01-03T20:44:35Zdkliban@redhat.com
<ul><li><strong>Description</strong> updated (<a title="View differences" href="/journals/23622/diff?detail_id=24073">diff</a>)</li></ul> Pulp - Story #3173: As a plugin author, I have documentation on how to implement a sync operation for my importerhttps://pulp.plan.io/issues/3173?journal_id=236292018-01-03T21:48:03Zdaviddavis
<ul><li><strong>Subject</strong> changed from <i>As an authenticated user, I can create a new repository version. </i> to <i>As an authenticated user, I can create a new repository version by POSTing a importer href.</i></li><li><strong>Description</strong> updated (<a title="View differences" href="/journals/23629/diff?detail_id=24079">diff</a>)</li><li><strong>Status</strong> changed from <i>ASSIGNED</i> to <i>NEW</i></li><li><strong>Assignee</strong> deleted (<del><i>daviddavis</i></del>)</li></ul> Pulp - Story #3173: As a plugin author, I have documentation on how to implement a sync operation for my importerhttps://pulp.plan.io/issues/3173?journal_id=236402018-01-03T22:15:52Zdkliban@redhat.com
<ul><li><strong>Groomed</strong> changed from <i>No</i> to <i>Yes</i></li><li><strong>Sprint Candidate</strong> changed from <i>No</i> to <i>Yes</i></li></ul> Pulp - Story #3173: As a plugin author, I have documentation on how to implement a sync operation for my importerhttps://pulp.plan.io/issues/3173?journal_id=237732018-01-09T14:08:16Zdkliban@redhat.com
<ul><li><strong>Blocks</strong> <i><a class="issue tracker-2 status-11 priority-6 priority-default closed child" href="/issues/3220">Task #3220</a>: Expand plugin writer's guide to include RepositoryVersion creating actions (including sync)</i> added</li></ul> Pulp - Story #3173: As a plugin author, I have documentation on how to implement a sync operation for my importerhttps://pulp.plan.io/issues/3173?journal_id=238002018-01-09T18:49:52Zamacdona@redhat.comaustin@redhat.com
<ul><li><strong>Blocks</strong> deleted (<i><a class="issue tracker-3 status-11 priority-6 priority-default closed child" href="/issues/3234">Story #3234</a>: As an authenticated user, I can create a new version by adding or removing content to the latest version.</i>)</li></ul> Pulp - Story #3173: As a plugin author, I have documentation on how to implement a sync operation for my importerhttps://pulp.plan.io/issues/3173?journal_id=238112018-01-09T19:57:33Zdkliban@redhat.com
<ul><li><strong>Description</strong> updated (<a title="View differences" href="/journals/23811/diff?detail_id=24254">diff</a>)</li><li><strong>Tags</strong> <i>Documentation</i> added</li></ul> Pulp - Story #3173: As a plugin author, I have documentation on how to implement a sync operation for my importerhttps://pulp.plan.io/issues/3173?journal_id=238122018-01-09T19:59:16Zdkliban@redhat.com
<ul><li><strong>Subject</strong> changed from <i>As an authenticated user, I can create a new repository version by POSTing a importer href.</i> to <i>As a plugin author, I have documentation on how to implement a sync operation for my importer</i></li></ul> Pulp - Story #3173: As a plugin author, I have documentation on how to implement a sync operation for my importerhttps://pulp.plan.io/issues/3173?journal_id=238132018-01-09T20:10:48Zttereshcttereshc@redhat.com
<ul></ul><p>I would move <code>- define a detail route on the Importer ViewSet for 'sync' that accepts a 'repository' POST body parameter</code> one level up or it seems like it's a part of requirements for the sync task.</p>
<p>Resource reservation should probably also be on a repo version, what do you think?</p>
<p>s/task's created list/<code>task.created_resources</code></p> Pulp - Story #3173: As a plugin author, I have documentation on how to implement a sync operation for my importerhttps://pulp.plan.io/issues/3173?journal_id=238142018-01-09T20:25:08Zdkliban@redhat.com
<ul></ul><p>If we are going to lock on the repository version being created, then the repository version needs to be created in the viewset. A lock on the repository should prevent a repository version from being deleted from under it. Please correct me if my understanding of the locking is wrong.</p> Pulp - Story #3173: As a plugin author, I have documentation on how to implement a sync operation for my importerhttps://pulp.plan.io/issues/3173?journal_id=238152018-01-09T20:26:50Zbmbouterbmbouter@redhat.com
<ul></ul><p>To align w/ the locking that core would do as part of <a class="issue tracker-3 status-11 priority-6 priority-default closed child" title="Story: Rewrite tasking system labels for versioned repositories (CLOSED - CURRENTRELEASE)" href="https://pulp.plan.io/issues/3186">#3186</a>. We need to tell them to lock on:</p>
<ul>
<li>The repo version</li>
<li>The repository itself</li>
<li>The importer being used</li>
</ul>
<p>The lock on the repository version is needed in addition to serialize any concurrent publishes that may also try to publish on that version. If that case is prevented due to the a publication not being allowed while complete=False then the lock would not be required.</p> Pulp - Story #3173: As a plugin author, I have documentation on how to implement a sync operation for my importerhttps://pulp.plan.io/issues/3173?journal_id=238172018-01-09T20:33:11Zdkliban@redhat.com
<ul></ul><p>We should definitely prevent publishing a repository version with complete=False. We would also need to lock on repository when deleting a repository version. Based on info in <a href="https://pulp.plan.io/issues/3219" class="external">https://pulp.plan.io/issues/3219</a> we are planning to do that. With this in mind, I don't think we need to lock on a repository version during a sync.</p> Pulp - Story #3173: As a plugin author, I have documentation on how to implement a sync operation for my importerhttps://pulp.plan.io/issues/3173?journal_id=238222018-01-09T21:51:50Zdkliban@redhat.com
<ul><li><strong>Description</strong> updated (<a title="View differences" href="/journals/23822/diff?detail_id=24261">diff</a>)</li></ul> Pulp - Story #3173: As a plugin author, I have documentation on how to implement a sync operation for my importerhttps://pulp.plan.io/issues/3173?journal_id=238242018-01-09T22:00:25Zamacdona@redhat.comaustin@redhat.com
<ul></ul><p>We do still need to lock on repo version. Otherwise, the version can be deleted, or the version before it could be deleted, which would modify the version in question.</p> Pulp - Story #3173: As a plugin author, I have documentation on how to implement a sync operation for my importerhttps://pulp.plan.io/issues/3173?journal_id=238252018-01-09T22:06:47Zttereshcttereshc@redhat.com
<ul></ul><p>So how publish task will behave if it sees incomplete repo version?<br>
Without lock on a repo version the publish task will run and fail? Or it won't be possible to create a publish task for incomplete repo version?</p>
<p>If sync task will lock on repo version then a publish task can be created and wait in a queue.</p> Pulp - Story #3173: As a plugin author, I have documentation on how to implement a sync operation for my importerhttps://pulp.plan.io/issues/3173?journal_id=238342018-01-10T15:12:23Zdkliban@redhat.com
<ul><li><strong>Sprint/Milestone</strong> set to <i>53</i></li></ul> Pulp - Story #3173: As a plugin author, I have documentation on how to implement a sync operation for my importerhttps://pulp.plan.io/issues/3173?journal_id=238482018-01-10T16:08:02Zdkliban@redhat.com
<ul><li><strong>Blocks</strong> deleted (<i><a class="issue tracker-2 status-11 priority-6 priority-default closed child" href="/issues/3220">Task #3220</a>: Expand plugin writer's guide to include RepositoryVersion creating actions (including sync)</i>)</li></ul> Pulp - Story #3173: As a plugin author, I have documentation on how to implement a sync operation for my importerhttps://pulp.plan.io/issues/3173?journal_id=240422018-01-18T13:19:23Zamacdona@redhat.comaustin@redhat.com
<ul><li><strong>Is duplicate of</strong> <i><a class="issue tracker-2 status-11 priority-6 priority-default closed child" href="/issues/3220">Task #3220</a>: Expand plugin writer's guide to include RepositoryVersion creating actions (including sync)</i> added</li></ul> Pulp - Story #3173: As a plugin author, I have documentation on how to implement a sync operation for my importerhttps://pulp.plan.io/issues/3173?journal_id=240632018-01-18T15:54:18Zamacdona@redhat.comaustin@redhat.com
<ul><li><strong>Groomed</strong> changed from <i>Yes</i> to <i>No</i></li></ul> Pulp - Story #3173: As a plugin author, I have documentation on how to implement a sync operation for my importerhttps://pulp.plan.io/issues/3173?journal_id=241772018-01-23T19:20:23Zamacdona@redhat.comaustin@redhat.com
<ul><li><strong>Status</strong> changed from <i>NEW</i> to <i>CLOSED - DUPLICATE</i></li></ul> Pulp - Story #3173: As a plugin author, I have documentation on how to implement a sync operation for my importerhttps://pulp.plan.io/issues/3173?journal_id=241852018-01-23T20:07:19Zamacdona@redhat.comaustin@redhat.com
<ul><li><strong>% Done</strong> changed from <i>0</i> to <i>100</i></li><li><strong>Parent issue</strong> deleted (<del><i>#3209</i></del>)</li></ul> Pulp - Story #3173: As a plugin author, I have documentation on how to implement a sync operation for my importerhttps://pulp.plan.io/issues/3173?journal_id=263482018-03-08T23:30:33Zbmbouterbmbouter@redhat.com
<ul><li><strong>Sprint</strong> set to <i>Sprint 31</i></li></ul> Pulp - Story #3173: As a plugin author, I have documentation on how to implement a sync operation for my importerhttps://pulp.plan.io/issues/3173?journal_id=263732018-03-08T23:31:03Zbmbouterbmbouter@redhat.com
<ul><li><strong>Sprint/Milestone</strong> deleted (<del><i>53</i></del>)</li></ul> Pulp - Story #3173: As a plugin author, I have documentation on how to implement a sync operation for my importerhttps://pulp.plan.io/issues/3173?journal_id=276752018-04-19T15:17:46Zdkliban@redhat.com
<ul><li><strong>Sprint/Milestone</strong> set to <i>3.0.0</i></li></ul> Pulp - Story #3173: As a plugin author, I have documentation on how to implement a sync operation for my importerhttps://pulp.plan.io/issues/3173?journal_id=427492019-04-26T20:37:14Zbmbouterbmbouter@redhat.com
<ul><li><strong>Tags</strong> deleted (<del><i>Pulp 3, Pulp 3 MVP</i></del>)</li></ul>