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 2019/10/26 22:41:00 UTC

[jira] [Commented] (AIRAVATA-3019) SEAGrid Desktop Client changes

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

ASF subversion and git services commented on AIRAVATA-3019:
-----------------------------------------------------------

Commit f674a986a0bff146f814e39f079b25b24dd9b7bb in airavata's branch refs/heads/staging from Marcus Christie
[ https://gitbox.apache.org/repos/asf?p=airavata.git;h=f674a98 ]

AIRAVATA-3019 last job status is most recent


> SEAGrid Desktop Client changes
> ------------------------------
>
>                 Key: AIRAVATA-3019
>                 URL: https://issues.apache.org/jira/browse/AIRAVATA-3019
>             Project: Airavata
>          Issue Type: Task
>            Reporter: Marcus Christie
>            Assignee: Marcus Christie
>            Priority: Major
>             Fix For: 0.19
>
>
> Update the SEAGrid Desktop Client to accommodate group based auth changes.
> h5. TODO
> - [x] specify group resource profile id in config
> -- similar to AIRAVATA-3085
> - -[ ] check group membership instead of roles-
> -- not relevant, SEAGrid DC assumes user has privileges
> - [ ] get last status in array for most recent one
> -- verified this is needed
> -- similar to AIRAVATA-3089
> - [x] setup sftp server in staging environment so that it can be tested
> - [ ] figure out how to integrate SEAGrid desktop builds with download links in Wagtail CMS



--
This message was sent by Atlassian Jira
(v8.3.4#803005)