Community Building Use Cases

XSEDE's original model (described in the Scientific Computing and Scientific Data use case areas) was to provide enhanced computing services to a modest set of highly focused research projects. But XSEDE is always exploring ways to help larger portions of the research community. The use cases in this area describe ways that XSEDE serves a broader community of researchers and scientists, both by offering services that can be used by a wider range of researchers and also by providing opportunities for new service providers to reach the XSEDE community.


Campus Bridging:

These use cases describe how campus information technology (IT) administrators and campus-based research projects: (a) treat XSEDE's resources as extensions of their campus environments, (b) offer services at their campuses to others in the XSEDE community, and (c) deliver new services to their campuses that leverage XSEDE’s experiences and solutions.

(15 use cases)
Use Case ID Title Use Case Description
CB-01 InCommon-based Authentication
CB-02 Share the XSEDE “environment” with campus resources
CB-03 Remote desktop services for researchers
CB-04 Access campus research data from XSEDE resources
CB-05 Workflow automation combining XSEDE and campus resources
CB-06 Sharing computational facilities among campuses
CB-07 Support for commercial service providers
CB-08 Use XSEDE SSO with campus login servers
CB-09 Access an XSEDE-hosted research data collection from campus
CB-10 Synchronize research data between campus and XSEDE resources
CB-11 Archive research data on an XSEDE resource
CB-12 Setup monitoring and usage reporting for a campus HPC resource
CB-13 Provide a simple interface to access any of the high-throughput computing queues available to a campus
CB-14 Submit tasks to any of the high-throughput computing queues available to a campus
CB-15 Develop an application or gateway that submits tasks to any of the high-throughput computing queues available to a campus


Community Infrastructure:

The XSEDE system is explicitly intended to be open and extensible: a "community infrastructure." Unlike a stand-alone product, XSEDE provides a framework for delivering research services and applications. In order to use this framework, community members (application developers, service providers, campus IT administrators) must be able to access details about the system’s design, implementation status, and the driving user needs.

Note: In these use cases, the terms “service” and “service provider” are used broadly. Any of the following would be examples of “services” if they are shared with researchers via XSEDE: a computer system, a website or web-based application, a computer system with a specific software application installed for use, a high-capacity data storage device, a long-term data archiving service, a virtual machine (IaaS) host, a software repository, or an identity provider.

(11 use cases)
Use Case ID Title Use Case Description
CI-01 Access system information
CI-02 Manually publish system information
CI-03 Automate changes to system information
CI-04 Publish current and desired system capabilities, their availability, and their implementation status
CI-05 Discover current and desired system capabilities, their availability, and their implementation status
CI-06 Rate the priority or quality of a community need or contribution
CI-07 Discuss a community activity
CI-08 Conduct an engineering review of a community contribution
CI-09 Discover and inspect system capabilities currently under development
CI-10 Discover and review engineering documents for a specific capability or component
CI-11 Manage the source code, documentation, and installable packages for a capability


Federation and Interoperation:

How XSEDE can contribute to scientific projects that already make use of other cyberinfrastructure resources.

(1 use cases)
Use Case ID Title Use Case Description
FI-01 A scientist who is trying to utilize as many resources as possible


OSG/LHC Integration:

This set of use cases was contributed to XSEDE by the ATLAS project: one of several scientific teams working with experimental data generated by the Large Hadron Collider (LHC) at CERN. The use cases were heavily influenced by Open Science Grid (OSG) architectural concepts. These combined use cases were a proposal for how to make XSEDE resources behave similarly to OSG's Compute Elements (CEs) and Storage Elements (SEs), and thus add XSEDE resources to the set of services available to OSG Virtual Organizations (VOs). The XSEDE-1 Architecture & Design team felt that these use cases, as currently written, were too closely tied to the one-of-a-kind LHC instrument, and too prescriptive of a specific implementation to be useful in the XSEDE foundational architecture. Though they are not recognized as a well-understood way to use the XSEDE system, they may serve both as a basis for understanding what OSG-based projects expect from a system and as a starting point for documenting how XSEDE can be used by projects that already use OSG. The Federation & Interoperation use cases, which are accepted as well-understood XSEDE use patterns, resulted from generalizing these OSG/LHC-specific use cases.

(6 use cases)
Use Case ID Title Use Case Description
FCI-01 VO authentication (myProxy services)
FCI-02 Pilot job submission (set up CE)
FCI-03 Software installation (CVMFS)
FCI-04 Data management (set up SE)
FCI-05 Set up full PanDA site (incl. DB access)
FCI-06 Use as ATLAS production site


Research Coordination:

Beyond supporting individual research projects, the XSEDE system can also serve as a gathering point for researchers who share common research topics or methods. The use cases in this area describe how researchers can use XSEDE to organize themselves as research communities and coordinate their activities for the greater good.

(4 use cases)
Use Case ID Title Use Case Description
RC-01 Participate in a research discussion forum
RC-02 Manage usage within an allocation
RC-03 Install software on a resource for use by a research community
RC-04 Find where a specific application or service is available within the system


Science Gateways:

Research communities use XSEDE and XSEDE resources to power their "science gateways," supporting the specialized needs of research fields, sub-fields, and joint initiatives. Science gateways are shared applications--most often web-based--that are used by groups of researchers with similar needs. Each gateway is developed and operated by one or more leaders in the research field, who applies for an XSEDE allocation to serve the community. Gateways may also help researchers with their own XSEDE allocations to use XSEDE resources by providing a more customized, user-friendly interface.

(6 use cases)
Use Case ID Title Use Case Description
SGW-01 Science Gateway user authentication and identity management
SGW-02 Science Gateway community file transfers
SGW-03 Science Gateway community execution management
SGW-04 Data movement between gateway users' desktops/laptops and XSEDE resources
SGW-05 Science Gateways Resource Information Management
SGW-06 Estimate when a submitted job is likely to be finished


Service Provider Integration:

XSEDE system features that allow Service Providers (SPs) to integrate their resources with the rest of the XSEDE system.

(8 use cases)
Use Case ID Title Use Case Description
SPI-01 Resource integration console
SPI-02 Guided resource discovery
SPI-03 View all resource information
SPI-04 Access resource information from an application
SPI-05 Active account information
SPI-06 Emergency account suspension
SPI-07 Enable a research community to install software on a resource
SPI-08 Register availability of a specific application or service for use