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:France-QR3"

From EGIWiki
Jump to navigation Jump to search
Line 87: Line 87:
===2.1. Progress Summary===
===2.1. Progress Summary===
<!-- Provide your test below -->
<!-- Provide your test below -->
- Set-up of national accounting DB, migration to AMQ completed
- Set-up of Nagios box dedicated to Biomed, circulated to SA1
- Prototype of decommissioning procedure, circulated to SA1


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

Revision as of 05:11, 11 February 2011


Quarterly Report Number NGI Name Partner Name Author
3 NGI_FRANCE CNRS, CEA Hélène Cordier


1. MEETINGS AND DISSEMINATION

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
  • for outcome, please list tangible agreements, decisions instead of listing program points or presentations you made. Otherwise put: “-“
  • include your local events only if there was any EGI-related topic on the agenda
  • provide an indico URL to your presentation (if available) or to the event itself.
    • 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.

1.1. CONFERENCES/WORKSHOPS ORGANISED

Date Location Title Participants Outcome (Short report & Indico URL)
<Date> <Location> <Title> <Participants> <Outcome>
<Date> <Location> <Title> <Participants> <Outcome>
<Date> <Location> <Title> <Participants> Test

1.2. OTHER CONFERENCES/WORKSHOPS ATTENDED

Date Location Title Participants Outcome (Short report & Indico URL)
24-25/01 Amsterdam Network Support OMB, OTAG Outcome
26/01 Amsterdam F2F COD 1 Outcome
<Date> <Location> Title Participants Outcome Test


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

- Set-up of national accounting DB, migration to AMQ completed - Set-up of Nagios box dedicated to Biomed, circulated to SA1 - Prototype of decommissioning procedure, circulated to SA1

2.2. Main Achievements

The French network activity has been impacted by internal restructuring: the current team will have to leave the project by the end of April. The CNRS is currently studying which part of this unfunded activity could be continued by a new team. As a result of this situation, during this quarter, the network activity of the French NGI focused, firstly, on the network troubleshooting task, in order to provide a first version of the tool called HINTS (Hints for Instant Network Trouble-Shooting) to NGI France and to the EGI network activity, and secondly, to prepare the handover of the activity (especially about the maintenance of HINTS, since sustainability is a major aspect from the point of view of the EGI community). These basic features of HINTS have been implemented with the Java-based ZK Framework. As the duration which was initially planned for this project has been reduced, some secondary features could not be implemented, but the software is already operational. HINTS has been demonstrated during at the Operations Management Board in Amsterdam the 24-25 January 2011 (https://www.egi.eu/indico/contributionDisplay.py?sessionId=1&contribId=10&confId=153) and the current team is still working on some additional features for a few more months.

2.3. Issues and mitigation

Issue Description Mitigation Description
Issue description Issue mitigation