QA » openQA Project

That is true, set_var does not sync variables back to openQA and I don't think we want it to. I see the variables in web ui as a job starting point (for reproducibility) and not the final state.

if you need the machines to talk to each other - you better make that 1:1. There are enough tools to have 2 machines talking to each other

but we can also add one within os-autoinst to tell PARALLEL_WITH jobs the os-autoinst URL of the other childrens and have a query_variables call into it.

coolo wrote:

if you need the machines to talk to each other - you better make that 1:1. There are enough tools to have 2 machines talking to each other

Yes , I understand there are ways to make 2 host talking to each other.

The difficult part to the multi-machine parallel job is :
you can not know which host is assign as parent, which host is asseng as child .

(correct me if i miss something)

There are at least these options:

• you can use fixed set of IPs, assigned via variables

• if you use DNS/DHCP on support server, the hostname included in DHCP requests is propagated to DNS and becomes resolvable on other hosts

Is there any reason why these options do not fit?

because the initial request omited one small detail: this is not testing in VMs, but using real hardware in real networks with real DHCP servers. And we don't want to hard code upfront which machine gets which role in the test.

yes , as coolo said , it's not running on virtualization machine in a isolate ENV.
For phy-machine : we may not have the permission to change the DHCP server.
we may not have the permission to modify the /etc/openq/openqa-worker.ini file

Currently , the workaround is blocked by https://progress.opensuse.org/issues/13972

Beside fixed this issue , as above comment , we still need modify the /etc/openqa/worker.ini to distinguish ipmi worker each other.

looks the set_var and save_var() work correctly sync the variable to the vars.json.

but still can NOT get the update setting from get_job_info($job_id) function in child job.

get_job_info($job_id) still queries the openqa server so it can be used only for the initial variables.

Use get_job_autoinst_vars($job_id) instead (not sure if it is already deployed).