Hi,
We are building a LAVA lab which will be soon integrated to KernelCI. We want to add most of our boards to LAVA that's why we created configuration files for the old dispatcher (the one used by KernelCI at this moment) for all device types we own.
I would like to know if you were interested in getting those configuration files to put them in your git repository (we are using some from: https://github.com/Linaro/lava-dispatcher/tree/release/lava_dispatcher/defau... If yes, what is your naming convention? I've seen sama53d for the SAMA5D3 Xplained for example.
This is the list of boards currently added to our lab: Board name Current configuration file's name NextThingCo. CHIP sun5i-r8-chip Boundary Devices Nitrogen6x imx6q-nitrogen6x ATMEL at91rm9200ek at91rm9200ek ATMEL at91sam9261ek at91sam9261ek ATMEL at91sam9m10g45ek at91sam9m10g45ek ATMEL at91sam9x25ek at91sam9x25ek ATMEL at91sam9x35ek at91sam9x35ek ATMEL sama5d31ek sama5d31ek ATMEL sama5d36ek sama5d36ek ATMEL sama5d44ek sama5d4ek Marvell Armada 385 AP armada-385-db-ap Solidrun Clearfog armada-388-clearfog Plathome OpenBlocks AX3 armada-xp-openblocks-ax3-4
Regards,
Quentin
Yes, absolutely, having extra device types supported in the codebase makes it easier for others using LAVA, even if those devices are not currently present in the Cambridge lab. (The Cambridge lab generally reflects the priorities of member companies in Linaro, so manufacturers outside Linaro are rarely represented.)
(This needs to be a section in the documentation.)
Naming conventions need to consider these factors:
0: the device-type name needs to be resolvable in the URL, so avoid characters that would need URL quoting, especially whitespace. 1: current device types are all lowercase, there could be hidden assumptions about lookups being case-insensitive, so it is likely best to keep names lowercase 2: The description field is lab-specific, so this can be used to put a free text description on the device type pages. 3: A quick check of other labs can be informative, e.g. kernelci, lava.collabora.co.uk
I would much prefer that contributions like this come through review.linaro.org which is covered here: https://validation.linaro.org/static/docs/v2/development.html#contributing-u... but I can also do it via a github pull-request, it's just that if there are questions, it is harder to get the review updated.
With LAVA V2 templates, there is room to have a comment specifying the contact details for the maintainer of the template. https://validation.linaro.org/static/docs/v2/pipeline-admin-example.html
On 29 March 2016 at 16:30, Quentin Schulz quentin.schulz@free-electrons.com wrote:
Hi,
We are building a LAVA lab which will be soon integrated to KernelCI. We want to add most of our boards to LAVA that's why we created configuration files for the old dispatcher (the one used by KernelCI at this moment) for all device types we own.
I would like to know if you were interested in getting those configuration files to put them in your git repository (we are using some from: https://github.com/Linaro/lava-dispatcher/tree/release/lava_dispatcher/defau... If yes, what is your naming convention? I've seen sama53d for the SAMA5D3 Xplained for example.
This is the list of boards currently added to our lab: Board name Current configuration file's name NextThingCo. CHIP sun5i-r8-chip Boundary Devices Nitrogen6x imx6q-nitrogen6x ATMEL at91rm9200ek at91rm9200ek ATMEL at91sam9261ek at91sam9261ek ATMEL at91sam9m10g45ek at91sam9m10g45ek ATMEL at91sam9x25ek at91sam9x25ek ATMEL at91sam9x35ek at91sam9x35ek ATMEL sama5d31ek sama5d31ek ATMEL sama5d36ek sama5d36ek ATMEL sama5d44ek sama5d4ek Marvell Armada 385 AP armada-385-db-ap Solidrun Clearfog armada-388-clearfog Plathome OpenBlocks AX3 armada-xp-openblocks-ax3-4
Regards,
Quentin _______________________________________________ Lava-users mailing list Lava-users@lists.linaro.org https://lists.linaro.org/mailman/listinfo/lava-users
Neil Williams neil.williams@linaro.org writes:
Yes, absolutely, having extra device types supported in the codebase makes it easier for others using LAVA, even if those devices are not currently present in the Cambridge lab. (The Cambridge lab generally reflects the priorities of member companies in Linaro, so manufacturers outside Linaro are rarely represented.)
(This needs to be a section in the documentation.)
Naming conventions need to consider these factors:
0: the device-type name needs to be resolvable in the URL, so avoid characters that would need URL quoting, especially whitespace. 1: current device types are all lowercase, there could be hidden assumptions about lookups being case-insensitive, so it is likely best to keep names lowercase 2: The description field is lab-specific, so this can be used to put a free text description on the device type pages. 3: A quick check of other labs can be informative, e.g. kernelci, lava.collabora.co.uk
For kernelCI we strongly prefer that the device-type matches exactly the DT name in the upstream kernel sources.
Kevin