Hi,
Is there a way to specify an arbitrary parameter, that is board specific, in device dictionary? The parameter should be available from test shell. The use case is as follows: DUT is connected to test supporting hardware (chamelium board in this case). Tests access supporting hardware using IP address. IP address is 'static' and the supporting hw is assumed to be always turned on. Supporting hardware is dedicated to specific DUT and can't be shared (because of HW connections) between other boards of the same type (similar to energy probes). Tests run directly on DUT and access supporting hardware from there.
I found 'exported parameters' in device dictionary docs: https://master.lavasoftware.org/static/docs/v2/lava-scheduler-device-diction.... But they only list device_ip, device_mac and storage_info. Is there a way to extend this list? If not, is there any other way to provide device specific information to test shells?
milosz
On Sun, 10 Feb 2019 at 16:17, Milosz Wasilewski milosz.wasilewski@linaro.org wrote:
Hi,
Is there a way to specify an arbitrary parameter, that is board specific, in device dictionary? The parameter should be available from test shell. The use case is as follows: DUT is connected to test supporting hardware (chamelium board in this case). Tests access supporting hardware using IP address. IP address is 'static' and the supporting hw is assumed to be always turned on. Supporting hardware is dedicated to specific DUT and can't be shared (because of HW connections) between other boards of the same type (similar to energy probes). Tests run directly on DUT and access supporting hardware from there.
I found 'exported parameters' in device dictionary docs: https://master.lavasoftware.org/static/docs/v2/lava-scheduler-device-diction.... But they only list device_ip, device_mac and storage_info. Is there a way to extend this list? If not, is there any other way to provide device specific information to test shells?
An extensible format could be investigated with Test Definition 2.0. For now, individual test shell helpers are added for specific information, just as with the energy probe support.
Please open an issue and specify the exact information required for this use case to create a specific helper. Generally, it is better to have one helper for one value but if you need more than three pieces of information or if the information is complex (e.g. the data includes values in pairs or sets) then a single helper will need to output all the data in a format which can be parsed.
milosz
Lava-users mailing list Lava-users@lists.lavasoftware.org https://lists.lavasoftware.org/mailman/listinfo/lava-users
On Mon, 11 Feb 2019 at 07:40, Neil Williams neil.williams@linaro.org wrote:
On Sun, 10 Feb 2019 at 16:17, Milosz Wasilewski milosz.wasilewski@linaro.org wrote:
Hi,
Is there a way to specify an arbitrary parameter, that is board specific, in device dictionary? The parameter should be available from test shell. The use case is as follows: DUT is connected to test supporting hardware (chamelium board in this case). Tests access supporting hardware using IP address. IP address is 'static' and the supporting hw is assumed to be always turned on. Supporting hardware is dedicated to specific DUT and can't be shared (because of HW connections) between other boards of the same type (similar to energy probes). Tests run directly on DUT and access supporting hardware from there.
I found 'exported parameters' in device dictionary docs: https://master.lavasoftware.org/static/docs/v2/lava-scheduler-device-diction.... But they only list device_ip, device_mac and storage_info. Is there a way to extend this list? If not, is there any other way to provide device specific information to test shells?
An extensible format could be investigated with Test Definition 2.0. For now, individual test shell helpers are added for specific information, just as with the energy probe support.
Please open an issue and specify the exact information required for this use case to create a specific helper. Generally, it is better to have one helper for one value but if you need more than three pieces of information or if the information is complex (e.g. the data includes values in pairs or sets) then a single helper will need to output all the data in a format which can be parsed.
In this case it's just one value - IP address. However I'm looking for sth like 'get_dict_value key_name'. This would allow to have arbitrary values defined for the lab/device. Common cases (device_ip, device_mac and storage_info) could just reuse this script.
I will open a ticket.
milosz
milosz
Lava-users mailing list Lava-users@lists.lavasoftware.org https://lists.lavasoftware.org/mailman/listinfo/lava-users
--
Neil Williams
neil.williams@linaro.org http://www.linux.codehelp.co.uk/
lava-users@lists.lavasoftware.org
-
Milosz Wasilewski -
Neil Williams