Return-Path: X-Original-To: apmail-airavata-dev-archive@www.apache.org Delivered-To: apmail-airavata-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id BFF99CA68 for ; Sat, 15 Nov 2014 21:23:40 +0000 (UTC) Received: (qmail 47991 invoked by uid 500); 15 Nov 2014 21:23:40 -0000 Delivered-To: apmail-airavata-dev-archive@airavata.apache.org Received: (qmail 47940 invoked by uid 500); 15 Nov 2014 21:23:40 -0000 Mailing-List: contact dev-help@airavata.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@airavata.apache.org Delivered-To: mailing list dev@airavata.apache.org Received: (qmail 47930 invoked by uid 99); 15 Nov 2014 21:23:40 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 15 Nov 2014 21:23:40 +0000 X-ASF-Spam-Status: No, hits=1.5 required=5.0 tests=HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of thejaka.amila@gmail.com designates 209.85.218.47 as permitted sender) Received: from [209.85.218.47] (HELO mail-oi0-f47.google.com) (209.85.218.47) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 15 Nov 2014 21:23:14 +0000 Received: by mail-oi0-f47.google.com with SMTP id v63so4369382oia.34 for ; Sat, 15 Nov 2014 13:21:43 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; bh=CzKar2OWGZNZWBBmJU/Yg56zF6admt3JUSJpxy3ojLE=; b=L2qqIffx3r0JjWrdoOG8qdk9P7HGlSd7ZqHzKjfw3n7gi1bKOkqcKkq6zccu9z97hI QtdN/8Wv1iehdM8N+EU6ZxkwhKSALOYPoRtECIMpI6isrl7/b1ErhhmEySoQ2o+FaOS3 aysu5X9JBRDzl4kQasxqLo7pH+EWlKACycs7GYwmNl2Y1Cxc9Jb5ijWtHyx3nPu9EwgV XINEsiFWR1PPPaUHQB78pgbebIPvU16BU02lfcWGJmdxAzO5utD1v9ZZJCYj40w77Ocp S1eTEApAIaVaJaKl+gHHcMi4wAQi+yXi4asanHOPHWnT0uoB3S9AvigCZF5YAp6yD457 lCNw== MIME-Version: 1.0 X-Received: by 10.60.174.16 with SMTP id bo16mr2374065oec.55.1416086503517; Sat, 15 Nov 2014 13:21:43 -0800 (PST) Received: by 10.76.36.162 with HTTP; Sat, 15 Nov 2014 13:21:43 -0800 (PST) In-Reply-To: References: Date: Sat, 15 Nov 2014 16:21:43 -0500 Message-ID: Subject: Re: [DiSCUSS] Hosted RabbitMQ Server for Airavata From: Amila Jayasekara To: dev Content-Type: multipart/alternative; boundary=089e011838ec0374520507ec5557 X-Virus-Checked: Checked by ClamAV on apache.org --089e011838ec0374520507ec5557 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable What about authentication and related security ? (I am not overly familiar with RabbitMQ though) Thanks -Amila On Thu, Nov 13, 2014 at 11:59 AM, Suresh Marru wrote: > Hi All, > > As we get ready for the 0.14 release, one thing which always comes up is > the installation of RabbitMQ. We addressed this for Zookeper by using > embedded server. But thats not a good approach for RabbitMQ server since > its in Erlang (and not in Java, unlike rest of Airavata) and forking of a= n > external process on different operating systems will lead to unpredictabl= e > errors. > > How about we mitigate this pointing the release build to a hosted service= ? > Here are some pros and cons: > > * This will alleviate the installation requirements and will go back to > one click installation. > * Users will not have to worry about downloading and starting up RabbitMQ > server. But can change it to local or other installations in properties > file. > * If a user is trying to use Airavata without having the need for interne= t > connectivity, then they have to have a local installation. > * There is a risk of the service being down and the release being pointed > to a stale service. This can be mitigated by a persistent CName alias whi= ch > points to a hosted server. > * There are popular rabbitmq hosted services [1], [2], [3] but are often > expensive [4] for a community project. > * Few of Airavata active developers (along with me) are part of a downloa= d > airavata project which runs airavata as a service. Within SciGaP project > [1] we could run a persistent service like rabbitmq-service.scigap.org > atleast for near future. > > Given these tradeoff=E2=80=99s and options, any opinions? > > Cheers, > Suresh > > [1] - https://cloud.google.com/solutions/rabbitmq/ > [2] - http://azure.microsoft.com/en-us/documentation/services/service-bus= / > (which claims to interoperate with rabbitmq) > [3] - https://www.cloudamqp.com/ > [4] - https://www.cloudamqp.com/plans.html > [5] - http://scigap.org/ --089e011838ec0374520507ec5557 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
What about authentication and related security ? (I am not= overly familiar with RabbitMQ though)

Thanks
= -Amila

On Thu, Nov 13, 2014 at 11:59 AM, Suresh Marru <smarru@apache.org>= wrote:
Hi All,

As we get ready for the 0.14 release, one thing which always comes up is th= e installation of RabbitMQ. We addressed this for Zookeper by using embedde= d server. But thats not a good approach for RabbitMQ server since its in Er= lang (and not in Java, unlike rest of Airavata) and forking of an external = process on different operating systems will lead to unpredictable errors.
How about we mitigate this pointing the release build to a hosted service? = Here are some pros and cons:

* This will alleviate the installation requirements and will go back to one= click installation.
* Users will not have to worry about downloading and starting up RabbitMQ s= erver. But can change it to local or other installations in properties file= .
* If a user is trying to use Airavata without having the need for internet = connectivity, then they have to have a local installation.
* There is a risk of the service being down and the release being pointed t= o a stale service. This can be mitigated by a persistent CName alias which = points to a hosted server.
* There are popular rabbitmq hosted services [1], [2], [3] but are often ex= pensive [4] for a community project.
* Few of Airavata active developers (along with me) are part of a download = airavata project which runs airavata as a service. Within SciGaP project [1= ] we could run a persistent service like rabbitmq-service.scigap.org atleast for = near future.

Given these tradeoff=E2=80=99s and options, any opinions?

Cheers,
Suresh

[1] - https://cloud.google.com/solutions/rabbitmq/
[2] - http://azure.microsoft.com/en-us/documentatio= n/services/service-bus/ (which claims to interoperate with rabbitmq) [3] - https://www.= cloudamqp.com/
[4] - ht= tps://www.cloudamqp.com/plans.html
[5] - http://scigap.org/

--089e011838ec0374520507ec5557--