Hi everyone, I'm trying to add own device-type to my lab, but I'm facing some difficulties when running jobs. I have the following log error:
I clearly understand the log but I'm not able to figure out what to do: I thought it will be enough describing boot/power actions into device-type. But it seems not... Do I need to create a .conf file into /usr/lib/python2.7/dist-packages/lava_dispatcher/default-config/lava-dispatcher/device-types folder ?
By the way I'm not sure to understand the .conf purpose ? Are they here, only to be some default files ?
I attached my device-type and my job, maybe it will help you !
Thanks a lot ;)
P.S: I already did some jobs on Qemu and bbb and read the whole documentation.
On 19 July 2017 at 10:27, Benjamin Auclair benjamin.auclair@devialet.com wrote:
Hi everyone, I'm trying to add own device-type to my lab, but I'm facing some difficulties when running jobs. I have the following log error:
This means that the dispatcher was unable to understand the device configuration - you've missed out some values which are needed to allow the dispatcher to build the pipeline of actions. In this case, in the deploy block.
Debugging this is not easy but is part of the device integration process. You may need to dig into the accepts functions of the Strategy classes in lava-dispatcher and work out which check is failing. (We are looking at how to make this easier but the process also has to be very fast, so it needs manual debugging at the moment.)
I clearly understand the log but I'm not able to figure out what to do: I thought it will be enough describing boot/power actions into device-type. But it seems not... Do I need to create a .conf file into /usr/lib/python2.7/dist-packages/lava_dispatcher/default-config/lava-dispatcher/device-types folder ?
No. that is for V1 configuration only. You are using V2, so all device configuration is on the server.
By the way I'm not sure to understand the .conf purpose ? Are they here, only to be some default files ?
These files only relate to V1 which is due for removal later this year.
I attached my device-type and my job, maybe it will help you !
Thanks a lot ;)
P.S: I already did some jobs on Qemu and bbb and read the whole documentation.
We're extending the device integration documentation at the moment - you may find this new content useful:
https://review.linaro.org/#/c/20604/
Probably the best thing to do is follow that new guidance to create a unit test in lava-server which you can run to ensure that the values you expect to be in the device configuration are being correctly created by the new template.
Thanks a lot for your quick answer !
This means that the dispatcher was unable to understand the device configuration - you've missed out some values which are needed to allow the dispatcher to build the pipeline of actions. In this case, in the deploy block.
Debugging this is not easy but is part of the device integration process. You may need to dig into the accepts functions of the Strategy classes in lava-dispatcher and work out which check is failing. (We are looking at how to make this easier but the process also has to be very fast, so it needs manual debugging at the moment.)
Okay now I know where to find it, I will dig into the source code !
We're extending the device integration documentation at the moment - you may find this new content useful:
https://review.linaro.org/#/c/20604/
Probably the best thing to do is follow that new guidance to create a unit test in lava-server which you can run to ensure that the values you expect to be in the device configuration are being correctly created by the new template.
Okay will look at this !
2017-07-19 11:37 GMT+02:00 Neil Williams neil.williams@linaro.org:
On 19 July 2017 at 10:27, Benjamin Auclair benjamin.auclair@devialet.com wrote:
Hi everyone, I'm trying to add own device-type to my lab, but I'm facing some difficulties when running jobs. I have the following log error:
This means that the dispatcher was unable to understand the device configuration - you've missed out some values which are needed to allow the dispatcher to build the pipeline of actions. In this case, in the deploy block.
Debugging this is not easy but is part of the device integration process. You may need to dig into the accepts functions of the Strategy classes in lava-dispatcher and work out which check is failing. (We are looking at how to make this easier but the process also has to be very fast, so it needs manual debugging at the moment.)
I clearly understand the log but I'm not able to figure out what to do: I thought it will be enough describing boot/power actions into device-type. But it seems not... Do I need to create a .conf file into /usr/lib/python2.7/dist-packages/lava_dispatcher/default-config/lava-
dispatcher/device-types
folder ?
No. that is for V1 configuration only. You are using V2, so all device configuration is on the server.
By the way I'm not sure to understand the .conf purpose ? Are they here, only to be some default files ?
These files only relate to V1 which is due for removal later this year.
I attached my device-type and my job, maybe it will help you !
Thanks a lot ;)
P.S: I already did some jobs on Qemu and bbb and read the whole documentation.
We're extending the device integration documentation at the moment - you may find this new content useful:
https://review.linaro.org/#/c/20604/
Probably the best thing to do is follow that new guidance to create a unit test in lava-server which you can run to ensure that the values you expect to be in the device configuration are being correctly created by the new template.
--
Neil Williams
neil.williams@linaro.org http://www.linux.codehelp.co.uk/
lava-users@lists.lavasoftware.org
-
Benjamin Auclair -
Neil Williams