FYI,

the transport layer, a camel-cellar endpoint, etc are in the Cellar roadmap.
Any contribution is welcome to help us on that ;)

Regards
JB

On 08/17/2011 09:38 AM, Andreas Pieber wrote:
Depending on your requirements and timeframe you have available you have
two options:

As Charles already said: fabric is opensource and has commercial support
(if this is what you're looking for)

Option b is (if you have some knowledge and time to share) to implement
clustering into cellar. While it is not implemented now cellar has the
potentials to do fallback and clustering;

So, as your time allows :-)

Kind regards,
Andreas

On Wed, Aug 17, 2011 at 09:33, Charles Moulliard <[email protected]
<mailto:[email protected]>> wrote:

    Hi Guru,

    If you need this kind of support, then you must considering using Fuse
    Fabric and fabric-camel by example. More info here :
    http://fabric.fusesource.org/

    I have created an example showing How to deploy a project using
    Zookeepeer on 3 differents Karaf instances (= zookeeper agent) and
    camel fabric allows to loadbalance requests between the agents.
    
(https://github.com/fusesource/fabric/tree/master/fabric-examples/fabric-camel-cluster-loadbalancing)

    Regards,

    Charles Moulliard

    Apache Committer

    Blog : http://cmoulliard.blogspot.com
    Twitter : http://twitter.com/cmoulliard
    Linkedin : http://www.linkedin.com/in/charlesmoulliard
    Skype: cmoulliard



    On Wed, Aug 17, 2011 at 9:17 AM, Achim Nierbeck
    <[email protected] <mailto:[email protected]>> wrote:
     > Hi Guru,
     >
     > I think we can bring it to one point for clustering right now.
     > Cellar as it works right now is meant for "farming" so you are
    able to
     > replicate the
     > installation state in your cluster.
     >
     > Right now there is no support for Session Failover as you might
    have expected.
     >
     > Regards, Achim
     >
     > 2011/8/17 Charles Moulliard <[email protected]
    <mailto:[email protected]>>:
     >> Hi Guru,
     >>
     >> As explained by Jean-Baptiste, Karaf Cellar is not at a loadbalancer
     >> nor a fault tolerant solution. Cellar is able to define features,
     >> bundles, properties to be deployed on Karaf instances which are part
     >> of the cellar but Cellar is not able to redirect request to another
     >> cellar instance if one node death. Please, remember, what I
    explain to
     >> you in a previous email.
     >>
     >> Regards,
     >>
     >> Charles Moulliard
     >>
     >> Apache Committer
     >>
     >> Blog : http://cmoulliard.blogspot.com
     >> Twitter : http://twitter.com/cmoulliard
     >> Linkedin : http://www.linkedin.com/in/charlesmoulliard
     >> Skype: cmoulliard
     >>
     >>
     >>
     >> On Wed, Aug 17, 2011 at 8:48 AM, Gnanaguru S
     >> <[email protected]
    <mailto:[email protected]>> wrote:
     >>>
     >>> Hi Jean,
     >>>
     >>> I obviously experienced it. Let me explain you what i did.
     >>>
     >>> I installed karaf and added camel, camel-blueprint to it.
     >>>
     >>> I deployed a simple use case in three cluster ( karaf-cellar
    installed ).
     >>>
     >>> When i killed the root node during the process of the use case.
    then i
     >>> noticed the process was not assigned to other cluster.
     >>>
     >>> Regards
     >>> Guru
     >>>
     >>> --
     >>> View this message in context:
    
http://karaf.922171.n3.nabble.com/Use-case-in-karaf-cellar-tp3260645p3260812.html
     >>> Sent from the Karaf - User mailing list archive at Nabble.com.
     >>>
     >>
     >
     >
     >
     > --
     > --
     > *Achim Nierbeck*
     >
     >
     > Apache Karaf <http://karaf.apache.org/> Committer & PMC
     > OPS4J Pax Web <http://wiki.ops4j.org/display/paxweb/Pax+Web/>
     > Committer & Project Lead
     > blog <http://notizblog.nierbeck.de/>
     >



--
Jean-Baptiste Onofré
[email protected]
http://blog.nanthrax.net
Talend - http://www.talend.com

Reply via email to