Return-Path: X-Original-To: apmail-airavata-dev-archive@www.apache.org Delivered-To: apmail-airavata-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 466EBFBF7 for ; Fri, 12 Apr 2013 15:30:18 +0000 (UTC) Received: (qmail 87924 invoked by uid 500); 12 Apr 2013 15:30:17 -0000 Delivered-To: apmail-airavata-dev-archive@airavata.apache.org Received: (qmail 87300 invoked by uid 500); 12 Apr 2013 15:30:16 -0000 Mailing-List: contact dev-help@airavata.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@airavata.apache.org Delivered-To: mailing list dev@airavata.apache.org Received: (qmail 86855 invoked by uid 99); 12 Apr 2013 15:30:16 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 12 Apr 2013 15:30:16 +0000 Date: Fri, 12 Apr 2013 15:30:15 +0000 (UTC) From: "Heshan Suriyaarachchi (JIRA)" To: dev@airavata.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Created] (AIRAVATA-823) Add an extension point to Airavata to have pluggable EC2 Scheduling Algorithms MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 Heshan Suriyaarachchi created AIRAVATA-823: ---------------------------------------------- Summary: Add an extension point to Airavata to have pluggable EC2 Scheduling Algorithms Key: AIRAVATA-823 URL: https://issues.apache.org/jira/browse/AIRAVATA-823 Project: Airavata Issue Type: Improvement Components: GFac, XBaya Affects Versions: 0.7 Reporter: Heshan Suriyaarachchi Fix For: 0.9 Let me explain the usecase here. >From Airavata 0.8 onwards, I'm planning to give the Airavata user the flexibility in selecting (optional) a scheduling algorithm when running EC2 workflows. The current trunk has the greedy algorithm and I will be adding a round robin algorithm for the 0.8 release. One value added extension-point would be to let a user (who is not familiar with our codebase) to implement his/her scheduling algorithm (by implementing a set of interfaces). Currently we have these interfaces which the user can use to implement his/her own alogrithm. Then, the Airavata eco-system should support, letting the user drop his/her custom algorithm implementation jar to the Airavata server and select it at runtime. This is something similar to the extension-points that we had at Synapse [1]. If we support this, the user would not have to mess around with the our codebase and they can do their scheduling algorithm implementations independently. [1] - http://synapse.apache.org/Synapse_Extending.html -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira