Hello,
As far as I can tell, LAVA currently doesn't set hostname of a LAVA board when running tests, which leads for usage of whatever generic (or random) value was configured in build image. That may pose problem if test/build uses hostname for some logging or identification.
For example, CBuild included hostname in build result id, based on which various logs and result bundles are named, and which then gets parsed by CBuild frontend to display build results. So, we got confusing and inconsistent results from LAVA builds. I so far worked that around by setting CBuild/LAVA builds' hostname to "lava", but that doesn't match how native CBuild builds work, for example, http://cbuild.validation.linaro.org/helpers/buildlog page shows build matrix per individual board, based on hostname.
I tried to investigate how it happened that lava-dispatcher doesn't try to set hostname, and actually found it used to, but that was tied to recognition of test prompts, and once that was refactored, setting hostname also gone, see http://bazaar.launchpad.net/~linaro-validation/lava-dispatcher/trunk/revisio... (grep for "_customize_ubuntu" - it got factored out to another file, and lost /etc/hostname setting in progress).
So, please let me know if the above makes sense, and should be files as lava-dispatcher bug, or are there other reasons for not setting a hostname.
Thanks, Paul
Linaro.org | Open source software for ARM SoCs Follow Linaro: http://www.facebook.com/pages/Linaro http://twitter.com/#%21/linaroorg - http://www.linaro.org/linaro-blog
On 01/28/2013 07:46 AM, Paul Sokolovsky wrote:
Hello,
As far as I can tell, LAVA currently doesn't set hostname of a LAVA board when running tests, which leads for usage of whatever generic (or random) value was configured in build image. That may pose problem if test/build uses hostname for some logging or identification.
I tried to investigate how it happened that lava-dispatcher doesn't try to set hostname, and actually found it used to, but that was tied to recognition of test prompts, and once that was refactored, setting hostname also gone, see http://bazaar.launchpad.net/~linaro-validation/lava-dispatcher/trunk/revisio... (grep for "_customize_ubuntu" - it got factored out to another file, and lost /etc/hostname setting in progress).
So, please let me know if the above makes sense, and should be files as lava-dispatcher bug, or are there other reasons for not setting a hostname.
I think this is a reasonable feature request. I think we could easily add something to the _customize_* functions to set the hostname. Probably takes less than an hour to implement/test/merge.
Paul Sokolovsky paul.sokolovsky@linaro.org writes:
I tried to investigate how it happened that lava-dispatcher doesn't try to set hostname, and actually found it used to, but that was tied to recognition of test prompts, and once that was refactored, setting hostname also gone, see http://bazaar.launchpad.net/~linaro-validation/lava-dispatcher/trunk/revisio... (grep for "_customize_ubuntu" - it got factored out to another file, and lost /etc/hostname setting in progress).
So, please let me know if the above makes sense, and should be files as lava-dispatcher bug, or are there other reasons for not setting a hostname.
Seems reasonable. Do you want hostname set to the device name ("panda01") or just something generic? Previously the dispatcher just set it to "linaro" I think...
Cheers, mwh
On Mon, Jan 28, 2013 at 7:37 PM, Michael Hudson-Doyle michael.hudson@linaro.org wrote:
Paul Sokolovsky paul.sokolovsky@linaro.org writes:
I tried to investigate how it happened that lava-dispatcher doesn't try to set hostname, and actually found it used to, but that was tied to recognition of test prompts, and once that was refactored, setting hostname also gone, see http://bazaar.launchpad.net/~linaro-validation/lava-dispatcher/trunk/revisio... (grep for "_customize_ubuntu" - it got factored out to another file, and lost /etc/hostname setting in progress).
So, please let me know if the above makes sense, and should be files as lava-dispatcher bug, or are there other reasons for not setting a hostname.
Seems reasonable. Do you want hostname set to the device name ("panda01") or just something generic? Previously the dispatcher just set it to "linaro" I think...
I don't feel we should start encoding anything useful into the hostname that doesn't help LAVA to reliably match the prompt.
All other ideas that come to our mind that read "use the prompt to identify..." probably just indicate the need for something that gives meta info about the id/host at hand. Here, idea would be to make a (busybox) tool we install on all targets that dumps information about the host ... like ec2metainfo or lsb_release -r ...
I assume we already talked about that in the past?
Cheers, mwh
On 01/28/2013 12:47 PM, Alexander Sack wrote:
On Mon, Jan 28, 2013 at 7:37 PM, Michael Hudson-Doyle michael.hudson@linaro.org wrote:
Paul Sokolovskypaul.sokolovsky@linaro.org writes:
I tried to investigate how it happened that lava-dispatcher doesn't try to set hostname, and actually found it used to, but that was tied to recognition of test prompts, and once that was refactored, setting hostname also gone, see http://bazaar.launchpad.net/~linaro-validation/lava-dispatcher/trunk/revisio... (grep for "_customize_ubuntu" - it got factored out to another file, and lost /etc/hostname setting in progress).
So, please let me know if the above makes sense, and should be files as lava-dispatcher bug, or are there other reasons for not setting a hostname.
Seems reasonable. Do you want hostname set to the device name ("panda01") or just something generic? Previously the dispatcher just set it to "linaro" I think...
I'd vote for the device name, ie panda01. Seems the most useful and unique.
I don't feel we should start encoding anything useful into the hostname that doesn't help LAVA to reliably match the prompt.
Think prompt and hostname are orthogonal. We (LAVA) set the prompt to something very specific. It just so happens a default Ubuntu prompt normally includes the hostname in it.
Hello,
On Tue, 29 Jan 2013 07:37:15 +1300 Michael Hudson-Doyle michael.hudson@linaro.org wrote:
Paul Sokolovsky paul.sokolovsky@linaro.org writes:
I tried to investigate how it happened that lava-dispatcher doesn't try to set hostname, and actually found it used to, but that was tied to recognition of test prompts, and once that was refactored, setting hostname also gone, see http://bazaar.launchpad.net/~linaro-validation/lava-dispatcher/trunk/revisio... (grep for "_customize_ubuntu" - it got factored out to another file, and lost /etc/hostname setting in progress).
So, please let me know if the above makes sense, and should be files as lava-dispatcher bug, or are there other reasons for not setting a hostname.
Seems reasonable. Do you want hostname set to the device name ("panda01") or just something generic? Previously the dispatcher just set it to "linaro" I think...
Thanks. Yes, to the device name as seen in LAVA web frontend, "panda01", "panda-es03", etc.
Cheers, mwh
On Tue, 29 Jan 2013 06:39:12 -0600 Andy Doan andy.doan@linaro.org wrote:
On 01/29/2013 04:48 AM, Paul Sokolovsky wrote:
Thanks. Yes, to the device name as seen in LAVA web frontend, "panda01", "panda-es03", etc.
This was merged last night and will be deployed sometime today (my afternoon)
That works, thanks Andy!
linaro-validation@lists.linaro.org
-
Alexander Sack -
Andy Doan -
Michael Hudson-Doyle -
Paul Sokolovsky