You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@airavata.apache.org by "Marcus Christie (JIRA)" <ji...@apache.org> on 2019/06/19 19:57:00 UTC

[jira] [Commented] (AIRAVATA-3074) Share both application deployment and group resource profile with the user group you want to use them

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

Marcus Christie commented on AIRAVATA-3074:
-------------------------------------------

Some ideas for helping admins understand what is shared:
* add controls for filtering application catalog by compute resource and user group. Listed application are executable by that user group on that compute resource.
* for an application deployment, list groups (or group resource profiles) that can execute the application. If no groups can execute it display a warning

> Share both application deployment and group resource profile with the user group you want to use them
> -----------------------------------------------------------------------------------------------------
>
>                 Key: AIRAVATA-3074
>                 URL: https://issues.apache.org/jira/browse/AIRAVATA-3074
>             Project: Airavata
>          Issue Type: Sub-task
>          Components: Django Portal
>    Affects Versions: 0.18
>            Reporter: Eroma
>            Assignee: Marcus Christie
>            Priority: Major
>
> 1. For gateway users to use a particular resource the group resource profile that contains the profile needed to be shared with that user/user group.
> 2. Even then if the deployment of an application is not shared, then users will not be able to submit jobs to the shared resource for that application.
> 3. So the deployment also needed to be shared.
> 4. If not for system level validations, have unavoidable messages to inform this.



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