[tools][hard][pvm] Enable the powerVM backend to conduct multimachine tests
In poo#21838 the need for multimachine tests on PowerVM was mentioned.
To cite coolo on what needs to be done:
I don't think there is inherit problem - but you would need to undo a lot of qemu specific hardcoding. But you can create vlans for the lpars and then have PARALLEL_WITH 2 lpars.
AC1: Multimachine tests can run on PowerVM
AC1.1: Implement vland handling for LPARs
AC1.2: Find all qemu hardcodings and adapt the backend to do MM tests on other backends
Configure vlans between the lpars and treat them as machines in the network with a proper worker class (see coolo's comment)
#4 Updated by coolo over 2 years ago
- Project changed from openQA Project to openQA Tests
- Subject changed from [tools][functional][hard][pvm] Enable the powerVM backend to conduct multimachine tests to [functional][hard][pvm] Enable the powerVM backend to conduct multimachine tests
- Category deleted (
I claim we don't do anything about it - and handle powervm lpars just like phyiscal machines in our network. They are there and if they can be used for MM tests is defined by worker class. If the admins setup a proper vlan or not is up to the tests writers.
- Project changed from openQA Tests to openQA Project
- Subject changed from [functional][u][hard][pvm] Enable the powerVM backend to conduct multimachine tests to [tools][hard][pvm] Enable the powerVM backend to conduct multimachine tests
- Category changed from New test to Feature requests
I think this belongs more in the openQA project
szarate I missed that you assigned this ticket to "[tools]" as you kept slindomansilla as assignee. IMHO the comment from #33697#note-4 is still valid and there are no plans by the QA tools team to do more implementation about this. However considering that our powerVM backends can be treated just the same as bare metal IMHO we have a solution already: Tests can be triggered in parallel with no problem and synchronization primitives can be used. As the network can not be fully virtual of course then the network admin needs to ensure according separation where needed. What we can do is maybe mention this explicitly in documentation.
- Status changed from New to Feedback
- Assignee changed from SLindoMansilla to okurz
Trying to clarify in documentation what can be done / needs to be done: https://github.com/os-autoinst/openQA/pull/3256
It's not that much though but I consider it's what we can do, the rest is for test maintainers to show what's possible and tell the network admin what's missing :)