Re: Best Practice for Setting up 19 Sites in Plone 4.3

Le 02/08/2014 00:44, Edward Soong a écrit :
> I work at an university school of engineering where they current have
> Plone 3.3.5 serving 19 sites on 1 zope instance using separate Data.fs
> files for each site (ZODB Mounting Point), which is described in this
> support document
> "http://plone.org/documentation/kb-old/multiple-plone-sites-per-zope-instance-using-separate-data-fs-files-for-each-one”
> <http://plone.org/documentation/kb-old/multiple-plone-sites-per-zope-instance-using-separate-data-fs-files-for-each-one%94>.
> It is using collective.recipe.filestorage
>
> (1) I am in the process to upgrade the 19 sites to Plone 4.3.3, but I
> am not certain if 4.3 supports separate Data.fs for each site on 1
> Zope instance.

It's well supported.

> (2) Or should I put 10 sites onto 1 Data.fs? We bought 2 server
> machines, planning to divide up the 19 sites, 10 on one server and 9
> on the other server, to increase web server performance.

You can also. The only advantage is to simplify backup procedures. You
will not increase server performance but their usage ratio.

> If 4.3 does, how do you configure buildout.cfg to support that? (The
> configuration in Plone 3.3.5 fails in 4.3.3). The last release of
> collective.recipe.filestorage was in 2010.

It may need some adjustment. Mount points are ZODB's low level feature
and there's not a lot of changes into decade. We used such
configurations since 2005.

> (3) I also read that zeoserver supports multiple zope instances,
> should I try 19 zone instances?

Yes, that's equivalent to the second proposal. Keep in mind that one
ZODB gives one ZEO Server.

> Any thoughts on these 3 options? Thanks in advance!

There's no better options. It depends how many buildout you want to
manage and how complicated buildout you are able to maintain.
The Unified Installer is quite good and really simple. It's easier to
maintain but imply one data.fs by site. You can make global modification
using patch like for other open source software. It's also easier to use
tools like Ansible or Salt with it.
A customed buildout will fit better your ideas but will be more
complicated to maintain. It will be harder to train someone to help you.

One other method to keep a simple buildout and mutualize the storage is
to use RelStorage (https://pypi.python.org/pypi/RelStorage
http://docs.silvacms.org/3.0/cluster/relstorage.html) in the Unified
Installer buildout.

Regards

-- 
Encolpe DEGOUTE
http://encolpe.degoute.free.fr/
Logiciels libres, hockey sur glace et autres activités cérébrales

------------------------------------------------------------------------------
Infragistics Professional
Build stunning WinForms apps today!
Reboot your WinForms applications with our WinForms controls. 
Build a bridge from your legacy apps to the future.
http://pubads.g.doubleclick.net/gampad/clk?id=153845071&iu=/4140/ostg.clktrk

_______________________________________________
Plone-Users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/plone-users