> Just configure the worker to connect to your master.
> This is done in /etc/lava-dispatcher/lava-slave
> An example configuration file is available at /usr/share/lava-dispatcher/
lava-slave
>
> For a first try, you can start without encryption and only define the
following variables in the configuration file:
> MASTER_URL="tcp://localhost:5556"
> LOGGER_URL="tcp://localhost:5555"
Hello Remi,
Do you, Linaro guys, have some Open Source Lava Server on the Cloud, where
I can create lava admin account, hook to it my Lava Worker and try it?
I need some access to create device-type BeagleBone Black and device BBB0x
as well.
This will be interesting experiment, don't you agree?
Thank you,
Zoran Stojsavljevic
_______
On Tue, Aug 7, 2018 at 1:53 PM, Remi Duraffort <remi.duraffort(a)linaro.org>
wrote:
> Hello,
>
> the worker will register itself to the master automatically. You don't
> have to create the worker manually.
>
> Just configure the worker to connect to your master.
> This is done in /etc/lava-dispatcher/lava-slave
> An example configuration file is available at /usr/share/lava-dispatcher/
> lava-slave
>
> For a first try, you can start without encryption and only define the
> following variables in the configuration file:
> MASTER_URL="tcp://localhost:5556"
> LOGGER_URL="tcp://localhost:5555"
>
> You can also specify the HOSTNAME if you want. By default the slave will
> use the name of the server it's running on.
>
> This will instruct you local lava-slave (this is the name of the service)
> to connect to the local lava-master.
> Then restart the lava-slave with "service lava-slave restart"
>
>
The document about installing lava system, does "Single Master Instance installation " mean master(include lava-server) and worker(include lava-dispatcher) can be installed in the one physical computer? In this simple mode,wheather the worker(logic unit)must only have one?
I am ready to deploy a local lava single master demo system. The server and dispatcher had be installed in a single computer.
In order to enable the server to kno the dispatcher(worker),Then how to configure something.
Is doing this?:
sudo lava-server manage workers add <HOSTNAME> ,that HOSTNAME is changed in /etc/lava-dispatcher/lava-slave file?
And when did,How to see whether dispatcher is working already?
Hi,
According to lava installation document ,I had installed lava-server to debian 9.5.0.Creating super user operation is ok(sudo lava-server manage createsuperuser --username $USERNAME --email=$EMAIL) . But when using firefox browser to login in by created name , response message:
--
SRF verification failed. Request aborted.
You are seeing this message because this site requires a CSRF cookie when submitting forms. This cookie is required for security reasons, to ensure that your browser is not being hijacked by third parties.
If you have configured your browser to disable cookies, please re-enable them, at least for this site, or for 'same-origin' requests.
--
After configured browser to disable cookies,the response is still so.
Jiang Lao
Hi,If there is no “dameon” program in DUT. How to add/update the program running in DUT
for example application test program or linux kernel or uboot etc.?Jiang Lao
--------------------------------------------
On Wed, 1 Aug 2018 at 10:18, ljh_dev <ljh_dev at 126.com> wrote:
> Hi,
> I have browsed the website documentation of lava overall. I think the
> DUT(Device Under Test) should has "dameon" program to communicate with the
> Worker Dispatcher module. But I did not find where the DUT "dameon"
> program source code is,and how to build&install this DUT "dameon" program.
>
It does not need to be built or installed. The lava-dispatcher package does
all that work for you.
https://validation.linaro.org/static/docs/v2/index.html#architecturehttps:/…
/var/log/lava-dispatcher/lava-slave.log
If there is no "dameon" program in DUT. How to add/update the program running in DUT for example application test program or linux kernel or uboot etc.?
Best regards,
Hi,
I have browsed the website documentation of lava overall. I think the DUT(Device Under Test) should has "dameon" program to communicate with the Worker Dispatcher module. But I did not find where the DUT "dameon" program source code is,and how to build&install this DUT "dameon" program.
thanks,
Jiang Lao
Hello Lava Users,
We are creating queries in LAVA and adding multiple conditions to query.For
example in our yaml job definition we have included os field in metadata
section which will have different values.For example following is the
metadata section for 2 different jobs
Job1:
metadata:
description: '"Build SiemensIPC-327E target with latest build"'
os: Debian
device: imx6q
Build_ID: QA-BUILD-F0150
Job2:
metadata:
description: '"Build SiemensIPC-327E target with latest build"'
os: Ubuntu
device: imx6q
Build_ID: QA-BUILD-F0150
Now with queries I am trying to just filter out job running with Build_ID(
QA-BUILD-F0150 ) and on only os debian.
Entity Field Operator Value
namedtestattribute
Build_ID
exact
QA-BUILD-F0150
namedtestattribute
os
exact
Debian
When I am creating queries with above information, as a user when I run the
query the query results will just list Job1 information but at present in
LAVA both the jobs are getting listed. Is this the expected behavior?The
LAVA server version used is 2018.5.post1 release.
Thanks,
Hemanth.
