Hello everyone,
is there any documentation on how Linaro uses Salt for configuring LAVA nodes? I know the infrastructure code is hosted at https://git.linaro.org/lava/lava-lab.git, but since I am new to Salt (and configuration management in general), I would love to have some kind of starting point. Where is this repository checked out? Who applies the defined Salt states and when? Are there any automatic processes happening when someone commits to the repository (e.g. changing a device type or health check job)? What is Linaro's workflow in these cases?
Mit freundlichen Grüßen / Best regards Tim Jaacks DEVELOPMENT ENGINEER Garz & Fricke GmbH Tempowerkring 2 21079 Hamburg Direct: +49 40 791 899 - 55 Fax: +49 40 791899 - 39 tim.jaacks@garz-fricke.com www.garz-fricke.com SOLUTIONS THAT COMPLETE!
Sitz der Gesellschaft: D-21079 Hamburg Registergericht: Amtsgericht Hamburg, HRB 60514 Geschäftsführer: Matthias Fricke, Manfred Garz
On Tue, 24 Jul 2018 at 09:07, Tim Jaacks tim.jaacks@garz-fricke.com wrote:
Hello everyone,
is there any documentation on how Linaro uses Salt for configuring LAVA nodes? I know the infrastructure code is hosted at https://git.linaro.org/lava/lava-lab.git, but since I am new to Salt (and configuration management in general), I would love to have some kind of starting point. Where is this repository checked out?
Adding Dave for more detailed responses.
By any admin with access to the relevant machines, on their local admin desktop, with appropriate SSH keys / config already available etc.
Who applies the defined Salt states and when?
Depends on the type of change - large changes get discussed within the team and the team lead runs the salt commands to deploy the changes. Smaller changes get salted by the admin making the change, typically after code review of the change itself.
Are there any automatic processes happening when someone commits to the repository (e.g. changing a device type or health check job)?
You can follow the links in review.linaro.org for lava-lab reviews to see the sanity checks. Just search for the ChangeId from a commit in lava-lab. e.g. https://ci.linaro.org/job/lava-lab-sanity-check/418/console That in turn runs: ${WORKSPACE}/lava-server/share/check-devices.py --device-types ${RUN}/device-types --devices ${RUN}/devices
What is Linaro's workflow in these cases?
Mit freundlichen Grüßen / Best regards Tim Jaacks DEVELOPMENT ENGINEER Garz & Fricke GmbH Tempowerkring 2 21079 Hamburg Direct: +49 40 791 899 - 55 Fax: +49 40 791899 - 39 tim.jaacks@garz-fricke.com www.garz-fricke.com SOLUTIONS THAT COMPLETE!
Sitz der Gesellschaft: D-21079 Hamburg Registergericht: Amtsgericht Hamburg, HRB 60514 Geschäftsführer: Matthias Fricke, Manfred Garz
Lava-users mailing list Lava-users@lists.linaro.org https://lists.linaro.org/mailman/listinfo/lava-users
lava-users@lists.lavasoftware.org
-
Neil Williams -
Tim Jaacks