Karaf clustering requirements

Here is the list of requirements as they have been expressed so far in the discussions in the mailing lists. In order to keep them as close as possible to the actual user requirements, they are expressed more like user stories>

• As a user I want to have multiple karaf instances running on different hosts and cooperating with each other, with minimal configuration effort.
  • Minimal / zero configuration implies autodiscovery, however the discovery mechanism should not be limited to multicast as its not allowed to Cloud environments (EC2 etc).
  • To avoid the management overhead configuration and provisioning on each node need be able to be applied to other nodes, but without having exact "clones" of the same instance.
  • To be able to organize the cluster,groups of nodes could share a "profile" that will encapsulate the clustering configuration and through which the role of each node could be specified.
  • It would be nice to have to have provisioning tools for the "profiles" so that profiles can be create/edited and assigned to nodes.

• I want to be able to change the configuration on all or some just of the nodes, without having to do so in every single node.
  • We need to implement a mechanism through which nodes of the same "profile" can share the same configuration.

• I want to be able to add a feature repository on all or just a group of nodes, without having to do so in every single node.
  • We need to implement a mechanism through which nodes of the same "profile" can share the same feature repositories
  • We need to implement a mechanism through which nodes of the same "profile" can share the same feature states.

• I want to be able to install/start/stop a bundle on all or just a group of nodes, without having to do so in every single node.
  • This somehow overlaps with the feature sharing, however since the use of features is optional, it would be nice if the same functionality could be provided for plain bundles.