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 "EGI-InSPIRE:Germany-QR3"

From EGIWiki
Jump to navigation Jump to search
 
(28 intermediate revisions by 3 users not shown)
Line 1: Line 1:
__NOTOC__
{{Template:EGI-Inspire menubar}}
 
{{Template:Inspire_reports_menubar}}
{{TOC_right}}


{| border="1" cellspacing="0" cellpadding="2"
{| border="1" cellspacing="0" cellpadding="2"
Line 8: Line 11:
!scope="col"| Author  
!scope="col"| Author  
|-
|-
|<Number of Quarterly report>
|3
|<NGI Name>
|NGI_DE
|<NGI Country>
|Germany
|<Name of person submitting the QR>
|Torsten Antoni
|-
|-
|}
|}
Line 20: Line 23:


==1. MEETINGS AND DISSEMINATION ==
==1. MEETINGS AND DISSEMINATION ==
=====GENERAL GUIDELINES FOR ALL EVENTS REPORTED IN THE FOLLOWING SECTIONS:=====
<!--=====GENERAL GUIDELINES FOR ALL EVENTS REPORTED IN THE FOLLOWING SECTIONS:=====
*please do not provide a list of participants, only give the number of people that attended
*please do not provide a list of participants, only give the number of people that attended
*for outcome, please list tangible agreements, decisions instead of listing program points or presentations you made. Otherwise put: “-“
*for outcome, please list tangible agreements, decisions instead of listing program points or presentations you made. Otherwise put: “-“
Line 27: Line 30:
**If your presentation is not available online, please send the slides to erika.swiderski@egi.eu.  
**If your presentation is not available online, please send the slides to erika.swiderski@egi.eu.  
Note: Complete the tables below by adding as many rows as needed.  
Note: Complete the tables below by adding as many rows as needed.  
Note: Complete the tables below by adding as many rows as needed.  
Note: Complete the tables below by adding as many rows as needed.
-->


===1.1. CONFERENCES/WORKSHOPS ORGANISED===
===1.1. CONFERENCES/WORKSHOPS ORGANISED===
Line 37: Line 41:
!scope="col"|Date||Location||Title||Participants||Outcome (Short report & Indico URL)  
!scope="col"|Date||Location||Title||Participants||Outcome (Short report & Indico URL)  
|-
|-
|Nov. 23,<br> Nov. 26, <br> Dec. 3, 2010||Berlin, Germany||Course on Grid Computing with hands-on|| 70 participants (students)||Learning the Grid concept and <br>job/data management on the Grids>
|Nov. 23,<br> Nov. 26, <br> Dec. 3, 2010||Berlin, Germany||Course on Grid Computing with hands-on|| 70 participants (students)||Learning the Grid concept and <br>job/data management on the Grids
|-
|-
|}
|}
Line 47: Line 51:
|-
|-
!scope="col"|Date||Location||Title||Participants||Outcome (Short report & Indico URL)  
!scope="col"|Date||Location||Title||Participants||Outcome (Short report & Indico URL)  
|-
|<Date>||<Location>||Title||Participants||Outcome
|-
|<Date>||<Location>||Title||Participants||Outcome
|-
|<Date>||<Location>||Title||Participants||Outcome Test
<!-- formatting text -->
<!-- formatting text -->
|-
|-
Line 70: Line 68:
!scope="col"|Publication title||Journal / Proceedings title||align="left" |Journal references<br> ''Volume number<br> Issue<br><br>Pages from - to''||align="left" |Authors ''<br>1.<br>2.<br>3.<br>Et al?''
!scope="col"|Publication title||Journal / Proceedings title||align="left" |Journal references<br> ''Volume number<br> Issue<br><br>Pages from - to''||align="left" |Authors ''<br>1.<br>2.<br>3.<br>Et al?''
|-
|-
|<Publication title>||<Journal/Proceedings>||Vol:<volume number><br>Issue:<Issue><br>Pg: <from> - <to>||1.<Author 1><br>2.<Author2><br>3. <Author3><br>
|-
|<Publication title>||<Journal/Proceedings>||Vol:<volume number><br>Issue:<Issue><br>Pg: <from> - <to>||1.<Author 1><br>2.<Author2><br>3. <Author3><br>
|-
|<Publication title>||<Journal/Proceedings>||Vol:<volume number><br>Issue:<Issue><br>Pg: <from> - <to>||1.<Author 1><br>2.<Author2><br>3. <Author3><br>
|}
|}


Line 82: Line 75:
===2.1. Progress Summary===
===2.1. Progress Summary===
<!-- Provide your test below -->
<!-- Provide your test below -->
In the reported period NGI_DE keeps the Grid running smoothly in the region. Operation problems are discussed in the regular coordination meeting. The ROD team works well. Grid services are maintained up-to-date. Security update was done by all sites. While keeping the Grid running, NGI_DE made efforts during the last three months in optimizing the use of computing resources and the quality of services. For example, KIT split a cluster into two clusters for efficiency and Uni-Dresden also split a cluster into two to run different OS versions for better services. A new site, FZJuelich, joined NGI-DE and is providing Grid services. The certification of the ZIB site is in progress.


===2.2. Main Achievements===
===2.2. Main Achievements===
Line 87: Line 81:
Provide your text below
Provide your text below
-->
-->
The main achievements of NGI_DE in the report period are the successful operation of the Grid infrastructure in the entire region. Some sites participated in Staged Rollout. All sites have patched the security vulnerabilities in time. Regional Nagios instance was updated to the latest version. New CREAM-CEs were installed. The following are concrete achievements of some sites:
* TUDresden-ZIH installed glite-Apel and a CREAM-CE.
* UNI-Wuppertal successfully performed the glite-Apel migration.
*      In DESY-HH more storage was committed. As a result DESY-HH now provides 2PB disk storage in three SE's (atlas,cms and others) with better efficiency for the grid jobs and better distribution of the data on the storage (average efficiency of the jobs on grid-wn's is more than 80% in January). The CEs of DESY-HH are very well occupied with the jobs, for example, in 4 of the 7 days in the second January week, 100% of the  job slots were occupied with the jobs.  DESY-HH also updated one of the SEs (cms) to the 1.9.10 dcache version (outside of golden release).
*      To enhance the efficiency, KIT split a cluster into two clusters and solved all related problems. KIT also tested the regional Nagios Monitoring of ARC services with Swiss sites.
*    Uni-Dresden split cluster in two OS versions (one half with SL and one cluster with slash).
*    FZJ was certified as an EGI site. Now the service endpoints dcache.fz-juelich.de and site-bdii.fz-juelich.de are in production and a first UNICORE service endpoint was registered in GOCDB.
*    UNI-Freiburg installed a CREAM-CE.
*    LRZ upgraded the hardware on compute nodes and storage nodes and performed the migration from SLES10 to SLES11.
*    SCAI migrated glite-MON to APEL, deployed glite-UI 3.2, replaced Nagios with Icinga, and performed decommission of LCG-CE.


===2.3. Issues and mitigation===
===2.3. Issues and mitigation===
Line 95: Line 100:
!scope="col"| Mitigation Description
!scope="col"| Mitigation Description
|-
|-
|Issue description || Issue mitigation
|DESY-HH received increasing interest from the hosted VOs for the support of the glite on 32 bits platform. || This issue will be discussed in the NGI_DE and EGI User Forum in April.
|-
|-
|FZJ reported a problem with integrating UNICORE resources. || It is needed that GOGDB supports adding new endpointURL fields for endpoint service types. A ticket was issued https://rt.egi.eu/rt/Ticket/Display.html?id=975, and it is still open. A solution is needed for properly adding UNICORE services to the EGI infrastructure.
|-
|Uni-Mainz-MaiGrid was suspended for a week because of bad availability values. || The site is now certified again after fixing some service issues.
|}
|}
<!--
<!--
  Please, fill the table below. You can add a line copyng the two lines
  Please, fill the table below. You can add a line copyng the two lines
Line 104: Line 111:
| Issue Description || Issue mitigation
| Issue Description || Issue mitigation
-->
-->
===2.4. Plans for the next period===
* TUDresden-ZIH plans to increase the size of dCache installation (10 TB more disc).
* UNI-Wuppertal plans to install a CREAM CE.
* DESY-HH plans commissioning the large portion of the storage (~1PB) and a hardware evaluation for the WN's procurement.
* FZJ prepares "UNICORE Services for EGI - Tutorial for Resource Providers" for the EGI User Forum 2011.
* MPPMU plans to update Apel/monbox, and deploy new storage and worker nodes.
* SCAI plans a middleware migration to gLite 3.2 for SE, LFC & VOMS.
* KIT plans to organize an EGI-CSIRT face-to-face meeting in April in Karlsruhe, and to migrate  glite-MON to APEL.
* UNI-Mainz-MaiGrid plans to fix the wrong published HEPSPEC06 values influencing the availability.

Latest revision as of 15:39, 7 January 2015

EGI Inspire Main page


Inspire reports menu: Home SA1 weekly Reports SA1 Task QR Reports NGI QR Reports NGI QR User support Reports



Quarterly Report Number NGI Name Partner Name Author
3 NGI_DE Germany Torsten Antoni


1. MEETINGS AND DISSEMINATION

1.1. CONFERENCES/WORKSHOPS ORGANISED

Date Location Title Participants Outcome (Short report & Indico URL)
Nov. 23,
Nov. 26,
Dec. 3, 2010
Berlin, Germany Course on Grid Computing with hands-on 70 participants (students) Learning the Grid concept and
job/data management on the Grids

1.2. OTHER CONFERENCES/WORKSHOPS ATTENDED

Date Location Title Participants Outcome (Short report & Indico URL)


1.3. PUBLICATIONS

Publication title Journal / Proceedings title Journal references
Volume number
Issue

Pages from - to
Authors
1.
2.
3.
Et al?

2. ACTIVITY REPORT

2.1. Progress Summary

In the reported period NGI_DE keeps the Grid running smoothly in the region. Operation problems are discussed in the regular coordination meeting. The ROD team works well. Grid services are maintained up-to-date. Security update was done by all sites. While keeping the Grid running, NGI_DE made efforts during the last three months in optimizing the use of computing resources and the quality of services. For example, KIT split a cluster into two clusters for efficiency and Uni-Dresden also split a cluster into two to run different OS versions for better services. A new site, FZJuelich, joined NGI-DE and is providing Grid services. The certification of the ZIB site is in progress.

2.2. Main Achievements

The main achievements of NGI_DE in the report period are the successful operation of the Grid infrastructure in the entire region. Some sites participated in Staged Rollout. All sites have patched the security vulnerabilities in time. Regional Nagios instance was updated to the latest version. New CREAM-CEs were installed. The following are concrete achievements of some sites:

  • TUDresden-ZIH installed glite-Apel and a CREAM-CE.
  • UNI-Wuppertal successfully performed the glite-Apel migration.
  • In DESY-HH more storage was committed. As a result DESY-HH now provides 2PB disk storage in three SE's (atlas,cms and others) with better efficiency for the grid jobs and better distribution of the data on the storage (average efficiency of the jobs on grid-wn's is more than 80% in January). The CEs of DESY-HH are very well occupied with the jobs, for example, in 4 of the 7 days in the second January week, 100% of the job slots were occupied with the jobs. DESY-HH also updated one of the SEs (cms) to the 1.9.10 dcache version (outside of golden release).
  • To enhance the efficiency, KIT split a cluster into two clusters and solved all related problems. KIT also tested the regional Nagios Monitoring of ARC services with Swiss sites.
  • Uni-Dresden split cluster in two OS versions (one half with SL and one cluster with slash).
  • FZJ was certified as an EGI site. Now the service endpoints dcache.fz-juelich.de and site-bdii.fz-juelich.de are in production and a first UNICORE service endpoint was registered in GOCDB.
  • UNI-Freiburg installed a CREAM-CE.
  • LRZ upgraded the hardware on compute nodes and storage nodes and performed the migration from SLES10 to SLES11.
  • SCAI migrated glite-MON to APEL, deployed glite-UI 3.2, replaced Nagios with Icinga, and performed decommission of LCG-CE.

2.3. Issues and mitigation

Issue Description Mitigation Description
DESY-HH received increasing interest from the hosted VOs for the support of the glite on 32 bits platform. This issue will be discussed in the NGI_DE and EGI User Forum in April.
FZJ reported a problem with integrating UNICORE resources. It is needed that GOGDB supports adding new endpointURL fields for endpoint service types. A ticket was issued https://rt.egi.eu/rt/Ticket/Display.html?id=975, and it is still open. A solution is needed for properly adding UNICORE services to the EGI infrastructure.
Uni-Mainz-MaiGrid was suspended for a week because of bad availability values. The site is now certified again after fixing some service issues.

2.4. Plans for the next period

  • TUDresden-ZIH plans to increase the size of dCache installation (10 TB more disc).
  • UNI-Wuppertal plans to install a CREAM CE.
  • DESY-HH plans commissioning the large portion of the storage (~1PB) and a hardware evaluation for the WN's procurement.
  • FZJ prepares "UNICORE Services for EGI - Tutorial for Resource Providers" for the EGI User Forum 2011.
  • MPPMU plans to update Apel/monbox, and deploy new storage and worker nodes.
  • SCAI plans a middleware migration to gLite 3.2 for SE, LFC & VOMS.
  • KIT plans to organize an EGI-CSIRT face-to-face meeting in April in Karlsruhe, and to migrate glite-MON to APEL.
  • UNI-Mainz-MaiGrid plans to fix the wrong published HEPSPEC06 values influencing the availability.