HowtoForge Forums | HowtoForge - Linux Howtos and Tutorials - multiserver strategy to migrate from 3.0.4.6 to 3.0.5

HowtoForge Forums | HowtoForge - Linux Howtos and Tutorials (http://www.howtoforge.com/forums/index.php)

- General (http://www.howtoforge.com/forums/forumdisplay.php?f=25)

- - multiserver strategy to migrate from 3.0.4.6 to 3.0.5 (http://www.howtoforge.com/forums/showthread.php?t=60713)

maumar

27th February 2013 10:28

multiserver strategy to migrate from 3.0.4.6 to 3.0.5

Hello
I have a multiserver infrastructure with more than 70 vm and one cp; further, in each site I have a VM with cp mysql db replica.

which is the correct strategy to migrate all of them from 3.0.4.6 to 3.0.5?
I argue that I should start from cp and then upgrade all the others 70 vm linkd to cp.

My questions are:
are database tables structure changed?
If they are as i can imagine, mail server will be unable to authenticate until i Upgrade ispconfig on them (I remember this when migrated by 3.4.3 to 3.0.4.4 and was changed password column or something similar)
when I upgrade cp, what happen to other VM? stop to sync until I upgrade them?

please share your experience if you have one :)

till	27th February 2013 11:10

> are database tables structure changed?

yes.

> If they are as i can imagine, mail server will be unable to authenticate until i Upgrade ispconfig on them (I remember this when migrated by 3.4.3 to 3.0.4.4 and was changed password column or something similar)

No. The table which is used for authentication ahs not been changed.

Quote:

when I upgrade cp, what happen to other VM? stop to sync until I upgrade them?

The servers of a cluster do not depend on the master for normal operation, you can even stop the master without affecting them. The only thing that you cant do unti the update is finsihed on all nodes is tao add new meilboxes or domains trough the master.

Btw. You should wait for the 3.0.5.1 release with the update as it contains bugfixes in the update procedure.

maumar

27th February 2013 14:59

So, a god strategy can be:
stop al cron

Code:



* * * * * /usr/local/ispconfig/server/server.sh > /dev/null 2>> /var/log/ispconfig/cron.log

30 00 * * * /usr/local/ispconfig/server/cron_daily.sh > /dev/null 2>> /var/log/ispconfig/cron.log

an all nodes. Then, upgrade master, then for each node i upgrade, I restart cron.

Thi sway I haven't any polling by nodes that query a db structure different by that they expect and all is clean and clear :)

maumar

28th February 2013 19:00

Last question: api are changed?
I ask b/c roundcube plugin has not been updated by many ages, but if api are unchanged, there a lot of probability that rc plugin still works :)
many thnx

till	28th February 2013 19:15

There are changes in the api like new functions and additiona attributes for websites but if I remember correctly none of these changes should cause poblems with the roundcube plugin.

All times are GMT +2. The time now is 05:23.