Two zeo clusters on the same OSX server...?

4 messages

Finlay Boo () Two zeo clusters on the same OSX server...?

Reply Threaded

I am currently getting to grips with buildout installs as I make the next version of our intranet.

Using buildout seems to be a good move towards a good disaster recovery in terms of being able to redeploy a site in the event of hardware failure (providing you have Data.fs backups of course). The only problem I have with it is when installing an egg that goes on to create problems, it's not necessarily clear as to how to get back to the previous install. I can look at the requires.txt in the EGG-INFO and determine what to delete but, of course, it isn't necessarily clear that the dependency has been installed for that particular product (if that makes sense). SVN would probably help, but I'm currently working/ developing on my local machine.

Anyway, I digress...

The production server that our intranet runs on is OSX and I'm currently developing the new site on my local MacBook but at some point I'll obviously be looking to go live with my dev and I would like some advice about doing this.

The current 3.1.7 live build is configured with a zeo server & 4 zope clients (all on the same box) running behind Apache.

Is it possible/ likely that I will be able to intsall a new 3.2.2 Plone zeo cluster (from the installer) onto the same box without affecting the current site?

Then I can add my buildout file and fine tune as required before asking Apache to point to the new 3.2.2.

Any thoughts?

Jim Biggs ()

RE: [Setup] Two zeo clusters on the same OSX server...?

Reply Threaded

Some javascript/style in this post has been disabled (why?)

If you wish to get back to a previous install – i.e. one that does not have an egg that you installed and no longer want/need, just rerun your buildout without that egg. As long as the egg uninstalls gracefully, it will be removed. The uninstalled egg will, however, still appear in your eggs directory and your zmi products directory – not an issue. I do suggest that before rerunning a buildout that removes an egg that you first delete any objects you created relating to that egg from your plone site – i.e. delete any objects from your plone site and then uninstall the product for that egg from our plone site.

You can easily have multiple clusters per zope. They will all be using the same zope resources – e.g. the eggs are all available, but do not have to be installed in the plone sites.

Regards… Jim

From: Finlay Boo (via Nabble) [mailto:[hidden email]]
Sent: Friday, July 10, 2009 9:05 AM
To: Jim Biggs
Subject: [Setup] Two zeo clusters on the same OSX server...?

View message @ http://n2.nabble.com/Two-zeo-clusters-on-the-same-OSX-server...--tp3236531p3236531.html
To start a new topic under Installation, Setup, Upgrades, email [hidden email]
To unsubscribe from Installation, Setup, Upgrades, click here.

Finlay Boo () RE: [Setup] Two zeo clusters on the same OSX server...?

Reply Threaded

Thank for your reply, Jim.

Only recently started getting to grips with buildout but I've found that where eggs have 'broken' my site (i.e. I get 'Couldn't adapt' type errors) then amending and re-running buildout didn't seem to be enough. I had to delete last added products and their dependencies.

Also, I'm not really after multiple clusters per zope. I would like two separate clusters on one box whereby one is the current intranet is running as it is now (ie not with buildout) and my new cluster (added with installer/ buildout) doesn't interfere with it whilst I configure. Does that make sense?

Jim Biggs ()

RE: [Setup] Two zeo clusters on the same OSX server...?

Reply Threaded

Some javascript/style in this post has been disabled (why?)

Take a look at the README.txt for the unifiedinstaller.

QUOTE:

Note that you may run install.sh repeatedly for the same target so long

as you either use a different installation method or specify different

instance names. Installations to the same target will share the same Python

and egg/download cache.

--instance=instance-name

Use to specify the name of the operating instance to be created.

This will be created inside the target directory.

Default is 'zinstance' for standalone, 'zeocluster' for ZEO.

Thus, install a new cluster:

# ./install.sh zeo --instance=zeocluster2

Assuming your first cluster used the default name (zeocluster), executing the command above will install a second cluster in your ZEO, named zeocluster2

Regards… Jim

From: Finlay Boo (via Nabble) [mailto:[hidden email]]
Sent: Friday, July 10, 2009 10:39 AM
To: Jim Biggs
Subject: RE: [Setup] Two zeo clusters on the same OSX server...?

View message @ http://n2.nabble.com/Two-zeo-clusters-on-the-same-OSX-server...--tp3236531p3236677.html
To start a new topic under Installation, Setup, Upgrades, email [hidden email]
To unsubscribe from Installation, Setup, Upgrades, click here.