Thanks Loannis for the description. I think i got the idea of OSGi and i
can see how making Helix OSGi ready can be useful in many applications,
infact Helix itself might benefit by allowing pluggable rebalancers. I
havent played with OSGi and dont think any one from the Helix dev team has
played with this. So we really dont know what it takes to make Helix OSGi
ready. Is this something you can drive, of course we can help you where
ever needed.

I am also assuming that we will have a separate helix-OSGi module within
Helix and thats the only module that might bring in additional dependency
jars from OSGi. I prefer Helix-core to be light weight and not add
additional dependency. Also making Helix OSGi ready does not mean thats the
only way to deploy it.

Let me know if any of my assumptions are wrong.

This surely looks exciting, if you are up for making this happen please
file a jira and I can ask more questions on the jira.

Andrei, we should start a separate discussion thread on Helix and
Provisionr.

thanks,
Kishore G





On Fri, Mar 22, 2013 at 1:31 AM, Ioannis Canellos <[email protected]> wrote:

> Hi Kishore,
>
> I am not sure about the implementation details of it. Are you proposing
> > that you can use Helix as the Orchestration layer for invoking various
> > phases in the life cycles and also manage the states.
> >
>
> This is not exactly what I had in mind.
>
> What I did have in mind is making is making sure that Helix is OSGi ready
> and can be deployed inside an OSGi container. Moreover, I am interested in
> integrating it with Apache Karaf, which is an OSGi runtime that among
> others provides a rich shell and providing helix commands for Karaf shell
> could be something interesting for Karaf and all projects that are built on
> top of Karaf ( e.g. Apache ServiceMix, Apache Provisionsr, Fuse Fabric
> etc). The last (Fuse Fabric) is used to provision and manage distributed
> OSGi runtimes and using Helix there could be really interesting (not sure
> if its going to be a good match yet, but it worths looking into it).
>
>
> --
> *Ioannis Canellos*
> *
>
> **
> Blog: http://iocanel.blogspot.com
> **
> Twitter: iocanel
> *
>

Reply via email to