Hi All,
Since 2020.09 it appears that workers using a version different than the master are refusing to start. Would it be possible to relax this constraint?
With workers spread all over the world in different places, it is hard to synchronize master and slaves upgrades. Also, we have always run with workers versions <= master version, without a single problem. So it would be great to allow version mismatch, and maybe print a simple warning when version differs?
Thanks,
Philippe
Hello,
is it possible in your use case to use lava-docker-worker? Because this service will automatically run the right worker version and upgrade/downgrade the local version (using docker containers) to match the server version.
It's in fact possible to make the version check optional. It's a matter of adding a setting and testing for the setting flag. Keep in mind that the version check is here to prevent against strange issues when version are not compatible. Like when the device-dictionary are changing and the dispatcher depends on such changes.
Le jeu. 19 nov. 2020 à 15:36, Philippe Mazet (OSS) < philippe.mazet@oss.nxp.com> a écrit :
Hi All,
Since 2020.09 it appears that workers using a version different than the master are refusing to start. Would it be possible to relax this constraint?
With workers spread all over the world in different places, it is hard to synchronize master and slaves upgrades. Also, we have always run with workers versions <= master version, without a single problem. So it would be great to allow version mismatch, and maybe print a simple warning when version differs?
Thanks,
Philippe
Lava-users mailing list Lava-users@lists.lavasoftware.org https://lists.lavasoftware.org/mailman/listinfo/lava-users
I tried the lava-docker-worker but found it too restrictive, since we can’t customize the Docker container at all (adding some tools, cfg files, ssh keys, etc…), and was imposing usage of Docker within the job themselves (that would force us to rewrite many of our existing tests).
As to “automatically run the right worker version”, I might have missed something. By checking lava-docker-worker sources, I concluded the Docker would simply refuse to start if version differs versus master. But do you mean it will automatically restart with the correct version when master is upgraded?
With my current understanding, I would still vote for allowing version mismatch… at our own risks of course.
Thank you,
Philippe
From: Remi Duraffort remi.duraffort@linaro.org Sent: Monday, November 23, 2020 5:44 PM To: Philippe Mazet (OSS) philippe.mazet@oss.nxp.com Cc: lava-users@lists.lavasoftware.org lava-users@lavasoftware.org Subject: Re: [Lava-users] Worker/master version mismatch
Hello,
is it possible in your use case to use lava-docker-worker? Because this service will automatically run the right worker version and upgrade/downgrade the local version (using docker containers) to match the server version.
It's in fact possible to make the version check optional. It's a matter of adding a setting and testing for the setting flag. Keep in mind that the version check is here to prevent against strange issues when version are not compatible. Like when the device-dictionary are changing and the dispatcher depends on such changes.
Le jeu. 19 nov. 2020 à 15:36, Philippe Mazet (OSS) <philippe.mazet@oss.nxp.commailto:philippe.mazet@oss.nxp.com> a écrit : Hi All,
Since 2020.09 it appears that workers using a version different than the master are refusing to start. Would it be possible to relax this constraint?
With workers spread all over the world in different places, it is hard to synchronize master and slaves upgrades. Also, we have always run with workers versions <= master version, without a single problem. So it would be great to allow version mismatch, and maybe print a simple warning when version differs?
Thanks,
Philippe
_______________________________________________ Lava-users mailing list Lava-users@lists.lavasoftware.orgmailto:Lava-users@lists.lavasoftware.org https://lists.lavasoftware.org/mailman/listinfo/lava-users
-- Rémi Duraffort LAVA Architect Linaro
Hello Philippe,
I tried the lava-docker-worker but found it too restrictive, since we can’t
customize the Docker container at all (adding some tools, cfg files, ssh keys, etc…), and was imposing usage of Docker within the job themselves (that would force us to rewrite many of our existing tests).
That's an interesting use case. Maybe something that we might want to support. A possibility would be to specify the docker registry that you want to use instead of docker hub.
As to “automatically run the right worker version”, I might have missed something. By checking lava-docker-worker sources, I concluded the Docker would simply refuse to start if version differs versus master. But do you mean it will automatically restart with the correct version when master is upgraded?
That would be an easy fix (just adding a settings to lava_server and return depending on the setting value). But keep in mind that this might break at any release.
Rgds
lava-users@lists.lavasoftware.org
-
Philippe Mazet (OSS) -
Remi Duraffort