EGI-InSPIRE:Germany-QR9
Jump to navigation
Jump to search
Quarterly Report Number | NGI Name | Partner Name | Author |
---|---|---|---|
QR 9 | NGI_DE | Germany | Jie Tao |
1. MEETINGS AND DISSEMINATION
1.1. CONFERENCES/WORKSHOPS ORGANISED
Date | Location | Title | Participants | Outcome (Short report & Indico URL) |
---|---|---|---|---|
May 07-09, 2012 | Karlsruhe, Germany | The 25th EUGridPMA and IGTF All Hands meeting | Members of the European Grid Policy Management Authority and members of the International Grid Trust Federation | Report and discussion on SHA-1 Risk assessment; updating of the Attribute Authority Operations guidelines; and so on. https://indico.scc.kit.edu/indico/conferenceDisplay.py?ovw=True&confId=11 |
May 10-11, 2012 | Karlsruhe, Germany | Security for Collaborating Infrastructures (SCI) meeting | security staff of EGI, OSG, PRACE, WLCG, and XSEDE | Discussion of the current draft text (V6) of the SCI document; creation of a complete first draft of the SCI document. http://indico.scc.kit.edu/indico/conferenceDisplay.py?confId=12 |
1.2. OTHER CONFERENCES/WORKSHOPS ATTENDED
Date | Location | Title | Participants | Outcome (Short report & Indico URL) |
---|---|---|---|---|
May 19-20, 2012 | New York | WLCG workshop | NGI_DE staff (DESY, KIT, etc.) | WLCG status, report |
May 21-25, 2012 | New York | CHEP 2012 | NGI_DE staff (DESY, KIT, etc.) | Talks and posters |
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
NGI_DE keeps smoothly operating Grid services in the region. The availability for core services reached 100% and the average availability of NGI_DE was 95%. The ROD team worked well with a fluent shift transfer. New hardware was installed and service software was upgraded. Stage rollout was performed.
2.2. Main Achievements
The following are concrete achievements of the NGI-DE sites:
- DESY-HH increased both storage and CPU resources on the cluster. For storage the old machines are removed from operation. Most of the services are running from emi-1 release. This site also setup (on request from wlcg) test emi queue with the emi(1)-wn, so that VO can test their software. Another contribution from this site is the running of own scheduler since February for the batch system (instead of maui) and the new scheduler is more stable and easier in configuration.
- FZJ contributed to UNICORE Integration Task Force. The site plans to solve site certification and OLA issues and integrate a VO, which uses UNICORE, into EGI.
- ITWM updated one of its CEs, SE, UI, and several WNs to SL6 x86_64 and EMI-2; performed staged rollout for the components EMI WN, TORQUE client and EMI DPM; and solved some problems with the nes SE releases.
- KIT performed EMI updating and is planning to use the Grid Engine batch system to connect some WNs.
- MPPMU decommissioned a few old pools and migrated data to the new pools
- Uni Freiburg updated the torque server to version 2.5.12. As no new packages in the Apel repository were available the site did its own work and everything runs smoothly now.
- SCAI updated UI, EMI WMS, and VOMS.
2.3. Issues and mitigation
Issue Description | Mitigation Description |
---|---|
In DESY-HH about 10% of the resources are misused (too long jobs, hitting the limit of time resources, or jobs which use more than the agreed in vo cards resources). Continued misusage of vo-card information was seen - requirements changed by vo without discussion in any committee (scrutiny group would be the best for such discussion) and this lead to situation that sites cannot formally fulfill this requirement (like increase in memory per job slot is not possible to make for old worker nodes, which were bought with previous requirement). | Discussion must be conducted. |
In FZJ Resource Centre Certification and Resource Centre Operational Level Agreement procedures and requirements as currently established do not match the reality of sites offering UNICORE services. | Discussions in the UNICORE Integration Task Force are ongoing. As EMI is developing a UNICORE interface to BDII, this could be the solution for publishing information to a BDII service. |
SCAI had gssapi problem, see http://www.eu-emi.eu/emi-2-matterhorn/updates/-/asset_publisher/KUa3/content/gss-gsoap-plugin-issues-with-globus-gssapi-gsi-%3E%3D-10-6 | Solution is in discussion |