https://pulp.plan.io/https://pulp.plan.io/favicon.ico2015-01-07T15:50:47ZPulpOSTree Support - Story #95: As a user, I can manage ostree content units by branchhttps://pulp.plan.io/issues/95?journal_id=1332015-01-07T15:50:47Zjortel@redhat.comjortel@redhat.com
<ul><li><strong>Description</strong> updated (<a title="View differences" href="/journals/133/diff?detail_id=127">diff</a>)</li></ul> OSTree Support - Story #95: As a user, I can manage ostree content units by branchhttps://pulp.plan.io/issues/95?journal_id=1342015-01-07T15:52:18Zjortel@redhat.comjortel@redhat.com
<ul><li><strong>Sprint/Milestone</strong> deleted (<del><i>9</i></del>)</li></ul> OSTree Support - Story #95: As a user, I can manage ostree content units by branchhttps://pulp.plan.io/issues/95?journal_id=1362015-01-07T15:54:35Zjortel@redhat.comjortel@redhat.com
<ul><li><strong>Tracker</strong> changed from <i>Issue</i> to <i>Story</i></li></ul> OSTree Support - Story #95: As a user, I can manage ostree content units by branchhttps://pulp.plan.io/issues/95?journal_id=1892015-01-12T16:47:08Zcduryeecduryee@redhat.com
<ul><li><strong>Sprint/Milestone</strong> set to <i>9</i></li></ul> OSTree Support - Story #95: As a user, I can manage ostree content units by branchhttps://pulp.plan.io/issues/95?journal_id=1952015-01-12T17:00:30Zjortel@redhat.comjortel@redhat.com
<ul><li><strong>Assignee</strong> set to <i>jortel@redhat.com</i></li></ul> OSTree Support - Story #95: As a user, I can manage ostree content units by branchhttps://pulp.plan.io/issues/95?journal_id=2002015-01-12T18:48:40Zrbarlow
<ul><li><strong>Project</strong> changed from <i>Pulp</i> to <i>OSTree Support</i></li></ul> OSTree Support - Story #95: As a user, I can manage ostree content units by branchhttps://pulp.plan.io/issues/95?journal_id=2802015-01-22T22:53:46Zjortel@redhat.comjortel@redhat.com
<ul></ul><p>libostree support for pull-local we'd planned to use for publishing needs work: <a href="https://bugzilla.redhat.com/show_bug.cgi?id=1185106" class="external">https://bugzilla.redhat.com/show_bug.cgi?id=1185106</a>. We'll likely need to shell out to ostree instead :(</p>
<p>Eg:</p>
<p>ostree --repo=repo-clone pull-local repo fcc7dc55bebb8f154c7c527c908349c4513165791ff3e010603b0915c48f08c2</p>
<p>Filed this RFE after discussing with Colin Walters: <a href="https://bugzilla.redhat.com/show_bug.cgi?id=1185106" class="external">https://bugzilla.redhat.com/show_bug.cgi?id=1185106</a></p> OSTree Support - Story #95: As a user, I can manage ostree content units by branchhttps://pulp.plan.io/issues/95?journal_id=2822015-01-23T13:37:45Zbmbouterbmbouter@redhat.com
<ul></ul><p>It sounds like we may have few alternatives, but what can be done about potential orphan processes if the task process suddenly gets killed with SIGKILL? With the 2.6.0 release plugin writers are told not to use subprocess. There is some talk of this in <a href="http://pulp.readthedocs.org/en/latest/user-guide/release-notes/2.6.x.html#plugin-api-changes" class="external">the 2.6.0 release notes</a></p>
<p>Perhaps the ostree will auto-exit after some time, like a timeout? Or maybe we can call subprocess in such a way that when the parent exits the child will also exit. Can we do that?</p> OSTree Support - Story #95: As a user, I can manage ostree content units by branchhttps://pulp.plan.io/issues/95?journal_id=2832015-01-23T14:27:02Zjortel@redhat.comjortel@redhat.com
<ul></ul><p>If we decide to shell out, I think this command is fast enough to run safely as a non-deamon child process without concern of orphans. That said, I really don't like the idea of it. We should still consider just using libostree without the additional API. The downside is that when newer features/constructs get introduced into ostree (and ostree repositories), we may need to patch pulp's use of the lib. When discussing with Colin, he referenced a new thing called "deltas" they are working on. I will discusss with Colin further to better understand the impact of this decision.</p>
<p>Example:</p>
<p>[root@icarus fedora-atomic]# ostree --repo=repo-clone init --mode=archive-z2<br>
[root@icarus fedora-atomic]# time ostree --repo=repo-clone pull-local repo fedora-atomic/rawhide/x86_64/docker-host<br>
Enumerating objects...</p>
<p>pull: 17537/17537 scanned, 17537 objects copied<br>
Writing 1 refs</p>
<p>real 0m0.321s<br>
user 0m0.249s<br>
sys 0m0.388s</p> OSTree Support - Story #95: As a user, I can manage ostree content units by branchhttps://pulp.plan.io/issues/95?journal_id=2892015-01-23T19:37:55Zbmbouterbmbouter@redhat.com
<ul></ul><p>@jortel: As long as the shell calls are guaranteed to exit on their own I think its fine. It sounds like they will. My main concern is orphan processes being leftover when cancel becomes a SIGKILL with 2.6.0.</p> OSTree Support - Story #95: As a user, I can manage ostree content units by branchhttps://pulp.plan.io/issues/95?journal_id=3522015-02-06T20:24:46Zmhrivnakmhrivnak@redhat.com
<ul><li><strong>Sprint/Milestone</strong> deleted (<del><i>9</i></del>)</li></ul> OSTree Support - Story #95: As a user, I can manage ostree content units by branchhttps://pulp.plan.io/issues/95?journal_id=3892015-02-09T17:00:36Zbmbouterbmbouter@redhat.com
<ul><li><strong>Tags</strong> <i>Sprint Candidate</i> added</li></ul> OSTree Support - Story #95: As a user, I can manage ostree content units by branchhttps://pulp.plan.io/issues/95?journal_id=4222015-02-09T20:46:35Zmhrivnakmhrivnak@redhat.com
<ul><li><strong>Sprint/Milestone</strong> set to <i>12</i></li></ul> OSTree Support - Story #95: As a user, I can manage ostree content units by branchhttps://pulp.plan.io/issues/95?journal_id=4592015-02-16T19:52:17Zjortel@redhat.comjortel@redhat.com
<ul><li><strong>Status</strong> changed from <i>NEW</i> to <i>ASSIGNED</i></li><li><strong>Start date</strong> changed from <i>01/07/2015</i> to <i>02/16/2015</i></li></ul> OSTree Support - Story #95: As a user, I can manage ostree content units by branchhttps://pulp.plan.io/issues/95?journal_id=4632015-02-17T15:19:25Zjortel@redhat.comjortel@redhat.com
<ul><li><strong>% Done</strong> changed from <i>0</i> to <i>10</i></li></ul> OSTree Support - Story #95: As a user, I can manage ostree content units by branchhttps://pulp.plan.io/issues/95?journal_id=5162015-02-27T14:53:29Zjortel@redhat.comjortel@redhat.com
<ul><li><strong>% Done</strong> changed from <i>10</i> to <i>100</i></li></ul> OSTree Support - Story #95: As a user, I can manage ostree content units by branchhttps://pulp.plan.io/issues/95?journal_id=5172015-02-27T15:09:25Zjortel@redhat.comjortel@redhat.com
<ul><li><strong>Status</strong> changed from <i>ASSIGNED</i> to <i>POST</i></li></ul> OSTree Support - Story #95: As a user, I can manage ostree content units by branchhttps://pulp.plan.io/issues/95?journal_id=17572015-03-02T21:53:28Zbmbouterbmbouter@redhat.com
<ul><li><strong>Tags</strong> deleted (<del><i>Sprint Candidate</i></del>)</li></ul> OSTree Support - Story #95: As a user, I can manage ostree content units by branchhttps://pulp.plan.io/issues/95?journal_id=17992015-03-03T02:16:59Zjortel@redhat.comjortel@redhat.com
<ul><li><strong>Status</strong> changed from <i>POST</i> to <i>MODIFIED</i></li></ul> OSTree Support - Story #95: As a user, I can manage ostree content units by branchhttps://pulp.plan.io/issues/95?journal_id=20362015-03-06T14:31:11Zjortel@redhat.comjortel@redhat.com
<ul><li><strong>Assignee</strong> deleted (<del><i>jortel@redhat.com</i></del>)</li></ul> OSTree Support - Story #95: As a user, I can manage ostree content units by branchhttps://pulp.plan.io/issues/95?journal_id=41902015-05-06T13:23:13Zdkliban@redhat.com
<ul><li><strong>Target Release - OSTree</strong> set to <i>master</i></li></ul> OSTree Support - Story #95: As a user, I can manage ostree content units by branchhttps://pulp.plan.io/issues/95?journal_id=50042015-06-15T20:44:48Zdkliban@redhat.com
<ul><li><strong>Status</strong> changed from <i>MODIFIED</i> to <i>5</i></li></ul> OSTree Support - Story #95: As a user, I can manage ostree content units by branchhttps://pulp.plan.io/issues/95?journal_id=57212015-08-04T19:49:05Zbmbouterbmbouter@redhat.com
<ul><li><strong>Assignee</strong> set to <i>jortel@redhat.com</i></li><li><strong>Groomed</strong> set to <i>No</i></li><li><strong>Sprint Candidate</strong> set to <i>No</i></li></ul><p>This was missing assignee so I added it.</p> OSTree Support - Story #95: As a user, I can manage ostree content units by branchhttps://pulp.plan.io/issues/95?journal_id=87812016-02-11T20:05:53Zrbarlow
<ul><li><strong>Status</strong> changed from <i>5</i> to <i>CLOSED - CURRENTRELEASE</i></li><li><strong>Target Release - OSTree</strong> changed from <i>master</i> to <i>1.0.0</i></li></ul> OSTree Support - Story #95: As a user, I can manage ostree content units by branchhttps://pulp.plan.io/issues/95?journal_id=250862018-03-08T18:10:37Zbmbouterbmbouter@redhat.com
<ul><li><strong>Sprint</strong> set to <i>February 2015</i></li></ul> OSTree Support - Story #95: As a user, I can manage ostree content units by branchhttps://pulp.plan.io/issues/95?journal_id=250992018-03-08T18:11:58Zbmbouterbmbouter@redhat.com
<ul><li><strong>Sprint/Milestone</strong> deleted (<del><i>12</i></del>)</li></ul> OSTree Support - Story #95: As a user, I can manage ostree content units by branchhttps://pulp.plan.io/issues/95?journal_id=407202019-04-15T21:21:36Zbmbouterbmbouter@redhat.com
<ul><li><strong>Tags</strong> <i>Pulp 2</i> added</li></ul>