Difference between revisions of "EGI-InSPIRE:Poland-QR7"
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 |- | | | …') |
m (moved Poland-QR7 to EGI-InSPIRE:Poland-QR7) |
||
(22 intermediate revisions by 2 users not shown) | |||
Line 1: | Line 1: | ||
{{Template:EGI-Inspire menubar}} | |||
{| | |||
{{Template:Inspire_reports_menubar}} | |||
{{TOC_right}} | |||
{| cellspacing="0" cellpadding="2" border="1" | |||
|- | |- | ||
| | ! scope="col" | Quarterly Report Number | ||
| | ! scope="col" | NGI Name | ||
| | ! scope="col" | Partner Name | ||
| | ! scope="col" | Author | ||
|- | |- | ||
| 7 | |||
| 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 26: | Line 27: | ||
**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 === | |||
{| | {| cellspacing="0" border="1" | ||
|- | |- | ||
!scope="col"|Date | ! scope="col" | 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=== | === 1.2. OTHER CONFERENCES/WORKSHOPS ATTENDED === | ||
{| | {| cellspacing="0" border="1" | ||
|- | |- | ||
!scope="col"|Date | ! scope="col" | | ||
Date | |||
! Location | |||
! Title | |||
! Participants | |||
! Outcome (Short report & Indico URL) | |||
|- | |- | ||
||||| | | 9-10/11/2011 | ||
| The Netherlands | |||
| NGI Coordinators Kick Off meeting | |||
| 1 | |||
| <br> | |||
|- | |- | ||
| 3-4/11/2011 | |||
| The Netherlands | |||
| Projekt Managment Board <br> EGI-Inspire | |||
| 1 | |||
| <br> | |||
|- | |||
| 23-24/01/2012 | |||
| The Netherlands | |||
| OMB | |||
| 1 | |||
| <br> | |||
|- | |||
| 26-24/01/2012 | |||
| The Netherlands | |||
| PMB EGI-INSPIRE | |||
| 1 | |||
| <br> | |||
|- | |||
| 12-18/11/2011 | |||
| Seattle, USA | |||
| Supercomputing 11 | |||
| 1 | |||
| http://sc11.supercomputing.org | |||
|} | |} | ||
Line 59: | Line 95: | ||
|<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.--> | |||
{| | {| 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?'' | |||
|} | |} | ||
== 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 === | |||
= | #'''Nagios''' | ||
##Production instance: Actualization to version SAM15 | |||
##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''' | |||
##Monitoring: testing, debugging and suggesting SAM fixes related to UNICORE. Refactoring of UNICORE configuration module for SAM. | |||
##Accounting: Integration with APEL enters testing phase. | |||
#'''Stage rollout components tested''' | |||
##UNICORE: UNICORE Gateway, UVOS | |||
##GLITE: EMI.apel, EMI.cream, EMI.dpm | |||
#'''Availability/Reliability metrics''' | |||
##NGI_PL metrics: November 96%, December 99%; All sites above the targets. | |||
##BDII metrics: November 99%, December 100%; | |||
#'''NGI_PL security team ''' | |||
##Incident response and investigation for security incident at Cyfronet, EGI CSIRT incident id: EGI-20111231-01 | |||
##Regular operational actions within EGI CSIRT IRTF | |||
##Taking part in weekly and monthly meetings of EGI CSIRT | |||
##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 NGI_PL''' | |||
##Coordination of lcg-CE decommission within NGI | |||
##Creation of NGI_PL_SERVICES site, designed for calculation RP availability and reliability metrics | |||
##ROD team didn't exceed ROD performance index target | |||
#'''Changes on sites ''' | |||
##CYFRONET-LCG2 | |||
###Decommission of lcg-CE | |||
###Upgrade of DPM<br> | |||
###New services: | |||
####cream02.grid - CREAMCE UMD<br> | |||
####wms01.grid - WMS EMI<br> | |||
####myproxy02.grid - MYPROXY 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 | |||
###New services: UNICORE, CREAM-CE<br> | |||
###New hardware: new cluster Galera Plus (192 nodes, each 12-cores), vSMP machine | |||
##WARSAW_EGEE | |||
###Actualization of unicore-gateway to version 4.2.0 and uvos-server to version 1.5.0 | |||
###New services: QosCosGrid | |||
###New hardware: 12 TFPS | |||
##New site certified: | |||
###NGI_PL_SERVICES - contains NGI_PL core services<br> | |||
###ICM - contains QCG and UNICORE services | |||
#'''Task forces in which NGI_PL participate''' | |||
##Regionalisation TF | |||
##UNICORE Integration TF<br> | |||
##Federated Clouds TF | |||
=== 2.2. Main Achievements === | |||
=== | 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 DB. | ||
</span></span> | |||
{| | === 2.3. Issues and mitigation === | ||
{| cellspacing="0" cellpadding="2" border="1" | |||
|- | |- | ||
! scope="col" | Issue Description | |||
! scope="col" | Mitigation Description | |||
|} | |} | ||
Latest revision as of 17: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
- Nagios
- Production instance: Actualization to version SAM15
- Testing instance: Actualization to version SAM15 and UNICORE probes testing
- Regional Helpdesk
- Moving to more automatized process of handling tickets in regional helpdesk.
- Moving to more automatized process of handling tickets in regional helpdesk.
- Unicore
- Monitoring: testing, debugging and suggesting SAM fixes related to UNICORE. Refactoring of UNICORE configuration module for SAM.
- Accounting: Integration with APEL enters testing phase.
- Stage rollout components tested
- UNICORE: UNICORE Gateway, UVOS
- GLITE: EMI.apel, EMI.cream, EMI.dpm
- Availability/Reliability metrics
- NGI_PL metrics: November 96%, December 99%; All sites above the targets.
- BDII metrics: November 99%, December 100%;
- NGI_PL security team
- Incident response and investigation for security incident at Cyfronet, EGI CSIRT incident id: EGI-20111231-01
- Regular operational actions within EGI CSIRT IRTF
- Taking part in weekly and monthly meetings of EGI CSIRT
- 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 NGI_PL
- Coordination of lcg-CE decommission within NGI
- Creation of NGI_PL_SERVICES site, designed for calculation RP availability and reliability metrics
- ROD team didn't exceed ROD performance index target
- Changes on sites
- CYFRONET-LCG2
- Decommission of lcg-CE
- Upgrade of DPM
- New services:
- cream02.grid - CREAMCE UMD
- wms01.grid - WMS EMI
- myproxy02.grid - MYPROXY UMD
- cream02.grid - CREAMCE UMD
- WCSS-PPS
- Migration from gLite 3.2 to UMD 1.0
- Moving Site-BDII from CREAM to new host
- PSNC
- New services: UNICORE
- New services: UNICORE
- TASK
- New services: UNICORE, CREAM-CE
- New hardware: new cluster Galera Plus (192 nodes, each 12-cores), vSMP machine
- New services: UNICORE, CREAM-CE
- WARSAW_EGEE
- Actualization of unicore-gateway to version 4.2.0 and uvos-server to version 1.5.0
- New services: QosCosGrid
- New hardware: 12 TFPS
- New site certified:
- NGI_PL_SERVICES - contains NGI_PL core services
- ICM - contains QCG and UNICORE services
- NGI_PL_SERVICES - contains NGI_PL core services
- CYFRONET-LCG2
- Task forces in which NGI_PL participate
- Regionalisation TF
- UNICORE Integration TF
- 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 |
---|