Make it possible to instanciate 1 NEO DB inside an ERP5 instance
authorSaurabh Bansod <saurabh.bansod@nexedi.com>
Thu, 2 Jul 2015 13:22:02 +0000 (13:22 +0000)
committerJulien Muchembled <jm@nexedi.com>
Wed, 8 Jul 2015 10:01:19 +0000 (12:01 +0200)
commitd35284d8739bd25dfa68164bbb44bd8e8d0a1e6a
treeb951999dad9412c31b4110072d244e24f97eccb1
parent6bbb61a88628331e4c83831cea81ffd70042ff2b
Make it possible to instanciate 1 NEO DB inside an ERP5 instance

Before it was only possible to make an ERP5 cluster connect to a NEO cluster
that was instanciated separately, by passing "name" and "master_nodes"
connection parameters in "storage-dict".

For an internal NEO DB, "name" and "master_nodes" is filled automatically
and you must instead pass a "server" dict, with same parameters as in NEO SR.
Currently, a NEO cluster name must be given. Later, we hope to generate a good
name automatically.

All this was implemented by refactoring NEO & ERP5 SR, with common files.
For the ERP5 SR, the root partition also serves as "root" partition for NEO
partitions: in other words, there's no second empty partition.
15 files changed:
software/erp5/instance-erp5-input-schema.json
software/neoppod/cluster.cfg.in
software/neoppod/instance-common.cfg.in [copied from software/neoppod/instance.cfg.in with 71% similarity]
software/neoppod/instance-logrotate-base.cfg.in [moved from stack/erp5/instance-logrotate-base.cfg.in with 100% similarity]
software/neoppod/instance-neo-input-schema.json
software/neoppod/instance-neo-storage-mysql.cfg.in
software/neoppod/instance.cfg.in
software/neoppod/root-common.cfg.in [copied from software/neoppod/cluster.cfg.in with 61% similarity]
software/neoppod/software-common.cfg [copied from software/neoppod/software.cfg with 58% similarity]
software/neoppod/software.cfg
stack/erp5/buildout.cfg
stack/erp5/instance-erp5.cfg.in
stack/erp5/instance-zope.cfg.in
stack/erp5/instance.cfg.in
stack/erp5/logrotate-base.cfg [deleted file]