https://progress.opensuse.org/https://progress.opensuse.org/themes/openSUSE/favicon/favicon.ico?15829177842020-05-29T15:11:31ZopenSUSE Project Management ToolopenQA Project - action #67468: Add the possibility to apply rootfs overlays on qcow2/raw imageshttps://progress.opensuse.org/issues/67468?journal_id=3039492020-05-29T15:11:31Zggardet_armguillaume.gardet@arm.com
<ul><li><strong>Subject</strong> changed from <i>Add the possibility to apply overlays on qcow2/raw images</i> to <i>Add the possibility to apply rootfs overlays on qcow2/raw images</i></li><li><strong>Description</strong> updated (<a title="View differences" href="/journals/303949/diff?detail_id=300631">diff</a>)</li></ul> openQA Project - action #67468: Add the possibility to apply rootfs overlays on qcow2/raw imageshttps://progress.opensuse.org/issues/67468?journal_id=3130212020-07-14T13:36:41Zokurzokurz@suse.com
<ul><li><strong>Priority</strong> changed from <i>Normal</i> to <i>Low</i></li><li><strong>Target version</strong> set to <i>future</i></li></ul><p>Hm, where would you rootfs come from? Maybe you could provide a proof-of-concept how you would create or where to get the rootfs from? In principle test code can run arbitrary code so you could merge the content from a rootfs overlay into the fs of a mounted qcow image and use that one for further tests</p>
openQA Project - action #67468: Add the possibility to apply rootfs overlays on qcow2/raw imageshttps://progress.opensuse.org/issues/67468?journal_id=3132822020-07-15T09:12:34Zggardet_armguillaume.gardet@arm.com
<ul></ul><p>The rootfs could be an archive pointed by <code>HDD_1_OVERLAY0</code> var and statically stored in <code>fixed/</code> asset folder or downloaded from <code>HDD_1_OVERLAY0_URL</code>.</p>
openQA Project - action #67468: Add the possibility to apply rootfs overlays on qcow2/raw imageshttps://progress.opensuse.org/issues/67468?journal_id=3134622020-07-16T12:03:34Zokurzokurz@suse.com
<ul></ul><p>I see. So is the important point for you that multiple rootfs overlays can be stored as openQA assets with different configuration and parameterized so that one can combine them within test configurations?</p>
<p>Again, currently I don't see any issue that should block that from openQA or os-autoinst point of view. Custom assets can be provided to tests (not only "iso" or "hdd"), see <a href="http://open.qa/docs/#_asset_handling" class="external">http://open.qa/docs/#_asset_handling</a> . Given that one could follow <a class="issue tracker-4 status-1 priority-3 priority-lowest" title="action: Add the possibility to apply rootfs overlays on qcow2/raw images (New)" href="https://progress.opensuse.org/issues/67468#note-2">#67468#note-2</a> to apply the overlay within the test flow.</p>