[AIRAVATA-964] Add single job support as a first class simple Apache Airavata Execution

• Type: Epic
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 0.12
• Component/s: Airavata Client, GFac
• Labels: Architecture
• Epic Name: Develop an Airavata Orchestrator
• Assignee: Unassigned
• Reporter: Suresh Marru
• Created: 10/Dec/13 01:43
• Updated: 14/Jan/16 16:59
• Resolved: 14/Jan/16 16:59

Description

Currently Airavata supports single jobs by wrapping it as a single node task within a workflow. This wrapping is justified if workflow is the predominant use of Airavata and single application execution is a rare usage pattern. As Airavata is getting more usage, the simple execution but for large number of invocations and diverse applications is getting more widely used.

Providing a first class way of a simple application execution will reduce the overhead in creating and managing workflows. But this takes away all the orchestration capabilities provided by the Workflow Interpreter. This Epic is to discuss a new component to Airavata which provides based job orchestration while persisting the request state to registry so the application management component (GFac) can be stateless and recover the job from a frequently checkpointed state from the registry

Sub-Tasks

• Changing registry to support orchestrator registry functionality: Resolved
• Creating orchestrator-service and orchestrator-core components: Resolved
• Implement the embeddedGFAc job submitter to orchestrator: Resolved
• Incorporate orchestrator changes with GFAC to store statuses: Resolved
• Implement pulling information and submitting to gfac embedded mode: Resolved
• Clone a created experiment in Orchestrator to launch on different host: Resolved
• Create a Orchestrator Thrift file: Closed