Allow for installation on partially clustered instances
-------------------------------------------------------
Key: MAGNOLIA-2697
URL: http://jira.magnolia-cms.com/browse/MAGNOLIA-2697
Project: Magnolia
Issue Type: Improvement
Components: core, updatemechanism
Affects Versions: 4.0.1
Reporter: Jan Haderka
Assignee: Philipp Bärfuss
When creating partially clustered Magnolia instances, installation is
cumbersome. In case of clustering "config" workspace only, other then first
installed cluser node will assume installation was already done and will
therefore not bootstrap content to other workspaces and not extract templates
and other files to local FS either. In case of clustering any other workspace,
installation will fail as soon as other then first installed node tries to
install/bootstrap content into such workspaces (which was already filled while
installing first cluster node) since it assumes installation was not yet
performed.
We need to think of mechanism how to configure the clustered instances or to
make it easy to discover clustered workspaces and act during installation as
appropriate.
Current workaround is to in first case replicate necessary content for other
workspaces and for FS manually and in second case to remove any offending
bootstrap files from the module on other then fist cluster node prior to
installing such a node.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.magnolia-cms.com/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
----------------------------------------------------------------
For list details see
http://www.magnolia-cms.com/home/community/mailing-lists.html
To unsubscribe, E-mail to: <[email protected]>
----------------------------------------------------------------
