airavata-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Pamidighantam, Sudhakar V" <>
Subject RE: Separate Thrift services- Code restructure
Date Tue, 28 Oct 2014 21:04:09 GMT
I am starting to look at Airavata with a background of having used an old snapshot in paramchem
Is there a place I can go to learn the current organization of the development.


From: Shameera Rathnayaka []
Sent: Tuesday, October 28, 2014 3:56 PM
To: dev
Subject: Re: Separate Thrift services- Code restructure

+1 for merging Workflow service with Orchestrator,
we are not get any advantage by keeping those two as separate services.


On Tue, Oct 28, 2014 at 4:35 PM, Raminderjeet Singh <<>>
I need to move workflow sever/client out out API server to remove extra dependencies on workflow
model. I am going to move workflow server and client to orchestrator server and can get rid
of server part as next step.


On Tue, Oct 28, 2014 at 3:49 PM, Suresh Marru <<>>
+ 1.

I think we can leave out the workflow service and its probably best to embedded it with orchestrator,
since there is so much overlap. So that leaves 3 services:

API Server - Client
Orchestrator Server -Client
GFac Server - Client


On Oct 28, 2014, at 3:32 PM, Raminder Singh <<>>

> Hi All,
> I am fixing AIRAVATA-1471 to create separate distributions for all the Thrift services
in Airavata so that we can run all in separate JVMs and dockerize (<>)
the servers. In this exercise, i found we don’t have client stubs for several components
in separate artifacts like Orchestrator Client is part of Orcherstrator Service, GFAC client
is part of Orcherstator-Core, Workflow server and client is part of Airavata API server and
client. To be consistent with API server and reduce maven dependency tree, i am going to create
airavata— <component>—stubs package and add the component client to that project.
I need to move the code and changed dependencies etc. Please let me know if there are any
objections. If not i will go ahead tomorrow and make the change and commit them after testing.
> Thanks
> Raminder

Best Regards,
Shameera Rathnayaka.

email: shameera AT<> , shameerainfo AT<>
Blog :
View raw message