Executive Summary: A researcher wants to install software on a community resource for use by a research community.
The functionality described in this use case is already 75% supported by the operational components listed here.
The effort required for the IPF publishing instructions review/edit is minimal (~1 day). The effort for the other proposed activity ("Enable researchers/developers to discover where Community Software Areas (CSAs) are available") is harder to estimate because it involves multiple XSEDE teams (user services, XCI, SPs). It is likely to require 2-4 weeks of total effort, with the majority being cross-team coordination and design/implementation of changes to the XSEDE website and/or XUP.
|Component||User facing?||Component’s role in the capability|
|Globus Toolkit GSISSH Client/Server||yes||The XSEDE Single Sign-On Hub uses the GSI-OpenSSH client internally. XSEDE L1/L2/L3 SPs provide GSI-OpenSSH services on their login nodes. Advanced users may install and configure the GSI-OpenSSH client on their own systems and use it directly to login to XSEDE resources, skipping the Single Sign-On Hub.|
|XSEDE Single Sign-On Hub||yes||The researcher logs in to a target resource and installs software into a CSA|
|XSEDE User Portal (XUP)||yes||The researcher discovers whether a target resource already has the desired software using https://portal.xsede.org/software#/|
|XSEDE Website||yes||Researcher identifies one or more XSEDE target resources where the software would be useful to his/her research community using https://www.xsede.org/ecosystem/resources|