Difference between revisions of "EGI-InSPIRE:Poland-QR10"

From EGIWiki
Jump to: navigation, search
 
(6 intermediate revisions by 3 users not shown)
Line 1: Line 1:
__NOTOC__
+
{{Template:EGI-Inspire menubar}}
  
 +
{{Template:Inspire_reports_menubar}}
 +
{{TOC_right}}
 
{| cellspacing="0" cellpadding="2" border="1"
 
{| cellspacing="0" cellpadding="2" border="1"
 
|-
 
|-
Line 8: Line 10:
 
! scope="col" | Author
 
! scope="col" | Author
 
|-
 
|-
| 10 - draft<br>  
+
| 10<br>  
 
| NGI_PL<br>  
 
| NGI_PL<br>  
 
| CYFRONET<br>  
 
| CYFRONET<br>  
Line 54: Line 56:
 
! Outcome (Short report &amp; Indico URL)
 
! Outcome (Short report &amp; Indico URL)
 
|-
 
|-
| 27-31.08.2012
+
| 27-31.08.2012  
| Karlsruhe
+
| Karlsruhe  
| GridKa School 2012
+
| GridKa School 2012  
| 2
+
| 2  
 
| http://indico.scc.kit.edu/indico/conferenceDisplay.py?ovw=True&amp;confId=6
 
| http://indico.scc.kit.edu/indico/conferenceDisplay.py?ovw=True&amp;confId=6
 
|-
 
|-
Line 77: Line 79:
 
|<Date>||<Location>||Title||Participants||Outcome  
 
|<Date>||<Location>||Title||Participants||Outcome  
 
|-
 
|-
-->
+
-->  
  
 
===1.3. PUBLICATIONS=== <!--List all publications as bullet points, detailing: Publication title, author(s), journal title, number/issue, date. Also mention any articles published further to interviews given by members of your activity.-->  
 
===1.3. PUBLICATIONS=== <!--List all publications as bullet points, detailing: Publication title, author(s), journal title, number/issue, date. Also mention any articles published further to interviews given by members of your activity.-->  
Line 99: Line 101:
 
##introduction of new functionality for emi.unicore.GlobalStorage probe (testing various access protocols)  
 
##introduction of new functionality for emi.unicore.GlobalStorage probe (testing various access protocols)  
 
#Availability/Reliability metrics  
 
#Availability/Reliability metrics  
##Availability August/September/October 94%/92%/ (not aviailable at 31.10.2012)
+
##Availability August/September/October 94%/92%/ 89%
##Reliability August/September/October&nbsp;&nbsp; 94%/93%/ (not aviailable at 31.10.2012)
+
##Reliability August/September/October&nbsp;&nbsp; 94%/93%/ 94%
 
##Top BDII: all instances above target  
 
##Top BDII: all instances above target  
 
#NGI_PL security team  
 
#NGI_PL security team  
Line 133: Line 135:
  
 
=== 2.2. Main Achievements  ===
 
=== 2.2. Main Achievements  ===
All sites runing obsolete software were informed about the necessity to upgrade or decomission obsolete services. This process is well on track.
+
 
Sites are deploying policy which requires user jobs to be equipped with proper compute grant ID (does not concern gLite software stack).
+
All sites runing obsolete software were informed about the necessity to upgrade or decomission obsolete services. This process is well on track. Sites are deploying policy which requires user jobs to be equipped with proper compute grant ID (does not concern gLite software stack).  
  
 
=== 2.3. Issues and mitigation  ===
 
=== 2.3. Issues and mitigation  ===
Line 148: Line 150:
 
|-
 
|-
 
| Issue Description || Issue mitigation
 
| Issue Description || Issue mitigation
-->  
+
-->
 
 
[[Category:NGI_QR_Reports]]
 

Latest revision as of 15:12, 9 January 2015

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
10
NGI_PL
CYFRONET
Tadeusz Szymocha


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)
27-31.08.2012 Karlsruhe GridKa School 2012 2 http://indico.scc.kit.edu/indico/conferenceDisplay.py?ovw=True&confId=6
17-21.09.2012
Prague
EGI Technical Forum
10
http://tf2012.egi.eu/
27-28.09.2012 Ljublana Terena TF-SCIRT Meeting 1 -


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. Update monitoring system to version SAM17.1 in September
  2. Unicore
    1. Preparation of Unicore Nagios probes for update SAM17.1
    2. introduction of new functionality for emi.unicore.GlobalStorage probe (testing various access protocols)
  3. Availability/Reliability metrics
    1. Availability August/September/October 94%/92%/ 89%
    2. Reliability August/September/October   94%/93%/ 94%
    3. Top BDII: all instances above target
  4. NGI_PL security team
    1. Regular operational actions within EGI CSIRT IRTF
    2. Taking part in weekly and monthly meetings of EGI CSIRT
    3. 2 representatives participated in EGI TF
    4. 1 representative participated in Terena TF-CSIRT meeting
    5. 1 site (ICM) participated in Security Site Challenge 6 organized by EGI CSIRT
  5. NGI_PL ROD team
    1. The team has been adapted to personnell changes. No service disturbance has been observed in ROD performance.
  6. Changes on sites
    1. new services
      1. WCSS64
        1. sBDII (tatooine.wcss.pl).
    2. Upgrades
      1. CAMK:
        1. Upgrade OS on all hosts to Scientific Linux 6.3
        2. Upgrade middleware on all hosts to UMD-2
      2. TASK
        1. Upgrade of se.grid.task.gda.pl to SL6 and to UMD2.0
        2. Upgrade of ce.grid.task.gda.pl (sBDII) to SL6 and to UMD2.0
      3. WCSS64
        1. Migration of CREAM to UMD 2.0.
      4. CYFRONET-LCG2
        1. Migration to EMI due to the end of gLite support
      5. ICM
        1. SLURM batch system with CREAM service has been deployed which required modification of GIP and plugins.
  7. task forces
    1. Federated Cloud Task Force
  8. trainings
    1. Due to personnel changes new COD members were trained in their duties internally at Cyfronet.

2.2. Main Achievements

All sites runing obsolete software were informed about the necessity to upgrade or decomission obsolete services. This process is well on track. Sites are deploying policy which requires user jobs to be equipped with proper compute grant ID (does not concern gLite software stack).

2.3. Issues and mitigation

Issue Description Mitigation Description