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-InSPIRE:MS108 core services

From EGIWiki
Jump to navigation Jump to search
EGI Inspire Main page

Notes to contributors

Assessment: (Provide an assessment of the delivery of services over the past year from a managerial perspective; highlight positive areas and areas for improvement; do not include future plans; text should be roughly 1-2 paragraphs)

Score: (assign a numerical score from 1 to 5 with a succinct explanation of what needs to be improved to increase your score – remove numerical description references upon completion) 1 = An unacceptable level of service was delivered

2 = A level of service that was below expectations was delivered

3 = An acceptable service level has been delivered

4 = A level of service that exceeded expectations was delivered, but there is scope for even further improvement

5 = An excellent service has been delivered that should be considered as best practice

Table 4: EGI Global task assessment:Core services
# Name Assessment Score How to Improve
# Core services Migrating Core Grid Services from other partners to GRNET/AUTH has been more difficult than initially anticipated, due to technical barriers, lack of clear documentation and the apparent inability the reach all the site administrators through the NGI channels. Sites were slow to to act on configuration changes and in the case of the DTEAM VO it took almost 3 months for all sites to change their configuration to use the new VOMS services, while the whole process from starting the service migration until the service was fully migrated, took almost 6 months. During this time following up with sites has been a almost a full time job.

Although the level of funding is sufficient for operating Core Grid Services for EGI, it can prove to be insufficient to support also the process of migrating complex core services with pre-existing data from other partners.

4 The migration process of core services from other partners to GRNET/AUTH is a one time process for each service. The communication between the global service operators and the site administrator have to go through the NGI channels, which should be responsible for properly inform their sites. Also after a core service is operational, the COD should be the responsible entity for following up with sites in order to make sure that they take the necessary actions.