[Zope] Re: [Plone-developers] the grand reunion
Rudá Porto Filgueiras schrieb: On Fri, Apr 11, 2008 at 1:23 PM, Florian Friesdorf [EMAIL PROTECTED] wrote: Hi Robert, On Fri, Apr 11, 2008 at 04:04:43PM +0200, robert rottermann wrote: hi yuri, when setting up a zope/zeo task and everything was still a bit of a challenge (at least to me) we tended to have everything in one big instance that served some 20 low traffic sites. since then setting up a site with all the tools it needs has become a trivially easy and quick to execute task. we have converted nearly all these sites to have their own instance. I would not do it differently anymore .. Do you have or are there any comparisons for RAM usage of one zope instance containing multiple plone instances vs. multiple zope instances containing a single plone instance only? It will be overkill. ;-) We run all Plone sitess in same instance as possible (plone provider), only creating one data.fs to each Plone Site and tunning cache objects to each site needs. you might be right, is is an overkill when you start. just creating a new folder and a new plone site in it is *so* easy. however, every site has its own lifecycle and tends to call for extra products, adaptations, plone product versions, you name it. every such change affects every site in a one zope/several plone site setup. and even if the change migth be trivial, it can have unwanted side effects for an other site. my experience is: dont do it! robert ___ Zope maillist - Zope@zope.org http://mail.zope.org/mailman/listinfo/zope ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope-dev )
Re: [Zope] Re: [Plone-developers] the grand reunion
I would like to have an easy way to develop without having to be subject to dependencies from other envinroment, minimize the effort to mantain it and focus on doing things :) Maybe not exactly what you are asking for but I recommend you play with buildout a bit - I'm sure you'll appreciate the ease with which you can manage independent installations in a repeatable and easily modifiable way. Is one big zope installation, with multiple instances, well suited for this tasks? Or is better different zope versions? What about the various Data.fs, is better to have them separated by application or by zope envinroment? I mean all the Plone in a single Data.fs or each one in a separated Data.fs? Without further knowing how these sites might be related or not this is hard to answer but often times I prefer to have separate Zope instances (- different ZODBs) for different Plone sites. Even if they share substantial configuration/add-ons etc. Again, using buildout makes it a snap to create and maintain as many Zope instances as you want. And using a common buildout cache they can also mostly share the basic installation. Just my 2 cents, Raphael hi yuri, when setting up a zope/zeo task and everything was still a bit of a challenge (at least to me) we tended to have everything in one big instance that served some 20 low traffic sites. since then setting up a site with all the tools it needs has become a trivially easy and quick to execute task. we have converted nearly all these sites to have their own instance. I would not do it differently anymore .. robert Thanks to all! It seems that a separate zope instance for each plone site is the way to go. Just a question: is it a problem for performance/bottleneck/big python lock? ___ Zope maillist - Zope@zope.org http://mail.zope.org/mailman/listinfo/zope ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope-dev )
[Zope] Re: [Plone-developers] the grand reunion
hi yuri, when setting up a zope/zeo task and everything was still a bit of a challenge (at least to me) we tended to have everything in one big instance that served some 20 low traffic sites. since then setting up a site with all the tools it needs has become a trivially easy and quick to execute task. we have converted nearly all these sites to have their own instance. I would not do it differently anymore .. robert Yuri schrieb: Hi! Actually I've two Plone working envinronment and one zope, each in a different machine: - one, with two zope 2.9 istances (one for developing), running both multiple Plone 2.5 instances - one, with zope 2.9, running multiple Plone 2.5 instances - one, with zope 2.7.9, running zope only applications We have bought big iron hardware now, where I can do almost everything (with a fiber channel network storage, multiple rack servers). tipically, I use one instance to develop, and one to deploy. This mean different zope instances which shares only the base, and having different products. I would like to have an easy way to develop without having to be subject to dependencies from other envinroment, minimize the effort to mantain it and focus on doing things :) Is one big zope installation, with multiple instances, well suited for this tasks? Or is better different zope versions? What about the various Data.fs, is better to have them separated by application or by zope envinroment? I mean all the Plone in a single Data.fs or each one in a separated Data.fs? So, what is the best approach to migrate the three servers? - This SF.net email is sponsored by the 2008 JavaOne(SM) Conference Don't miss this year's exciting event. There's still time to save $100. Use priority code J8TL2D2. http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone ___ Plone-developers mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/plone-developers ___ Zope maillist - Zope@zope.org http://mail.zope.org/mailman/listinfo/zope ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope-dev )
