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

I thought Abrek was a monkey? If we're talking Soviet space program animals anyway. :)

Dave

On 19 May 2011, at 08:52, Zygmunt Bazyli Krynicki wrote:

...

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?

It's the name of certain space-faring dog.

Best regards ZK

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

Any good suggestions for a new name for abrek? I don't want to encourage bike shedding on this, so unless someone has a much better suggestion, I would suggest we just go with lava-test (skip the -tool) and be done with it.

Thanks, Paul Larson On May 31, 2011 7:55 PM, "Michael Hudson-Doyle" michael.hudson@linaro.org wrote:

On Tue, 31 May 2011 13:42:56 +0800, Spring Zhang spring.zhang@linaro.org

wrote:

...

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.

Ah yes, I should have followed up on this thread when I made the changes. So far:

• lava was renamed to lava-dispatcher
• lava-scheduler was created, but is only a skeleton
• launch-control was renamed to lava-dashboard, but there is a redirect

in place

• launch-control-tool was renamed to lava-dashboard-tool (with redirect)
• lava was created as a new project group, and all the above projects

added to it.

I haven't renamed abrek yet.

Cheers, mwh

On 1 Jun 2011, at 08:59, Zygmunt Krynicki wrote:

W dniu 01.06.2011 09:56, Paul Larson pisze:

...

Any good suggestions for a new name for abrek? I don't want to encourage bike shedding on this, so unless someone has a much better suggestion, I would suggest we just go with lava-test (skip the -tool) and be done with it.

I like lava-test (despite not following foo-tool)

ZK

Gets my vote too.

Dave