airavata-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Suresh Marru (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (AIRAVATA-1259) When cloning an experiment we should decide which information to clone, which to obtain from the user at the time of clone and which information to drop
Date Fri, 23 May 2014 15:29:02 GMT

    [ https://issues.apache.org/jira/browse/AIRAVATA-1259?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14007242#comment-14007242
] 

Suresh Marru commented on AIRAVATA-1259:
----------------------------------------

I agree, we should not be cloning job information. Probably even change the method name to
cloneExperimentConfiguration($experimentID, $newExpName, $newExpDescription)

> When cloning an experiment we should decide which information to clone, which to obtain
from the user at the time of clone and which information to drop
> --------------------------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: AIRAVATA-1259
>                 URL: https://issues.apache.org/jira/browse/AIRAVATA-1259
>             Project: Airavata
>          Issue Type: Improvement
>    Affects Versions: 0.12
>            Reporter: Eroma
>
> When cloning an experiment we should decide which information to clone, which to obtain
from the user at the time of clone and which information to drop.
> 1. Meta data such as exp name, description, etc... should be obtained from the user
> 2. configurations sch a  CPU count, wall time, node count, resource, etc... should be
cloned
> 3. job & task related data, errors, etc.. should be dropped



--
This message was sent by Atlassian JIRA
(v6.2#6252)

Mime
View raw message