We've been using Zope 2.51 on RH 7.3. It's been exceptionally stable and easily handles our workload. We are now about to refactor the system, add new features, add multiple hardware servers, some with ZEO front-ends, go to an multiple instance organization, to scale up for another order of magnitude or two of users. We are having to rethink system security (e.g., SSL), backup strategies, and add fail-soft support. If we are going to migrate to another Zope release, now would be a good time. What advice would you give. Zope 2.6.1 would be the obvious choice although if Zope 2.7.X will be released soon it might be another possibility. Any advice? hidden gotchas? release schedule intelligence? Thanks.
If we are going to migrate to another Zope release, now would be a good time. What advice would you give. Zope 2.6.1 would be the obvious choice although if Zope 2.7.X will be released soon it might be another possibility.
Any advice? hidden gotchas? release schedule intelligence?
Zope 2.6 series is good, esp. with regard to caching. But: I've had a few problems with moving old ZODBs (originating at 2.3 or so) to 2.6.1 from 2.5.1. If you're doing something similar, make sure that your testing of the new version really hits the server hard, or you won't expose the problem until you're live. Which is bad. If you do run into this, well, I don't know how to fix it yet. Someday I'll export/import everything to a new ZODB (possibly on DirectoryStorage) and see it that works. I expect it will. Also, some ZClasses have problems with the move, but that (and the solution) is well documented. On the list, at least. Other than that, I've found 2.6.1 to be a fine release. As to 2.7, well, I wouldn't anticipate it. Sure, it'll come out the day you deploy 2.6.1, but that's just how it goes. --jcc
On Fri, Apr 25, 2003 at 11:23:55AM -0700, Dennis Allison wrote:
If we are going to migrate to another Zope release, now would be a good time. What advice would you give. Zope 2.6.1 would be the obvious choice although if Zope 2.7.X will be released soon it might be another possibility.
Any advice? hidden gotchas? release schedule intelligence?
One big hidden gotcha with 2.6.1: DON'T PACK YOUR FILESTORAGE. there is a known bug that can cause data loss. As if to add insult to injury, the fsrecover.py that ships with 2.6.1 does not work. I got fsrecover.py from current CVS (2.6 branch) and it seems to work OK. on zodb-dev list there has been talk of releasing a Zope 2.6.2 to address some of the zodb problems. No release date mentioned. -- Paul Winkler http://www.slinkp.com
On Friday 25 April 2003 8:40 pm, Paul Winkler wrote:
On Fri, Apr 25, 2003 at 11:23:55AM -0700, Dennis Allison wrote:
If we are going to migrate to another Zope release, now would be a good time. What advice would you give. Zope 2.6.1 would be the obvious choice although if Zope 2.7.X will be released soon it might be another possibility.
Any advice? hidden gotchas? release schedule intelligence?
One big hidden gotcha with 2.6.1: DON'T PACK YOUR FILESTORAGE. there is a known bug that can cause data loss.
That bug has been present since at least 2.5, possibly earlier. -- Toby Dickenson http://www.geminidataloggers.com/people/tdickenson
participants (5)
-
Dennis Allison -
J Cameron Cooper -
Lennart Regebro -
Paul Winkler -
Toby Dickenson