Name: EGI User Virtualisation Workshop Discussions
Start: 2011-05-12T10:00:00+02:00
End: 2011-05-13T16:00:00+02:00
Location: Science Park, Amsterdam

EGI User Virtualisation Workshop Discussions

from Thursday, 12 May 2011 (10:00) to Friday, 13 May 2011 (16:00)

Monday, 9 May 2011
Tuesday, 10 May 2011
Wednesday, 11 May 2011
Thursday, 12 May 2011
10:00 Welcome & Vision - Steven Newhouse (EGI.EU)
Welcome & Vision
- Steven Newhouse (EGI.EU)
10:00 - 10:30
Room: Z011 (Turingzaal) Describe the aims of the workshop and what we want to get out of it by the end.
10:30 Validating the Use Cases
Validating the Use Cases
10:30 - 11:30
Room: Z011 (Turingzaal) Participating projects and user communities validate the EGI Cloud Architecture Use Cases by presenting overlap and disparity of their own use cases: - Which project/community use cases fit well with the EGI Cloud Architecture Use Cases? - Which project/community use cases do not fit in? This is an open session where projects and communities can align their planned use of clouds to the 6 identified scenarios and where their planned use goes beyond these 6 scenarios.

11:30 Identifying and endorsing new use cases
Identifying and endorsing new use cases
11:30 - 12:00
Room: Z011 (Turingzaal) Following on from the Use Case validation session, which of the 6 scenarios are going to be adopted? What are the clouds usage models that are not supported by these 6 scenarios? Can we group and prioritise these usage models and decide if they are things we need to consider now or are marked for inclusion into future iterations of the EGI Cloud Architecture document.

12:00 Lunch
Lunch
12:00 - 13:00
Room: Z011 (Turingzaal)
13:00 Breakout session: Accounting - John Gordon (STFC)
Breakout session: Accounting
- John Gordon (STFC)
13:00 - 15:00
Room: Z010 (Newtonzaal)
Breakout session: VM Management - Alexander Papaspyrou (Technische Universität Dortmund)
Breakout session: VM Management
- Alexander Papaspyrou (Technische Universität Dortmund)
13:00 - 15:00
Room: Z011 (Turingzaal)
15:00 Coffee
Coffee
15:00 - 15:30
Room: Z011 (Turingzaal)
15:30 Breakout session: Information - MORRIS RIEDEL (JUELICH SUPERCOMPUTING CENTRE)
Breakout session: Information
- MORRIS RIEDEL (JUELICH SUPERCOMPUTING CENTRE)
15:30 - 17:30
Room: Z011 (Turingzaal)
Breakout session: Monitoring - Jeffrey Templon
Breakout session: Monitoring
- Jeffrey Templon
15:30 - 17:30
Room: Z010 (Newtonzaal)
Friday, 13 May 2011
09:00 Breakout session stand-ups - Jeffrey Templon John Gordon (STFC) Alexander Papaspyrou (Technische Universität Dortmund) MORRIS RIEDEL (JUELICH SUPERCOMPUTING CENTRE)
Breakout session stand-ups
- Jeffrey Templon
- John Gordon (STFC)
- Alexander Papaspyrou (Technische Universität Dortmund)
- MORRIS RIEDEL (JUELICH SUPERCOMPUTING CENTRE)
09:00 - 10:00
Room: Z011 (Turingzaal) A representative summarises the findings of the respective breakout session using the provided template.
10:00 Coffee
Coffee
10:00 - 10:30
Room: Z011 (Turingzaal)

10:30 Technical discussion: Gap analysis
Technical discussion: Gap analysis
10:30 - 12:00
Room: Z011 (Turingzaal) Using the information reported from the breakout sessions, this plenary performs a gap analyisis by triaging the presented issues and merges them into a single prioritised list of work items for Technology Providers to pick up.

12:00 Lunch
Lunch
12:00 - 13:00
Room: Z011 (Turingzaal)

13:00 Technical discussion: Implementation roadmap
Technical discussion: Implementation roadmap
13:00 - 14:30
Room: Z011 (Turingzaal) From the prioritised gap analysis and list of issues developed in the previous session, Technology Providers and other members of the community have an opportunity to show how their work can fill now, or how their implementation roadmaps will soon fill, the identified gaps.

14:30 Coffee
Coffee
14:30 - 15:00
Room: Z011 (Turingzaal)

15:00 Wrap-up and next steps
Wrap-up and next steps
15:00 - 16:00
Room: Z011 (Turingzaal) A final review of the technology gaps that remain unfilled from the earlier requirements sessions and providers presentations, and the identification of groups to start the deployment of these technologies. There should be a clear list of actions to be tackled before the attendees depart.