AC 3 of parent task:
worker_bridge will report back job results to the masterUI job results once the job on the slaveUI has any new status to report (once job is set to done, regadless of the state)
This should be done in an independant manner, so that poo#14580 can be addressed too.
#8 Updated by szarate about 2 years ago
- Subject changed from [tools][Sprint 201711.2] Allow the worker_bridge to sync job status from a slaveUI to a masterUI to Allow the worker_bridge to sync job status from a slaveUI to a masterUI
- Assignee deleted (
The idea for the implementation of this was:
Have the slaveUI check for jobs with FEDERATED_URL != '' that don't have a backend_info field in the databse with something like "already_updated". (That field is supposed to be not currently used, but can be used to store json information for example.). This is/would be for the startup of the worker.
For the normal execution of the worker, the bridge would simply monitor for job_done event, and the same condition of FEDERATED_URL not being empty and backend_info property being not set, then simply add the job to a queue (possibly a minion job?) and start the upload. Once job is sucessfully uploaded to the remoteUI, "already_updated" property would be set.
Jobs being restarted, is still unclear, but for the time being they simply refresh on the remote UI.