openSUSE Project Management Tool: Issueshttps://progress.opensuse.org/https://progress.opensuse.org/themes/openSUSE/favicon/favicon.ico?15829177842023-09-11T00:02:02ZopenSUSE Project Management Tool
Redmine openSUSE admin - tickets #135437 (Workable): Update openSUSE mirroring documentation/processeshttps://progress.opensuse.org/issues/1354372023-09-11T00:02:02Zluc14n0
<p>I want to make sure our documentation on mirroring is up to date -- or at the very least, decent enough -- for both the one setting up a mirror and the one registering/managing it. My motivation comes from seeing many mirror-related tickets around where we basically assign it to Andrii and forget about it. Sometimes I see Alex giving a hand, but still that doesn't scale well long term. Of course I don't expect to see a boom on people wanting to register, or make changes to their mirrors. However, the bus factor is lurking around the corner.</p>
<p>And in order to getting people aboard on helping with such tasks, having decent documentation is the corner stone, in my opinion. I'm basically going to need to borrow "trained eyes" when I update bits and pieces of the documentation, just to make sure I didn't misunderstand something or maybe even update a part of the process that's deprecated nowadays.</p>
<p>This would be a good opportunity to also "retire" all that MirrorBrain stuff and put more emphasis on MirrorCache, I hope.</p>
openQA Project - action #132458 (New): Fix documentation ambiguity about openQA-worker installati...https://progress.opensuse.org/issues/1324582023-07-07T13:25:35Zokurzokurz@suse.com
<a name="Motivation"></a>
<h2 >Motivation<a href="#Motivation" class="wiki-anchor">¶</a></h2>
<p>From <a href="https://suse.slack.com/archives/C02CANHLANP/p1688627949540039">https://suse.slack.com/archives/C02CANHLANP/p1688627949540039</a> the problem became apparent that our documentation mentions a command like <code>zypper in openQA-worker</code> twice and in both cases it's not clear what applies for SLE in particular:</p>
<blockquote>
<p>(Qi Wang) Last question: Officially not supported openQA-worker, since it is not supported, why is there a source of SLE openqa. openQA-worker is not supported on SLE, but the OpenQA is supported on slećwhy<br>
(Oliver Kurz) openQA includes the worker, both the webUI and worker are supported on SLE<br>
(Qi Wang) OK, Thank you,I will do some try. I installed openQA successfully on SLE15SP5 ,but when i check the packaged ,openQA-worker not installed. So i try to install on openQA-worker on it,then the come across the same problem which lack of dependency packages.<br>
(Oliver Kurz) Did you follow the instructions from <a href="http://open.qa/docs/#installing">http://open.qa/docs/#installing</a> and activated the SLE modules including package hub?<br>
(Qi Wang) I see. you means this . /etc/os-release<br>
SUSEConnect -p sle-module-desktop-applications/$VERSION_ID/$CPU<br>
SUSEConnect -p sle-module-development-tools/$VERSION_ID/$CPU<br>
SUSEConnect -p sle-we/$VERSION_ID/$CPU -r $sled_key<br>
SUSEConnect -p PackageHub/$VERSION_ID/$CPU<br>
zypper in openQA<br>
(Oliver Kurz) yes<br>
(Qi Wang) hello,Oliver I don't see how to install openQA-worker on sle in the documentation where only have opensuse and fedora <a href="http://open.qa/docs/#_run_openqa_workers">http://open.qa/docs/#_run_openqa_workers</a>, so are there any special settings to config? I tried and the installation also failed.<br>
(Oliver Kurz) I see that our documentation is not exactly clear on that as SLE and the necessary SLE modules are only mentioned in the top section, not in the worker specific section</p>
</blockquote>
<a name="Acceptance-criteria"></a>
<h2 >Acceptance criteria<a href="#Acceptance-criteria" class="wiki-anchor">¶</a></h2>
<ul>
<li><strong>AC1:</strong> The documentation is clear about SLE pre-requisites when installing the openQA worker</li>
<li><strong>AC2:</strong> No unnecessary duplication so likely no double mention of <code>zypper in openQA-worker</code></li>
</ul>
<a name="Suggestions"></a>
<h2 >Suggestions<a href="#Suggestions" class="wiki-anchor">¶</a></h2>
<ul>
<li>Try to not mention <code>zypper in openQA-worker</code> in two places instead link from one place to the other</li>
<li>Maybe put the SLE module activation in a separate code block and reference it from both the instructions for webUI and worker package</li>
</ul>
openQA Project - action #90341 (Workable): [easy][beginner] section numbering on http://open.qa/d...https://progress.opensuse.org/issues/903412021-03-19T10:03:03Zokurzokurz@suse.com
<a name="Motivation"></a>
<h2 >Motivation<a href="#Motivation" class="wiki-anchor">¶</a></h2>
<p><a href="http://open.qa/docs/" class="external">http://open.qa/docs/</a> is getting big. We render the document without numbering of sections which could help structuring</p>
<a name="Acceptance-criteria"></a>
<h2 >Acceptance criteria<a href="#Acceptance-criteria" class="wiki-anchor">¶</a></h2>
<ul>
<li><strong>AC1:</strong> section header in <a href="http://open.qa/docs/" class="external">http://open.qa/docs/</a> include numbers</li>
<li><strong>AC2:</strong> Numbers do not need to be manually maintained</li>
</ul>
<a name="Suggestions"></a>
<h2 >Suggestions<a href="#Suggestions" class="wiki-anchor">¶</a></h2>
<ul>
<li>Explore how we can render the document differently without too much changes to the structure, maybe asciidoctor just allows this with an option</li>
</ul>
<a name="Further-details"></a>
<h2 >Further details<a href="#Further-details" class="wiki-anchor">¶</a></h2>
<p>entrance level issue</p>