dependencies between actions in the dispatcher

[yong qin]

>
> 1) Change submit results to not be an action.

2) Add a result_locations list and action_data dictionary to
>   LavaContext.  My half-thought through idea is that actions will use
>   the action name as a prefix, e.g. deploy_linaro_image for a qemu
>   client might set 'deploy_linaro_image.qemu_img_path' in this dict.
> 3) Change the lava-test and lava-android-test to store into
>   result_locations and the submit step to read from there.
> 4) Use action data to have deploy_linaro_image and boot_linaro_image
>   (and maybe lava_test_install and lava_test_run) talk to each other.
>
> about the action, from the point used by lava(lava-server,lava-dashboard,
lava-scheduler),
some actions are not necessary to specified, or to say they are certainly
executed. like:
1. submit results
     if no results submitted, the test will no meaning.
2. deploy and boot the test target
    if not deploy and boot, then no target to test.
3. the installation of various test.
    if the test is not installed, we can install it before run.

They can be or should be execute implicitly I think.

Thanks,
Yongqin Liu
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.linaro.org/pipermail/linaro-dev/attachments/20111111/f5b90ff7/attachment.html>