Two questions here:
1. If a master-only instance here, how to upgrade without data loss?
2. If a slave-only instance here, how to upgrade without data loss?
Please suggest, thanks.
On Fri, 11 Jan 2019 at 07:08, Larry Shen larry.shen@nxp.com wrote:
Two questions here:
If a master-only instance here, how to upgrade without data loss?If a slave-only instance here, how to upgrade without data loss?
Larry,
I'm not sure if I understand your question correctly but you should run master and slave from the same code. Usual upgrade doesn't delete the data from database. Could you describe in more detail what you're trying to do?
milosz
Please suggest, thanks.
Lava-users mailing list Lava-users@lists.lavasoftware.org https://lists.lavasoftware.org/mailman/listinfo/lava-users
On Fri, 11 Jan 2019 at 11:47, Milosz Wasilewski milosz.wasilewski@linaro.org wrote:
On Fri, 11 Jan 2019 at 07:08, Larry Shen larry.shen@nxp.com wrote:
Two questions here:
If a master-only instance here, how to upgrade without data loss?
The packages handle the process of upgrading without data loss. The services are stopped automatically, the code upgraded and the services restarted automatically.
If a slave-only instance here, how to upgrade without data loss?
The only data on a LAVA worker is configuration (like ser2net) and some local lab scripts to control remote power etc. There is no LAVA data that is relevant to upgrading the LAVA software on a worker. Test jobs continue to run in their own temporary directories and ZMQ handles any buffering of log messages whilst the upgrade itself occurs.
Larry,
I'm not sure if I understand your question correctly but you should run master and slave from the same code. Usual upgrade doesn't delete the data from database. Could you describe in more detail what you're trying to do?
milosz
Please suggest, thanks.
Lava-users mailing list Lava-users@lists.lavasoftware.org https://lists.lavasoftware.org/mailman/listinfo/lava-users
Lava-users mailing list Lava-users@lists.lavasoftware.org https://lists.lavasoftware.org/mailman/listinfo/lava-users
Got it. I have confirm this when upgrade from 2018.1 to 2018.11 thanks
________________________________ 收件人: Neil Williams neil.williams@linaro.org 发送时间: 星期一, 一月 21, 2019 18:58 收件人: Milosz Wasilewski 抄送: Larry Shen; lava-users@lists.lavasoftware.org 主题: Re: [Lava-users] How to upgrade lava without data loss?
On Fri, 11 Jan 2019 at 11:47, Milosz Wasilewski milosz.wasilewski@linaro.org wrote:
On Fri, 11 Jan 2019 at 07:08, Larry Shen larry.shen@nxp.com wrote:
Two questions here:
- If a master-only instance here, how to upgrade without data loss?
The packages handle the process of upgrading without data loss. The services are stopped automatically, the code upgraded and the services restarted automatically.
- If a slave-only instance here, how to upgrade without data loss?
The only data on a LAVA worker is configuration (like ser2net) and some local lab scripts to control remote power etc. There is no LAVA data that is relevant to upgrading the LAVA software on a worker. Test jobs continue to run in their own temporary directories and ZMQ handles any buffering of log messages whilst the upgrade itself occurs.
Larry,
I'm not sure if I understand your question correctly but you should run master and slave from the same code. Usual upgrade doesn't delete the data from database. Could you describe in more detail what you're trying to do?
milosz
Please suggest, thanks.
Lava-users mailing list Lava-users@lists.lavasoftware.org https://emea01.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.lav...
Lava-users mailing list Lava-users@lists.lavasoftware.org https://emea01.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.lav...
--
Neil Williams ============= neil.williams@linaro.org https://emea01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.linux....
lava-users@lists.lavasoftware.org
-
Larry Shen -
Milosz Wasilewski -
Neil Williams