Difference between revisions of "EGI-InSPIRE:France-QR11"
Jump to navigation
Jump to search
(Created page with "{{Template:Op menubar}} {{Template:Inspire_reports_menubar}} {{TOC_right}} <br> {| class="wikitable" |- ! scope="col" | Quarterly Report Number ! scope="col" | NGI Name ! s...") |
|||
Line 10: | Line 10: | ||
! scope="col" | Author | ! scope="col" | Author | ||
|- | |- | ||
| < | | <Q11> | ||
| <NGI | | <NGI FRANCE> | ||
| < | | <France/CNRS> | ||
| < | | <Gilles MATHIEU> | ||
|} | |} | ||
Line 34: | Line 34: | ||
! Outcome (Short report & Indico URL) | ! Outcome (Short report & Indico URL) | ||
|- | |- | ||
| | |29/11 | ||
| | |Bordeaux | ||
| | |FG Operations workshop | ||
| | |25 | ||
| | |https://indico.in2p3.fr/conferenceTimeTable.py?confId=6900#20121129 | ||
|- | |- | ||
| | |30/11 | ||
| | |Bordeaux | ||
| | |FG Cloud workshop | ||
| | |25 | ||
| | |https://indico.in2p3.fr/conferenceTimeTable.py?confId=6900#20121130 | ||
|} | |} | ||
Line 63: | Line 57: | ||
! Outcome (Short report & Indico URL) | ! Outcome (Short report & Indico URL) | ||
|- | |- | ||
| | |10-16/11 | ||
|Salt Lake City | |||
|Supercomputing 2012 | |||
|3 | |||
|http://sc12.supercomputing.org/ | |||
| | |||
| | |||
| | |||
| | |||
|- | |- | ||
| | |29-30/01 | ||
| | |Amsterdam | ||
| | |Evolving EGI Workshop | ||
| | |4 | ||
| | |https://indico.egi.eu/indico/conferenceTimeTable.py?confId=1252 | ||
|} | |} | ||
Line 116: | Line 104: | ||
===2.1. Progress Summary=== <!-- Provide your test below --> | ===2.1. Progress Summary=== <!-- Provide your test below --> | ||
===2.2. Main Achievements=== <!-- | ===2.2. Main Achievements=== <!-- | ||
Provide your text below | Provide your text below | ||
--> | --> | ||
Finalised transition from glite software to EMI | |||
=== 2.3. Issues and mitigation === | === 2.3. Issues and mitigation === | ||
Line 128: | Line 119: | ||
! scope="col" | Mitigation Description | ! scope="col" | Mitigation Description | ||
|- | |- | ||
| | | Delayed migration to EMI | ||
| | | close follow-up with sites to ensure migration could be complete without loosing quality of service | ||
|} | |} | ||
Revision as of 15:27, 31 January 2013
Main | EGI.eu operations services | Support | Documentation | Tools | Activities | Performance | Technology | Catch-all Services | Resource Allocation | Security |
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 |
---|---|---|---|
<Q11> | <NGI FRANCE> | <France/CNRS> | <Gilles MATHIEU> |
1. MEETINGS AND DISSEMINATION
Note: Complete the tables below by adding as many rows as needed.
1.1. CONFERENCES/WORKSHOPS ORGANISED
Date | Location | Title | Participants | Outcome (Short report & Indico URL) |
---|---|---|---|---|
29/11 | Bordeaux | FG Operations workshop | 25 | https://indico.in2p3.fr/conferenceTimeTable.py?confId=6900#20121129 |
30/11 | Bordeaux | FG Cloud workshop | 25 | https://indico.in2p3.fr/conferenceTimeTable.py?confId=6900#20121130 |
1.2. OTHER CONFERENCES/WORKSHOPS ATTENDED
Date | Location | Title | Participants | Outcome (Short report & Indico URL) |
---|---|---|---|---|
10-16/11 | Salt Lake City | Supercomputing 2012 | 3 | http://sc12.supercomputing.org/ |
29-30/01 | Amsterdam | Evolving EGI Workshop | 4 | https://indico.egi.eu/indico/conferenceTimeTable.py?confId=1252 |
1.3. PUBLICATIONS
Publication title | Journal / Proceedings title | Journal references Volume number Issue Pages from - to |
Authors 1. 2. 3. Et al? |
---|---|---|---|
<Publication title> | <Journal/Proceedings> | Vol:<volume number> Issue:<Issue> Pg: <from> - <to> |
1.<Author 1> 2.<Author2> 3. <Author3> |
<Publication title> | <Journal/Proceedings> | Vol:<volume number> Issue:<Issue> Pg: <from> - <to> |
1.<Author 1> 2.<Author2> 3. <Author3> |
<Publication title> | <Journal/Proceedings> | Vol:<volume number> Issue:<Issue> Pg: <from> - <to> |
1.<Author 1> 2.<Author2> 3. <Author3> |
2. ACTIVITY REPORT
2.1. Progress Summary
2.2. Main Achievements
Finalised transition from glite software to EMI
2.3. Issues and mitigation
Issue Description | Mitigation Description |
---|---|
Delayed migration to EMI | close follow-up with sites to ensure migration could be complete without loosing quality of service |