Hello karsten,

I wrote down a basic ansible playbook for lava-server. Some important pieces are missing (like starting apache with the right config) but it will install lava-server cleanly.
It's more or loss a copy of the one we use internally for lavasotware.org
It's available at https://git.lavasoftware.org/lava/pkg/ansible

It's pretty basic for the moment so I will try to find some time to extend it.
Please have a look at it, fork it on our gitlab and feel free improve it if it's of some use to you.


Cheers

Le mer. 20 févr. 2019 à 17:22, Remi Duraffort <remi.duraffort@linaro.org> a écrit :
Hello Karsten,

if you happen to write down an ansible playbook for lava, please share it!
That might even be a good idea to host the playbook git in our gitlab instance so people can contribute.
And I would happily contribute (with a limit amount of time but still) to such playbook (as I wrote the one we use internally).


Cheers

Le mer. 20 févr. 2019 à 16:26, Neil Williams <neil.williams@linaro.org> a écrit :
On Wed, 20 Feb 2019 at 14:41, Karsten Tausche <karsten@fairphone.com> wrote:
>
> Hi,
>
> Are the Ansible playbook for setting up LAVA available somewhere?
> There is an old migrated issue on GitLab [1] which is closed

Sorry, that issue is probably misleading.

That issue relates to the ansible playbook for setting up
lavasoftware.org, not a LAVA instance. (Although a LAVA instance is
part of it, master.lavasoftware.org does not have any devices, so the
bulk of the playbook is not applicable.)

>, but the link to an implementation in there is dead. Is that playbook only internally available for Linaro? Is there anything you could share?

Ansible is used in a small part of the Harston lab but the majority of
the work is done by salt. That configuration is managed in
https://git.linaro.org/lava/lava-lab but is highly specific to the
Harston lab.

> It looks like many people are moving to Docker in the moment, but that's not an option for us (at least not for dispatchers), as we need LXC for Android testing.

That's not actually the case and there is work ongoing to move all
AOSP testing to Docker. There are some udev changes required and the
scripts aren't finalised at this stage.

The main issue is persistence and we are working on that for 2019.03 -
see https://git.lavasoftware.org/lava/lava/issues/114

In the end, I suspect that every playbook / salt config for LAVA is
going to need to be created from scratch.

You will need to consider how to manage secrets, that is one
problematic area. The database access password needs to be protected
and you may also have LDAP passwords etc.

--

Neil Williams
=============
neil.williams@linaro.org
http://www.linux.codehelp.co.uk/

_______________________________________________
Lava-users mailing list
Lava-users@lists.lavasoftware.org
https://lists.lavasoftware.org/mailman/listinfo/lava-users


--
Rémi Duraffort
LAVA Team, Linaro


--
Rémi Duraffort
LAVA Team, Linaro