[one-users] Highly available ONE?

[Claude Noshpitz]

Hello Nebulans,

Wondering if anyone has been thinking about how to make ONE highly available
by running multiple masters cooperatively.

Among other things, this might mean abstracting out the current Sqlite
dependencies to rely on a more "distributable" DB solution (one which could
itself be independently master-slaved or otherwise made HA).  It seems
unlikely that one could finesse HA for Sqlite by e.g. storing its data in a
distributed/redundant filesystem (fancy NFS, Gluster) unless there's really
strong record locking.

Another consideration would involve the consequences of multiple masters
sharing a pool of worker nodes -- perhaps this would "just work" if the
underlying DB was shared, or not.  There's the question of how to manage the
shared VM state in $ONE_LOCATION/var too, but that could be handled with a
robust shared filesystem.

Ideas?  Opinions?

Thanks!

--Claude