[
https://issues.apache.org/jira/browse/AIRAVATA-2152?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15596164#comment-15596164
]
Marcus Christie commented on AIRAVATA-2152:
-------------------------------------------
I discussed with [~smarru] what to do with the UI, whether to only show to
"campus users" or not. We [had previously
discussed|https://issues.apache.org/jira/browse/AIRAVATA-2152?focusedCommentId=15571994&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-15571994]
using roles to hide/show this information, but now that seems like overkill,
especially since it has implications for backend authorization, but this isn't
an authorization problem, just a UI problem. So I'm not going to pursue the
"campus user" role idea.
Here are my notes on what we discussed:
* In the UI, change Resource => Accounts
* also in the UI, add some text or a help link describing why/when a user would
setup the personal compute/storage accounts
* maybe add a flag on compute resources for whether they support individual
accounts, community accounts, or both and then only allow users to configure
accounts on compute resources that support individual accounts
* for now we'll wait on feedback from users about the user interface
> UI for to add compute resource/storage allocations
> --------------------------------------------------
>
> Key: AIRAVATA-2152
> URL: https://issues.apache.org/jira/browse/AIRAVATA-2152
> Project: Airavata
> Issue Type: Bug
> Components: PGA PHP Web Gateway
> Reporter: Marcus Christie
> Assignee: Marcus Christie
>
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
