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.

EGI-InSPIRE:Germany-QR3

From EGIWiki
Jump to navigation Jump to search


Quarterly Report Number NGI Name Partner Name Author
<Number of Quarterly report> <NGI Name> <NGI Country> <Name of person submitting the QR>


1. MEETINGS AND DISSEMINATION

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
  • for outcome, please list tangible agreements, decisions instead of listing program points or presentations you made. Otherwise put: “-“
  • include your local events only if there was any EGI-related topic on the agenda
  • provide an indico URL to your presentation (if available) or to the event itself.
    • 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.

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)
<Date> <Location> Title Participants Outcome
<Date> <Location> Title Participants Outcome


1.3. PUBLICATIONS

Publication title Journal / Proceedings title Journal references
Volume number
Issue

Pages from - to
Authors
1.
2.
3.
Et al?
<Publication title> <Journal/Proceedings> Vol:<volume number>
Issue:<Issue>
Pg: <from> - <to>
1.<Author 1>
2.<Author2>
3. <Author3>
<Publication title> <Journal/Proceedings> Vol:<volume number>
Issue:<Issue>
Pg: <from> - <to>
1.<Author 1>
2.<Author2>
3. <Author3>
<Publication title> <Journal/Proceedings> Vol:<volume number>
Issue:<Issue>
Pg: <from> - <to>
1.<Author 1>
2.<Author2>
3. <Author3>

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.
  • 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
Issue description Issue mitigation