openSUSE Project Management Tool: Issueshttps://progress.opensuse.org/https://progress.opensuse.org/themes/openSUSE/favicon/favicon.ico?15829177842024-02-14T15:28:07ZopenSUSE Project Management Tool
Redmine openQA Project - action #155491 (New): Extend documentation for single-instance-container coverin...https://progress.opensuse.org/issues/1554912024-02-14T15:28:07Zokurzokurz@suse.com
<a name="Motivation"></a>
<h2 >Motivation<a href="#Motivation" class="wiki-anchor">¶</a></h2>
<p>Based on a conversation we had regarding <a href="https://github.com/os-autoinst/openQA/pull/5472" class="external">https://github.com/os-autoinst/openQA/pull/5472</a> and <a class="issue tracker-4 status-6 priority-4 priority-default closed child" title="action: Avoid the need for API keys within the same container/client (Rejected)" href="https://progress.opensuse.org/issues/155473">#155473</a> . There are some good ideas in the original proposal from mkittler and some comments what could be done to improve in <a href="https://github.com/os-autoinst/openQA/pull/5472#discussion_r1488683658" class="external">https://github.com/os-autoinst/openQA/pull/5472#discussion_r1488683658</a></p>
<a name="Acceptance-criteria"></a>
<h2 >Acceptance criteria<a href="#Acceptance-criteria" class="wiki-anchor">¶</a></h2>
<ul>
<li><strong>AC1:</strong> The openQA documentation presents easy examples how to trigger/clone existing jobs applicable to the single-instance-container</li>
</ul>
<a name="Suggestions"></a>
<h2 >Suggestions<a href="#Suggestions" class="wiki-anchor">¶</a></h2>
<ul>
<li>Read the code commented in <a href="https://github.com/os-autoinst/openQA/pull/5472#discussion_r1488683658" class="external">https://github.com/os-autoinst/openQA/pull/5472#discussion_r1488683658</a> and the according comments</li>
<li>Extend the existing user guide showing some easy examples how to run an openQA client, e.g. from a client container, or – for experts – commands in the running instance of the container</li>
<li>Optional: Rework GettingStarted.asciidoc to feature spawing the single-instance-container and using it to trigger/clone existing jobs</li>
<li>Optional: After <a href="https://github.com/os-autoinst/openQA/blob/master/docs/Installing.asciidoc?plain=1#L68" class="external">https://github.com/os-autoinst/openQA/blob/master/docs/Installing.asciidoc?plain=1#L68</a> add another section how to have a persistent database or asset management in openQA containers</li>
</ul>
openQA Project - action #128423 (New): [gsoc] Container-based backend for openQAhttps://progress.opensuse.org/issues/1284232023-04-28T18:02:38Zokurzokurz@suse.com
<p>From <a href="https://github.com/openSUSE/mentoring/issues/120">https://github.com/openSUSE/mentoring/issues/120</a></p>
<p><strong>Project Title:</strong> Container-based backend for openQA</p>
<p><strong>Description:</strong></p>
<p><a href="https://open.qa" class="external">openQA</a> is an automated test tool for operating systems and the engine at the heart of openSUSE's automated testing initiative. It provides already several backends that allows testing an O.S. on a variety of architectures and scenarios including baremetal and different kinds of virtualized environment.</p>
<p>A backend capable of directly interacting with different containers technologies would allow us to test container images before release - that could be really useful and enhance the development and publication workflow of containerized environments. </p>
<p>The new container backend ideally should provide an abstract interface to allow <a href="https://github.com/os-autoinst/os-autoinst" class="external">os-autoinst</a> and the test cases to interact with the specific container technology ( that could be Kubernetes, Rancher, podman, Docker, LXD/LXC, rkt, etc. ) and provide the same integration to our current workflow (e.g. tests that runs under a VM).</p>
<p>If you haven't already, <a href="https://openqa.opensuse.org" class="external">have a look at openQA in action</a>.</p>
<p><strong>Deliverable:</strong> Code is merged with the necessary tests to prove each feature created. Abstract interface design and at least one specific backend container implementation is expected.</p>
<p><strong>Mentor:</strong> <a class="user active user-mention" href="https://progress.opensuse.org/users/17668">@okurz</a>, @kalikiana</p>
<p><strong>Skills:</strong> podman/docker, a bit of Perl, some general knowledge of containerized environment and container management frameworks</p>
<p><strong>Skill Level:</strong> Medium</p>
<p><strong>Get started:</strong></p>
<ul>
<li><p>Engage with the development team! We hang out in <a href="https://app.element.io/#/room/#openqa:opensuse.org">https://app.element.io/#/room/#openqa:opensuse.org</a> and [#opensuse-factory](irc://libera.chat/opensuse-factory) on Libera.Chat!</p></li>
<li><p>Start forking the <a href="https://github.com/os-autoinst/openQA" class="external">openQA</a> and the <a href="https://github.com/os-autoinst/os-autoinst" class="external">os-autoinst</a> repo</p></li>
<li><p>General hints and advices for good project proposals:</p>
<ul>
<li><a href="https://google.github.io/gsocguides/student/writing-a-proposal">https://google.github.io/gsocguides/student/writing-a-proposal</a></li>
<li><a href="https://hackernoon.com/7-things-you-need-to-know-to-ace-your-gsoc-proposal-92ff7ef23f5a">https://hackernoon.com/7-things-you-need-to-know-to-ace-your-gsoc-proposal-92ff7ef23f5a</a></li>
<li><a href="https://medium.com/oppia-org/things-i-learned-from-reviewing-gsoc-proposals-154707cdcca5">https://medium.com/oppia-org/things-i-learned-from-reviewing-gsoc-proposals-154707cdcca5</a></li>
</ul></li>
</ul>
openQA Project - action #91631 (New): [easy][beginner][doc] document suggestions how to include t...https://progress.opensuse.org/issues/916312021-04-23T11:08:34Zokurzokurz@suse.com
<a name="Motivation"></a>
<h2 >Motivation<a href="#Motivation" class="wiki-anchor">¶</a></h2>
<p>Rough text suggestion based on a chat protocol:</p>
<p>"The problem is that your worker can not find the test definitions. That's what it says with "'SCHEDULE' not set and opensuse/main.pm not found, need one of both". you can do one of four options: 1. instead of cloning a production test that relies on a local checkout of tests use tests cloning from git, in the format as in <a href="https://github.com/os-autoinst/os-autoinst/blob/master/doc/backend_vars.asciidoc" class="external">https://github.com/os-autoinst/os-autoinst/blob/master/doc/backend_vars.asciidoc</a> under CASEDIR, 2. link a local test clone into the worker container with a volume mount, 3. configure the worker to use caching to sync tests from the central webUI instance or 4. manually provide the test definition within the worker filesystem</p>
<a name="Further-details"></a>
<h2 >Further details<a href="#Further-details" class="wiki-anchor">¶</a></h2>
<p>entrance level issue</p>