Support clustered deployment for Zanata Platform

Description

To run well on top of platforms like OpenShift, Zanata needs to support high availability, with automatic fail-over of the application when a node goes down, without affecting availability of the service as a whole.

This will require moving state out of the Zanata process (singletons) into eg replicated Infinispan caches, or into the database.

Data stored in the file system may need to be moved (perhaps to a database), or if we use shared filesystems, we need to ensure that all nodes co-operate when using the filesystem.

Lower priority: centralised management of logging, performance stats (JavaMelody), performance enhancements (eg eliminating some replicated caches, or accepting reduced/eventual cache consistency).

Status

Assignee

Unassigned

Reporter

Sean Flanigan

Labels

Tested Version/s

None

Priority

High

Epic Name

Clustering
Configure