multiserver strategy to migrate from 188.8.131.52 to 3.0.5
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 184.108.40.206 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 220.127.116.11 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 :)
> 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 18.104.22.168 and was changed password column or something similar)
No. The table which is used for authentication ahs not been changed.
Btw. You should wait for the 22.214.171.124 release with the update as it contains bugfixes in the update procedure.
So, a god strategy can be:
stop al 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 :)
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 :)
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 17:37.|
Powered by vBulletin® Version 3.8.7
Copyright ©2000 - 2014, vBulletin Solutions, Inc.