https://progress.opensuse.org/https://progress.opensuse.org/themes/openSUSE/favicon/favicon.ico?15829177842016-05-25T18:43:46ZopenSUSE Project Management ToolopenQA Project - action #12130: [tools]'Proper Interactive Mode' - Making openQA gods gift to developershttps://progress.opensuse.org/issues/12130?journal_id=237082016-05-25T18:43:46ZAdamWill
<ul></ul><p>target date: YESTERDAY GODDAMNIT GIVE THIS TO ME NOW</p>
openQA Project - action #12130: [tools]'Proper Interactive Mode' - Making openQA gods gift to developershttps://progress.opensuse.org/issues/12130?journal_id=237142016-05-26T07:29:13Zokurzokurz@suse.com
<ul><li><strong>Subject</strong> changed from <i>'Proper Interactive Mode' - Making openQA gods gift to developers.</i> to <i>'Proper Interactive Mode' - Making openQA gods gift to developers</i></li><li><strong>Description</strong> updated (<a title="View differences" href="/journals/23714/diff?detail_id=24714">diff</a>)</li></ul> openQA Project - action #12130: [tools]'Proper Interactive Mode' - Making openQA gods gift to developershttps://progress.opensuse.org/issues/12130?journal_id=237222016-05-27T08:26:32Zokurzokurz@suse.com
<ul></ul><p>SUSE studio is already offering something in this direction. We can take their approach for motivation (but consider that the source code is closed).</p>
<p>From a technical perspective connecting to the machine and continuing execution for a virtual machine works by using the qemu machine commands so it will be beneficial if we first gather in better documentation what we have and then improve to have a more streamlined GUI approach.</p>
openQA Project - action #12130: [tools]'Proper Interactive Mode' - Making openQA gods gift to developershttps://progress.opensuse.org/issues/12130?journal_id=237242016-05-27T08:44:40Zcoolocoolo@suse.com
<ul></ul><p>why is this High priority? what can't we do unless this is done?</p>
openQA Project - action #12130: [tools]'Proper Interactive Mode' - Making openQA gods gift to developershttps://progress.opensuse.org/issues/12130?journal_id=237282016-05-27T09:58:42Zokurzokurz@suse.com
<ul></ul><p>It's high because rbrown is stoked about it :-) But he still set it for "future" milestone, i.e. it's not planned to do it right now. That's kinda conflicting but as multiple persons tell "this is already possible right now" and we don't have a good guide to point bug investigators to I would also see this as high priority.</p>
openQA Project - action #12130: [tools]'Proper Interactive Mode' - Making openQA gods gift to developershttps://progress.opensuse.org/issues/12130?journal_id=237822016-05-30T07:14:27Zcoolocoolo@suse.com
<ul></ul><p>So you want random users to be able to stop jobs or do you want to introduce a 'bug investigator' role with certain permissions?</p>
openQA Project - action #12130: [tools]'Proper Interactive Mode' - Making openQA gods gift to developershttps://progress.opensuse.org/issues/12130?journal_id=239982016-06-01T13:14:57Zdheidlerdheidler@suse.com
<ul></ul><p>The current interactive mode will stop the VM but not qemu (so new vnc clients can connect, but can't do anything).</p>
<p>Most workers allow vnc connections (without auth, but with the -shared option).<br>
Workers with the name openqaworkerX (where X ∈ ℕ) don't accept the connection for some reason.</p>
openQA Project - action #12130: [tools]'Proper Interactive Mode' - Making openQA gods gift to developershttps://progress.opensuse.org/issues/12130?journal_id=249682016-07-08T13:55:41Zokurzokurz@suse.com
<ul></ul><p>Based on my recent experiences I wrote down <a href="https://progress.opensuse.org/projects/openqatests/wiki#Interactive-investigation" class="external">https://progress.opensuse.org/projects/openqatests/wiki#Interactive-investigation</a> which might be useful to keep in mind when working on this issue.</p>
openQA Project - action #12130: [tools]'Proper Interactive Mode' - Making openQA gods gift to developershttps://progress.opensuse.org/issues/12130?journal_id=299722016-10-14T13:08:20Zoholecekoholecek@suse.com
<ul><li><strong>Assignee</strong> set to <i>oholecek</i></li></ul><p>Working on this. The idea is that test does not call testapi directly instead it calls testapi wrapper which talks to testapi::server (through socket) doing the actual changes. This way, when test is in waiting, I can unpause the VM and provide interface with available testapi calls - these can not only change the VM, but also be recorded to create proper openQA test.</p>
<p>Regarding the security, I'm tempting to allow this only when controlling openqa webui is running on localhost, or on config-allowed FQDNs - i.e. test developer working on machine she has access to.</p>
openQA Project - action #12130: [tools]'Proper Interactive Mode' - Making openQA gods gift to developershttps://progress.opensuse.org/issues/12130?journal_id=313862016-11-10T09:06:34Zmkittlermarius.kittler@suse.com
<ul><li><strong>Related to</strong> <i><a class="issue tracker-4 status-6 priority-3 priority-lowest closed" href="/issues/14668">action #14668</a>: interactive mode - needle editor is not stable or crashed in most use cases</i> added</li></ul> openQA Project - action #12130: [tools]'Proper Interactive Mode' - Making openQA gods gift to developershttps://progress.opensuse.org/issues/12130?journal_id=337322016-12-06T10:56:44Zokurzokurz@suse.com
<ul><li><strong>Priority</strong> changed from <i>High</i> to <i>Normal</i></li></ul><p>oholecek, are you really working on this? I guess it's time again to deprioritize a bit. I am pretty sure we can near never really solve this but we should keep this user epic around and link tickets to it with more specific ideas.</p>
openQA Project - action #12130: [tools]'Proper Interactive Mode' - Making openQA gods gift to developershttps://progress.opensuse.org/issues/12130?journal_id=437602017-03-14T11:01:33ZRBrownSUSErbrown@suse.com
<ul><li><strong>Subject</strong> changed from <i>'Proper Interactive Mode' - Making openQA gods gift to developers</i> to <i>[tools]'Proper Interactive Mode' - Making openQA gods gift to developers</i></li></ul> openQA Project - action #12130: [tools]'Proper Interactive Mode' - Making openQA gods gift to developershttps://progress.opensuse.org/issues/12130?journal_id=731442017-11-21T13:51:34Zcoolocoolo@suse.com
<ul><li><strong>Assignee</strong> deleted (<del><i>oholecek</i></del>)</li></ul> openQA Project - action #12130: [tools]'Proper Interactive Mode' - Making openQA gods gift to developershttps://progress.opensuse.org/issues/12130?journal_id=1296912018-06-15T19:07:44Zokurzokurz@suse.com
<ul><li><strong>Target version</strong> changed from <i>future</i> to <i>future</i></li></ul> openQA Project - action #12130: [tools]'Proper Interactive Mode' - Making openQA gods gift to developershttps://progress.opensuse.org/issues/12130?journal_id=2224702019-06-20T16:01:49Zokurzokurz@suse.com
<ul><li><strong>Category</strong> changed from <i>124</i> to <i>Feature requests</i></li></ul> openQA Project - action #12130: [tools]'Proper Interactive Mode' - Making openQA gods gift to developershttps://progress.opensuse.org/issues/12130?journal_id=2501212019-10-15T10:19:34Zcoolocoolo@suse.com
<ul><li><strong>Status</strong> changed from <i>New</i> to <i>Resolved</i></li></ul><p>I think everyone agrees we succeeded</p>