airavata-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Marcus Christie (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (AIRAVATA-2980) Experiment clone
Date Thu, 21 Feb 2019 21:21:00 GMT

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

Marcus Christie commented on AIRAVATA-2980:
-------------------------------------------

I typoed the Jira issue number in the commit message for this one:

https://gitbox.apache.org/repos/asf?p=airavata-django-portal.git;h=4cf6092

> Experiment clone
> ----------------
>
>                 Key: AIRAVATA-2980
>                 URL: https://issues.apache.org/jira/browse/AIRAVATA-2980
>             Project: Airavata
>          Issue Type: Sub-task
>            Reporter: Marcus Christie
>            Assignee: Marcus Christie
>            Priority: Major
>
> Details:
>  - unlike PGA which displays a modal for the user to select the project to clone into,
just clone in the same project if writeable or the most recently used project or the first
writeable project. User can change the project in the experiment editor.
> TODO
>  - [x] Copy input files into directory for cloned experiment. But, the input files may
no longer be in gateway storage so need to keep going if one or more are missing. Register
data products for all of these.
>  - [x] On userConfigurationData, update
>  -- experimentDataDir
>  -- storageId
>  - [x] UI: clone button should wait for clone to succeed and then redirect to editing
the cloned experiment
>  - [x] UI: allow cloning from experiment summary, experiment list
>  - [x] Testing: make sure that if cloning user doesn't have access to Group Resource
Profile or deployment on the compute resource that those are unselected in the ExperimentEditor



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Mime
View raw message