Difference between revisions of "EGI-InSPIRE:Poland-QR12"
Jump to navigation
Jump to search
Line 93: | Line 93: | ||
=== 2.1. Progress Summary === | === 2.1. Progress Summary === | ||
#Availability/Reliability metrics | #Availability/Reliability metrics | ||
##Availability | ##Availability Feb/Mar/Apr 98%/95%/ ???% | ||
##Reliability | ##Reliability Feb/Mar/Apr 98%/98%/ ???% | ||
##Top BDII: | ##Top BDII: Feb/Mar/Apr 100%/100%/ ???% | ||
#NGI_PL security team | #NGI_PL security team | ||
##Regular operational actions within EGI CSIRT IRTF | ##Regular operational actions within EGI CSIRT IRTF | ||
##Taking part in weekly and monthly meetings of EGI CSIRT | ##Taking part in weekly and monthly meetings of EGI CSIRT | ||
##1 representative participated in EGI-CSIRT Face2Face Meeting in Linkoping, 24-25.02.2013<br> | ##1 representative participated in EGI-CSIRT Face2Face Meeting in Linkoping, 24-25.02.2013<br> | ||
#NGI_PL ROD team | #NGI_PL ROD team | ||
##RPI | ##RPI Feb/Mar/Apr 3/4/9 | ||
#Changes on sites | #Changes on sites | ||
##new services | ##new services | ||
Line 121: | Line 117: | ||
####Updates of Unicore and QCG services | ####Updates of Unicore and QCG services | ||
#task forces | #task forces | ||
##Federated Cloud Task Force | ##Federated Cloud Task Force | ||
##Resource Allocation Task Force<br> | ##Resource Allocation Task Force<br> | ||
Revision as of 14:30, 29 April 2013
Main | EGI.eu operations services | Support | Documentation | Tools | Activities | Performance | Technology | Catch-all Services | Resource Allocation | Security |
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 |
---|---|---|---|
12 - draft |
NGI_PL |
CYFRONET |
Magda Szopa |
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.03.2013 | Amsterdam | EGI.EU Council Meeting | 1 | |
8-12.04.2013 | Manchester, UK | EGI Community Forum | 14 | |
24-25.04.2013 | Linkoping, Sweden | EGI-CSIRT Face2Face Meeting | 1 | regular technical meeting of EGI-CSIRT group |
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
- Availability/Reliability metrics
- Availability Feb/Mar/Apr 98%/95%/ ???%
- Reliability Feb/Mar/Apr 98%/98%/ ???%
- Top BDII: Feb/Mar/Apr 100%/100%/ ???%
- NGI_PL security team
- Regular operational actions within EGI CSIRT IRTF
- Taking part in weekly and monthly meetings of EGI CSIRT
- 1 representative participated in EGI-CSIRT Face2Face Meeting in Linkoping, 24-25.02.2013
- NGI_PL ROD team
- RPI Feb/Mar/Apr 3/4/9
- Changes on sites
- new services
- WUT
- 6 machines with Xeon E5 - 8 cores, new disk array.
- WUT
- Upgrades
- PSNC
- Update of 2 CREAMCE to EMI-2
- WUT
- Upgrade of all services to UMD-2
- CYFRONET-LCG2
- Migration to EMI due to the end of gLite support (contiuation)
- Migration to EMI due to the end of gLite support (contiuation)
- ICM
- Updates of Unicore and QCG services
- PSNC
- new services
- task forces
- Federated Cloud Task Force
- Resource Allocation Task Force
2.2. Main Achievements
NGI_PL submitted two proposals for PMB mini-projects call, both related to operations in the area of Resource Allocation (coordinated by Cyfronet) and Service Availability calculation. SAM/nagios system has been reconfigured for new regional service types which has been introduced in GOCDB. All sites are in-line with requirements for software retirement calendar as well as all sites are publishing user DNs.
NGI_PL has proposed one of two schemes for Resource Allocation in EGI within Resource Allocation Task Force. We also declared some resources for Resource Allocation Testbed where RA procedures will be tested.
2.3. Issues and mitigation
Issue Description | Mitigation Description |
---|