Am Mittwoch, 5. Juni 2013, 15:48:14 schrieb Stephan Kulow:
On 05.06.2013 15:30, Adrian Schröter wrote:
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"/>
With multiple binary backends you get
I like to change this xml to following structure to solve the following issues * no different meanings of arch= attribute * no need in clients to find the right backend groups (called sibiling)
I only have a small problem with the word sibling in this context. It sounds confusing that you call a group of schedulers one sibling when it's actually a group of things. One sibling is an individual - why not use the name you already used in your text: <backend/> ?
Well, the backend is using the word "sibling" in it's config currently. However, this is git master code, nothing is in stone yet. But calling something "backend" on the "backend" does not sound too wise either... -- 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