Very good! But in that case, shouldn't the new Zope 2.7 install and startup stuff support it?
It does. It's just that the default setup is still to use a non-ZEOd FileStorage for your main database. But you can change options in the config file to make it use a ZEO ClientStorage. This is in lieu of of requiring you to edit custom_zodb.py as you needed to do in 2.6 and prior.
It's clear that the Zope source distro should support the use of ClientStorage "out of the box". It's not however so clear that the Zope source distro should make it to set up a ZEO server (although it does happen to include the necessary files to run a ZEO server too, it doesn't include a 'zeoctl' or a zeo.conf, etc).
Chris, have you looked at ZEO/mkzeoinst.py? It uses a somewhat simpler approach than the new Zope setup, but it creates a zeoctl script and a zeo.conf configuration file.
That's not to say that it shouldn't be easy to set up a ZEO server, but that making it easy should probably the job of a package other than Zope proper. The right thing to do would be to package up a ZEO server installer separate from Zope 2.7 with a similar kind of buildout, support files, and configuration file. At least that's been my idea so far.
Not needed; it's all there (though far simpler in approach than the Zope installer). --Guido van Rossum (home page: http://www.python.org/~guido/)