I think the obvious concern for me here is that now we would be proposing to require a growing stack of web components, django, etc in order to just get a cli tool to submit a job. That seems like quite a lot of overhead for such a simple thing. I'm a little surprised you wouldn't rather group all the cli tools together. Also, from the BP summary, it's not clear to me what the benefit is that you are trying to achieve. On Mar 26, 2012 1:07 PM, "Zygmunt Krynicki" zygmunt.krynicki@linaro.org wrote:
Hi.
This time a small blueprint that can be easily done in one or two days. I think that, if successful, we could apply this pattern to other tools to cut down the number of parts we need to release.
(offtopic) If successful I'd like to schedule the following merges:
lava-dashboard-tool + lava-dashboard -> lava-dashboard lava-scheduler-tool + lava-scheduler -> lava-scheduler lava-server + lava-tool -> lava-core
The last part would define the core dependency of any lava component. This may be a good idea or a bad idea, depending on how you think about it. Feel free to think about it and comment but please keep the separation of concerns so that this (dashboard focused) blueprint can be considered without runaway discussion. (ontopic)
The blueprint is on the lava-dashboard-tool project. Please comment here on the mailing list.
https://blueprints.launchpad.net/lava-dashboard-tool/+spec/lava-dashboard-to...
Thanks ZK -- Zygmunt Krynicki Linaro Validation Team
linaro-validation mailing list linaro-validation@lists.linaro.org http://lists.linaro.org/mailman/listinfo/linaro-validation