airavata-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Supun Kamburugamuva <supu...@gmail.com>
Subject Re: Do we really have to automatically registering URLs
Date Mon, 10 Sep 2012 15:56:01 GMT
You can keep the current solution and give precedence to property file
configurations as well.

Thanks,
Supun..

On Mon, Sep 10, 2012 at 11:40 AM, Lahiru Gunathilake <glahiru@gmail.com> wrote:
> Hi Devs,
>
> 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.
>
> 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.
>
> 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.
>
> User configure it on repository.properties one time thats it .. if its not
> working its deployers fault .. not a fault of Airavata !
>
> WDYT ? If you agree I can do this fix in to 0.5 release.
>
> Regards
> Lahiru
>
> --
> System Analyst Programmer
> PTI Lab
> Indiana University



-- 
Supun Kamburugamuva
Member, Apache Software Foundation; http://www.apache.org
E-mail: supun06@gmail.com;  Mobile: +1 812 369 6762
Blog: http://supunk.blogspot.com

Mime
View raw message