action #3136: support remote workers
upload_logs needs to map openqa.suse.de only on local hosts
upload_logs does a pretty nasty trick to map $OPENQA_HOSTNAME within the VM to a local IP. this only works if the worker runs locally. I guess we should be able to get away without this mapping
#2 Updated by coolo almost 8 years ago
BS workers have no network at all - and I think it's pretty boring to test functionality without network. But the problem here is that we try to work around DNS and that fails, so requiring DNS is ok. The problem is that it needs to work within VM - even at times when network setup failed. That was the idea behind it.
#3 Updated by oholecek almost 8 years ago
Apart cgi-proxy or tiny http server ideas, what about using libguestfs?
e.g. standardize that all logs should end up in /var/tmp/openqa/logs (in the VM). Then, after tests finish, they are moved to testresults directory on worker directly from VM disk (e.g. by using guestfs).
#4 Updated by coolo almost 8 years ago
this only works for cases where yast already installed. And you need to know a lot about the disk setup the test did - i.e. RAID,LVM,cryptlvm, ...
I think our easiest solution still is relying on DNS - and only if we get a real problem with it switch back to localhost and proxying.
#6 Updated by coolo almost 8 years ago
- Assignee set to coolo
so I had a chat with Bernhard about it and we came to the conclusion that having the uploadlogs in openqa is not necessary. So to also make os-autoinst more self contained I'll implement a HTTP interface in os-autoinst (reusing issue #1308) to store the logs in the pool and the worker can then copy it together with the rest.
#7 Updated by coolo almost 8 years ago
https://github.com/os-autoinst/os-autoinst/pull/123 is the result - openQA worker will need to move back the uploaded logs from pool dir