You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@airavata.apache.org by "ASF subversion and git services (Jira)" <ji...@apache.org> on 2022/05/06 21:29:00 UTC
[jira] [Commented] (AIRAVATA-3576) In the Django portal ability to hide the Computational resource properties such as node, CPU and wall time
[ https://issues.apache.org/jira/browse/AIRAVATA-3576?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17533096#comment-17533096 ]
ASF subversion and git services commented on AIRAVATA-3576:
-----------------------------------------------------------
Commit 2ba4bccc665dbc83ca5b4c15a1a27c072fe37487 in airavata-django-portal's branch refs/heads/develop from Marcus Christie
[ https://gitbox.apache.org/repos/asf?p=airavata-django-portal.git;h=2ba4bccc ]
AIRAVATA-3576 UI setting to control whether to show queue settings for app interface
> In the Django portal ability to hide the Computational resource properties such as node, CPU and wall time
> ----------------------------------------------------------------------------------------------------------
>
> Key: AIRAVATA-3576
> URL: https://issues.apache.org/jira/browse/AIRAVATA-3576
> Project: Airavata
> Issue Type: New Feature
> Components: Django Portal
> Reporter: Eroma
> Assignee: Marcus Christie
> Priority: Major
>
> In Django Portal per application at Create experiment, Edit experiment, and in cloned experiment view the computational resource properties should be hidden from the gateway user.
> The experiments will be submitted with the default values defined for the resource.
> Users should be able to select the computational resource, if there are multiple resources but should not be able to select the number of nodes, CPUs, or walltime.
> This resource property hiding should be at the application level.
> This information needs to be hidden from create experiment, edit experiment and experiment summary but should be visible in experiment statistics for gateway admins.
--
This message was sent by Atlassian Jira
(v8.20.7#820007)