https://pulp.plan.io/https://pulp.plan.io/favicon.ico2018-11-20T14:06:54ZPulpContainer Support - Story #4174: As a user, I can lazy sync a docker repositoryhttps://pulp.plan.io/issues/4174?journal_id=320252018-11-20T14:06:54Zipanova@redhat.comipanova@redhat.com
<ul><li><strong>Description</strong> updated (<a title="View differences" href="/journals/32025/diff?detail_id=32772">diff</a>)</li></ul> Container Support - Story #4174: As a user, I can lazy sync a docker repositoryhttps://pulp.plan.io/issues/4174?journal_id=320302018-11-20T16:00:13Zamacdona@redhat.comaustin@redhat.com
<ul><li><strong>Description</strong> updated (<a title="View differences" href="/journals/32030/diff?detail_id=32776">diff</a>)</li></ul><p>Currently, the pulp3 lazy sync implementation plan is to disable the ArtifactDownload and ArtifactSaver stages. This will not work for Docker since these stages are used to download and save metadata (tags, manifests, and manifest lists) as well as blobs/layers (which would not be downloaded or saved for lazy).</p>
<p>We have a couple options to implement this for docker, and it may also be possible to make a contribution to pulpcore to enable easy implementation for other plugins with multiple metadata files.</p>
<p>Idea 1: Add a field to the DeclarativeArtifact</p>
<p>Using a new field, DeclarativeArtifact.metadata (defaults to false), the ArtifactDownload and ArtifactSaver stages could potentially be updated to skip them when da.metadata=false and lazy=true.</p>
<p>Idea 2: Override ArtifactDownload and ArtifactSaver stages</p>
<p>If we override, we just have to add a little logic that checks the type of the DeclarativeContent.content. If lazy and type is Blob, don't download or save.</p> Container Support - Story #4174: As a user, I can lazy sync a docker repositoryhttps://pulp.plan.io/issues/4174?journal_id=325682018-12-05T15:04:18Zamacdona@redhat.comaustin@redhat.com
<ul><li><strong>Related to</strong> <i><a class="issue tracker-3 status-11 priority-6 priority-default closed child" href="/issues/4209">Story #4209</a>: As a plugin writer, I can implement lazy sync for plugins with multiple metadata files</i> added</li></ul> Container Support - Story #4174: As a user, I can lazy sync a docker repositoryhttps://pulp.plan.io/issues/4174?journal_id=409642019-04-18T15:12:48Zipanova@redhat.comipanova@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><li><strong>Sprint</strong> set to <i>Sprint 52</i></li></ul> Container Support - Story #4174: As a user, I can lazy sync a docker repositoryhttps://pulp.plan.io/issues/4174?journal_id=409742019-04-18T19:53:37Zdkliban@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> Container Support - Story #4174: As a user, I can lazy sync a docker repositoryhttps://pulp.plan.io/issues/4174?journal_id=409802019-04-18T20:41:41Zdkliban@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_docker/pull/344" class="external">https://github.com/pulp/pulp_docker/pull/344</a></p> Container Support - Story #4174: As a user, I can lazy sync a docker repositoryhttps://pulp.plan.io/issues/4174?journal_id=411572019-04-24T16:17:24Zdkliban@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 commit:pulp_docker|75fc777756b95e1df5da7bd2b08a32c2945742dc.</p> Container Support - Story #4174: As a user, I can lazy sync a docker repositoryhttps://pulp.plan.io/issues/4174?journal_id=422302019-04-26T20:33:17Zbmbouterbmbouter@redhat.com
<ul><li><strong>Tags</strong> deleted (<del><i>Pulp 3</i></del>)</li></ul> Container Support - Story #4174: As a user, I can lazy sync a docker repositoryhttps://pulp.plan.io/issues/4174?journal_id=431902019-04-29T21:26:54Zkersom
<ul><li><strong>Related to</strong> <i><a class="issue tracker-5 status-13 priority-6 priority-default closed" href="/issues/4126">Test #4126</a>: Test sync with different download policies</i> added</li></ul> Container Support - Story #4174: As a user, I can lazy sync a docker repositoryhttps://pulp.plan.io/issues/4174?journal_id=447232019-06-14T18:19:24Zkersom
<ul><li><strong>Related to</strong> <i><a class="issue tracker-5 status-12 priority-6 priority-default closed" href="/issues/4973">Test #4973</a>: Docker - Test sync with different download policies</i> added</li></ul> Container Support - Story #4174: As a user, I can lazy sync a docker repositoryhttps://pulp.plan.io/issues/4174?journal_id=493902019-11-20T18:21:27Zipanova@redhat.comipanova@redhat.com
<ul><li><strong>Project</strong> changed from <i>Docker Support</i> to <i>Container Support</i></li></ul> Container Support - Story #4174: As a user, I can lazy sync a docker repositoryhttps://pulp.plan.io/issues/4174?journal_id=502442019-12-12T22:39:00Zipanova@redhat.comipanova@redhat.com
<ul><li><strong>Status</strong> changed from <i>MODIFIED</i> to <i>CLOSED - CURRENTRELEASE</i></li></ul> Container Support - Story #4174: As a user, I can lazy sync a docker repositoryhttps://pulp.plan.io/issues/4174?journal_id=523392020-01-22T19:00:52Zipanova@redhat.comipanova@redhat.com
<ul><li><strong>Sprint/Milestone</strong> set to <i>1.0.0</i></li></ul>