Seems lava-dispatcher online now, some blueprints change from lava to lava-dispatcher, https://blueprints.launchpad.net/lava-dispatcher/+spec/linaro-platforms-o-la..., also lava-server and lava-scheduler.
On 24 May 2011 12:02, Michael Hudson-Doyle michael.hudson@linaro.orgwrote:
On Thu, 19 May 2011 17:05:09 +1200, Michael Hudson-Doyle < michael.hudson@linaro.org> wrote:
Hi there,
Some of you know about this already as it was discussed a bit at LDS, but probably not very inclusively.
We have a slightly strange arrangement of projects on Launchpad, with the main ones being "launch-control" and "lava". AIUI, Zygmunt really wanted to call "launch-control" "dashboard" from day 1, but that was clearly an overly generic name. Since then, we've come up with the "lava" name to cover our automated validation efforts, but currently the "lava" project just contains code to do with the validation farm in Cambridge, which is only part of the story.
So. We have a plan to reorganize the projects like so (also documented
on
https://blueprints.launchpad.net/linaro-validation-misc/+spec/linaro-platfor... ):
I've started to do this now, and have mostly split launch-control into lava-server and lava-dashboard. It's been a bit complicated, to be honest, but I think it sort of works now. If you create a virtualenv, get both lp:lava-server and lp:lava-dashboard and run "$VIRTUALENV/bin/python setup.py develop" in both, then "$VIRTUALENV/bin/python lava_server/manage.py runserver" in the lp:lava-server checkout, you should be able to browse around to some extent. Some things that are clearly lacking: the dashboard has no front page now, and we need to work on the bread crumbs a bit, but I think it basically works.
I'll try to catch Zygmunt tonight and see what needs to be done to finish the launch-control split, and work on splitting up what's in lp:lava tomorrow.
Cheers, mwh