You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@airavata.apache.org by "Lahiru Gunathilake (Created) (JIRA)" <ji...@apache.org> on 2012/04/10 17:19:18 UTC
[jira] [Created] (AIRAVATA-358) Integrate GFac with XBaya to run in
embedded mode
Integrate GFac with XBaya to run in embedded mode
-------------------------------------------------
Key: AIRAVATA-358
URL: https://issues.apache.org/jira/browse/AIRAVATA-358
Project: Airavata
Issue Type: New Feature
Components: GFac, XBaya
Environment: Mac
Reporter: Lahiru Gunathilake
Fix For: 0.4-INCUBATING
Integrating GFac API in to Workflow interpreter will help users to run the GFac core inside Workflow Interpreter. So we avoid another service call from Interpreter to GFac. This is configurable in Interpreter service side. Client has to send the myproxy data and trusted cert location to the backend.
This will initially tested using the AiravtaClient API later we need to support this to work out of the box with XBaya GUI.
Lahiru
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Closed] (AIRAVATA-358) Integrate GFac with XBaya to run in
embedded mode
Posted by "Suresh Marru (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AIRAVATA-358?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Suresh Marru closed AIRAVATA-358.
---------------------------------
Assignee: Lahiru Gunathilake
The emebedded invocation is working reliably.
> Integrate GFac with XBaya to run in embedded mode
> -------------------------------------------------
>
> Key: AIRAVATA-358
> URL: https://issues.apache.org/jira/browse/AIRAVATA-358
> Project: Airavata
> Issue Type: New Feature
> Components: GFac, XBaya
> Environment: Mac
> Reporter: Lahiru Gunathilake
> Assignee: Lahiru Gunathilake
> Fix For: 0.4-INCUBATING
>
>
> Integrating GFac API in to Workflow interpreter will help users to run the GFac core inside Workflow Interpreter. So we avoid another service call from Interpreter to GFac. This is configurable in Interpreter service side. Client has to send the myproxy data and trusted cert location to the backend.
> This will initially tested using the AiravtaClient API later we need to support this to work out of the box with XBaya GUI.
> Lahiru
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (AIRAVATA-358) Integrate GFac with XBaya to run
in embedded mode
Posted by "Lahiru Gunathilake (Resolved) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AIRAVATA-358?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Lahiru Gunathilake resolved AIRAVATA-358.
-----------------------------------------
Resolution: Fixed
I have committed the initial features which we can invoke a GFac service with embedded mode by invoking from AiravataClient.
Lahiru
> Integrate GFac with XBaya to run in embedded mode
> -------------------------------------------------
>
> Key: AIRAVATA-358
> URL: https://issues.apache.org/jira/browse/AIRAVATA-358
> Project: Airavata
> Issue Type: New Feature
> Components: GFac, XBaya
> Environment: Mac
> Reporter: Lahiru Gunathilake
> Fix For: 0.4-INCUBATING
>
>
> Integrating GFac API in to Workflow interpreter will help users to run the GFac core inside Workflow Interpreter. So we avoid another service call from Interpreter to GFac. This is configurable in Interpreter service side. Client has to send the myproxy data and trusted cert location to the backend.
> This will initially tested using the AiravtaClient API later we need to support this to work out of the box with XBaya GUI.
> Lahiru
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira