Alert.png The wiki is deprecated and due to be decommissioned by the end of September 2022.
The content is being migrated to other supports, new updates will be ignored and lost.
If needed you can get in touch with EGI SDIS team using operations @ egi.eu.

Difference between revisions of "RA policy survey"

From EGIWiki
Jump to navigation Jump to search
Line 66: Line 66:
| NGI_PL/PL-Grid
| NGI_PL/PL-Grid
| Marcin Radecki  
| Marcin Radecki  
| Q1: There is no single document for the NGI.  
| Q1: There is no single document for the NGI. Sites have freedom in deciding which request to support. Their decision is mainly based on value of scientific outcome promised in the application.
| Q2: Sites are multidisciplinary. Resources can be used by people affiliated with a Polish research or education organization. In practice if a foreign researcher want to use our resource he/she needs to find a collaborator sufficiently affiliated.
| Q2: Sites are multidisciplinary. Resources can be used by people affiliated with a Polish research or education organization. In practice if a foreign researcher want to use our resource he/she needs to find a collaborator sufficiently affiliated.
| Q3: NGI_PL requires acknowledgements in scientific publication in a form "this TODO"
| Q3: NGI_PL requires acknowledgements in scientific publication in a form "this TODO"

Revision as of 11:52, 19 August 2014

Main EGI.eu operations services Support Documentation Tools Activities Performance Technology Catch-all Services Resource Allocation Security


EGI Resource Allocation menu:




Local polices regarding EGI Resource Allocation process

Why

On July OMB (see minutes) Resource Allocation team got an action to contact NGIs to find out the situation of the local policies in order to understand obstacles in taking part in EGI Resource Allocation process. The process goal is to put EGI Customers and Resource Providers closer together in order to reach agreement on using resources. It does not mean collecting resources by EGI.eu and claiming management rights over it.

Scope

Whenever we refer to "resource allocation" we mean allocation of resources integrated with EGI.

The survey is meant to be filled out by both NGI and site managers.

Survey

Identification - Site/NGI Name, Name/Surname

Q1: What is the resource allocation policy document at your NGI/site and who defines it? (document specifying who can be supported, to what amount of resources, etc.)

Q2: Are there any specific requirements regarding who (what scientific domain etc.) can apply for resources? (including foreign scientists)

Q3: Are there any requirements for accounting of used resources e.g. acknowledgements in publications.

Q4: Who is in charge to make decisions about resource allocation requests at your site/NGI? (Site Manager)

Q5: What system your site/NGI uses for handling resource allocation requests? (face to face/paper/web/other)

Q6: What is the frequency of submiting/handling the requests and how long does it take to handle it? (on-demand/weekly/monthly/yearly/other)

Q7: Is it possible to share current resource allocation at your site/NGI? (i.e. how many core/CPU hours are given to customers)

Q8: What main obstacles do you see to include your resources in EGI Resource Allocation process? https://wiki.egi.eu/wiki/Resource_Allocation


Site/NGI Name Name/Surname Q1 Q2 Q3 Q4 Q5 Q6 Q7 Q8
NGI_PL/PL-Grid Marcin Radecki Q1: There is no single document for the NGI. Sites have freedom in deciding which request to support. Their decision is mainly based on value of scientific outcome promised in the application. Q2: Sites are multidisciplinary. Resources can be used by people affiliated with a Polish research or education organization. In practice if a foreign researcher want to use our resource he/she needs to find a collaborator sufficiently affiliated. Q3: NGI_PL requires acknowledgements in scientific publication in a form "this TODO" Q4: Site manager. Some allocations can be done by PL-Grid operator. Q5: Web system developed by PL-Grid. Q6: On-demand. For simple requests they are handled within one day. For milion-hour requests up to two weeks. Q7: Yes it is. Q8: No obstacles. We already take part.