https://pulp.plan.io/https://pulp.plan.io/favicon.ico2017-08-01T13:32:41ZPulpPulp - Refactor #2950: Improve Custom Storage Backend for 3.0https://pulp.plan.io/issues/2950?journal_id=213392017-08-01T13:32:41Zbmbouterbmbouter@redhat.com
<ul></ul><p>Can links be posted to the code to be removed?</p> Pulp - Refactor #2950: Improve Custom Storage Backend for 3.0https://pulp.plan.io/issues/2950?journal_id=213442017-08-01T14:55:13Zttereshcttereshc@redhat.com
<ul><li><strong>Tracker</strong> changed from <i>Issue</i> to <i>Refactor</i></li><li><strong>% Done</strong> set to <i>0</i></li></ul><p>Consider adding to the current sprint after grooming</p> Pulp - Refactor #2950: Improve Custom Storage Backend for 3.0https://pulp.plan.io/issues/2950?journal_id=213462017-08-01T15:02:17Zjortel@redhat.comjortel@redhat.com
<ul></ul><p>I ended up writing the <em>FileStorage</em> because getting the django builtin file storage engine to work was just too hard. It has behaviors that did not fit well with how we store artifacts. The <em>file</em> stuff in django is poorly documented (and in many cases poorly written) and I burned a lot of time digging though the code. That said, perhaps I missed something easy we can do to use the builtin storage. I am very much in favor of doing this task but I do not think it should be done before the alpha.</p> Pulp - Refactor #2950: Improve Custom Storage Backend for 3.0https://pulp.plan.io/issues/2950?journal_id=213552017-08-01T21:15:35Zbmbouterbmbouter@redhat.com
<ul><li><strong>Subject</strong> changed from <i>remove custom storage backend from 3.0</i> to <i>Remove Custom Storage Backend from 3.0</i></li><li><strong>Description</strong> updated (<a title="View differences" href="/journals/21355/diff?detail_id=21886">diff</a>)</li><li><strong>Priority</strong> changed from <i>Normal</i> to <i>High</i></li><li><strong>Tags</strong> deleted (<del><i>Pulp 3 Plugin Writer Alpha</i></del>)</li></ul><p>I added a link to the description. I agree not doing this for the alpha is OK. I've removed the alpha tag. I changed it to high priority because I think we need to swap this out soon.</p> Pulp - Refactor #2950: Improve Custom Storage Backend for 3.0https://pulp.plan.io/issues/2950?journal_id=213562017-08-01T21:17:09Zbmbouterbmbouter@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><p>I think this is ready to be groomed. If others don't want it groomed or think it needs more discussion please ungroom.</p> Pulp - Refactor #2950: Improve Custom Storage Backend for 3.0https://pulp.plan.io/issues/2950?journal_id=219462017-09-21T13:22:35Zmhrivnakmhrivnak@redhat.com
<ul></ul><p>Some users will want to look at the file on disk for various reasons, particularly if they suspect something has gone wrong. We see that a lot with Pulp 2. So I think it's valuable to return the path on disk through the API. If we don't, those users will go digging through the database to find it, and we'd rather not give them reason to go in there.</p> Pulp - Refactor #2950: Improve Custom Storage Backend for 3.0https://pulp.plan.io/issues/2950?journal_id=219712017-09-21T14:53:33Zmhrivnakmhrivnak@redhat.com
<ul><li><strong>Sprint/Milestone</strong> set to <i>45</i></li></ul> Pulp - Refactor #2950: Improve Custom Storage Backend for 3.0https://pulp.plan.io/issues/2950?journal_id=220402017-09-25T16:19:21Zjortel@redhat.comjortel@redhat.com
<ul></ul><p>The <em>FileStorage</em> class conforms to the django <em>Storage</em> interface, is tested and works. I'm in favor of revisiting this at some point but given the number of features that still need to be implemented and bugs that need to get fixed in pulp3, we should not be spending time on this now. I should have objected during sprint 26 planning.</p> Pulp - Refactor #2950: Improve Custom Storage Backend for 3.0https://pulp.plan.io/issues/2950?journal_id=220412017-09-25T17:54:15Zdkliban@redhat.com
<ul></ul><p>The only part of the custom storage backend that should remain is the implementation for the _save() method. This is the functionality that will allow us to put bits on disk once and then use the move operation to only logically move the file in it's final destination. The rest of the implementation should use the default behavior from Django.</p> Pulp - Refactor #2950: Improve Custom Storage Backend for 3.0https://pulp.plan.io/issues/2950?journal_id=221232017-09-28T18:31:38Zdkliban@redhat.com
<ul><li><strong>Status</strong> changed from <i>NEW</i> to <i>ASSIGNED</i></li><li><strong>Assignee</strong> set to <i>dkliban@redhat.com</i></li></ul> Pulp - Refactor #2950: Improve Custom Storage Backend for 3.0https://pulp.plan.io/issues/2950?journal_id=221262017-09-28T18:51:32Zdkliban@redhat.com
<ul><li><strong>Status</strong> changed from <i>ASSIGNED</i> to <i>POST</i></li></ul><p><a href="https://github.com/pulp/pulp/pull/3178" class="external">https://github.com/pulp/pulp/pull/3178</a></p> Pulp - Refactor #2950: Improve Custom Storage Backend for 3.0https://pulp.plan.io/issues/2950?journal_id=221562017-10-01T17:25:43Zdkliban@redhat.com
<ul><li><strong>Subject</strong> changed from <i>Remove Custom Storage Backend from 3.0</i> to <i>Improve Custom Storage Backend for 3.0</i></li><li><strong>Description</strong> updated (<a title="View differences" href="/journals/22156/diff?detail_id=22663">diff</a>)</li></ul><p>I updated the issue description with everything I learned while working on this ticket.</p> Pulp - Refactor #2950: Improve Custom Storage Backend for 3.0https://pulp.plan.io/issues/2950?journal_id=221572017-10-01T17:26:53Zdkliban@redhat.com
<ul><li><strong>Description</strong> updated (<a title="View differences" href="/journals/22157/diff?detail_id=22664">diff</a>)</li></ul> Pulp - Refactor #2950: Improve Custom Storage Backend for 3.0https://pulp.plan.io/issues/2950?journal_id=224392017-10-18T15:28:26Zjortel@redhat.comjortel@redhat.com
<ul><li><strong>Sprint/Milestone</strong> changed from <i>45</i> to <i>46</i></li></ul> Pulp - Refactor #2950: Improve Custom Storage Backend for 3.0https://pulp.plan.io/issues/2950?journal_id=225442017-10-23T19:53:52Zdkliban@redhat.com
<ul><li><strong>Status</strong> changed from <i>POST</i> to <i>MODIFIED</i></li><li><strong>% Done</strong> changed from <i>0</i> to <i>100</i></li></ul><p>Applied in changeset <a class="changeset" title="The FileSystemStorage backend provided by Django has been extended to conform to Pulp needs. When..." href="https://pulp.plan.io/projects/pulp/repository/pulp/revisions/15857fb0831c0998219a32e8d6ba52abdba20888">pulp|15857fb0831c0998219a32e8d6ba52abdba20888</a>.</p> Pulp - Refactor #2950: Improve Custom Storage Backend for 3.0https://pulp.plan.io/issues/2950?journal_id=262402018-03-08T23:25:24Zbmbouterbmbouter@redhat.com
<ul><li><strong>Sprint</strong> set to <i>Sprint 27</i></li></ul> Pulp - Refactor #2950: Improve Custom Storage Backend for 3.0https://pulp.plan.io/issues/2950?journal_id=262522018-03-08T23:25:42Zbmbouterbmbouter@redhat.com
<ul><li><strong>Sprint/Milestone</strong> deleted (<del><i>46</i></del>)</li></ul> Pulp - Refactor #2950: Improve Custom Storage Backend for 3.0https://pulp.plan.io/issues/2950?journal_id=416822019-04-25T16:46:34Zdaviddavis
<ul><li><strong>Sprint/Milestone</strong> set to <i>3.0.0</i></li></ul> Pulp - Refactor #2950: Improve Custom Storage Backend for 3.0https://pulp.plan.io/issues/2950?journal_id=428622019-04-26T20:38:04Zbmbouterbmbouter@redhat.com
<ul><li><strong>Tags</strong> deleted (<del><i>Pulp 3</i></del>)</li></ul> Pulp - Refactor #2950: Improve Custom Storage Backend for 3.0https://pulp.plan.io/issues/2950?journal_id=507062019-12-13T17:25:17Zbmbouterbmbouter@redhat.com
<ul><li><strong>Status</strong> changed from <i>MODIFIED</i> to <i>CLOSED - CURRENTRELEASE</i></li></ul>