Thank you Suresh. I will try sticky Nginx.
Thanks also to Alex.
not sure what you mean by implementation [of the allocation of the Zeo
clients]
Yes, I was wondering which is the best way of customizing Buildout for my
case: don't know how to adapt to Plone 4 (blobstorage) the second part of
the following article:
http://plone.org/documentation/kb/multiple-plone-sites-per-zope-instance-using-separate-data-fs-files-for-each-one
I think that the ZODB must be managed by one ZeoServer, even if it is
extended with a few mount-points. Thus, the current scenario would include:
- sticky Nginx
- ZODB with 2-3 mount-points, one per Plone site
- ZeoServer
- at least 2 Zeo clients.
As to the Zeo clients, is the hypothesis below reasonable?
- anonymous user: one client per each semi-critical site, one for all the
other sites
- authenticated user: one client for all sites.
Thank you again, Giovanni
----- Original Message -----
From: "Suresh V." <suresh...@yahoo.com>
To: <setup@lists.plone.org>
Sent: Wednesday, March 02, 2011 2:32 AM
Subject: Re: [Setup] Plone on the cloud: how to keep it simple but modular ?
Giovanni Toffoli wrote:
http://nathanvangheem.com/news/nginx-with-built-in-load-balancing-and-caching
My questions:
- is Nginx + Varnish ok?
1. All you need is nginx. You have the correct reference. sticky nginx
works great.
- how to allocate Zeo clients? per site, class of user, both?
- how to implement the allocation of the Zeo clients?
Use a fixed number of ZEO clients and let nginx with sticky handle the
allocation.
Suresh
_______________________________________________
Setup mailing list
Setup@lists.plone.org
https://lists.plone.org/mailman/listinfo/setup
_______________________________________________
Setup mailing list
Setup@lists.plone.org
https://lists.plone.org/mailman/listinfo/setup
