We moved forward with just exposing the data folder of the database as a volume because operations here already backs up all volumes automatically. But I will have two instances of lava so I can certainly still point the database of the dev instance to aws-RDS. I will post updates over in the lava-devel mailing list. I understand that the container deployment is a very new thing for lava but since we're just starting off with lava we won't have a lot to migrate if breaking changes occur. On Sun, Dec 9, 2018 at 11:47 PM Neil Williams neil.williams@linaro.org wrote:
On Fri, 7 Dec 2018 at 12:21, Remi Duraffort remi.duraffort@linaro.org wrote:
Hello,
when trying to backup a lava instance, keep in mind that lava is made of two parts : the server (only one) and the dispatchers (usually more than one).
For the server you should backup:
- the database (see /etc/lava-server/instance.conf)
- the configuration:
** /etc/lava-server/ ** /etc/lava-dispatcher/certificates.d
- the job artifacts: /var/lib/lava-server/default/media/job-output
On the dispatchers, you should backup:
- dispatcher config: /etc/lava-dispatcher/
- all the changes you did like, /etc/ser2net.conf, udev rules, ...
Hope that helps.
Le jeu. 6 déc. 2018 à 18:35, Chris Sauer csauer@peoplenetonline.com a écrit :
Im deploying lava using the docker container and I am looking at the correct paths to mount as volumes as to not lose data between cluster rollovers. (and to have to backups) If I change the instance.conf to point to a database that is outside of the container that gets backed up and includes these paths in my volume mounts is that all I need to do? Or is there additional paths/files that should be included.
We haven't actually had a chance to test using an external database upstream yet. We will be looking at this and other similar issues in January and discussions will happen on the lava-devel mailing list (https://lists.lavasoftware.org/mailman/listinfo/lava-devel). More details will be announced soon.
For now, simply pointing the instance.conf elsewhere should work - it leaves a redundant but fully configured database in the container - but has not been tested. If you want to use a database outside the container, test your changes carefully on a staging or test instance and please let us know your results on the lava-devel mailing list.
https://master.lavasoftware.org/static/docs/v2/admin-backups.html
If anyone knows anything about this thanks!
Lava-users mailing list Lava-users@lists.lavasoftware.org https://lists.lavasoftware.org/mailman/listinfo/lava-users
-- Rémi Duraffort LAVA Team _______________________________________________ Lava-users mailing list Lava-users@lists.lavasoftware.org https://lists.lavasoftware.org/mailman/listinfo/lava-users
--
Neil Williams
neil.williams@linaro.org http://www.linux.codehelp.co.uk/