On Wed, Apr 13, 2011 at 15:57, Ioannis Canellos <ioca...@gmail.com> wrote: >> >> Maybe we could start from use cases instead of solutions ? >> > Agree, so let me put things more in a use case format and recap: > > a) I want to have multiple karaf instances running on different hosts and > cooperating with each other, with minimal configuration effort. > b) I want to be able to change the configuration all or some of the nodes, > without having to do so in every single node. > c) 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.
I definitely agree with those requirements. And I think this notion of group is really a key point here. I think we should be able to describe some kind of profile (maybe as simply as a list of features with the related configuration) and associate a profile to a node. I think we should have a description of those profiles available somewhere so that nodes can update themselves according to the profile associated to them. This way, changing the profile would affect all associated nodes. I think having each node pulling the configuration is safer than pulling changes to it. For example, if one node is stopped in your group, you want the changes to be applied when it will come back up, so the description of the wanted state need to be available. > d) 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. I think that would have to be tied to a notion of feature lifecycle that we don't currently have. I don't see many reasons for stopping a single bundle unless you want to stop the feature it belongs too. > e) I want to be able and register a service on a single node and invoke from > other nodes. Something like DOSGi but with more tools and options like > provisioning, loadbalance etc. I'm slightly unsure about that one. I would tend to defer it, as I don't want to step on camel or servicemix toes. The CXF DOSGi could server the purpose and I think things like loadbalanding looks way too much like what camel / servicemix provide. -- Cheers, Guillaume Nodet ------------------------ Blog: http://gnodet.blogspot.com/ ------------------------ Open Source SOA http://fusesource.com
