SourceForge : View Wiki Page: ResourceAllocation

Search Wiki Pages Project: IPG Wiki > ResourceAllocation > View Wiki Page

wiki2171: ResourceAllocation

Resource Allocation Policies and Procedures

A description of the resource allocation policies and procedures of the five member grids

	DEISA	EGEE	NAREGI	OSG	TeraGrid	WestGrid
Policy Available	Y	Y	Y	Y	Y	Y
Policy Locatable	N	N	N	Y/N	Y	Y
Scope	User aimed to guide access requests	Registering a community with EGEE, both resource providers and users	Resources offered by providers (9 computer centers)	Description of opportunistic utilisation of other members resources	Guidance for a PI who wishes to obtain time on TeraGrid Resources	Guidance for a PI who wishes to obtain time (more than default) on WestGrid (or Compute Canada (CC)) resources.
Users	Project based, a project has no upper or lower limit on number of participants, starting to deal with community support, FP7 projects etc	Individuals may only participate as part of a virtual organisation	Individual user must be part of a virtual organisation	Individual user must be part of a virtual organisation	1 allocation per PI, multiple projects to be distributed internally how they wish, US led projects only, no minimum size	PIs can apply for a National Allocation and a local (WestGrid) allocation. On WestGrid they may only have 1 allocation per PI, but that can span multiple systems.
Criteria	Academically reviewed 12 month project allocation, “Chosen on the basis of innovation potential, scientific excellence”, annual competition	No view on the scientific merits of the VO taken centrally. EGEE doesn’t own resources, relying on local policies	Undefined	Assumed VO is donating resources or associated with a partner institution, fully locally controlled access to VO	Locally reviewed Startup or Education <30000 SU Peer Reviewed Research. “to enhance scientific discovery.” Quarterly competition	RAC allocations required if PIs require a "large" allocation. Allocations given based on quality of science, need and availability of resources.
Allocation process	Resource access granting to a preselected ‘most suitable resource’ by allocation committee, following national evaluation @ stage 1	No allocation given directly by EGEE other than seed resources Resource allocation Group for allocation of seed and some brokering functionality	Resource selection made by a user in workflow or by brokering functionality in NAREGI superscheduler	Opportunistic utilisation of other members resources except for scheduled production runs, no further information	Resource selection made by user during application, an extra criteria, overall review by Resource Allocations Committee	Users can specify a preference for a system on which they would like to run their jobs, but the WestGrid RAC reserves the right to make allocates on the most appropriate system given technical requirements and availability of resources.
Units of Allocation	Standardised CPU-core-hours, internal exchange rates	Unlisted, no current measure since not dealing with user-resource relationship	resource unit (#cpu and walltimelimit) made by a user in workflow	Currently undefined in specific units	Service Units defined which have been benchmarked to 1hr of TG1 resource (HP linpack)	CPU hours that can be used continuously on a given system (these are implemented as targets not actual CPU hours).
Portals and Gateways	(Portal) No explicit reference other than technical team will explore user access mechanism possibilities	Support for specific portals (tools rather than community specific), P-GRADE, GENIUS and RESPECT program	NAREGI portal operated by a virtual organisation	Gateways	Science Gateways are one of the approved research allocation requests that can be made. A separate ‘How to write a successful bid is produced”	No explicit formal policy, but technical team will explore user access mechanism possibilities

Initial Alignment

Projects and/or virtual organisations
- Consider in the longer term allocation of resources within both EGI dependant on measurable criteria? NGI already doing this in places for example
- Current direct VO to resource centre relationship skews towards large VO
- Users must be able to work out what resources they need beforehand
- Communities cannot be individually reviewed (DEISA)
Consider (please!)
- common name
- common structure where possible of the policy documents
- common location for policy document
- common focus, user community or resource provider etc

Longer term issues

Charging for utilisation
- NGI resources will come from shared functionality resource operating under internal business models,
- users must be able to show proof of ability to pay where necessary
Co-allocation, new user communities requiring both HTC & HPC,
- Common allocation units required
- Must always be dependant on most stringent requirements
Data only users,
- specific mentions of data allocation etc

Data Allocation Policies

	DEISA	EGEE	NAREGI	OSG	TeraGrid	WestGrid
Is data separately defined within policy document	N	N	N	N	Y	Y
Can the allocation of data be Separate Allocation process	N	N/A	N	N/A	Y	Y
Required information during application	N	N/A	N/A	N/A	Size(data and Community), Importance of the data, Type of Data, Connection or not to a compute allocation, Means of access	Same as TeraGrid
Storage System Types available to users	GPFS	SRM	gFarm	SRM	SRB, Database, GPFS	GPFS, SRM (some groups run other data managers eg: iRods)
Data Type handled within the allocation	File	File	File	File	File, Relational, Collection	File

Show Details