The following major features are under consideration for ongoing Workbench development:
Priority | Feature | Description |
---|---|---|
Authentication and authorization | Add support for integration with external authentication and authorization systems. This includes adding OAuth/OIDC support; integration with CILogon/COManage and Globus Auth. Support authorization models to enable access to data and other resources. | |
Workbench/Cloud | Ability to install Workbench in commercial cloud environments with storage support. Simplified installation in OpenStack environments. Integration with other orchestration environments (e.g., Swarm). Ability to export services to run in VM or container-based environments. | |
Workbench/HPC | Ability to run analysis developed in Workbench via HPC using standard APIs (Airavata, Agave). Convert Docker containers to Singularity. Login node replacement (i.e., use workbench as parallel resource to HPC system to support development, interactive analysis and visualization. | |
Workbench/Gateway | Ability to develop applications in Workbench and deploy/publish for wider access (TERRA-REF "Shiny" use case), GCMC; Ability to develop and deploy data portals. | |
Container preservation | Zenodo for Dockerhub/Singularity. Provide a centralized and distributed registry/cache specific to scientific/research oriented software that includes DOIs. This came up as a case at CAE Workshop and is not solved by WT. | |
Education and training | Ability to easily "spin up" instances near data for workshops and training; models for creating temporary training accounts; integration with external systems (e.g., map reduce, etc). Casea: PI4, Einstein Toolkit. | |
Private/public data | Support for mounting and publishing data in a variety of formats. Cases: NBI raw/Mongo DB, TERRA BETYdb, ThinkChicago data. Requires permissions model; | |
Batch/Workflow support | Ability to integrate with batch and workflow systems; both via containers and outside. Casea: LIGO, BrAPI, CyVerse, KnowEng | |
Custom catalog/branding | ||
Backup, recovery, failover, monitoring | Improve backup/recovery, failover and monitoring support. | |
Configurable resource limits | Ability to request more resources for interactive sessions from container-based environment (ala JupyterHub "profiles") | |
Integration with Data Portals | Clowder, HubZero, DataVerse, Girder – ability to fulfill DataDNS vision. | |
JupyterHub interoperability | ||
For-fee service | Process for requesting workbench instance for some duration with associated fees. Similar to system used by events group. | |
Administration console | Admin web interface for common functions | |
Usage reporting |