You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@airavata.apache.org by Suresh Marru <sm...@apache.org> on 2013/03/23 14:28:17 UTC

Re: [jira] [Created] (AIRAVATA-344) [GSoC] Load balancing Workflow execution

Hi Saminda,

I think this task is confusing. Here we confuse Workflow Interpreter to GFac to load balancing with Workflow to underlying cluster load balancing. Which one are you intending to address here. Having a cluster of GFac's and WI decides which ones to invoke? 

Suresh

On Mar 14, 2012, at 11:44 AM, Saminda Wijeratne (Created) (JIRA) <ji...@apache.org> wrote:

> [GSoC] Load balancing Workflow execution
> ----------------------------------------
> 
>                 Key: AIRAVATA-344
>                 URL: https://issues.apache.org/jira/browse/AIRAVATA-344
>             Project: Airavata
>          Issue Type: New Feature
>            Reporter: Saminda Wijeratne
> 
> 
> Workflows are handed over to the GFac servers in order to be scheduled to be executed. Currently the user have to specify which GFac server should execute this workflow and the GFac server has a primitive scheduling mechanism to schedule the worksflows and its tasks. Large number of job submissions would require intelligent job submission from users end for the executions to yield efficiently. With some effort we should be able to get Airavata itself to perform better scheduling tasks. This can be in several layers.
> 
> GFac server as a cluster: User will submit the workflow execution to a cluster rather than a single GFac server. The cluster will decide which GFac instance is most suitable for the workflow to be scheduled based on some cost parameter.
> Workflow scheduling: The BE should estimate some cost of running a workflow & try to schedule the workflows in a way which will minimize the cost of running all the workflows currently in the queue. 
> Executing services: The BE should determine which implementation of the service to execute for a workflow node given there are more than one candidate.  
> 
> --
> 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
> 
>