Infrastructure Area Phone Conference

Europe/Zurich
CERN

CERN

Description
Title: Infrastructure Area Phone Conference Community: EMI Password: EMIIA Meeting Access Information: - Meeting URL http://evo.caltech.edu/evoNext/koala.jnlp?meeting=M9MIMi2I28DDD89v9DDD99 - Password: EMIIA - Phone Bridge ID: 2325493 Password: 3495 - Phone Bridges Numbers http://evo.caltech.edu/evoGate/telephone.jsp
    • Agenda

      1) New Twiki Page
      2) PT Status Reports
      3) Task Force Status Reports
      4) EMI 1.0 Roadmap
      5) AOB

      Attendance:
      Laurence Field (LF), Lionel Cons (LC), Zdenk Sustr, Antony Wilson

      Apologies:
      Jason Daivandy, Shiraz Memon


      1) New Twiki Page

      The new Twiki page for the infrastructure area was explained.  The pages is split into five sections: Technical Objectives, Year One Tasks, EMI 1.0 RoadMap, Product Teams, Task Forces and Internal Communication. The Technical Objectives give the project objectives over the full three years for the infrastructure area and were extracted from the Technical Development Plan.  The One Year Tasks are the extracted from the Infrastructure Area Work Plan.  The other sections are self explanatory. This pages is the "dashboard" from the infrastructure area and will form the bases for most of the phone meetings.


      2) PT Reports

      L&B : v2.1 is ready for production.  v2.2 will be ready for EMI 1.0 (Feb 2011). This version will include the ability to use messaging. Due to the new functionality, t might be renamed v3.0.

      Messaging: Working on collecting requirements, spoken to the L&B PT and Unicore. The survey is in progress.

      LF Raised a question about how the L&B PT can include messaging before the messaging PT has a product. LC replied that they are using the C++ stomp library and the EGI infrastructure for tests. LF mentioned the feedback from the EGI Technical Forum presentation that EGI do not want EMI to keep changing the messaging interface and asked if this was a possiblity as the L&B PT were implementing a messaging based solution before the survery has been finished. LC replied that this was a possibility.

      gLite IS: The new top-level BDII service is in staged rollout.  The messaging investigation has been complete but needs writing up.

      SAGA SD: Testing with GLUE 2.0 information.

      ARC Infosys: No representation
      APEL: No representation
      DGAS: No representation
      Registry: No representation

      4) Task Force Status

      Cloud: No representation

      Virtualization: No representation

      Configuration and Instrumentation: No representation

      Service Monitoring : No representation


      3) EMI 1.0 Roadmap

      L&B :  v2.2 which may be renamed 3.0 is intended for EMI 1.0

      Messaging: Nothing to include for EMI 1.0

      gLite IS: No plans to introduce anything new for EMI 1.0. Will check to see if the latest release will be in EMI 0.

      SAGA SD: Nothing new to include.

      ARC Infosys: No representation
      APEL: No representation
      DGAS: No representation
      Registry: No representation


      AOB:
      None


      Next meeting: 5th October