RC-03: Install software and/or data on a resource for use by a research community, SPI-07: Enable a research community to install software or data on a resource
Effort and Costs:
Staff Name (Lastname, Firstname)
Effort (person weeks)
Roles or Contributions
Coordinate activity and prepare documentation deliverables
Supply community codes requirements and review deliverables
Ensure that SP integration process includes flagging CSA support, and that helpdesk processes are in place to handle CSA requests.
Ensure that CSA owners have appropriate startup or developer allocation processes available
Setup CSA support (each)
XUP or XCI teams
Implement a way for CSA owners to discover which resources support CSAs
Test CSA process on L1 and L2 SPs
CSA Publishing Design
CSA Developer Documentation
CSA Operations and SP Documentation
CSA Allocations Documentation
by TRR (post)
TRR Baseline* (Shava)
Test Report* (Shava)
Click on "Deliverables" tab for URL.
Planned Launch Date:
Actual Launch Date:
Planned Design Review Date:
Planned Test Readiness Review Date:
Planned Complete Date:
Community Software Areas's (CSAs) have been a part of XSEDE since the TeraGrid days. With Operations, Services Providers, and ECSS document the use case, prepare a capability delivery plan, and launch related activities that deliver a consistent CSA capability.
There are comments for XCI-231 that can be viewed with XSEDE authentication.