Hi, current git master code allows to have multiple binary backends with it's own set of schedulers. This has an effect in the status reporting. With only one backend the interface stays like it is currently on api.opensuse.org osc api /build/_workerstatus <workerstatus> .... <waiting arch="x86_64" jobs="381"/> ... <blocked arch="x86_64" jobs="20173"/> ... <buildavg arch="armv5el" buildavg="114238.589179981"/> .... <scheduler arch="x86_64" state="running" starttime="1370304869"> <queue high="0" med="461" low="1439" next="16401"/> </scheduler> ... <scheduler arch="warden" state="running" starttime="1370304793"/> <sibling name="backend1"> <daemon type="scheduler" arch="x86_64" state="running" starttime="1370304869"> <queue high="0" med="461" low="1439" next="16401"/> </daemon> <daemon type="warden" state="running" starttime="1370304793"/> .... </sibling> <sibling name="backend2"> ... </sibling> </workerstatus> That means that old clients may not show data anymore, but they should not crash since all lines were optional anyway (no scheduler or dispatcher may run also in the past) any opinions on that? -- Adrian Schroeter email: adrian@suse.de SUSE LINUX GmbH, GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer, HRB 21284 (AG Nürnberg) Maxfeldstraße 5 90409 Nürnberg Germany -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner@opensuse.org