community.aegirproject.org

I am in the process of writing a "lightweight" cluster module that would not require syncing files around: it would assume that your favorite sysadmin (probably you) has setup some file-sharing mechanism (NFS or else) that allows Aegir to just assume slaves have /var/aegir on hand.

I am hesitant in extending the existing cluster module, because I need to break backwards compatibility, mostly on small things like variable names and I do not want to bother with the upgrade path.

Right now I have named the new module 'pack' (as in "pack of wolves"), and the idea is that people would be able to migrate over the new module by changing their content types in the database and changing their aliases by hand. But if really nobody is using the current cluster code, I would just go ahead and replace it completely and don't bother with the "pack" name...

So far, I have branched off our quiet 2.x to create the dev-webpack branches on both our main projects. Code is still totally untested. Comments and feedback welcome.