Name: TCB-19 (F2F)
Start: 2013-06-17T10:00:00+02:00
End: 2013-06-17T16:05:00+02:00
Location: Amsterdam

- EGI ecosystem support model
  
  Held in a workshop style, this session will begin with setting the context for Technology Providers in the larger picture.
  
  Through discussions and active participation and contribution this session seeks to elicit specific and concrete support models for different types of Technology Providers: Ranging from small teams taking ownership of a set of specific libraries to Platform Integrators that assemble and bundle services, libraries and other types of software into self-sufficient and well defined Community Platforms, all contributions are part of the EGI ecosystem.
  
  The goal of this session is to find commonalities and differences between support models, as well as backing Technology Providers that are interested in taking discussions further into commitment agreements for these models.
  document
  
  EGI-1098-D230-final.pdf
  
  EGI-InSPIRE-D2.33-FINAL.pdf
  
  EGI-InSPIRE-MS514-FINAL.pdf
  
  EGI-TCB-1778-v6.pdf
- 12:30
  
  Lunch
- EGI Platform Architecture
  
  After having identified, in the previous session, a number of support models and Technology Providers that fit that scheme and are interested in discussing committing to it, this 2 hour session will examine and validate the EGI Platform architecture.
  
  Participants will look at the current EGI Platform Architecture, what subsystems and services each modeled platform will or should comprise of, and where the interaction and integration points between different platforms will be.
  
  In this workshop, participants will also work towards drafting a number of Community Platforms, identify product teams that wish to contribute software to them, and who shall be responsible for assembly, integration and provisioning.
  - 1
    
    Introduction
    
    Overview, organisation of the whole picture, and alignment with the EGI strategy
  - 2
    
    EGI Platforms
    
    An overview and scope of the EGI principal platforms: The EGI Core Infrastructure Platform - A solution to federate distributed e-Infrastructures. The EGI Cloud Infrastructure Platform - A federated IaaS Cloud platform The EGI Collaboration Platform - Services to facilitate collaboration across Research Communities
  - 3
    
    Community Platforms, UMD and the Software Repository
    
    What is EGI's definition of a Community Platform? Does it fit the current landscape, does it sufficiently capture reality? What needs to be changed in that definition, and for which reasons? Which Grid stacks would fit this definition and might emerge as marketable Community Platforms in the ecosystem? Which research communities do these Community Platforms support? What will happen with the UMD? What will it provide? What is the scope of the UMD, and does it have the potential to cannibalise on Community Platforms? Which role does the EGI Software Repository play in this ecosystem? Which services can it offer to Technology Providers, and are Product Teams required to use it, and under which conditions?
  - 4
    
    Discussion
    
    Back to back with the discussions around community platforms, this contribution aims to focus on aligning Community Platforms and the EGI Platforms with each other. Another topic of discussion here is a potential new platform to discuss: An "EGI Commodity Computing Platform", a simple (or simplified) set of components bundled together to lower the barrier for research communities to engage with EGI. Which components and services would fit such a platform? Who owns it? Who maintains it? which type of researchers does it target?
- Admin & Regulars
  - 5
    
    Actions Review
  - 6
    
    Task Forces reports
  - 7
    
    AOB