EGI-InSPIRE:Poland-QR7

From EGIWiki
Revision as of 17:52, 22 January 2015 by Krakow (talk | contribs) (moved Poland-QR7 to EGI-InSPIRE:Poland-QR7)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to: navigation, search
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
7 NGI_PL CYFRONET Małgorzata Krakowian


1. MEETINGS AND DISSEMINATION

1.1. CONFERENCES/WORKSHOPS ORGANISED

Date Location Title Participants Outcome (Short report & Indico URL)
4-7.01.2012 Zakopane, Poland Grid Computing - The Next Decade 47

https://gridlab.man.poznan.pl/Meetings/Zakopane2012/indexman.html

1.2. OTHER CONFERENCES/WORKSHOPS ATTENDED

Date

Location Title Participants Outcome (Short report & Indico URL)
9-10/11/2011  The Netherlands NGI Coordinators Kick Off meeting 1
3-4/11/2011   The Netherlands Projekt Managment Board
EGI-Inspire
1
23-24/01/2012   The Netherlands OMB 1
26-24/01/2012   The Netherlands PMB EGI-INSPIRE 1
12-18/11/2011 Seattle, USA Supercomputing 11 1 http://sc11.supercomputing.org


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

  1. Nagios
    1. Production instance: Actualization to version SAM15
    2. Testing instance: Actualization to version SAM15 and UNICORE probes testing
  2. Regional Helpdesk
    1. Moving to more automatized process of handling tickets in regional helpdesk.
  3. Unicore
    1. Monitoring: testing, debugging and suggesting SAM fixes related to UNICORE. Refactoring of UNICORE configuration module for SAM.
    2. Accounting: Integration with APEL enters testing phase.
  4. Stage rollout components tested
    1. UNICORE: UNICORE Gateway, UVOS
    2. GLITE: EMI.apel, EMI.cream, EMI.dpm
  5. Availability/Reliability metrics
    1. NGI_PL metrics:  November 96%, December 99%; All sites above the targets.
    2. BDII metrics: November 99%, December 100%;
  6. NGI_PL security team
    1. Incident response and investigation for security incident at Cyfronet, EGI CSIRT incident id: EGI-20111231-01
    2. Regular operational actions within EGI CSIRT IRTF
    3. Taking part in weekly and monthly meetings of EGI CSIRT
    4. Removing critical vulnerabilities in IFJ-PAN-BG, including checking whole site infrastructure
    5. Performing security pentesting for WUT site
    6. Submission of 1 vulnerability to EGI SVG
    7. Delegating participant to D4.4 "Security Risk Assessment of the EGI Infrastructure"
  7. ROD NGI_PL
    1. Coordination of lcg-CE decommission within NGI
    2. Creation of NGI_PL_SERVICES site, designed for calculation RP availability and reliability metrics
    3. ROD team didn't exceed ROD performance index target 
  8. Changes on sites
    1. CYFRONET-LCG2
      1. Decommission of lcg-CE
      2. Upgrade of DPM
      3. New services: 
        1. cream02.grid - CREAMCE  UMD
        2. wms01.grid    - WMS EMI
        3. myproxy02.grid - MYPROXY UMD
    2. WCSS-PPS
      1. Migration from gLite 3.2 to UMD 1.0
      2. Moving Site-BDII from CREAM to new host
    3. PSNC
      1. New services: UNICORE
    4. TASK
      1. New services: UNICORE, CREAM-CE
      2. New hardware: new cluster Galera Plus (192 nodes, each 12-cores), vSMP machine
    5. WARSAW_EGEE
      1. Actualization of unicore-gateway to version 4.2.0 and uvos-server to version 1.5.0
      2. New services: QosCosGrid
      3. New hardware: 12 TFPS
    6. New site certified:
      1. NGI_PL_SERVICES - contains NGI_PL core services
      2. ICM - contains QCG and UNICORE services
  9. Task forces in which NGI_PL participate
    1. Regionalisation TF
    2. UNICORE Integration TF
    3. Federated Clouds TF

2.2. Main Achievements

All the biggest sites (CYFRONET-LCG2, PSNC, WCSS, TASK, WARSAW-EGEE) in NGI_PL support a wide range of middlewares (glite, UNICORE, QCG) to adapt to the demands and needs of users. All the services are registerd in GOC DB.

2.3. Issues and mitigation

Issue Description Mitigation Description