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-QR7"

From EGIWiki
Jump to navigation Jump to search
 
(20 intermediate revisions by 2 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
|-
|-
| 7
| 7  
| NGI_PL
| NGI_PL  
| CYFRONET
| CYFRONET  
| Małgorzata Krakowian
| Małgorzata Krakowian
|}
|}
Line 37: Line 39:
! Outcome (Short report & Indico URL)
! Outcome (Short report & Indico URL)
|-
|-
| 4-7.01.2012
| 4-7.01.2012  
| Zakopane, Poland
| Zakopane, Poland  
| Grid Computing - The Next Decade
| Grid Computing - The Next Decade  
| 47
| 47  
|  
|  
https://gridlab.man.poznan.pl/Meetings/Zakopane2012/indexman.html
https://gridlab.man.poznan.pl/Meetings/Zakopane2012/indexman.html  


|}
|}


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


{| cellspacing="0" border="1"
{| cellspacing="0" border="1"
|-
|-
! scope="col" | Date
! scope="col" |  
! Location
Date  
! Title
 
! Participants
! Location  
! Title  
! Participants  
! Outcome (Short report & Indico URL)
! Outcome (Short report & Indico URL)
|-
|-
|  
| 9-10/11/2011
|  
|  The Netherlands
|  
| NGI Coordinators Kick Off meeting
|  
| 1
|  
| <br>
|-
| 3-4/11/2011
| &nbsp; The Netherlands
| Projekt Managment Board <br> EGI-Inspire
| 1
| <br>
|-
| 23-24/01/2012
| &nbsp; The Netherlands
| OMB
| 1
| <br>
|-
| 26-24/01/2012
| &nbsp; The Netherlands
| PMB EGI-INSPIRE
| 1
| <br>
|-
| 12-18/11/2011
| Seattle, USA
| Supercomputing 11
| 1
| http://sc11.supercomputing.org
|}
|}


Line 73: Line 101:
{| cellspacing="0" cellpadding="2" border="1"
{| cellspacing="0" cellpadding="2" border="1"
|-
|-
! scope="col" | Publication title
! scope="col" | Publication title  
! Journal / Proceedings title
! Journal / Proceedings title  
! align="left" | Journal references<br> ''Volume number<br> Issue<br><br>Pages from - to''
! 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?''
! align="left" | Authors ''<br>1.<br>2.<br>3.<br>Et al?''
|}
|}
Line 81: Line 109:
== 2. ACTIVITY REPORT == <!--''Note: just report activities relevant to this Quarter.''-->  
== 2. ACTIVITY REPORT == <!--''Note: just report activities relevant to this Quarter.''-->  


=== 2.1. Progress Summary ===
=== 2.1. Progress Summary ===


#'''Nagios'''  
#'''Nagios'''  
##Production instance: Polish NGI integrated own tests into offcial EGI SAM/nagios production instance: scientific applications, additional UNICORE and QCG middleware tests
##Production instance: Actualization to version SAM15
##Testing instance: UPDATE-14 (with UNICORE tests) was installed and tested. Our testing instance also started to test uncertified sites.<br>  
##Testing instance: Actualization to version SAM15 and UNICORE probes testing<br>
#<span style="font-weight: bold;">Regional Helpdesk</span>
##Moving to more automatized process of handling tickets in regional helpdesk.<br>  
#'''Unicore'''  
#'''Unicore'''  
##Preparation of UNICORE tests for SAM&nbsp;update 14, testing and debuging
##Monitoring: testing, debugging and suggesting SAM fixes related to UNICORE. Refactoring of UNICORE&nbsp;configuration module for SAM.
##<span lang="en" id="result_box" class="short_text"><span class="hps">Initiation of work on</span></span> UNICORE accounting intergation with APEL
##Accounting:&nbsp;Integration with APEL enters testing phase.
#'''Stage rollout components tested'''
##UNICORE:&nbsp;UNICORE Gateway, UVOS
##GLITE:&nbsp;EMI.apel, EMI.cream, EMI.dpm
#'''Availability/Reliability metrics'''  
#'''Availability/Reliability metrics'''  
##NGI _PL availability for August 80% and in September 89; low A/R due to new services and hardware integration.  
##NGI_PL metrics:&nbsp; November 96%, December 99%; All sites above the targets.  
##BDII metrics: November 99%, December 100%;
#'''NGI_PL security team '''  
#'''NGI_PL security team '''  
##regular operational actions within EGI CSIRT IRTF  
##Incident response and investigation for security incident at Cyfronet, EGI CSIRT incident id: EGI-20111231-01
##taking part in weekly and monthly meetings of EGI CSIRT  
##Regular operational actions within EGI CSIRT IRTF  
##participation in EGI CSIRT F2F meeting in Lyon (2 attendants)
##Taking part in weekly and monthly meetings of EGI CSIRT  
##submission of 2 vulnerabilities to EGI SVG'''<br>'''
##Removing critical vulnerabilities in IFJ-PAN-BG, including checking whole site infrastructure
##Performing security pentesting for WUT site
##Submission of 1 vulnerability to EGI SVG  
##Delegating participant to D4.4 "Security Risk Assessment of the EGI Infrastructure"
#'''ROD&nbsp;NGI_PL'''  
#'''ROD&nbsp;NGI_PL'''  
##NGI_PL registered QCG and CUSTOM_SERVICE services in GOCDB. NGI_PL is testing alarm generation in Operations Portal for these services.
##Coordination of lcg-CE decommission within NGI
##Creation of NGI_PL_SERVICES site, designed for calculation RP availability and reliability metrics
##ROD&nbsp;team didn't exceed ROD&nbsp;performance index target&nbsp;
#'''Changes on sites '''  
#'''Changes on sites '''  
##WCSS64
##CYFRONET-LCG2
###new services UNICORE, QCG<br>  
###Decommission of lcg-CE
##CAMK
###Upgrade of DPM<br>
###Migration to ScientificLinux 5.6 and gLite 3.2  
###New services:&nbsp;
###SE is working right now as SRM and SRMv2
####cream02.grid - CREAMCE&nbsp; UMD<br>
###new services: CREAMCE, APEL
####wms01.grid&nbsp;&nbsp;&nbsp; - WMS EMI<br>  
###new hardware 120TB disc space RAID6 and 144 cores Xeon X5650
####myproxy02.grid - MYPROXY&nbsp;UMD
##WCSS-PPS
###Migration from gLite 3.2 to UMD 1.0
###Moving Site-BDII from CREAM to new host<br>
##PSNC
###New services: UNICORE<br>
##TASK  
##TASK  
###new services:&nbsp;QosCosGrid and UMD Cream
###New services: UNICORE, CREAM-CE<br>
###new hardware: 191 nodes and vSMP machine.
###New hardware: new cluster Galera Plus (192 nodes, each 12-cores), vSMP machine  
##WARSAW_EGEE  
##WARSAW_EGEE  
###new services: ce.polgrid.pl&lt;span class="clickylink" /&gt;, se5.polgrid.pl &lt;span class="clickylink" /&gt;
###Actualization of unicore-gateway to version 4.2.0 and uvos-server to version 1.5.0
###<span class="clickylink">new hardware:</span> 120 x (2CPU (Intel Xeon X5660) + 24GB RAM ), and&nbsp; 32x ( 2CPU(AMD Opteron 2435)&nbsp; + 32GB RAM),&nbsp; SunFire 4540 48TB raw
###New services: QosCosGrid
##New site certified: WUT<br>  
###New hardware: 12 TFPS
##New site certified:  
###NGI_PL_SERVICES - contains NGI_PL core services<br>  
###ICM - contains QCG&nbsp;and UNICORE services
#'''Task forces in which NGI_PL&nbsp;participate'''  
#'''Task forces in which NGI_PL&nbsp;participate'''  
##Regionalisation TF  
##Regionalisation TF  
##UNICORE Integration TF  
##UNICORE Integration TF<br>
##<br>
##Federated Clouds TF


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


# NGI_PL is highly involved in several task forces. We support and introduce a <span lang="en" id="result_box" class="short_text"><span class="hps">wide range of middlewares (glite, UNICORE, QCG) to </span></span><span lang="en" id="result_box" class="short_text"><span class="hps">adapt to the</span> <span class="hps">demands and</span> <span class="hps">needs of users.</span></span>  
All the biggest sites (CYFRONET-LCG2, PSNC, WCSS, TASK, WARSAW-EGEE) in NGI_PL support a <span lang="en" id="result_box" class="short_text"><span class="hps">wide range of middlewares (glite, UNICORE, QCG) to </span></span><span lang="en" id="result_box" class="short_text"><span class="hps">adapt to the</span> <span class="hps">demands and</span> <span class="hps">needs of users. All the services are registerd in GOC&nbsp;DB.
</span></span>  


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


{| cellspacing="0" cellpadding="2" border="1"
{| cellspacing="0" cellpadding="2" border="1"

Latest revision as of 16:52, 22 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
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