Alert.png The wiki is deprecated and due to be decommissioned by the end of September 2022.
The content is being migrated to other supports, new updates will be ignored and lost.
If needed you can get in touch with EGI SDIS team using operations @ egi.eu.

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

From EGIWiki
Jump to navigation Jump to search
Line 1: Line 1:
__NOTOC__
__NOTOC__  


{| border="1" cellspacing="0" cellpadding="2"
{| cellspacing="0" cellpadding="2" border="1"
|-
|-
!scope="col"| Quarterly Report Number
! scope="col" | Quarterly Report Number  
!scope="col"| NGI Name
! scope="col" | NGI Name  
!scope="col"| Partner Name
! scope="col" | Partner Name  
!scope="col"| Author  
! scope="col" | Author
|-
|5
|NGI_PL
|CYFRONET
|Małgorzata Krakowian
|-
|-
| 5
| NGI_PL
| CYFRONET
| Małgorzata Krakowian
|}
|}


<!--  
<!--  
Fill the second line of the table replacing the <...> stuff with your data.
Fill the second line of the table replacing the <...> stuff with your data.
-->
-->  


==1. MEETINGS AND DISSEMINATION ==
==1. MEETINGS AND DISSEMINATION == <!--=====GENERAL GUIDELINES FOR ALL EVENTS REPORTED IN THE FOLLOWING SECTIONS:=====
<!--=====GENERAL GUIDELINES FOR ALL EVENTS REPORTED IN THE FOLLOWING SECTIONS:=====
*please do not provide a list of participants, only give the number of people that attended
*please do not provide a list of participants, only give the number of people that attended
*for outcome, please list tangible agreements, decisions instead of listing program points or presentations you made. Otherwise put: “-“
*for outcome, please list tangible agreements, decisions instead of listing program points or presentations you made. Otherwise put: “-“
Line 27: Line 25:
**If your presentation is not available online, please send the slides to erika.swiderski@egi.eu.  
**If your presentation is not available online, please send the slides to erika.swiderski@egi.eu.  
Note: Complete the tables below by adding as many rows as needed.  
Note: Complete the tables below by adding as many rows as needed.  
Note: Complete the tables below by adding as many rows as needed. -->
Note: Complete the tables below by adding as many rows as needed. -->  
 
===1.1. CONFERENCES/WORKSHOPS ORGANISED===


=== 1.1. CONFERENCES/WORKSHOPS ORGANISED  ===


{| border="1" cellspacing="0" cellpadding="2"
{| cellspacing="0" border="1"
<!-- |+Provided by each SA1 partner. Just report events relevant to SA1 activities.-->
|-
!scope="col"|Date||Location||Title||Participants||Outcome (Short report & Indico URL)
|-
|-
|
! scope="col" | Date
|
! Location
|
! Title
|
! Participants
|
! Outcome (Short report &amp; Indico URL)
|-
|-
| <br>
| <br>
| <br>
| <br>
| <br>
|}
|}


===1.2. OTHER CONFERENCES/WORKSHOPS ATTENDED===
=== 1.2. OTHER CONFERENCES/WORKSHOPS ATTENDED ===


{| border="1" cellspacing="0" cellpadding="2"
{| cellspacing="0" border="1"
<!-- |+Provided by each SA1 partner. Just report events relevant to SA1 activities.-->
|-
|-
!scope="col"|Date||Location||Title||Participants||Outcome (Short report & Indico URL)  
! scope="col" | Date  
|-
! Location  
|||||||||
! Title  
! Participants  
! Outcome (Short report &amp; Indico URL)
|-
|-
| <br>
| <br>
| <br>
| <br>
| <br>
|}
|}


Line 60: Line 65:
|<Date>||<Location>||Title||Participants||Outcome  
|<Date>||<Location>||Title||Participants||Outcome  
|-
|-
-->
-->  


===1.3. PUBLICATIONS===
===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.-->  
<!--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.-->


{| border="1" cellspacing="0" cellpadding="2"
{| cellspacing="0" cellpadding="2" border="1"
|-
!scope="col"|Publication title||Journal / Proceedings title||align="left" |Journal references<br> ''Volume number<br> Issue<br><br>Pages from - to''||align="left" |Authors ''<br>1.<br>2.<br>3.<br>Et al?''
|-
|-
! scope="col" | Publication title
! Journal / Proceedings title
! align="left" | Journal references<br> ''Volume number<br> Issue<br><br>Pages from - to''
! align="left" | Authors ''<br>1.<br>2.<br>3.<br>Et al?''
|}
|}


== 2. ACTIVITY REPORT ==
== 2. ACTIVITY REPORT == <!--''Note: just report activities relevant to this Quarter.''-->  
<!--''Note: just report activities relevant to this Quarter.''-->


=== 2.1. Progress Summary  ===
=== 2.1. Progress Summary  ===
Line 84: Line 89:
##NGI _PL availability for May 94% was&nbsp; and in June&nbsp;96%  
##NGI _PL availability for May 94% was&nbsp; and in June&nbsp;96%  
##None of NGI_PL sites were below the thresholds: availability 70% and reliability 75%  
##None of NGI_PL sites were below the thresholds: availability 70% and reliability 75%  
#NGI_PL '''security team'''
#NGI_PL '''security team'''  
## 1. W tym okresie były prowadzone standardowe działania operacyjne
##actions within EGI IRTF<br>
obejmujące prace w ramach grupy EGI CSIRT, czyli:
##taking part in weekly and monthly meetings <br>
- udział pracach grupy EGI IRTF (bieżące monitorowanie i zabezpieczanie
##support of emerging vulnerabilities (2 issues) and to ensure security improvements Polish centres<br>
stanu infrastruktury)
##SSC5 (Security Site Challenge 5) organized<br>
- udział w cotygodniowych i comiesiecznych spotkaniach
##removal of all High class vulnerabilities in all NGI_PL centres<br>
- tygodniowy (13-19.06.2011) dyżur pracownika WCSS'u jako dyżurny oficer
 
bezpieczeństwa EGI CSIRT (Security Officer on Duty)
2. Zgłoszone zostały do EGI SVG i EGI CSIRT 2 podatności w
oprogramowaniu systemów kolejkowych. EGI SVG określiło poziom zagrożenia
jednej jako High, a drugiej jako Moderate. We współpracy z tymi grupami
dokonano oceny ryzyka podatności oraz opracowano i przetestowano metody
tymczasowego zabezpieczenia się przed nimi.
3. Przeprowadzone zostało SSC5 (Security Site Challenge 5) organizowane
przez EGI CSIRT. Była to symulacja incydentu bezpieczeństwa w skali
całego EGI. Testom poddany był Cyfronet. Pracownik WCSS jako NGI
Security Officer zajmowałem się koordynacją i współpracą z EGI CSIRT.
Całość miała miejsce na przełomie maja i czerwca.
4. Zlikwidowano wszystkie podatności klasy High we wszystkich ośrodkach.
#NGI_PL '''ROD team'''  
#NGI_PL '''ROD team'''  
##ROD&nbsp;team involved also in application alarms handling  
##ROD&nbsp;team involved in NGI_PL application alarms handling  
#'''Changes on sites''':  
#'''Changes on sites''':  
##PSNC - LB, Top-BDII, 69 blejdów AMD, dwunastordzeniowych. infiibank, mpi<br>  
##PSNC  
##WCSS64- infiniband, mpi<br>
###New services:&nbsp;LB, Top-BDII  
##CYFRONET - 162 serwerów, każdy 2-procesorowy, 12-rdzeniowy, 24GB RAM, 250GB dysk
###New hardware:&nbsp;69 blade servers AMD, 12-cores<br>  
##warszawa - Zmigrowaliśmy TopBDII i SiteBDII do najnowszych wersji. Nie obyło się bez problemów, mogę podać numery ticketów
##CYFRONE-LCG2
###New hardware: 162 servers, 12-cores, 24GB RAM, 250GB disc
##WARSAW-EGEE
###Update:&nbsp;Migrating TopBDII and SiteBDII to newest versions<br>


=== 2.2. Main Achievements ===
=== 2.2. Main Achievements ===


===2.3. Issues and mitigation===
=== 2.3. Issues and mitigation ===


{| border="1" cellspacing="0" cellpadding="2"
{| cellspacing="0" cellpadding="2" border="1"
|-
!scope="col"| Issue Description
!scope="col"| Mitigation Description
|-
|-
! scope="col" | Issue Description
! scope="col" | Mitigation Description
|}
|}



Revision as of 09:07, 29 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

  1. Unicore infrastructure
    1. Testing UNICORE EMI-1 and EGI-preview releases
    2. Supporting EGI effort to integrate PL-Grid UNICORE probes with SAM-Nagios
    3. Review of the OLA and site certification policy w.r.t. UNICORE middleware
    4. Testing of the UNICORE service types and the service endpoint URL feature in GOCDB (bug reports submitted)
  2. Availability/Reliability metrics
    1. NGI _PL availability for May 94% was  and in June 96%
    2. None of NGI_PL sites were below the thresholds: availability 70% and reliability 75%
  3. NGI_PL security team
    1. actions within EGI IRTF
    2. taking part in weekly and monthly meetings
    3. support of emerging vulnerabilities (2 issues) and to ensure security improvements Polish centres
    4. SSC5 (Security Site Challenge 5) organized
    5. removal of all High class vulnerabilities in all NGI_PL centres
  1. NGI_PL ROD team
    1. ROD team involved in NGI_PL application alarms handling
  2. Changes on sites:
    1. PSNC
      1. New services: LB, Top-BDII
      2. New hardware: 69 blade servers AMD, 12-cores
    2. CYFRONE-LCG2
      1. New hardware: 162 servers, 12-cores, 24GB RAM, 250GB disc
    3. WARSAW-EGEE
      1. Update: Migrating TopBDII and SiteBDII to newest versions

2.2. Main Achievements

2.3. Issues and mitigation

Issue Description Mitigation Description