On 19 May 2011, at 08:08, Alexander Sack wrote:
On Thu, May 19, 2011 at 7:05 AM, 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...):
- lava -- project group containing:
- lava-server -- contains the django settings file and templates
- this well mostly be extracted from what is lp:launch-control today
- lava-scheduler -- django application for scheduling jobs
- what exists for this is in lp:lava currently
- lava-dispatcher -- tool that runs tests on hardware
- this is also in lp:lava currently
- lava-dashboard -- django application for showing test results
- this is lp:launch-control currently
- lava-tool -- command line entry point and framework
- this actually exists already and has the right name!
- lava-dashboard-tool
- new name for launch-control-tool
- lava-test-tool -- plugin for lava-tool that adds commands for running tests
- new name and refactoring for abrek
Thanks for tackling this. I am positive on almost all the suggested names here ...
Does this mean that we want to rename abrek to "lava-test-tool"? Paul, what does abrek stand for?
--
- Alexander
I wholeheartedly agree with the changes. Makes things much clearer, and abrek was always an ugly name. :)
Thanks
Dave