[
https://issues.apache.org/jira/browse/AIRAVATA-1008?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13907514#comment-13907514
]
Saminda Wijeratne edited comment on AIRAVATA-1008 at 2/20/14 9:32 PM:
----------------------------------------------------------------------
This is relating to current GFac interface : org.apache.airavata.gfac.cpi.GFac
IMO it would make sense to change,
public boolean submitJob(String experimentID) throws... to
public void submitTask(String TaskID) throws...
Functions to add
cancelTask(...)
But do we need a restartTask(...)?
Do we have a realtime notification on GFacTask status changes? This is
important for the workflow interpreter since it is inefficient for the
interpreter to poll the registry and wait for status changes to trigger its
node executions.
was (Author: samindaw):
This is relating to current GFac interface : org.apache.airavata.gfac.cpi.GFac
IMO it would make sense to change,
public boolean submitJob(String experimentID) throws... to
public void submitTask(String TaskID) throws...
Functions to add
cancelTask(...)
But do we need a restartTask(...)?
> Craft the GFac CPI
> ------------------
>
> Key: AIRAVATA-1008
> URL: https://issues.apache.org/jira/browse/AIRAVATA-1008
> Project: Airavata
> Issue Type: Sub-task
> Reporter: Suresh Marru
>
> GFac is not directly exposed from Airavata API but will invoked by
> Orchestrator and Workflow Interpreter. The goals for the GFac CPI is to
> expose functions to manage application execution. These include methods for
> execution, termination and recovery of applications.
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
