You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@airavata.apache.org by "Eroma (JIRA)" <ji...@apache.org> on 2015/04/07 21:04:14 UTC

[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

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

Eroma commented on AIRAVATA-1259:
---------------------------------

Tested in http://dev.test-drive.airavata.org/portal/pga/public
When  COMPLETED experiment is cloned Job and task information is not cloned. Tasks and job information only get populated when the newly cloned experiment is launched.

> 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.3.4#6332)