Focus on:  Hide Contributions
Back to Conference View
Login

EGEE to EGI Transition Meeting: Middleware

→ Europe/Amsterdam
H331 (EGI.eu)

H331

EGI.eu

Science Park 105 1098 XG Amsterdam The Netherlands
Steven Newhouse (EGI.eu)
Description
Discussion relating to the work of the EGI.eu middleware unit and its interaction with the software providers, the delivery of the software to the production infrastructure, and the organisation of the process - including the role of the MCB.
Participants
Support
    • EGEE to EGI Transition Meeting: Middleware

      Introductory session highlighting the roles of the various actors in the middleware requirements, definition, prioritisation, specification, monitoring, delivery, verification, rollout, and release.

      • 1
        Introductions and Overview of the Technology process in EGI
        Who's who and what are they doing here, and what is their role in the process. * Overview of the Middlware Unit activities (Ales) * Middleware Unit: Coordination, Process, Repository, Criteria Definition & Verification, Rollout * Software Providers: EMI, IGE, EDGI, StratusLab
        Speaker: Ales Krenek
        Slides
      • 2
        Overview of planned structure and processes within the Software Providers
        Presentations on how the software projects expect to work, how they are structured and the potential interaction points with EGI.eu * Initiative for Globus in Europe (IGE - Alexander Papaspyrou) * European Middleware Initiative (EMI - Alberto Di Meglio) * EDGI (Peter Kacsuk) * StratusLab (Ioannis Liabotis) Consider the role of the Deployed Middleware Support Unit within EGI with the software providers.
        Slides
    • Rolling out into Production

      What happens after the software is marked ready for staged rollout from the repository?

      • 3
        Detailed Process Discussions
        How do IBERGrid see the activity working: * Requirements needed from the Repository * Support needed from the sites * Support needed from the software providers
        Speaker: Mario David
        Issues
        Issues 2
        MU Ibergrid Tasks transistion plan
    • Repository

      The repository has a key role in bringing together the middleware unit, the external software provider and the operations staff rolling out the technology into production. What is needed from it?

      • 4
        Features Required from the Repository
        The Repository links the various actors in the EGI Middleware process * The contribution from the software providers * The verification of the releases by the MU * The rolling out into production of the software * The download of the software by sites * The use of the repository as a community driven contribution site (e.g. RESPECT) The session will start with a presentation from GRNET with their view of the feature set and then expand into a broader discussion.
        Speaker: Ioannis Liabotis
        Slides
    • Managing the Process
      • 5
        Managing the Process
        The requirements, specification, monitoring, and verification is executed by the EGI.eu CTO through the MCB and with representatives from various stakeholders. This session will discuss the various stakeholders and how they interact: * Middleware Requirements: Coming from the VRCs and the operations staff * Prioritisation: Reviewed and agreed with the MCB * Specification: Negotiation with the 'customers' of the new functionality and the stakeholders mediated by the MU to define what will be delivered. * Commissioning: Reporting to the MCB what will be delivered when and by who to do what! * Monitoring: Review of the work of the software provider in delivering commissioned work. * Verification: Has the what been delivered as requested?
        Speaker: Steven Newhouse
Powered by Indico v3.2.7