Marco Mornati wrote:
Anyway... here a little mod to func-transmit to make a call for
getting result for provided job
if method=="list_minions":
[...]
elif method == "job_results":
server_spec = "*"
overlord = fc.Overlord(server_spec)
(return_code, async_results) =
overlord.job_status(params.get('parameters'))
results = {}
results[return_code] = async_results
else:
[...]
What you receive is a dictionary with
process_status: [machine: result], [machine: result]
Is not so a brilliant result... but you can read in a bit if there are
machines in error or not...
Could be useful?
Bye
Marco
This needs to be submitted using "git-format-patch/git-send-email" in
order to take it. Right now this is not in patch format.
Why would "results" not just be "async_results" but has the extra hash
key in there? I'd remove that.
Also it should be "job_status" to match the overlord API call.
--Michael
Marco Mornati wrote:
Hi guys,
I'm making some improvements to Func-Java bindings and I'm having
some "async problems".
If I call in async mode func-transmit, I received, as expected, the
process ID of launched process... but, by now, I'm not able to call
func-transmit, to get the process result (func '*' --job-status PID).
Do you think could be useful to call func-transmit also for get the
result of a previous call? The only reason why I prefer to have
something in func-transmit is to get result in a "standard way"
inside the bindings api (in this case YAML)... if I call func I
receive a simple String as result.
Bye
Marco
_______________________________________________
Func-list mailing list
Func-list@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/func-list
