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

From EGIWiki
Jump to: navigation, search
(2. ACTIVITY REPORT)
 
(11 intermediate revisions by 4 users not shown)
Line 1: Line 1:
__NOTOC__
+
{{Template:EGI-Inspire menubar}}
 +
 
 +
{{Template:Inspire_reports_menubar}}
 +
{{TOC_right}}
  
 
{| border="1" cellspacing="0" cellpadding="2"
 
{| border="1" cellspacing="0" cellpadding="2"
Line 20: Line 23:
  
 
==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 30:
 
**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===
Line 36: Line 39:
 
|-
 
|-
 
!scope="col"|Date||Location||Title||Participants||Outcome (Short report & Indico URL)  
 
!scope="col"|Date||Location||Title||Participants||Outcome (Short report & Indico URL)  
 +
|-
 +
|01-03 December 2010
 +
|Wrocław, Poland
 +
|I3 Conference
 +
| 3
 +
|Many of the conference participants were involved in Polish NGI project. There were also many talks concerning NGI work mainly focused on operational problems and grid security aspects.
 
|-
 
|-
 
|}
 
|}
Line 47: Line 56:
 
|-
 
|-
 
|24.01-26.01||Amsterdam||OMB meeting||3||https://www.egi.eu/indico/conferenceDisplay.py?confId=153
 
|24.01-26.01||Amsterdam||OMB meeting||3||https://www.egi.eu/indico/conferenceDisplay.py?confId=153
 +
|-
 +
|23-26.01.2011||Utrecht, Nederland||EUGridPMA meeting||1||http://www.eugridpma.org/meetings/2011-01/
 +
|-
 +
|7-12.11.2010||Madrid, Spain||Fussion community support technical meeting||1||
 +
|-
 +
|24 January 2011||University of Göttingen / Germany||Network Requirements for LHC data analysis||32|| The meeting covered network requirements for Tier2 centers seen from the
 +
perspective of the largest EGI users community. The discussion concerned
 +
mainly bandwidth requirements, desired network topology and the
 +
possibility of using dedicated channels within NRENs infrastructure to
 +
directly connect Tier1/2 centers. The outcome was to switch to mesh-like
 +
topology to lessen the load on connections between Tier1s and their
 +
associated Tier2s. For Polish NGI this means that general Geant
 +
connection becomes more important than dedicated link to DFN.
 +
 +
http://indico.desy.de/conferenceTimeTable.py?confId=3823
 
|-
 
|-
 
|}
 
|}
Line 69: Line 93:
  
 
===2.1. Progress Summary===
 
===2.1. Progress Summary===
NGI_PL is fully operational. All necessary operational teams and tools are established.  
+
NGI_PL continued works related to operations. ROD and Regional Technical Support teams operated seamlessly. The size of the NGI in terms of computing and storage capabilities is growing due to recent procurements.
 +
 
 +
During last quarter all monitoring system updates were regularly applied to regional instance to keep consistency with EGI.  
  
During last quarter all monitoring system updates were regularly applied to regional instance to keep consistency with EGI and some fixes to web service interface between GGUS and NGI_PL helpdesk system were implemented.  
+
All sites completed migration from RGMA to ActiveMQ APEL.
  
 
===2.2. Main Achievements===
 
===2.2. Main Achievements===
  
NGI_PL representatives participate in OLA task force and in O-E-11 task (The Coordination of interoperations between NGIs and with other Grids) in terms of integration of UNICORE probes into SAM/Nagios.  
+
NGI_PL representatives participate in OLA task force and took part in discussions related to UNICORE within "Coordination of interoperations between NGIs and with other Grids" task.  
  
NGI_PL also take part in UNICORE integration task force which was recently created. The goal of the task force is to discuss various integration issues related to UNICORE middleware in terms of operations.
+
NGI_PL also take part in "UNICORE integration task force" which has been recently created. The goal of the task force is to discuss various technical integration issues related to UNICORE middleware in terms of operations.
  
 
===2.3. Issues and mitigation===
 
===2.3. Issues and mitigation===
Line 85: Line 111:
 
!scope="col"| Issue Description
 
!scope="col"| Issue Description
 
!scope="col"| Mitigation Description
 
!scope="col"| Mitigation Description
|-
 
|Issue description || Issue mitigation
 
 
|-
 
|-
 
|}
 
|}

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
3 NGI_PL CYFRONET Małgorzata Krakowian


1. MEETINGS AND DISSEMINATION

1.1. CONFERENCES/WORKSHOPS ORGANISED

Date Location Title Participants Outcome (Short report & Indico URL)
01-03 December 2010 Wrocław, Poland I3 Conference 3 Many of the conference participants were involved in Polish NGI project. There were also many talks concerning NGI work mainly focused on operational problems and grid security aspects.

1.2. OTHER CONFERENCES/WORKSHOPS ATTENDED

Date Location Title Participants Outcome (Short report & Indico URL)
24.01-26.01 Amsterdam OMB meeting 3 https://www.egi.eu/indico/conferenceDisplay.py?confId=153
23-26.01.2011 Utrecht, Nederland EUGridPMA meeting 1 http://www.eugridpma.org/meetings/2011-01/
7-12.11.2010 Madrid, Spain Fussion community support technical meeting 1
24 January 2011 University of Göttingen / Germany Network Requirements for LHC data analysis 32 The meeting covered network requirements for Tier2 centers seen from the

perspective of the largest EGI users community. The discussion concerned mainly bandwidth requirements, desired network topology and the possibility of using dedicated channels within NRENs infrastructure to directly connect Tier1/2 centers. The outcome was to switch to mesh-like topology to lessen the load on connections between Tier1s and their associated Tier2s. For Polish NGI this means that general Geant connection becomes more important than dedicated link to DFN.

http://indico.desy.de/conferenceTimeTable.py?confId=3823


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

NGI_PL continued works related to operations. ROD and Regional Technical Support teams operated seamlessly. The size of the NGI in terms of computing and storage capabilities is growing due to recent procurements.

During last quarter all monitoring system updates were regularly applied to regional instance to keep consistency with EGI.

All sites completed migration from RGMA to ActiveMQ APEL.

2.2. Main Achievements

NGI_PL representatives participate in OLA task force and took part in discussions related to UNICORE within "Coordination of interoperations between NGIs and with other Grids" task.

NGI_PL also take part in "UNICORE integration task force" which has been recently created. The goal of the task force is to discuss various technical integration issues related to UNICORE middleware in terms of operations.

2.3. Issues and mitigation

Issue Description Mitigation Description