action #45365
closed[functional][u] Provide an option to set up openQA very easily
0%
Description
Motivation¶
Setting up openQA can be a bit complicated.
Therefore we should provide a way for users to do this with a single command.
This would allow non-qa engineers to reproduce openqa jobs.
Acceptance criteria¶
- AC1: There is a reasonably long one-line command that we feel confident to provide in bug reports to help non-openQA experienced users to reproduce openQA tests
Updated by dheidler about 6 years ago
https://w3.suse.de/~dheidler/openqa-container.html
Created two scripts:
https://w3.suse.de/~dheidler/openqa-bootstrap-container.sh will setup a container and run the 2nd script within the container.
https://w3.suse.de/~dheidler/openqa-bootstrap.sh will setup openQA (including a worker). This works in a container as well as on a normal linux system.
Updated by dheidler about 6 years ago
- Related to coordination #43706: [epic] Generate "download&use" docker image of openQA for SUSE QA added
Updated by dheidler about 6 years ago
- Subject changed from Provide an option to set up openQA very easy to [functional] Provide an option to set up openQA very easy
- Assignee set to dheidler
Updated by mkittler about 6 years ago
This sound like a much simpler and therefore better approach than using Docker. I haven't tested the scripts yet, but they look clean and one understands what is done. Likely easier and faster to read than the setup guide.
So I would say this could be added to the openQA repository similar to the Dockerfiles we have there as well. Or you create an own repo for now. Since it is containing URLs to internal services the internal GitLab would make most sense.
This is basically the same idea, just for creating a development setup where everything comes from Git and is executed as the regular user: https://github.com/martchus/openQA-helper
Maybe I copy your way of dealing with the API key :-)
Updated by dheidler about 6 years ago
Note that this won't really work well within docker as it is not designed to run systemd unless you do this:
docker run -d --cap-add=SYS_ADMIN -v /sys/fs/cgroup:/sys/fs/cgroup: ro tumbleweed /bin/systemd
Also you would need to make sure that /dev/kvm is available within the container.
Updated by okurz about 6 years ago
- Subject changed from [functional] Provide an option to set up openQA very easy to [functional][u] Provide an option to set up openQA very easily
- Description updated (diff)
- Category set to Feature requests
- Target version set to Milestone 22
@dheidler I added an acceptance criterion, please provide me feedback if you think it's wrong
Updated by dheidler about 6 years ago
Updated by dheidler almost 6 years ago
- Status changed from In Progress to Resolved
Tested on tumbleweed.
Added some docs.
Updated by okurz almost 6 years ago
- Status changed from Resolved to Feedback
dheidler wrote:
- AC1: There is a reasonably long one-line command that we feel confident to provide in bug reports to help non-openQA experienced users to reproduce openQA tests
Can you provide that "one-line" command that would also work on other operating system versions, e.g. Leap 15.1 (15.0?), as part of the documentation as we discussed today? E.g. something like curl … | bash -
If you prefer you can mention that in another ticket and close this one again
Updated by dheidler almost 6 years ago
See my PR regarding doc: https://github.com/os-autoinst/openQA/pull/1945
Updated by okurz almost 6 years ago
documentation PR merged. Now what is still missing is an automatic test for the new command.
Updated by dheidler almost 6 years ago
- Status changed from Feedback to In Progress
Now creating test for openQA-bootstrap that runs within openQA.
Updated by dheidler almost 6 years ago
- Status changed from In Progress to Feedback
Updated by okurz almost 6 years ago
PR merged. However, the tests https://openqa.opensuse.org/tests/840027 and https://openqa.opensuse.org/tests/840026 did not work and can not work because they want to boot an image that is not available on that machine selection. I delete these scenarios from the job group for now to not interfer with the Tumbleweed release process. You can experiment in the Development Tumbleweed job group. At best we can reuse an existing image to not use too much space. That means no "4G-40GB" machine but one of the existing ones if that works reliably.
Updated by dheidler almost 6 years ago
- Status changed from Feedback to Resolved
https://openqa.opensuse.org/tests/855997
https://openqa.opensuse.org/tests/855996
This is done and there are tests running on openqa.
Updated by okurz almost 6 years ago
Thank you. For reference: http://open.qa/docs/#_openqa_quick_bootstrap describes the easy and fast way to setup openQA. This is what we should also suggest to anyone that wants to quickly setup openQA, e.g. in bug reports, as mentioned in the motivation/AC
Updated by okurz almost 6 years ago
- Copied to action #48425: [functional][u] Provide an option to set up openQA *and* immediately clone a job very easily added