Choose timezone
Your profile timezone:
SA1 coordination meeting
→
Europe/Zurich
28-R-06 (CERN)
28-R-06
CERN
Description
Minutes, https://edms.cern.ch/document/923879
Actions, https://twiki.cern.ch/twiki/bin/view/EGEE/SA1_CoordinationTasks
This meeting is 10:00 to 11:30 UTC+2
Remote Participation via EVO in the EGEE Community.
Meeting Access Information:
- Meeting URL
http://evo.caltech.edu/evoGate/koala.jnlp?meeting=MvM2Ml2D2iDIDu9a9lDe9v
- Password: SA1
- Phone Bridge:
ID: 1715260
Password: 7164
-
-
10:00
→
10:10
Admin matters
- DSA1.5: Operations Cookbook
- MSA1.12: Revised Operation Process, Policy, Procedures and Interfaces for EGI
- DSA1.2.2
-
10:10
→
10:30
Transition to EGI
Regular review:
- O-E-9: Coordination of middleware roll-out and deployment: Report about early experiences.
- O-E-10: Coordination of resource allocation and of brokering support for VOs from NGIs, from Poland to Amsterdam. Action on Poland to document present procedures to be transferred to Amsterdam.
- O-E-11: Coordination of interoperations between NGIs and other grids. EGI.eu, from CERN to Sweden. New responsible name known?
- O-E-14: Operation of production grid core software services, catch-all services for international VOs, catch-all CA, from all ROCs to GRNET. Clarify list of services included
- dteam future
- NGI prototyping progress and issues
-
10:30
→
10:45
Final periodic report for EGEE III
The following is extracted from an e-mail sent to all EGEE III AMB members. Please note the date of submission of 30th April. Maite and I will be needing input from the tasks leaders/ROCs/JRUs/partners, mainly about this last quarter. To get the report ready in time, we will need this input by 23rd April. Please start gathering the necessary data, exacly as you would for a quarterly report.
=
The periodic report covering May 2009 – April 2010 and responses to the EC recommendations must be prepared and must be submitted by Friday 30th April 2010 at the latest to the PO (project-eu-egee-po@cern.ch).
The activity progress should be reported, paying particular attention to:
• A summary of progress towards objectives and details for each task
• Highlight clearly significant results
• If applicable, explain the reasons for deviations from Annex I (Description of Work) and their impact on other tasks as well as on available resources and planning
• If applicable, explain the reasons for failing to achieve critical objectives and/or not being on schedule and explain the impact on other tasks as well as on available resources and planning (the explanations should be coherent with the declaration by the project coordinator)
• a statement on the use of resources, in particular highlighting and explaining deviations between actual and planned person-months per work package and per beneficiary in Annex 1 (Description of Work)Templates have been provided for each activity on the basis of the EC requirements for the Project Periodic Report, pre-filled by the PO (with DoW objectives against which to measure progress and deliverable and milestone tables) and provided in the attached file. The relevant activity sections are in pages 11 – 19. We have also added text from the DoW (usually in yellow) that highlights the work that has changed in the 2nd year so please take this into account.
Please bear in mind that much of the material reported in your PM23 Deliverables as well as in previous QRs:
5th QR: https://edms.cern.ch/document/1011593/2
6th QR: https://edms.cern.ch/document/1060661/1
7th QR: https://edms.cern.ch/document/1055688/1NOTE that as no QR8 is in preparation and it is included in this periodic report, particular attention must be paid to including the whole period duration (all 4 quarters) in your report.
Link to the previous periodic report (first year of EGEE-III): https://edms.cern.ch/document/991129/3
You can see the text corresponding to each activity’s “work progress and achievements during the period” starting from page 33 onwards.
= -
10:45
→
11:05
New version of operations manual for validation
The EGEE Grid Operations manuals have been updated to reflect changes in the operations dashboard and the new NAGIOS monitoring system. Many grammatical and typographical errors have also been fixed.
Revised manuals are as follows:
* Operational Procedures Manual for ROCs and Sites:
https://twiki.cern.ch/twiki/bin/view/EGEE/DRAFTOperationalProceduresforCCOD
* Operational Procedures Manual for Regional Operations (ROD):
https://twiki.cern.ch/twiki/bin/view/EGEE/DRAFTOperationalProceduresforROCsAndSites
* Operational Procedures Manual for central COD (C-COD):
https://twiki.cern.ch/twiki/bin/view/EGEE/DRAFTOperationalProceduresforRODChanges:
<u>Significant changes</u>:
* all references to the old SAM tests have been replaced with equivalent NAGIOS tests
* sections of note are the monitoring and problem tracking tools in all manuals.
* changes to the dashboard tool description.
* revised the tool procedures to reflect the latest dashboard release.<u>Minor changes include</u>:
* Links cross checked to reflect new tools
* Broken links were also replaced
* Grammatical and spelling checks
* Re-wording of parts of procedures for clarity. -
11:05
→
11:20
GStat 2 15m
-
11:20
→
11:30
End of support of "classic" pre-production infrastructure
Over the last few months, the pre-production service (PPS) has slowly but steadily been replaced by two new processes: the staged roll-out and the pilot services.
Although the permanent PPS infrastructure was unsupported during EGEE III some of the services have been kept running on a best-efforts basis in support of the transition to the new model. Now that the transition is fully established, with LIP taking on the coordination role, it’s a good time to “formally” release these resources.
The site CERN_PPS has been offering so far some ‘gluing’ services to the infrastructure which won’t be supported anymore starting from the beginning of April. They are:
* Top-level BDII (a new instance is now available at LIP in the context of the support to staged roll-out )
* PPS AFS UI (not supported elsewhere)
* SAM PPS (will run on best effort until the end of the project but then will stop)
* PPS website (this will be supported by LIP across the end of the project specifically in the sections regarding pilot services and staged roll-out until a corresponding EGI site is set-up)
Centres that still want to run PPS sites or that are in the process of integrating them in the production system will have eventually to negotiate through their ROC/NGI with the Ibergrid/Spanish NGI for possible extensions to the above services. -
11:30
→
11:35
AOB
-
10:00
→
10:10
