QA » openQA Project

results from slepos team discussion:

• one (virtual) machine per worker (we could use remote workers on different archs)
• synchronization via openQA scheduler
• implement synchronization primitives in scheduler and API to access them
• network configuration daemon
• communicate with scheduler, which is the only part having the complete information
• investigate cloud solutions
• individual machine tests defined in separate modules (e.g boot_worker1.pm, consoletest_worker2.pm)
• scheduler set different ENV variables for different workers, e.g. worker 1 will have WORKER=1, worker 2 will have WORKER=2
• distinguished in is_applicable hook of individual modules
• job specification using job variables e.g. JOB_WORKERS=n
• individual hw requirements in same way e.g. WORKER_1_CPU, WORKER_2_MEM, etc.

Full discussion here:
https://etherpad.nue.suse.com/p/NCC-1701-openQA