Executive Summary: A science gateway developer or application developer needs to enable an application to submit and manage jobs on remote high-performance computing (HPC) or high-throughput computing (HTC) resources. Application examples include: a web application (e.g., science gateway), a workflow system (e.g., Galaxy, Pegasus, Kepler), a campus job queueing service, or a high-throughput system (Condor glide-ins).
No effort is proposed at this time.The functionality described in this use case is fully supported by the operational components listed here, with only a few minor gaps that will not be addressed at this time.
|Component||User facing?||Component’s role in the capability|
|AMIE||no||A mechanism used by XSEDE and Level 1 and 2 SPs to share project group membership information between XCDB and local authorization systems.|
|Genesis II||yes||Provide the user interface for submitting and managing jobs on XSEDE L1 resources. May be installed on end user systems, campus systems, science gateway systems, or XSEDE login servers.|
|UNICORE||yes||Provides both thick client and command line interface to submitting and managing jobs on XSEDE L1 resources. May be installed on end user systems, campus systems, science gateways systems, or XSEDE login servers.|
|UNICORE Basic Execution Service (BES)||no||Provide the server interface for submitting and managing jobs on XSEDE L1 resources that are accessed via the Genesis II or UNICORE clients.|
|XSEDE Central Database (XCDB)||no||Provides a database of allocated user projects and project groups that define the users who are authorized to submit jobs to specific resources.|