On Mon, 30 May 2011 21:43:10 +0200, Zygmunt Krynicki zygmunt.krynicki@linaro.org wrote:

Hi

I finally made lava-dashboard run on lava-server. The relevant code is in lp:lava-server (trunk) and in lp:~zkrynicki/lava-dashboard/zyga (merge request). Feel free to look at the request to see if I did some accidental edits (bzr commit --interactive does not work for me on bzr 2.4 :-(

It seems mostly sane, although the diff in the merge proposal is basically useless.

The next step is to make development smooth by packaging prerequisites (a few new packages are needed both in debian and pypi) and sorting out setup-dev-env.sh

Yeah, I've just hacked my way through what the dashboard for setup-dev-env.sh (using a virtualenv) and ... it's a bit messy. We need to change lava-server to install its manage.py somewhere.

I'm considering rewriting setup-dev-env.sh to be .py file that calls into extensions to set themselves up properly but it may be non-trivial. I'll see how it will work, if you have any suggestions feel free to say so.

I dunno, I think it make make sense to have each project (lava-dashboard, lava-scheduler) have something like setup-dev-env.sh.

If nothing breaks tomorrow I'll release lava-server 0.1 and lava-dashboard 0.5 and start 11.06 cycle. Initial stories plus a few tasks are listed here: http://fracture.suxx.pl/rb/taskboards/12 I'll be adding more items to that as I sort out priorities with plars this evening.

Awesome.

Michael: when can we expect the shuffle of launchpad projects? Are we staying with lava-server and lava-dashboard and abandoning launch-control?

I've shuffled things around between launch-control and lava-dashboard just now, and pushed your lava-server-using branch to lp:lava-dashboard.

I've also renamed lava to lava-dispatcher (although it still contains some stuff related to the scheduler), launch-control-tool to lava-dashboard-tool, created lava as a project group and made the various lava projects part of the new project group.

Cheers, mwh