As usually happens at the beginning of a release cycle, we've made a big change in trunk that will require slightly more than an ordinary svn update. This one moves from using ZEO/FileStorage to using RelStorage stored in MySQL. This provides a major speed increase.
If you're running the trunk, here's what you have to do:
1) svn up Products, bin and inst
2) Build MySQLdb (upgraded), RelStorage (new), and memcache (new):
$ cd /path/to/inst
$ make mysql-python-install
$ make relstorage-install
$ make python-memcache-install
3) For speed, run zeopack (optional):
$ zeopack -h localhost -p 8100
4) Execute the object store migration script, passing in any necessary options:
$ $ZENHOME/bin/changeObjectStore.py --host localhost --port 3306 --user zenoss --passwd zenoss --db zodb --rootpw=""
(Those are the default options; if you didn't set a root password on MySQL you can probably just use the defaults and pass in no options.)
That's it. Please let me know if you have any questions or problems.
This change is a complete PITA and I really think you should have made a formal proposal to discuss it's implementation.
I use my ZEO's for a range of non-Zenoss back-ends as well and have no intention of RelStorage-ing these. I really hope I'm not expected to set up a separate ZODB mount for my /zport in order to run up Zenoss.
At the very least, this performance enhancement should be optional - preferably opt-in. I suspect that is probably so - excepting of course, it's coming as your standard zeo.conf setting.
Follow Us On Twitter »
||Latest from the Zenoss Blog »||Community||Products||Services||Customers||About Us|
Copyright © 2005-2011 Zenoss, Inc.