Mailinglist Archive: opensuse-buildservice (247 mails)

< Previous Next >
Re: [opensuse-buildservice] Proposal for api /build/_workerstatus change
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"/>
</workerstatus





With multiple binary backends you get

<scheduler arch="backend1:x86_64" ...
<scheduler arch="backend1:warden" ...



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/> ?

Greetings, Stephan

--
Bit off more than my mind could chew,
Shower or suicide, what do I do?
-- Julie Brown, "Will I Make it Through the Eighties?"
--
To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@xxxxxxxxxxxx
To contact the owner, e-mail: opensuse-buildservice+owner@xxxxxxxxxxxx

< Previous Next >
Follow Ups
References