Hi Suresh,
I will try.
Thanks
Amila
On Fri, Feb 28, 2014 at 1:46 PM, Suresh Marru wrote:
> Good point Amila, thats needs to be done too.
>
> Will you have some time before or after the release to change the sample
> gateway to use the API. That will help you critique the API hands-on.
>
> Su
Hi Lahiru,
Thanks for your suggestions, Ok sure i am happy to be the first user :) , I
started to build the trunk and i got a test failure in
airavata-orchestrator-service module are you still working on this
component?. Meanwhile I will go through the doc and validate the content
and steps.
Tha
Hi Shameera,
One important thing is once we provide the samples and howto's (if we are
planning to do so), you can review them and test our sample code.
In this release we are not providing any UI to use so everything has to be
done programatically. Programming against the airavata-api is the mos
Hi Suresh/Marlon,
Thanks for your suggestions, i will work on integration test and
documentation parts for now.
As Suresh suggest i will check the possibility of using thrift native JS
support which i think the best way to support JS client API. If we use the
JS-API layer which wrap the thrift ja
Hi Shameera,
Your help will be greatly in need. As Amila and Marlon pointed out, integration
tests will be great. But even better might be to start integrating with the
JS-API. So far, we have been focusing on Java and PHP clients for thrift which
will use the socket communications. We stayed o
Definitely detailed testing of the release candidates will be useful as
0.12 will be significantly different from 0.11. Fixing and improving
the integration tests (and, as a precursor, demanding better
documentation so that you know what to do) is also very important.
Other suggestions for Shamee
Hi All,
Is there anyway that i can participate this release? some task may be, As
this is first release after i got my airavata committership i would like to
help you guys :)
Thanks,
Shameera.
On Sat, Mar 1, 2014 at 12:16 AM, Suresh Marru wrote:
> Good point Amila, thats needs to be done too.
Good point Amila, thats needs to be done too.
Will you have some time before or after the release to change the sample
gateway to use the API. That will help you critique the API hands-on.
Suresh
On Feb 28, 2014, at 1:41 PM, Amila Jayasekara wrote:
> I assume that integration tests will be mo
I assume that integration tests will be modified according to the new API
and they will be fixed.
Thanks
Amila
On Fri, Feb 28, 2014 at 1:29 PM, Marlon Pierce wrote:
> Here is a summary of stuff that is needs to be wrapped up before we have
> a release candidate. I'm posting this for the recor
Here is a summary of stuff that is needs to be wrapped up before we have
a release candidate. I'm posting this for the record.
1. End to end testing of Registry, Orchestrator, GFAC, and Monitoring:
Chathuri and Lahiru are committing here.
2. GFAC Monitoring Info deposited to Registry: Raminder i
10 matches
Mail list logo
