airavata-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Chathuri Wimalasena (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 Thu, 22 May 2014 18:03:02 GMT

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

Chathuri Wimalasena commented on AIRAVATA-1259:
-----------------------------------------------

Hi Eroma, 

Cloning is just making a copy of existing experiment. I'm not sure whether we should allow
users to update even metadata. They can always use updateExperiment if they want to change
the metadata. 

> 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