Michael Hudson-Doyle <[email protected]> writes:
> Kevin Hilman <[email protected]> writes:
>
>> Hi LAVA folks,
>>
>> I'm working on using LAVA to boot boards in my own board farm, and for
>> starters, am trying to use a job without a 'deploy' step (so I can use
>> the existing on-board u-boot, and control it via boot_cmds.)
>>
>> Currently, the dispatcher assumes that a 'deploy' step has happened
>> before a 'boot_linaro_image' step, which is not needed for my case, so
>> here's a patch to set some defaults so a deploy step is not needed:
>
> FWIW, there is a dummy_deploy action for this use case:
>
> "actions": [
> {
> "command": "dummy_deploy",
> "parameters": {
> "type": "ubuntu"
> }
> },
> {
> "command": "boot_linaro_image"
> }
> ]
Thanks for the pointer, but this doesn't work either.
While dummy_deploy may be dumb, it's not dumb enough. It still wants to
(re)boot into a master image (which I don't wan't.)
What I need is this:
=== modified file 'lava_dispatcher/actions/deploy.py'
--- lava_dispatcher/actions/deploy.py 2013-04-17 08:23:50 +0000
+++ lava_dispatcher/actions/deploy.py 2013-05-03 20:30:01 +0000
@@ -106,3 +106,22 @@
device = self.client.target_device
device.boot_master_image()
device.deployment_data = device.target_map[type]
+
+class cmd_I_mean_really_dumb_dummy_deploy(BaseAction):
+
+ parameters_schema = {
+ 'type': 'object',
+ 'properties': {
+ 'type': {'type': 'string', 'enum':['ubuntu', 'oe', 'android',
'fedora']},
+ },
+ 'additionalProperties': False,
+ }
+
+ def run(self, type):
+ device = self.client.target_device
+ device.deployment_data = device.target_map[type]
+
+ # KJH
+ device.deployment_data['TESTER_PS1_PATTERN'] = '# '
+ device.deployment_data['TESTER_PS1_INCLUDES_RC'] = False
+
_______________________________________________
linaro-validation mailing list
[email protected]
http://lists.linaro.org/mailman/listinfo/linaro-validation
