Dear LAVA-Users,
We are trying to integrate a new device into our LAVA infrastructure, apart from our work with Raspberry Pis. We still lack experience with LAVA and I wanted to reach out to the community for some help with the setup.
The Device we want to integrate is a QC-DB-P10003 from mouser with Android 9 and the following specifications:
[cid:image001.png@01D71691.AA0089F0]
Also here<https://www.mouser.de/ProductDetail/515-QC-DB-P10003/> a link to the product page, which contains the complete data sheet for the device.
Does someone have experience with this device and can give some advice on how to create a device templates or if there is already one available in LAVA which would work.
Also tips for defining a device dictionary and test jobs to run Android on this device are very welcome. Has anyone maybe configured a similar device and can suggest us some
Steps on how to proceed.
Kind Regards,
Marcel
_____________________________________________________________________________________
Expleo Germany GmbH
Sitz der Gesellschaft | Corporate Headquarters: M?nchen
Handelsregister | Commercial Register: Amtsgericht M?nchen HRB 83252
Gesch?ftsf?hrung | Management: Ralph Gillessen, Marcus Ganguin
This message contains information that may be privileged or confidential. It is intended only for the person to whom it is addressed.
If you are not the intended recipient, you are not authorized to read, print, retain, copy, disseminate, distribute, or use this message or any part thereof.
If you receive this message in error, please notify the sender immediately and delete all copies of this message.
_________________________________________________________
EMAIL LEGAL MENTION / DISCLAIMER
This message contains information that may be privileged or confidential and is the property of the Expleo Services SAS, RCS Versailles 831 178 348, located, 3 avenue des Pr?s, 78180 Montigny Le Bretonneux - France. It is intended only for the person to whom it is addressed. If you are not the intended recipient, you are not authorized to read, print, retain, copy, disseminate, distribute, or use this message or any part thereof. If you receive this message in error, please notify the sender immediately and delete all copies of this message.
Ce message contient des informations qui peuvent ?tre privil?gi?es ou confidentielles et elles sont de la propri?t? d'Expleo Services SAS, RCS Versailles 831 178 348, situ?, 3 avenue des Pr?s, 78180 Montigny le Bretonneux-France. Il est destin? uniquement ? la personne ? qui est adress?. Si vous n'?tes pas le destinataire vis?, vous n'?tes pas autoris? ? lire, imprimer, conserver, copier, diffuser, distribuer ou utiliser ce message ou toute partie de celui-ci. Si vous recevez ce message par erreur, veuillez en avertir imm?diatement l'exp?diteur et supprimer toutes les copies de ce message.
Hi,
It looks only the scripts in "lava_dispatcher\lava_test_shell" will be overlayed to rootfs when lava do deploy.
So, my question is:
If we have some way in job to define a script file location: e.g. http://site/a.sh, then lava could also fetch the http://site/a.sh, then overlay it to rootfs?
Does lava has such kinds of manipulate rootfs function already? Or I have to put this scripts in the /usr/lib/python3/dist-packages/lava_dispatch/lava_test_shell of every worker?
Thanks.
Hello, I have a question about "count" in lava multinode, for next:
lava-multinode:
roles:
device:
count: 2
device_type: xxx
What does "count" mean? I know the job will only be scheduled if there are 2 "xxx" based device idle.
But, after that, how I could use one device do one task, and use another device to do another task? How can I assign different tasks to the 2 devices with the same devicetype?
E.g.
device xxx1 based on xxx
device xxx2 based on xxx
Then xxx1 run "ls" while xxx2 run "uname"?
Hi：
We upgrade lava 2018 to 2021, we met the problem when we submit jobs：
Job error: Invalid job data: ['Device not configured to support serial connection.', 'Device not configured to support serial connection.']
Hi Lava Users,
After upgrading to LAVA 2021.01, we are facing an issue of jobs not completing/exiting (once submitted) and getting stuck in "Running" state, doesn't matter if the job is successful or unsuccessful/incomplete/fail. After sometime if we try to cancel the job it gets stuck in "Cancelling" state. Due to this the device gets blocked and subsequent jobs are sent to "Scheduled" state.
Now only possible solution to free up the device, is to delete the job from LAVA administration
LAVA Administration > Test jobs (under lava_scheduler_app) > {job id} > Delete .
Though this way the device is recovered but the whole job gets deleted.
I have tried with different boot and deploy methods like nfs, uuu, ums, and minimal. In all cases I am getting similar issue.
This issue is only observed while using imx devices.
Ssh based jobs are working properly and also other x86 based devices while booting through minimal method.
I have attached screenshot of the jobs (Lava-job-begin.PNG and Lava-job-end.PNG).
What can be the issue here ?
Thanks,
Bhargav
Thanks a lot for your reply!
The LAVA link you sent seems pretty outdated, and I don't think it can be applied as-is to docker-compose solution. It is for a host install on Debian (not Docker).
More recent documentation seems to be here: https://lava.readthedocs.io/en/latest/admin/basic-tutorials/instance/backup/
However it tells how to create a .sql backup file (which I have), not how to restore it.
About the postgres link you sent, it is for postgres running on host, not within docker I think.
For Docker, it is described in https://registry.hub.docker.com/_/postgres/ (chapter "Initialization scripts").
But then when I try to place my .sql file in /docker-entrypoint-initdb.d/ folder, I get the error mentioned in my email: database "lavaserver" already exists.
Thus my question: what procedure is followed by Linaro for the backup/restore of their docker-compose instances?
Thanks again,
Philippe
From: Lava-users <lava-users-bounces(a)lists.lavasoftware.org> On Behalf Of koti
Sent: Friday, March 19, 2021 2:15 PM
To: lava-users(a)lists.lavasoftware.org
Subject: [Lava-users] LAVA master backup/restore
Hi Philippe Mazet,
Please find my comments inline.
Questions:
- Does Linaro's docker-compose solution modify postgres restore mechanism in any way?
[Koti] --> I am not sure about this.
- How do you handle backup/restore at linaro?
[Koti] ----> still are you facing the backup/restore issue after following the below documentation?
1. https://docs.lavasoftware.org/lava/admin-backups.html
2. http://postgresguide.com/utilities/backup-restore.html
Regards,
Koti
On Fri, 19 Mar 2021 at 17:30, <mailto:lava-users-request@lists.lavasoftware.org> wrote:
Send Lava-users mailing list submissions to
lava-users(a)lists.lavasoftware.org
To subscribe or unsubscribe via the World Wide Web, visit
https://lists.lavasoftware.org/mailman/listinfo/lava-users
or, via email, send a message with subject or body 'help' to
lava-users-request(a)lists.lavasoftware.org
You can reach the person managing the list at
lava-users-owner(a)lists.lavasoftware.org
When replying, please edit your Subject line so it is more specific
than "Re: Contents of Lava-users digest..."
Today's Topics:
1. LAVA master backup/restore (Philippe Mazet (OSS))
----------------------------------------------------------------------
Message: 1
Date: Thu, 18 Mar 2021 15:22:20 +0000
From: "Philippe Mazet (OSS)" <mailto:philippe.mazet@oss.nxp.com>
To: "mailto:lava-users@lists.lavasoftware.org" <mailto:lava-users@lavasoftware.org>
Subject: [Lava-users] LAVA master backup/restore
Message-ID:
<PR3PR04MB7244B9C1456CAD918574F1218B699(a)PR3PR04MB7244.eurprd04.prod.outlook.com>
Content-Type: text/plain; charset="us-ascii"
Hi all,
I am using the docker-compose solution to run a master: https://git.lavasoftware.org/lava/pkg/docker-compose
I was wondering how to extract a backup of the DB, and re-inject it in a different instance.
I found that postgres image has its own "restore" mechanism, based on initdb.d folder, as mentioned in the documentation:
https://registry.hub.docker.com/_/postgres/
The entrypoint.sh script (https://github.com/docker-library/postgres/blob/master/docker-entrypoint.sh) handles the restore whenever the folder is /docker-entrypoint-initdb.d/ contains a .sql file.
But when we store a backup in the container's /docker-entrypoint-initdb.d/ folder, and remove both the postgres image and its db-data volume, we get this error on next start:
ERROR: database "lavaserver" already exists
Full startup log attached.
Questions:
- Does Linaro's docker-compose solution modify postgres restore mechanism in any way?
- How do you handle backup/restore at linaro?
Thanks a lot in advance,
Philippe Mazet
NXP Semiconductors - Edge Processing
Email: philippe.mazet(a)nxp.com
Hi Philippe Mazet,
Please find my comments inline.
Questions:
- Does Linaro's docker-compose solution modify postgres restore mechanism
in any way?
[Koti] --> I am not sure about this.
- How do you handle backup/restore at linaro?
[Koti] ----> still are you facing the backup/restore issue after
following the below documentation?
1. https://docs.lavasoftware.org/lava/admin-backups.html
2. http://postgresguide.com/utilities/backup-restore.html
Regards,
Koti
On Fri, 19 Mar 2021 at 17:30, <lava-users-request(a)lists.lavasoftware.org>
wrote:
> Send Lava-users mailing list submissions to
> lava-users(a)lists.lavasoftware.org
>
> To subscribe or unsubscribe via the World Wide Web, visit
> https://lists.lavasoftware.org/mailman/listinfo/lava-users
> or, via email, send a message with subject or body 'help' to
> lava-users-request(a)lists.lavasoftware.org
>
> You can reach the person managing the list at
> lava-users-owner(a)lists.lavasoftware.org
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of Lava-users digest..."
>
>
> Today's Topics:
>
> 1. LAVA master backup/restore (Philippe Mazet (OSS))
>
>
> ----------------------------------------------------------------------
>
> Message: 1
> Date: Thu, 18 Mar 2021 15:22:20 +0000
> From: "Philippe Mazet (OSS)" <philippe.mazet(a)oss.nxp.com>
> To: "lava-users(a)lists.lavasoftware.org" <lava-users(a)lavasoftware.org>
> Subject: [Lava-users] LAVA master backup/restore
> Message-ID:
> <
> PR3PR04MB7244B9C1456CAD918574F1218B699(a)PR3PR04MB7244.eurprd04.prod.outlook.com
> >
>
> Content-Type: text/plain; charset="us-ascii"
>
> Hi all,
>
> I am using the docker-compose solution to run a master:
> https://git.lavasoftware.org/lava/pkg/docker-compose
> I was wondering how to extract a backup of the DB, and re-inject it in a
> different instance.
>
> I found that postgres image has its own "restore" mechanism, based on
> initdb.d folder, as mentioned in the documentation:
> https://registry.hub.docker.com/_/postgres/
>
> The entrypoint.sh script (
> https://github.com/docker-library/postgres/blob/master/docker-entrypoint.sh)
> handles the restore whenever the folder is /docker-entrypoint-initdb.d/
> contains a .sql file.
>
> But when we store a backup in the container's
> /docker-entrypoint-initdb.d/ folder, and remove both the postgres image and
> its db-data volume, we get this error on next start:
> ERROR: database "lavaserver" already exists
> Full startup log attached.
>
> Questions:
> - Does Linaro's docker-compose solution modify postgres restore mechanism
> in any way?
> - How do you handle backup/restore at linaro?
>
> Thanks a lot in advance,
>
>
> Philippe Mazet
> NXP Semiconductors - Edge Processing
> Email: philippe.mazet(a)nxp.com
>
>
>
>
Hello lava users,
I have to deal with a board with a very limited storage size. Overall capacity is 64 MB, with about 30 MB remaining.
This is a clear limitation for Lava usage. Hence my questions:
* Is there a possibility to configure Lava tests installation on an external storage, such as an USB drive?
* In Lava recent versions, is it possible to optimize the overlay tests structure?
* Today, assuming that tests are stored in a git repo, for each test the complete repo is copied in each overlay
* A balance has to be made between one git containing all the tests and one git per test (extreme configurations)
* Is there a better way to manage this? In a ideal world, that would mean copy only what is needed and not more
Thanks, have a nice day
