EGI-InSPIRE:Netherlands-QR7
Revision as of 13:58, 5 February 2012 by Ron (talk | contribs) (→1.2. OTHER CONFERENCES/WORKSHOPS ATTENDED)
Quarterly Report Number | NGI Name | Partner Name | Author |
---|---|---|---|
7 | NGI_NL | SARA | Ron Trompert |
1. MEETINGS AND DISSEMINATION
1.1. CONFERENCES/WORKSHOPS ORGANISED
Date | Location | Title | Participants | Outcome (Short report & Indico URL) |
---|---|---|---|---|
1.2. OTHER CONFERENCES/WORKSHOPS ATTENDED
Date | Location | Title | Participants | Outcome (Short report & Indico URL) |
---|---|---|---|---|
9-10/11/2011 | Netherlands | NGI Coordinators Kick Off meeting | 1 | |
3-4/11/2011 | Netherlands | Projekt Managment Board EGI-Inspire |
1 | |
23-24/01/2012 | Netherlands | OMB | 1 | |
26-24/01/2012 | Netherlands | PMB EGI-INSPIRE | 1 | |
23rd Jan 2012 | Amesterdam, Netherlands | WLCG TEG - Operations | 2 |
|
24th-25th Jan 2012 | Amesterdam, Netherlands | WLCG TEG - Storage Management & Data Management | 2 |
|
26th Jan 2012 | Amesterdam, Netherlands | WLCG TEG - Security | ~ 2 |
|
30-31 Jan 2012 | LBL Berkeley, USA | LHCOPN and LHCONE joint meeting | 1 |
|
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
We have started the preparation for tender procedures to add 3.5PB of disk storage and approximately 2500 cores to our infrastructure. As their operation is ramping up, the LOFAR VO has written 1PB of data to us the last few months of 2011. At the moment, the LOFAR VO has more data on tape at SARA than, for example, ATLAS.
BiGGrid HPC Cloud has been taken into production on January 1st this year. This hardware is also used for projects originating from EGI's federated cloud task force.
We have put out a tender for the replacement of Life Sciences Grid hardware. The offers have been received in the meantime and the winner has been selected. We expect to replace the hardware in the spring.
2.2. Main Achievements
business as usual.
2.3. Issues and mitigation
Issue Description | Mitigation Description |
---|