action #115418
closedSetup ow19+20 to be able to run MM tests size:M
100%
Description
Acceptance criteria¶
- AC1: ow19+20 are capable (and configured by adding the "tap" worker class) to run MM tests
- AC2: GRE tunnels are configured to allow traffic between ow19+20 and existing MM workers ow1+4+7
Suggestions¶
- Come up with a scripted solution as touching configuration files manually on now 5 workers (ow19+20 and existing ow1+4+7) would be come quite tedious.
- Our salt states already show how especially the creation of the GRE tunnel config (
/etc/wicked/scripts/gre_tunnel_preup.sh) can be automated using a jinja template. However, we'd preferably stay independent of using the salt machinery here. - Writing a simple script that logs into all relevant worker hosts and runs the appropriate commands should be quite simple. Note that when using Perl we could also utilize the Mojolicious template system for generating files. (It can easily be used outside of the context of a web application, see this example.)
- Our salt states already show how especially the creation of the GRE tunnel config (
- As a general reference, look into documentation on https://open.qa/docs/#_tap_based_network and our salt states and what has already been configured on ow1+4+7.
- There's also one section in particular that explains cloning test jobs: https://open.qa/docs/#_verify_the_setup
Updated by mkittler over 1 year ago
- Related to action #111473: Get replacements for imagetester and openqaworker1 size:M added
Updated by livdywan over 1 year ago
- Subject changed from Setup ow19+20 to be able to run MM tests to Setup ow19+20 to be able to run MM tests size:M
- Status changed from New to Workable
Updated by livdywan over 1 year ago
- Related to action #115547: openqaworker20 fails to boot, broken hardware size:M added
Updated by mkittler over 1 year ago
Note that ow20 is currently broken, see #115547. So I'd exclude it for now from this ticket.
Updated by livdywan over 1 year ago
Note: This ticket is not blocked. ow19 can be configured for this.
Updated by livdywan over 1 year ago
- Seems like we used to have this in worker.sls but it was turned into a comment because somebody disliked wicked.
- https://github.com/os-autoinst/os-autoinst-distri-opensuse/blob/cae6400303ef59c58de143fbaf3050bf5e22457e/lib/wickedbase.pm
- https://github.com/os-autoinst/salt-states-openqa/blob/master/openqa/openvswitch.sls
- Take steps/ commands from https://open.qa/docs/#_tap_based_network to be scripted
- Add a script to https://github.com/os-autoinst/scripts
However, we'd preferably stay independent of using the salt machinery here.I think is supposed to say we can't use salt since these are o3 workers 😛️ We were initially assuming this was supposed to be used on osd because of that misleading phrasing.- Taking what's documented and comparing with what's already setup on ow1 into a script: https://github.com/os-autoinst/scripts/pull/190
Updated by livdywan over 1 year ago
- Status changed from Workable to Feedback
- Assignee set to livdywan
We got as far as verifying that the generated configuration looks sensible. Whether this setup works properly still needs to be confirmed with actual jobs; and no change to work classes was made for now.
Updated by favogt over 1 year ago
cdywan wrote:
We got as far as verifying that the generated configuration looks sensible. Whether this setup works properly still needs to be confirmed with actual jobs; and no change to work classes was made for now.
Did you also configure the GRE tunnel so that all workers can reach each other?
Updated by livdywan over 1 year ago
favogt wrote:
cdywan wrote:
We got as far as verifying that the generated configuration looks sensible. Whether this setup works properly still needs to be confirmed with actual jobs; and no change to work classes was made for now.
Did you also configure the GRE tunnel so that all workers can reach each other?
It's all in the script. If the script does it the answer is yes 😉️
Updated by livdywan over 1 year ago
Seems like @okurz was also working on a script to do the same thing: #119008#note-17
Updated by livdywan over 1 year ago
I'll pick it up again. I had left this on the side due to other infra tickets but it seems fine to continue now.
Updated by favogt over 1 year ago
- Assignee changed from livdywan to favogt
During setup of ow20 (https://progress.opensuse.org/issues/115547?issue_count=145&issue_position=29&next_issue_id=115418&prev_issue_id=115763#note-41) I tried to copy the config from ow19 but found that the tap/ovs parts were incomplete/broken. After setting it up for ow20 I completed/fixed the ow19 setup as well:
- eth0 was in
publicinstead oftrusted /etc/wicked/scripts/gre_tunnel_preup.shwas broken, I fixed and reranopenqa-prepare-mm-setup- Added ow19 and ow20 to the
gre_tunnel_preup.shscript on ow1, ow4 and ow7
firewalld-policy-* passed: https://openqa.opensuse.org/tests/2929273#dependencies
I'll do some more tests tomorrow and if they look good I'll add the tap class to both.
Updated by favogt over 1 year ago
- Status changed from Feedback to Resolved
- % Done changed from 0 to 100
I'll do some more tests tomorrow and if they look good I'll add the tap class to both.
I did it the other way around: Add the tap class and see what happens. So far no issues observed.
Updated by okurz over 1 year ago
- Related to action #121771: openqaworker20 has no heartbeat added
Updated by okurz over 1 year ago
- Related to action #121789: MultiMachine tests lose ability to communicate added
Updated by okurz 9 months ago
- Related to action #133025: Configure Virtual Interfaces instructions do not work on Leap 15.5 size:M added