EGI Operations EGI Feedback on removing the
Description: EGI Operations EGI Feedback on removing the Information provider from WLCG storage resources V. Spinoso A. Paolini P. Solagna Outline Operational motivations Public relations motivations Effort allocated on BDII development (cloud)
Related Topics
Download Presentation
"EGI Operations EGI Feedback on removing the" is the property of its rightful owner. Permission is granted to download and print the materials on this website for personal, non-commercial use only, and to display it on your personal computer provided you do not modify the materials and that you retain all copyright notices contained in the materials. By downloading content from our website, you accept the terms of this agreement.
Presentation Transcript
slide1. EGI Operations EGI Feedback on removing the Information provider from WLCG storage resources V. Spinoso – A. Paolini – P. Solagna<br>
slide2. Outline Operational motivations
Public relations motivations
Effort allocated on BDII development (cloud)
Assessment needed WLCG Information System Evolution Task Force meeting – 16 Jun 2016<br>
slide3. Installed capacity EGI needs BDII on storage resources to assess the total installed storage capacity
NGIs and EGI as a whole need to know the installed capacity, to justify national and European investments in the infrastructure
BDII serves well the purpose, publishing information on used/total
NGIs need those information for different purposes (funding, accounting, advertising)<br>
slide4. Installed capacity EGI and NGI reports need to retrieve the installed capacity
Per site
Per VO
Per NGI
Per EGI<br>
slide5. Effort to maintain the BDII EGI hosts hundreds of VOs
Many of the VOs are very small
Using the BDII helps with automatic VO management
EGI hosts hundreds of sites
Many of the sites are small
Effort available for site administration is usually small
Sites are usually happy with the BDII because it is simple to maintain
PIC difficulties related to dCache information provider, not really a technology problem<br>
slide6. Operational motivations For the EGI Helpdesk it is hard to debug issues that are affecting for example a CE and a non published SE, without EGI monitoring
1st and 2nd level support will not have monitoring data for all the involved services, which makes difficult to collect clues and get the complete picture
Taking services out of the EGI scope will stop applying any operational procedure to these services
i.e. software updates campaigns (StoRM publishes correctly the version)<br>
slide7. Cloud development EGI is actively working in integrating cloud extensions into the GLUE2.1 schema
EGI Engage funded activity ongoing https://wiki.egi.eu/wiki/EGI-Engage:TASK_JRA2.4_Accelerated_Computing
Extensive report given by Alessandro for the OGF
https://redmine.ogf.org/dmsf/glue-wg?folder_id=6616<br>
slide8. Which sites are involved? It is very important to EGI to understand exactly which sites will be affected by potential changes, to assess the impact of the changes
At last meeting EGI was able to provide some tentative lists (browsing the BDII!), but an official statement is needed to evaluate the differences before and after the changes<br>
slide2. Outline Operational motivations
Public relations motivations
Effort allocated on BDII development (cloud)
Assessment needed WLCG Information System Evolution Task Force meeting – 16 Jun 2016<br>
slide3. Installed capacity EGI needs BDII on storage resources to assess the total installed storage capacity
NGIs and EGI as a whole need to know the installed capacity, to justify national and European investments in the infrastructure
BDII serves well the purpose, publishing information on used/total
NGIs need those information for different purposes (funding, accounting, advertising)<br>
slide4. Installed capacity EGI and NGI reports need to retrieve the installed capacity
Per site
Per VO
Per NGI
Per EGI<br>
slide5. Effort to maintain the BDII EGI hosts hundreds of VOs
Many of the VOs are very small
Using the BDII helps with automatic VO management
EGI hosts hundreds of sites
Many of the sites are small
Effort available for site administration is usually small
Sites are usually happy with the BDII because it is simple to maintain
PIC difficulties related to dCache information provider, not really a technology problem<br>
slide6. Operational motivations For the EGI Helpdesk it is hard to debug issues that are affecting for example a CE and a non published SE, without EGI monitoring
1st and 2nd level support will not have monitoring data for all the involved services, which makes difficult to collect clues and get the complete picture
Taking services out of the EGI scope will stop applying any operational procedure to these services
i.e. software updates campaigns (StoRM publishes correctly the version)<br>
slide7. Cloud development EGI is actively working in integrating cloud extensions into the GLUE2.1 schema
EGI Engage funded activity ongoing https://wiki.egi.eu/wiki/EGI-Engage:TASK_JRA2.4_Accelerated_Computing
Extensive report given by Alessandro for the OGF
https://redmine.ogf.org/dmsf/glue-wg?folder_id=6616<br>
slide8. Which sites are involved? It is very important to EGI to understand exactly which sites will be affected by potential changes, to assess the impact of the changes
At last meeting EGI was able to provide some tentative lists (browsing the BDII!), but an official statement is needed to evaluate the differences before and after the changes<br>