Last update: July 27, 2020
To manage its allocations processes, XSEDE has developed the XSEDE Resource Allocations System (XRAS). With XRAS, XSEDE handles more than 200 allocation requests at each of its quarterly allocation meetings along with more than 200 Startup, Education, and other requests received continually each quarter.
XRAS was developed as a software-as-a-service (SaaS) tool with the goal of allowing other organizations to leverage XSEDE's investment for the national research computing infrastructure. Since being deployed for XSEDE in 2014, XRAS has been adopted by half a dozen organizations. Most recently, XSEDE leveraged XRAS to support the review of requests being submitted to the COVID-19 HPC Consortium.
In addition to XSEDE, XRAS is now provided via service agreements to three clients, and more clients are ramping up.
The Texas Advanced Computing Center (TACC) is using XRAS to manage allocation requests for the Frontera system.
The Pittsburgh Supercomputing Center (PSC) has begun managing allocation requests for its Anton 2 system via XRAS.
The National Center for Supercomputing Allocations (NCSA) is in the process of deploying XRAS to support its non-XSEDE allocation processes.
NCAR's Earth Observing Lab is using XRAS to manage requests for the NSF-supported Lower Atmosphere Observing Facilities.
NCAR's Computational and Information Systems Lab uses XRAS to manage its university community allocations.
XRAS now supports the ability for ORCID member institutions to post information about allocated projects to your users' ORCID profiles via integration with ORCID for Research Resources. Project metadata includes user, resource, and project details. Through this integration, as the ORCID site notes, "Research resources ... and sponsoring organizations stand to benefit from improved acknowledgement of resource use and a better understanding of the impact of the work undertaken by researchers using them. Resource-hosting organizations can make the reporting process more straightforward and reliable by embedding identifiers in the application process, and by creating and sharing connections between users and resources."
To take advantage of this feature, XRAS clients must also be ORCID members and, for the moment, be able to collect ORCID permissions from their users (outside of XRAS). We are working to enhance XRAS with the ability to collect user authorizations and permissions for you.
To continue improving the system to support the needs of advanced research computing at universities and elsewhere, XSEDE is seeking a small number of campuses interested in piloting an XRAS deployment for their user communities. The pilot effort is designed to support the allocation needs of the campus while helping the XSEDE team understand needs and requirements for new XRAS client organizations.
XRAS provides interfaces and components to support the submission, review, and administration of allocation requests. A variety of submission requirements and policies can be supported by the rules engine. The review component enforces conflicts of interest and allows allocation panel members to view requests, download documents, and enter their reviews. The administrative system provides panel management, tools for meeting logistics and review assignments, email notification capabilities, and award entry and processing functions.
Sites with lightweight allocation procedures can choose not to use the review and panel management features, instead focusing on using XRAS for allocation tracking and basic administration.
A number of features are currently in development to improve the XRAS service for non-XSEDE clients. These features include customizable submission interfaces, integrated reporting capabilities for allocations staff, and a streamlined allocations workflow.
To use XRAS, your site needs to meet only minimal technical requirements. Primarily, the resources to be allocated by your site must be entered into the XSEDE Resource Description Repository (RDR) and your site must be a member of the XSEDE SP Forum at Level 3 or higher. (The main integration requirement for becoming a Level 3 Service Provider is listing your primary resources in the RDR.) XRAS also supports optional integration with your local identity management and authentication system and your local accounting system; XRAS clients also have the option of developing custom submission user interfaces, tailored to their needs and embedded with their organization's web or portal sites.
Last update: July 27, 2020