Hi.
I've registered a new blueprint about a new proposed component. Please read the blueprint and comment here on the mailing list. My goal is to put planning for that in this cycle and perhaps one small blueprint that would implement some of the code behind that.
You can find the blueprint on the new project page:
https://blueprints.launchpad.net/lava-device-manager/+spec/lava-device-manag...
Thanks ZK
On Mon, 26 Mar 2012 18:05:55 +0200, Zygmunt Krynicki zygmunt.krynicki@linaro.org wrote:
Hi.
I've registered a new blueprint about a new proposed component. Please read the blueprint and comment here on the mailing list. My goal is to put planning for that in this cycle and perhaps one small blueprint that would implement some of the code behind that.
You can find the blueprint on the new project page:
https://blueprints.launchpad.net/lava-device-manager/+spec/lava-device-manag...
This triggers my "yikes, lots of complexity, lots of work, run away" instincts, I'm afraid. It also makes me think of http://xkcd.com/927/ after s/standard/service/.
I guess I just don't see the work invovled in adding devices to LAVA to be a particular burden _for us_ currently. I know that it is a problem for people trying to deploy LAVA for themselves, but I think we have other problems we should solve even for external users before this one (like better test result display, for example).
Cheers, mwh
linaro-validation@lists.linaro.org