<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Openqa on x00/</title><link>https://fleax.codeberg.page/tags/openqa/</link><description>Recent content in Openqa on x00/</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Sun, 26 Apr 2026 07:52:44 +0200</lastBuildDate><atom:link href="https://fleax.codeberg.page/tags/openqa/index.xml" rel="self" type="application/rss+xml"/><item><title>openQA Scheduler Design</title><link>https://fleax.codeberg.page/2026/04/openqa-scheduler-design/</link><pubDate>Sun, 26 Apr 2026 07:52:44 +0200</pubDate><guid>https://fleax.codeberg.page/2026/04/openqa-scheduler-design/</guid><description>&lt;p&gt;When we say scheduling in openQA we are talking about the trigger which runs one or more tests in the framework.&#10;Usually we use &lt;code&gt;isos post&lt;/code&gt; to refer to the this - when we call them by terminal. the &lt;code&gt;isos post&lt;/code&gt; in fact, is the API&#10;which calls the endpoint which says to the according controller to perform the action. And it looks like this&lt;/p&gt;&#10;&lt;div class="highlight"&gt;&lt;pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;-webkit-text-size-adjust:none;"&gt;&lt;code class="language-bash" data-lang="bash"&gt;&lt;span style="display:flex;"&gt;&lt;span&gt;❯ openqa-cli api --host http://localhost --apikey &amp;lt;apik&amp;gt; --apisecret &amp;lt;apis&amp;gt; -X POST isos&#10;&lt;/span&gt;&lt;/span&gt;&lt;span style="display:flex;"&gt;&lt;span&gt;&lt;span style="color:#ae81ff"&gt;400&lt;/span&gt; Bad Request&#10;&lt;/span&gt;&lt;/span&gt;&lt;span style="display:flex;"&gt;&lt;span&gt;Error: missing parameters: DISTRI VERSION FLAVOR ARCH&#10;&lt;/span&gt;&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;&lt;/div&gt;&lt;p&gt;This is one way, and as it is shown above any job requires some particular&#10;variables, DISTRI VERSION FLAVOR ARCH but it will also need ISO at the minimum&#10;or/and BUILD GROUP even.&lt;/p&gt;</description></item><item><title>My openqa dev env</title><link>https://fleax.codeberg.page/2023/03/my-openqa-dev-env/</link><pubDate>Sat, 04 Mar 2023 00:00:00 +0000</pubDate><guid>https://fleax.codeberg.page/2023/03/my-openqa-dev-env/</guid><description>&lt;ul&gt;&#10;&lt;li&gt;Second OpenQA Instance&lt;/li&gt;&#10;&lt;/ul&gt;&#10;&lt;p&gt;This is an clumsy approach to run an openQA development environment besides the regular one. And yes it seems to&#10;be possible, with some caveats i guess. I am guessing because it is not fully functional and i wonder whether it&#10;is conflicted by other services somehow.&lt;/p&gt;&#10;&lt;p&gt;With this intro, i warn that this is not a complete guide and i take it as i will have to come back on it some other time.&lt;/p&gt;</description></item><item><title>Setup remote workers on OpenQA</title><link>https://fleax.codeberg.page/2021/07/setup-remote-workers-on-openqa/</link><pubDate>Sat, 10 Jul 2021 00:00:00 +0000</pubDate><guid>https://fleax.codeberg.page/2021/07/setup-remote-workers-on-openqa/</guid><description>&lt;p&gt;As an extension of the [[main documentation][http://open.qa/docs/#_configuring_remote_workers]] i write this describing what it took for me to&#10;setup another machine with remote workers.&lt;/p&gt;&#10;&lt;h1 id="remote-worker-side"&gt;Remote Worker side&lt;/h1&gt;&#10;&lt;p&gt;I installed [[Leap15.3][https://get.opensuse.org/leap/#download]] with ssh enabled and i updated the packages and immediately i run&lt;/p&gt;&#10;&lt;pre tabindex="0"&gt;&lt;code&gt;sudo zypper install openQA-worker&#10;&lt;/code&gt;&lt;/pre&gt;&lt;p&gt;As per documentation we can choose the share storage. This can be rsync or nfs for example. if the later you might want to install the package as well&lt;/p&gt;</description></item><item><title>How is it to work with openqa</title><link>https://fleax.codeberg.page/2021/05/how-is-it-to-work-with-openqa/</link><pubDate>Sat, 08 May 2021 00:00:00 +0000</pubDate><guid>https://fleax.codeberg.page/2021/05/how-is-it-to-work-with-openqa/</guid><description>&lt;h3 id="meet-openqa"&gt;Meet OpenQA&lt;/h3&gt;&#10;&lt;p&gt;OpenQA is different.&lt;/p&gt;&#10;&lt;p&gt;It is also a demostration of the power emerges from the open source world and the beast that it can create.&#10;A bit ambiquous and chaotic if you ask me. It is also slow. And if you are looking for a 21st century UI, i&#10;doubt it would impress you.&lt;/p&gt;&#10;&lt;p&gt;The first time i heard about it, I was like i should certainly try it. I gave up. Everything i knew at the time,&#10;i was not able to apply any of them. I used to have an easy approach to start, right? Run some script, setup dev&#10;environment, run the software, check out the code and stuff. And some fancy documentation some times.&lt;/p&gt;</description></item></channel></rss>