Difference between revisions of "EGI-InSPIRE:Poland-QR5"
Jump to navigation
Jump to search
(Created page with '__NOTOC__ {| border="1" cellspacing="0" cellpadding="2" |- !scope="col"| Quarterly Report Number !scope="col"| NGI Name !scope="col"| Partner Name !scope="col"| Author |- |5 |N…') |
|||
Line 74: | Line 74: | ||
<!--''Note: just report activities relevant to this Quarter.''--> | <!--''Note: just report activities relevant to this Quarter.''--> | ||
===2.1. Progress Summary=== | === 2.1. Progress Summary === | ||
#'''Nagios''' | |||
##SAM UPDATE-09 from 08.03.2011 applied | |||
##NGI_PL developers are writing probes to monitor glite UI | |||
##WMS tests added into vo.plgrid.pl operations test list - probes will raise alarms for vo.plgrid.pl WMS'es | |||
###New WMS test developed - wms-list-match: the test checks basic functionality if WMS can match any CE for given job<br> | |||
##Ongoing work with Operations Portal developers on vo.plgrid.pl test publication to dashboard | |||
##NGI_PL developers are writing probes to monitor glite UI | |||
#'''Helpdesk''' | |||
##In April was introduced change in ticket processing flow according to ITIL recommendations. This also required reorganization of support units. | |||
#'''Unicore infrastructure''' | |||
##NGI_PL is taking an active role in its work in UNICORE integration task force. | |||
##Requirements for integration of UNICORE services with GOCDB were collected, discussed with GOCDB developers and were included in the GOCDB roadmap. | |||
##The first real GGUS ticket to UNICORE middleware support unit was submitted and procedure for handling UNICORE ticked established (in cooperation with EMI and NGI_DE). | |||
##The NGI_PL UNICORE monitoring solution (probes and Nagios configurator) were presented, discussed and passed to SAM developers for integration with SAM Nagios. | |||
#'''Availability/Reliability metrics''' | |||
##NGI _PL availability for February was 95% and in March 90% | |||
##None of NGI_PL sites were below the thresholds: availability 70% and reliability 75% | |||
#NGI_PL '''security team''' is regularly taking part in actions within EGI CSIRT: | |||
##actions within EGI IRTF | |||
##coordination of cooperation between NGI_PL and EGI CSIRT | |||
##taking part in weekly and monthly meetings | |||
##support of emerging vulnerabilities (2 issues) and to ensure security improvements Polish centres | |||
##analysis of 2 created and released documents | |||
#'''SAMAP''' tool decomission | |||
#NGI_PL '''ROD team''' | |||
##presentation of NGI_PL ROD team in ROD newsletter in February 2011. The goal of this action was to share best practices applied in NGI_PL with other regions. | |||
#'''Changes on sites''': | |||
##All sites set up site information in BDII according to the instructions: https://wiki.egi.eu/wiki/MAN1_How_to_publish_Site_Information | |||
##PSNC | |||
###Cream CE upgraded to glite-CREAM-3.2.10-0.sl5.x86_64<br> | |||
##WCSS | |||
###320 12-cores nodes added insted of 150 4-cores nodes | |||
===2.2. Main Achievements=== | ===2.2. Main Achievements=== | ||
Revision as of 11:57, 15 July 2011
Quarterly Report Number | NGI Name | Partner Name | Author |
---|---|---|---|
5 | NGI_PL | CYFRONET | Małgorzata Krakowian |
1. MEETINGS AND DISSEMINATION
1.1. CONFERENCES/WORKSHOPS ORGANISED
Date | Location | Title | Participants | Outcome (Short report & Indico URL) |
---|---|---|---|---|
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
- Nagios
- SAM UPDATE-09 from 08.03.2011 applied
- NGI_PL developers are writing probes to monitor glite UI
- WMS tests added into vo.plgrid.pl operations test list - probes will raise alarms for vo.plgrid.pl WMS'es
- New WMS test developed - wms-list-match: the test checks basic functionality if WMS can match any CE for given job
- New WMS test developed - wms-list-match: the test checks basic functionality if WMS can match any CE for given job
- Ongoing work with Operations Portal developers on vo.plgrid.pl test publication to dashboard
- NGI_PL developers are writing probes to monitor glite UI
- Helpdesk
- In April was introduced change in ticket processing flow according to ITIL recommendations. This also required reorganization of support units.
- Unicore infrastructure
- NGI_PL is taking an active role in its work in UNICORE integration task force.
- Requirements for integration of UNICORE services with GOCDB were collected, discussed with GOCDB developers and were included in the GOCDB roadmap.
- The first real GGUS ticket to UNICORE middleware support unit was submitted and procedure for handling UNICORE ticked established (in cooperation with EMI and NGI_DE).
- The NGI_PL UNICORE monitoring solution (probes and Nagios configurator) were presented, discussed and passed to SAM developers for integration with SAM Nagios.
- Availability/Reliability metrics
- NGI _PL availability for February was 95% and in March 90%
- None of NGI_PL sites were below the thresholds: availability 70% and reliability 75%
- NGI_PL security team is regularly taking part in actions within EGI CSIRT:
- actions within EGI IRTF
- coordination of cooperation between NGI_PL and EGI CSIRT
- taking part in weekly and monthly meetings
- support of emerging vulnerabilities (2 issues) and to ensure security improvements Polish centres
- analysis of 2 created and released documents
- SAMAP tool decomission
- NGI_PL ROD team
- presentation of NGI_PL ROD team in ROD newsletter in February 2011. The goal of this action was to share best practices applied in NGI_PL with other regions.
- Changes on sites:
- All sites set up site information in BDII according to the instructions: https://wiki.egi.eu/wiki/MAN1_How_to_publish_Site_Information
- PSNC
- Cream CE upgraded to glite-CREAM-3.2.10-0.sl5.x86_64
- Cream CE upgraded to glite-CREAM-3.2.10-0.sl5.x86_64
- WCSS
- 320 12-cores nodes added insted of 150 4-cores nodes
2.2. Main Achievements
2.3. Issues and mitigation
Issue Description | Mitigation Description |
---|