1. Steve Brewer Stichting European Grid Initiaitive
WP5: Proofs of Concept
Steve Brewer
Stichting European Grid Initiaitive

2. Resource Infrastructure Providers
Resource Centres
EGI-InSPIRE & EGI Council members
326
Including integrated RPs
352
Countries 42 54
Integrated EGI-InSPIRE Partners and EGI Council Members
Internal/External Resource Providers (being integrated)
External Resource Providers (integrated)
Peer Resource Providers

3. EGI: strategy for 2020 Pillars of the strategy:
European-wide coordination and interaction with research communities and national resource infrastructure providers
Coordination, maintenance, operation and delivery of an open uniform European-wide federated production infrastructure
Developing and promoting technologies for federating new resources
Supporting the integration and operation of scalable interdisciplinary Virtual Research Environments personalised to each research community

4. EGI Technical forum, Prague

5. Federated Clouds Task Force
Community driven testbed activity
61 individuals, 23 institutions, 13 countries
Diverse stakeholders
15 Resource Providers, 7 Technology Providers, 4 Research Communities
Many Cloud management solutions
7 OpenNebula, 5 OpenStack, 3 StratusLab, …
Prototype demonstration in March 2012
7 Resource Provider participating
2 Cloud Management interfaces: OCCI and CDMI
4 services: Information System, Marketplace, Monitoring and Accounting

6. EGI’s Cloud Strategy
Personalised environments for individual research communities
in the European Research Area
Community Services
Community Services
SaaS
Globus
Genesis II
Community Platform
Core software and support
EGI.eu Coordination
PaaS
dCache
gLite
ARC
Globus
UNICORE
NGI
VM Mgmt
Data
Information
Monitoring
Accounting
Notification
EGI-wide message bus
NGI
VM Mgmt
Data
Information
Monitoring
Accounting
Notification
NGI
VM Mgmt
Data
Information
Monitoring
Accounting
Notification
Commercial
VM Mgmt
Data
Information
Monitoring
Accounting
Notification
IaaS

7. WP5 - Objectives
WP5 aims to prove in concrete experiments the concepts established by WP proofs will be carried out in correspondence of deliverable D3.1 and D3.2 - The results of the proofs will inform the evolution of the Roadmap design. The execution of the proofs of concept will be based on the re-use of the eCulture Science Gateway produced by INDICATE. INFN agreed to upgrade the service with the upload function that will enable the content providers to store their data. 6 pilot sites for the proof of concepts are foreseen in Europe, led by EGI.eu: - Italy with e-infrastructure facilities provided by INFN & data provided by ICCU - Poland with e-infrastructure facilities and data provided by PSNC - Hungary with e-infrastructure facilities provided by NIIFI and data provided by Hungarian cultural institutions that will cooperate with NIIFI - Sweden, Belgium and Estonia, with e-infrastructure facilities provided by the NGI exploiting the Memorandum of Understanding signed in the frame of DC-NET and data provided by the DCH-RP partners.

8. Description of work and role of partners
Task Technical planning of the first run of proof of concept (month 1 - 3) EGI.eu
Task Upgrade of the eCulture Science Gateway (month 1 - 6) – INFN
Task First proof of concept (month ) – EGI.eu
Task Second proof of concept (month ) – EGI.eu

9. List of deliverables for WP5
Number
Deliverable Title
Delivery date
D5.1 Technical Plan for DCH-RP proofs of
concept 3
D5.2 Upgraded eCulture Science Gateway 6
D5.3 Report on the first proof of concept 12
D5.4 Report on the second proof of 21

10. Description of deliverables
D5.1) Technical Plan for DCH-RP proofs of concept: This deliverable provides a detailed planning of the technical activities to be carried out by each partner involved in the proof of concept. [month 3]
D5.2) Upgraded eCulture Science Gateway: This deliverable is the eCulture Science Gateway already available from the INDICATE project, that is upgraded with the upload functions required to run the proof of concept of DCH-RP. [month 6]
D5.3) Report on the first proof of concept: Detailed report of the results of the first proof of concept. Lessons learnt are illustrated and commented, highlighting recommendations to WP3. [month 12]
D5.4) Report on the second proof of concept: This is the final report of WP5. It provides: - the detailed description of the results of the second proof of concept - lessons learnt in this second run, highlighting differences from the first run - recommendations to WP3 for the final design of the Roadmap - description of what remains to be done within other future/parallel initiatives [month 21]

11. Schedule of milestones (WP5)
Mile-stone number
Milestone name
Lead bene-ficiary number
Delivery date
Comments
MS12
Technical planning of the proof of concept 7 3
Detailed plans are delivered that can be used by the partners involved in the proofs of concept to plan their activities
MS13
eCulture Science Gateway upgraded 8 6
the eCulture Science Gateway is upgraded with the upload functions and it is ready to be used in the proof of concept
MS14
First run of the proof of concept completed
Experimented completed and report delivered
MS15
Second run of proof of concept completed 15
Proof of concept completed and final report delivered

12. Steve Brewer steve.brewer@egi.eu
What happens next?
Capture more technical details of the eCSG
Capture more technical details of the 6 pilot sites
Check calendars for opportunities and clashes
Explore how EGI’s cloud model can support and extend the eCSG services
Introduce dissemination teams
Produce detailed technical plan for the WP (PM3)
Upgrade eCulture Science Gateway (PM6)
First run of the proof of concept completed (PM8)
Report on the first proof of concept (PM12)
Steve Brewer
Rome, 8/10/2012
Kick-off meeting - 12