mirror of
https://github.com/rocky-linux/os-autoinst-distri-rocky.git
synced 2024-06-02 02:40:16 +00:00
f59343403a
Summary: These require openQA tap networking to allow the server and client boxes to communicate, and require masquerading (NAT) so the server at least can reach a repository (dnf/rolekit really, really do not want to work without a repo connection). They use the 'parallel' test support to have the server deploy run first while the client enrol test waits at the grub menu until the server is done before it goes ahead. This is all deployed and working on stg. The really tricky bit was getting all the openvswitch and firewall config right in ansible. We *could* do the server deploy test as a follow-on from the default install test to save the install, but then we'd have to teach it to change the hostname and set up static networking post-install. I'm not sure if it's worth doing that. This requires the corresponding openqa_fedora_tools commit that adds the hard disks (containing the kickstarts - it's possible to get them from remote during install, but we have to set up name resolution or hard code the IP of the server). Test Plan: Deploy this and the openqa_fedora_tools commit, generate the disks, configure the networking (good luck! See the docs in openqa_fedora_tools) and see if you can run the tests. If you're using Docker, uh...sorry. You somehow need to set things up so the workers can use tap interfaces that can talk to each other and are NATed to the outside world. Have fun. I can talk you through it on IRC... Reviewers: jskladan, garretraziel Reviewed By: garretraziel Subscribers: tflink Differential Revision: https://phab.qadevel.cloud.fedoraproject.org/D831
17 lines
301 B
JSON
17 lines
301 B
JSON
{
|
|
"area": [
|
|
{
|
|
"height": 30,
|
|
"type": "match",
|
|
"width": 56,
|
|
"xpos": 72,
|
|
"ypos": 49
|
|
}
|
|
],
|
|
"properties": [],
|
|
"tags": [
|
|
"text_console_login",
|
|
"ENV-DISTRI-fedora",
|
|
"ENV-FLAVOR-develop"
|
|
]
|
|
} |