migrate an one ezpublish site to ezdfs architecture
migrate an one ezpublish site to ezdfs architecture
Friday 08 June 2012 5:45:58 pm - 1 reply
Hi
what is the consequence for the code of a passage from a single-server architecture to ezdfs archi (nfs cluster two servers) using the single instance ? en francais :Le passage d'une archi monoserveur ez en ezdfs (deux serveurs cluster nfs http://doc.ez.no/eZ-Publish/Technical-manual/4.x/Features/Clustering ) en se servant de l'instance mono , entraine t elle une réecriture d'une partie du développement ?Et qu'elle est l'impact sur le mode connecté et non connecté ?Car en lisant les docs , on a l'impression que la migration se passe facilement .
ps: C'est l'anglais du vendredi soir
Saturday 09 June 2012 12:06:48 am
Hi Nicolas,
The migration from single server to ezdfs cluster should be easy enough with the use of the migration script.
Regarding custom extensions, all depends of what they do. For example if they generate a file that will be stored in the var/ folder then you might want to share those files between the nodes of the cluster (i.e. store in the ezdfs storage). So you will need to rewrite the code that store the files using the ez publish's API.
But anyway, you will want to clone your production server to a test server and test everything thoroughly.
You must be logged in to post messages in this topic!