airavata-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Marlon Pierce (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (AIRAVATA-1283) local host is hard coded in all the thrift clients
Date Wed, 11 Jun 2014 15:32:02 GMT

    [ https://issues.apache.org/jira/browse/AIRAVATA-1283?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14027886#comment-14027886
] 

Marlon Pierce commented on AIRAVATA-1283:
-----------------------------------------

It worked ok for me.  I used 

patch -p1 < 0001-AIRAVATA-1283-Added-support-for-hostname-in-all-serv.patch 

> local host is hard coded in all the thrift clients 
> ---------------------------------------------------
>
>                 Key: AIRAVATA-1283
>                 URL: https://issues.apache.org/jira/browse/AIRAVATA-1283
>             Project: Airavata
>          Issue Type: Bug
>          Components: Airavata Client, Airavata Orchestrator
>    Affects Versions: 0.12
>         Environment: mac
>            Reporter: Lahiru Gunathilake
>             Fix For: 0.12
>
>         Attachments: 0001-AIRAVATA-1283-Added-support-for-hostname-in-all-serv.patch
>
>
> In all the places each thrift client is hard coded with host and some places with port
too. In this case even though these are different thirft services these cannot be hosted in
two different machines.
> I think this is a bad practice and unnecessary limitation. Ideally we should read the
ip from ip property and ports should be configurable.
> any thrift service can be removed from airavata by removing server list in airavata-server.properties.



--
This message was sent by Atlassian JIRA
(v6.2#6252)

Mime
View raw message