Community Software Area Request

Home > User Info > Software > Community Software Area Request

The Community Software Area (CSA) is available for the installation of executables and libraries that will be used by a community of users. A CSA provides a software maintainer with a consistent, backed up location for software at multiple TeraGrid sites, for example $TG_COMMUNITY/my_physics_application.

CSAs are intended to reduce the use of home directories to install shared community applications, libraries, scripts, etc.

The software in CSAs is maintained by users and is not guaranteed to be in any particular level of readiness. While software in a CSA should be accessible by a group, safe programming practices suggest that developers set access permissions such that only authorized users may replace or modify software.

Additional functionality can be provided to a community through the use of SoftEnv keys. SoftEnv is a tool that makes it easy for users to modify Unix shell environment variables as necessary to make software available. To request a SoftEnv key that defines an environment for users making use of the software in the requested CSA, please send email to the Help Desk listing which environment variable definitions should be included in the key definition.

Sites will accommodate requests based on available disk space.

To request community space on GPFS-WAN, fill out the GPFS-WAN request form instead of (or in addition to) this form.

Please complete all fields before submitting.
1.	First Name
2.	Last Name
3.	Duration of need
4.	Approximate disk space needed
5.	Community directory name A TG_COMMUNITY/community-name directory will be created on all requested platforms. Please specify a preferred Unix directory name for the community-name.
6.	Group member(s) Enter all usernames for the directory owner and group members at each of the sites where a CSA is requested. The owner account must exist at each site. Only existing accounts will be added to the group as a result of submitting this form. NOTE: The first username listed will become the directory owner.
7.	Community directory owner email Email address of TG_COMMUNITY/community-name directory owner.
8.	Community member email addresses Other email addresses of usernames in section 6.
9.	Requested TeraGrid sites For site specifications see: Compute and Visualization Resources list TeraGrid Resources Catalog for customized views TeraGrid Systems Monitor on Resources tab of User Portal NOTE: The owner of the directory specified in section 5 must have user accounts on all the requested TeraGrid sites. Add accounts via the User Portal. (Log in to the portal and fill out the Add/Remove Users form in the My TeraGrid tab.)	IU e1350 (Big Red) NCSA IA-64 (Mercury) SGI Altix (Cobalt) Xeon Cluster (Tungsten) IBM p690 (Copper) Condor Pool (Radium) PSC Altix 4700 (Pople) Cray XT3 (Big Ben) Purdue Common area between IBM SP and Linux areas Separate IBM SP and Linux clusters areas SDSC IA-64 SDSC BlueGene SDSC p655 (DataStar) SDSC p690 (DataStar) TACC Sun Constellation Cluster (Ranger) Cray-Dell Linux Cluster (Lonestar) Sun Large-Scale Visualization (Maverick) UC/ANL Common area between IA-32 and IA-64 architectures Separate IA-32 and IA-64 areas
	The requesting PI agrees to respect the quotas set by each TeraGrid Resource Provider, to be responsible to both ETF and to community members for the content placed into the area, and to cooperate with ETF in supporting the users.
10.	Short Description of Project: (please also include reason(s) why normal scratch space and mass storage are insufficient for your needs)