Difference between revisions of "RA policy survey"
(→Survey) |
|||
Line 51: | Line 51: | ||
<br> | <br> | ||
{| | {| cellspacing="0" cellpadding="5" border="1" width="80%" | ||
|- | |- | ||
! width="300" | NGI Name | ! width="300" | NGI Name | ||
Line 332: | Line 332: | ||
| 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. | | 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 publications. | | Q3: NGI_PL requires acknowledgements in scientific publications. | ||
| Q4: Site manager. Some allocations can be done by PL-Grid operator. | | Q4: Site manager. Some allocations can be done by PL-Grid operator. | ||
| Q5: Web system developed by PL-Grid. | | Q5: Web system developed by PL-Grid. | ||
Line 450: | Line 450: | ||
|- | |- | ||
| ROC_CANADA | | ROC_CANADA | ||
| | | Di Qing | ||
| Q1: | | Q1: There is not central policy, and site defines it individually. | ||
| Q2: | | Q2: No. | ||
| Q3: | | Q3: No | ||
| Q4: | | Q4: Site Manager | ||
| Q5: | | Q5: face to face/email <br> | ||
| Q6: | | Q6: Not clear | ||
| Q7: | | Q7: No | ||
| Q8: | | Q8: The resources are dedicated. | ||
|- | |- | ||
| ROC_LA | | ROC_LA | ||
Line 485: | Line 485: | ||
<br> | <br> | ||
{| | {| cellspacing="0" cellpadding="5" border="1" width="80%" | ||
|- | |- | ||
! width="300" | Site Name | ! width="300" | Site Name | ||
Line 498: | Line 498: | ||
! width="200" | Q8 | ! width="200" | Q8 | ||
|- | |- | ||
| DESY-HH / NGI_DE | | DESY-HH / NGI_DE | ||
| Andreas Gellrich | | Andreas Gellrich | ||
| Q1: There is know general resource allocation policy document but sites <br>have commitments according to MoUs with the VOs. | | Q1: There is know general resource allocation policy document but sites <br>have commitments according to MoUs with the VOs. | ||
| Q2: No, but is intended that the VOs which demand resources fit the <br>scientific portfolio of the site. | | Q2: No, but is intended that the VOs which demand resources fit the <br>scientific portfolio of the site. |
Revision as of 08:45, 17 September 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, Contact (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
NGI Name | Contact (Name/Surname) | Q1 | Q2 | Q3 | Q4 | Q5 | Q6 | Q7 | Q8 |
---|---|---|---|---|---|---|---|---|---|
NGI_AEGIS | Antun Balaz | Q1: There is no single allocation policy document. Sites regulate their allocations individually. | Q2: No. | Q3: Yes, acknowledgment to NGI is requested. | Q4: Site manager(s). | Q5: Face to face/e-mail. | Q6: Weakly to yearly. | Q7: Yes, smaller fractions. | Q8: Funding for providing of additional resources to share, since the current ones are mostly dedicated. |
NGI_ARMGRID | Q1: | Q2: | Q3: | Q4: | Q5: | Q6: | Q7: | Q8: | |
NGI_BA | Mihajlo Savic | Q1: No central policy, sites regulate independently. | Q2: No. | Q3: No. | Q4: Site manager. | Q5: Face/e-mail. | Q6: On demand. | Q7: No. | Q8: Existing resources are dedicated. Currently there is no local funding for expansion of resources. |
NGI_BG | Q1: | Q2: | Q3: | Q4: | Q5: | Q6: | Q7: | Q8: | |
NGI_BY | Q1: | Q2: | Q3: | Q4: | Q5: | Q6: | Q7: | Q8: | |
NGI_CH | Sigve Haug | Q1: There is no single allocation policy document. Sites regulate their allocations individually. | Q2: No. | Q3: No. | Q4: The site managers. | Q5: Face to face. | Q6: Weekly to yearly. | Q7: Smaller fractions can be shared, O(10%) | Q8: Current resources are dedicated. Without scientific partnership or payment, usage from outside will hardly get accepted. |
NGI_CHINA | Q1: | Q2: | Q3: | Q4: | Q5: | Q6: | Q7: | Q8: | |
NGI_CYGRID | Q1: | Q2: | Q3: | Q4: | Q5: | Q6: | Q7: | Q8: | |
NGI_CZ | Q1: | Q2: | Q3: | Q4: | Q5: | Q6: | Q7: | Q8: | |
NGI_DE | Q1: | Q2: | Q3: | Q4: | Q5: | Q6: | Q7: | Q8: | |
NGI_FI | Q1: | Q2: | Q3: | Q4: | Q5: | Q6: | Q7: | Q8: | |
NGI_FRANCE | Jerome Pansanel | Q1: A draft of single allocation policy document is available, but it is not complete. Therefore, Sites regulate their allocations individually. | Q2: No. | Q3: Yes, acknowledgment to NGI is requested. | Q4: The site managers. | Q5: Face to face or e-mail | Q6: On-demand. | Q7: Sites are currently not publishing the share. It may be feasible using the CECapability Glue tag. | Q8: Current resources are dedicated. Without scientific partnership or payment, usage from outside will hardly get accepted. |
NGI_GE | Q1: | Q2: | Q3: | Q4: | Q5: | Q6: | Q7: | Q8: | |
NGI_GRNET | Q1: | Q2: | Q3: | Q4: | Q5: | Q6: | Q7: | Q8: | |
NGI_HR | Q1: | Q2: | Q3: | Q4: | Q5: | Q6: | Q7: | Q8: | |
NGI_HU | Q1: | Q2: | Q3: | Q4: | Q5: | Q6: | Q7: | Q8: | |
NGI_IBERGRID | Q1: | Q2: | Q3: | Q4: | Q5: | Q6: | Q7: | Q8: | |
NGI_IL | Q1: | Q2: | Q3: | Q4: | Q5: | Q6: | Q7: | Q8: | |
NGI_IT | Q1: | Q2: | Q3: | Q4: | Q5: | Q6: | Q7: | Q8: | |
NGI_MARGI | Q1: | Q2: | Q3: | Q4: | Q5: | Q6: | Q7: | Q8: | |
NGI_MD | Q1: | Q2: | Q3: | Q4: | Q5: | Q6: | Q7: | Q8: | |
NGI_ME | Q1: | Q2: | Q3: | Q4: | Q5: | Q6: | Q7: | Q8: | |
NGI_NDGF | Q1: | Q2: | Q3: | Q4: | Q5: | Q6: | Q7: | Q8: | |
NGI_NL | Q1: | Q2: | Q3: | Q4: | Q5: | Q6: | Q7: | Q8: | |
NGI_PL | 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 publications. | 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. |
NGI_RO | Q1: | Q2: | Q3: | Q4: | Q5: | Q6: | Q7: | Q8: | |
NGI_SI | Q1: | Q2: | Q3: | Q4: | Q5: | Q6: | Q7: | Q8: | |
NGI_SK | Q1: | Q2: | Q3: | Q4: | Q5: | Q6: | Q7: | Q8: | |
NGI_TR | Q1: | Q2: | Q3: | Q4: | Q5: | Q6: | Q7: | Q8: | |
NGI_UA | Q1: | Q2: | Q3: | Q4: | Q5: | Q6: | Q7: | Q8: | |
NGI_UK | Q1: | Q2: | Q3: | Q4: | Q5: | Q6: | Q7: | Q8: | |
AfricaArabia | Q1: | Q2: | Q3: | Q4: | Q5: | Q6: | Q7: | Q8: | |
AsiaPacific | Q1: | Q2: | Q3: | Q4: | Q5: | Q6: | Q7: | Q8: | |
CERN | Q1: | Q2: | Q3: | Q4: | Q5: | Q6: | Q7: | Q8: | |
IDGF | Q1: | Q2: | Q3: | Q4: | Q5: | Q6: | Q7: | Q8: | |
ROC_CANADA | Di Qing | Q1: There is not central policy, and site defines it individually. | Q2: No. | Q3: No | Q4: Site Manager | Q5: face to face/email |
Q6: Not clear | Q7: No | Q8: The resources are dedicated. |
ROC_LA | Q1: | Q2: | Q3: | Q4: | Q5: | Q6: | Q7: | Q8: | |
Russia | Q1: | Q2: | Q3: | Q4: | Q5: | Q6: | Q7: | Q8: |
Site Name | Contact (Name/Surname) | Q1 | Q2 | Q3 | Q4 | Q5 | Q6 | Q7 | Q8 |
---|---|---|---|---|---|---|---|---|---|
DESY-HH / NGI_DE | Andreas Gellrich | Q1: There is know general resource allocation policy document but sites have commitments according to MoUs with the VOs. |
Q2: No, but is intended that the VOs which demand resources fit the scientific portfolio of the site. |
Q3: Nothing explicit. | Q4: Site manager | Q5: e-mail / personal contacts | Q6: on-demand | Q7: All VOs use one common Grid infrastrucuture. Typically 2/3 are guaranteed to MoU partners. |
Q8: We are already well saturated. |
Q1: | Q2: | Q3: | Q4: | Q5: | Q6: | Q7: | Q8: | ||
Q1: | Q2: | Q3: | Q4: | Q5: | Q6: | Q7: | Q8: | ||
Q1: | Q2: | Q3: | Q4: | Q5: | Q6: | Q7: | Q8: | ||
Q1: | Q2: | Q3: | Q4: | Q5: | Q6: | Q7: | Q8: | ||
Q1: | Q2: | Q3: | Q4: | Q5: | Q6: | Q7: | Q8: | ||
Q1: | Q2: | Q3: | Q4: | Q5: | Q6: | Q7: | Q8: | ||
Q1: | Q2: | Q3: | Q4: | Q5: | Q6: | Q7: | Q8: | ||
Q1: | Q2: | Q3: | Q4: | Q5: | Q6: | Q7: | Q8: | ||
Q1: | Q2: | Q3: | Q4: | Q5: | Q6: | Q7: | Q8: |