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] [Updated] (AIRAVATA-3019) SEAGrid Desktop Client changes
Date Mon, 28 Oct 2019 16:36:00 GMT

     [ https://issues.apache.org/jira/browse/AIRAVATA-3019?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Marcus Christie updated AIRAVATA-3019:
--------------------------------------
    Description: 

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
- [x] 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
- [x] figure out how to integrate SEAGrid desktop builds with download links in Wagtail CMS
- [x] how much work to query for accessible app module, group resource profile, accessible
app deployments, etc.?
-- in ExperimentCreateController
--- Need to switch app interface calls to getAccessibleAppModules
--- Need to add group resource profile picker
--- Need to load compute resources with getApplicationDeploymentsForAppModuleAndGroupResourceProfile
-- this seems fairly doable, if time permitting I'll implement this and we won't need a hard
coded group resource profile id
- [ ] Switch to group based auth methods
- [ ] Add a login-desktop to Django like the one in PGA to allow the Desktop client to get
an access token


  was:
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
- [x] 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
- [x] figure out how to integrate SEAGrid desktop builds with download links in Wagtail CMS
- [x] how much work to query for accessible app module, group resource profile, accessible
app deployments, etc.?
-- in ExperimentCreateController
--- Need to switch app interface calls to getAccessibleAppModules
--- Need to add group resource profile picker
--- Need to load compute resources with getApplicationDeploymentsForAppModuleAndGroupResourceProfile
-- this seems fairly doable, if time permitting I'll implement this and we won't need a hard
coded group resource profile id
- [ ] Add a login-desktop to Django like the one in PGA to allow the 


> 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
> - [x] 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
> - [x] figure out how to integrate SEAGrid desktop builds with download links in Wagtail
CMS
> - [x] how much work to query for accessible app module, group resource profile, accessible
app deployments, etc.?
> -- in ExperimentCreateController
> --- Need to switch app interface calls to getAccessibleAppModules
> --- Need to add group resource profile picker
> --- Need to load compute resources with getApplicationDeploymentsForAppModuleAndGroupResourceProfile
> -- this seems fairly doable, if time permitting I'll implement this and we won't need
a hard coded group resource profile id
> - [ ] Switch to group based auth methods
> - [ ] Add a login-desktop to Django like the one in PGA to allow the Desktop client to
get an access token



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

Mime
View raw message