Mailing-List: contact airavata-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: airavata-dev@incubator.apache.org
Received-SPF: neutral (nike.apache.org: 129.79.1.188 is neither permitted nor
 denied by domain of raminderjsingh@gmail.com)
From: Raminderjeet Singh <raminderjsingh@gmail.com>
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: multipart/alternative; boundary=Apple-Mail-3--381154990
Subject: Re: Do we really have to automatically registering URLs
Date: Mon, 10 Sep 2012 12:07:12 -0400
In-Reply-To: 
 <CAKq9_6JaGQtHzk9YBRpZifDMJ7jCTcZdTqujK-mKmxERvKCY_Q@mail.gmail.com>
To: airavata-dev@incubator.apache.org
References: 
 <CAKq9_6JaGQtHzk9YBRpZifDMJ7jCTcZdTqujK-mKmxERvKCY_Q@mail.gmail.com>
Message-Id: <6F225F34-7C6E-461A-A08B-544824294D3B@gmail.com>

--Apple-Mail-3--381154990
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii

Big +1 for letting the admin to configure service IP's. We already have =
2 JIRA issues relate to this =
https://issues.apache.org/jira/browse/AIRAVATA-565 and  =
https://issues.apache.org/jira/browse/AIRAVATA-441.=20

Thanks
Raminder


On Sep 10, 2012, at 11:40 AM, Lahiru Gunathilake wrote:

> Hi Devs,
>=20
> We recently had some issues when we deploy airavata in production with
> firewalls and on VMs. We automatically pick the URLs of the services =
using
> Axis2Configuration and get the service names and register them in to
> Registry. I wrote this piece of code since it looks handy to do it in =
that
> way. But I think this is an extra headache we always get when we have =
a
> complex network configuration in our deployment environment.
>=20
> I think to avoid this we can simply ask users to configure four urls =
in
> repository.properties file, we go and register these urls in to =
registry.
> It there are multiple gfac running all will be having same registry =
url so
> we are good to go with out future plans to handle multiple urls.
>=20
> Of course we can find some solutions to pick correct url by validating =
them
> but still we are validating from the same deployment environment, not =
from
> out side world. So I think this is an unnecessary feature since its =
just
> four urls user have to configure.
>=20
> User configure it on repository.properties one time thats it .. if its =
not
> working its deployers fault .. not a fault of Airavata !
>=20
> WDYT ? If you agree I can do this fix in to 0.5 release.
>=20
> Regards
> Lahiru
>=20
> --=20
> System Analyst Programmer
> PTI Lab
> Indiana University


--Apple-Mail-3--381154990--