EGEE to EGI Transition Meeting: User Community & Operations

Europe/Amsterdam
Z009 (EGI.eu)

Z009

EGI.eu

Science Park 105 1098 XG Amsterdam The Netherlands
Description
A focus on the transition of the EGEE NA2, NA3 and NA4 activities to the EGI era with significantly reduced EC funding during the first day, followed by more general transition of EGEE operations to NGI operations from Tuesday afternoon.
Participants
  • Alexei Altuhov
  • Aleš Křenek
  • Andoena Balla
  • Andrew Richards
  • Angela Poschlad
  • Antun Balaz
  • Boro Jakimovski
  • Catherine Gater
  • Charles Loomis
  • Claire Devereux
  • Claudio Vuerli
  • Cyril Lorphelin
  • Cécile Germain-Renaud
  • David Durvaux
  • Evangelos Floros
  • Gabriel Zaquine
  • Gert Svensson
  • Guillaume Cessieux
  • Helene CORDIER
  • Ignacio Blanquer
  • Isabel Campos Plasencia
  • Jamie shiers
  • Jan Astalos
  • Javier Lopez
  • Jelena Tamuliene
  • Johan Montagnat
  • John Walsh
  • Ladislav Hluchy
  • Luuk Uljee
  • Marcin Radecki
  • Maria Girone
  • Mario David
  • Mariusz Sterzel
  • Markus Baumgartner
  • Nicholas Loulloudes
  • Patricia Mendez Lorenzo
  • Rolandas Naujikas
  • Siarhei Salamianka
  • Steven Newhouse
  • Tiziana Ferrari
  • Tomas Kouba
  • Tomasz Szepieniec
  • Torsten Antoni
  • Tristan Glatard
  • Valeria Ardizzone
  • Vera Hansper
Support
    • Post EGEE Requirements for NA4/NA3 & NA2

      As there will not be support for all of the NA2, AN3 and NA4 activities after EGEE what does need to be supported by EGI and what can be supported by the community?

      • 1
        Input from NA4
        What services are they really looking to be sustained by EGI.eu across VOs, training, dissemination, etc.? This should NOT be a list of items that were requested in ROSCOE, SAFE, CUE & TAPAS but a review of the critical items needed to sustain their community that cannot be provided through other sources.
        Speaker: Cal Loomis
      • 2
        Services for the User Community
        Through EGI-InSPIRE, EGI.eu are already planning a minimal set of services: * Human Coordination: Interaction with VRCs, Definition & Identification of VRCs, Meeting support through an annual User Forum, Requirements collection and monitoring [EGI.eu] * Training Events and Training Repository [UK] * Applications Database [GRNET] * Software Database [GRNET - Primarily for MU] * VO Services (VOMS, VO Database, Portal infrastructure, VO Dashbaord [IBERGrid] Representatives from each group should expand briefly on each area w.r.t. how they meet or could adapt to the requirements requested by the user community. The EGI Helpdesk will be there to coordinate community based support units - which communities will contribute such a resource?
        Speakers: Ignacio Blanquer, Ioannis Liabotis, Robin McConnell, Vangelis Floros
      • 3
        Other Communities beyond NA4
        Update from other VRC proposals. * eSSNMR * WeNMR (Alexandre M.J.J. Bonvin [a.m.j.j.bonvin@uu.nl])
      • 15:00
        break
      • 4
        Support for and from the HUCs (SA3 in EGI-InSPIRE)
        What support options are planned within SA3 that could be used to support the existing NA4 community? * HEP, shared Dashboards and Applications: Jamie * LS, shared Hydra & Dashboards: Johan * Shared workflow, schedulers & MPI: Isabel
        Speakers: Isabel Campos Plasencia, Jamie Shiers, Johan Montagnat
      • 5
        VRC support from the NGIs
        One source of support for the VRCs is from the NGIs. For an upcoming EGEE deliverable the VOs will be asked to provide details as to the national commitments they have for support and resources.
        Speaker: Gabriel Zaquine
    • Support Options from EGI & NGI for the VRCs

      How can the support models within EGI-InSPIRE be adapted to work without ROSCOE, SAFE, TAPAS and CUE?

      • 6
        Discussion of Community support options
        How can the community support activities be distributed? * EGI.eu * NGIs * VRCs Review of what can be supported by who. What adaptations need to be considered in the EGI-InSPIRE DoW and general NGI activities.
    • 10:30
      NGI Staff Should Arrive Here!

      Coffee available

    • NGI support VRCs
      • 7
        Review of User Requirements
        The previous day's discussion will have clarified the support being offered by EGI.eu through the global tasks and identified additional tasks that could be taken up by the NGIs.
        Speaker: Juergen Knobloch
        Slides
      • 8
        NGI Support for VRCs
        The probable failure of the SAFE, ROSCOE, TAPAS and CUE proposals will force more VRCs to obtain support through NGIs. What support will the NGIs offer? * Training * Application Porting * Dissemination Will this be across all VOs or specific VOs?
        Speakers: John Gordon, Tiziana Ferrari
        Italy
        UK
    • Moving to NGI Operations

      EGEE is based upon a Regional model. EGI will move towards a national model. Some ROCs are already there (single country ROCs) others are easier to migrate (two country ROCs). What is the state of readiness with the rest?

      • 9
        Moving from ROCs to NGIs
        Experience from CE and the plans for SEE to migrate
        Speaker: Tomasz Szepieniec
        Slides
      • 10
        What do ALL NGIs need to do?
        The move from ROCs to NGIs means new responsibilities for an NGI: * Security: Contacts and Operational procedures (O-E-15 & 16) * Networking: How should you interact with your NREN and networking issues (O-E-12) * Helpdesk: NGI Operations support unit (O-E-5, O-E-6 & O-E-7)
        Speakers: Mario Reale (GARR), Sven Gabriel, Torston Antoni
      • 15:00
        break
      • 11
        What do SOME NGIs need to do?
        The move from a central to a national structures means that SOME NGIs need to participate actively in some activities: * Middleware Rollout. Sites are needed to put releases of new software services into a production use for communities to verify their ability to operate at production loads. (O-E-9) * Interoperation. Some new software releases will change the public interfaces used by other middlewares deployed within EGI or by our international partners. We need sites willing and able to put new releases into production and verify that interoperability remains. (O-E-11)
        Speaker: Mario David
        Feedback from sites and ROCs
        Slides
      • 12
        Dealing with different middleware
        EGI will work to define middleware interfaces that need to be supported in production as opposed to naming specific middleware instances. Operationally, particular middleware distributions will need to be integrated into production. This will have an impact on: * Integration into monitoring tools * Accounting of resource usage into national/central accounting databases * Deployment, interoperation and support.
        Speakers: Alexander Papaspyrou, John Gordon
        Accounting
      • 13
        NGI and VO Readiness Survey
        NA1 has an upcoming deliverable examining the state of the NGIs in preparation for transition. As part of that a survey will be sent out to NGIs and VOs.
        Speaker: Gabriel Zaquine
        Slides
    • Site Monitoring and Tools

      What changes are needed to the operational tools and operational models for sites?

      • 14
        Tools for NGI Monitoring
        What are the tools that an NGI and a site need to deploy and use? What will their status be at the end of EGEE?
        Speaker: James Casey
        Slides
      • 15
        Tool Regionalisation
        There seems to be a reduced interest for deployment of operational tools at a national level. Given the limited support for this activity within EGI-InSPIRE is a better alternative too have regional/national views of centrally support tools. How should this be reflected in the planned EGI-InSPIRE work. If this is not desired - where will the effort come from to develop and support these deployed instances?
        Speaker: Tiziana Ferrari
        Slides
      • 16
        SLA/SLDs for a site
        Given the monitoring capabilities, what will a site and an NGI commit to providing to the infrastructure in terms of availability, reliability, middleware upgrades, support and other monitoring metrics.
        Speaker: Nick Thackary
        Slides
      • 10:30
        break
      • 17
        NGIs need to become more involved!
        The bulk of EGI activity will come from outside the EGI-InSPIRE project. NGIs need to bring additional NGI resources to the activity. * Development, testing and deployment of operational tools * Staged rollout of middleware and interoperation testbeds * ....
      • 18
        Summary and Next Steps