Re: Please review blueprint linaro-n-validation-job-dispatcher

2011-02-17 Thread Paul Larson
Right now, it uses a headless image and has some, but not too much room for additional things to be installed. There is a possibility that we may, at some point, want to implement this master image in flas though. If that happens, it would likely be something like initramfs/busybox. For now, it i

Re: Please review blueprint linaro-n-validation-job-dispatcher

2011-02-17 Thread Zygmunt Krynicki
On 02/17/2011 11:28 AM, Spring Zhang wrote: Hi, Paul, For the python environment in the deployed test image, how much support will it provide? Can we deploy additional python libs to the test image if required? Dispatcher client part may need some. What dependencies are you thinking of? IMHO

Re: Please review blueprint linaro-n-validation-job-dispatcher

2011-02-17 Thread Spring Zhang
Hi, Paul, For the python environment in the deployed test image, how much support will it provide? Can we deploy additional python libs to the test image if required? Dispatcher client part may need some. -- Best wishes, Spring Zhang ___ linaro-dev mai

Re: Please review blueprint linaro-n-validation-job-dispatcher

2011-02-15 Thread Paul Larson
On Tue, Feb 15, 2011 at 10:23 AM, Mirsad Vojnikovic < mirsad.vojniko...@linaro.org> wrote: > ... > I think this looks good. Is this the JSON file definition we will use > initially? Asking this because the corresponding Dispatcher WI is set to > done "[qzhang] Define the job description both on di

Re: Please review blueprint linaro-n-validation-job-dispatcher

2011-02-15 Thread Mirsad Vojnikovic
On 9 February 2011 20:12, Paul Larson wrote: > On Mon, Jan 31, 2011 at 11:58 AM, Paul Larson wrote: > >> 2. One queue TOTAL. One queue may seem like a bottleneck, but I don't think it has to be in practice. One process can monitor that queue, then launch a process or thread to handle

Re: Please review blueprint linaro-n-validation-job-dispatcher

2011-02-15 Thread Paul Larson
On Tue, Feb 15, 2011 at 5:39 AM, Spring Zhang wrote: > > > On 28 January 2011 08:12, Paul Larson wrote: > >> Other questions... >> >> >> >> What does it do after running the test? How, and where does it leave the >> results? What get's added to the results (e.g. serial log) and how does >> that

Re: Please review blueprint linaro-n-validation-job-dispatcher

2011-02-15 Thread Spring Zhang
On 28 January 2011 08:12, Paul Larson wrote: > Other questions... > > > What does it do after running the test? How, and where does it leave the > results? What get's added to the results (e.g. serial log) and how does > that happen? What is the mechanism for then taking that bundle and pushin

Re: Please review blueprint linaro-n-validation-job-dispatcher

2011-02-14 Thread Paul Larson
On Mon, Feb 14, 2011 at 5:58 AM, Mirsad Vojnikovic < mirsad.vojniko...@linaro.org> wrote: > > I have a question regarding test job json file and messages from Scheduler > to Dispatcher: is this file created by Scheduler and put in the message > queue where Dispatcher will fetch it from, or how sho

Re: Please review blueprint linaro-n-validation-job-dispatcher

2011-02-14 Thread Mirsad Vojnikovic
On 9 February 2011 20:12, Paul Larson wrote: > On Mon, Jan 31, 2011 at 11:58 AM, Paul Larson wrote: > >> 2. One queue TOTAL. One queue may seem like a bottleneck, but I don't think it has to be in practice. One process can monitor that queue, then launch a process or thread to handle

Re: Please review blueprint linaro-n-validation-job-dispatcher

2011-02-09 Thread Paul Larson
On Mon, Jan 31, 2011 at 11:58 AM, Paul Larson wrote: > 2. One queue TOTAL. One queue may seem like a bottleneck, but I don't >>> think it has to be in practice. One process can monitor that queue, then >>> launch a process or thread to handle each new job that comes in. >>> >> I think RabbitMQ m

Re: linaro-n-validation-job-dispatcher

2011-02-02 Thread Paul Larson
Moving this thread to the linaro-dev mailing list because I'd like it to be public discussion, and specifically to involve Rob since we talked about his interest in getting involved with LAVA development and especially the job dispatcher. 2. One queue TOTAL. One queue may seem like a bottleneck, b