airavata-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Marlon Pierce <marpi...@iu.edu>
Subject Re: Make RabbitMQ default AMQP implementation and prerequisites from next release
Date Tue, 03 Mar 2015 13:26:36 GMT
I'm concerned about releasing Airavata with a dependency (Qpid) that we 
probably don't want to support.  I realize we do this with DBs already, 
but that is in part due to licensing, and this seems like a bigger 
maintenance issue.

On 3/2/15 6:15 PM, Danushka Menikkumbura wrote:
> Well I am not sure what the current status of Qpid is but it used to have
> some serious memory leaks, which seemed to be too mysterious to be fixed.
> Therefore if you plan to use Qpid please do a memory profile/load test in
> the first place.
>
> On Mon, Mar 2, 2015 at 4:56 PM, Chathuri Wimalasena <kamalasini@gmail.com>
> wrote:
>
>> +1. I think we discussed to use apache qpid by default.
>>
>> On Mon, Mar 2, 2015 at 4:17 PM, Shameera Rathnayaka <
>> shameerainfo@gmail.com> wrote:
>>
>>> Hi Devs,
>>>
>>> As of now  all the main components(Orchestrator , Workflow Enactment,
>>> GFac and XBaya) depend on RabbitMQ AMQP implementation(Some of this
>>> implementations are in the correspondent feature branch). I think it is
>>> good to make rabbitMQ default from next release. WDYS? , Here we need to
>>> update our airavata-server.properties files in the source and update the
>>> sample wiki which says to enable rabbitMQ by editing property file.
>>>
>>> Thanks,
>>> Shameera.
>>>
>>> --
>>> Best Regards,
>>> Shameera Rathnayaka.
>>>
>>> email: shameera AT apache.org , shameerainfo AT gmail.com
>>> Blog : http://shameerarathnayaka.blogspot.com/
>>>
>>


Mime
View raw message