Extraordinary PTB Meeting

Tuesday 5 Oct 2010, 09:00 → 10:00 Europe/Zurich

Teleconference

Extraordinary PTB meeting

Duration: 9-10, Tuesday 5th October

 

Calling details:  skype test conferencing service (call mailmagnes in skype)

Screensharing: https://my.dimdim.com/arc-emi  (12345)

 

Proposed agenda:
----------------

1) SAGA-SD in view of the  EMI service discovery (infosys API) plans

 

 

 

Extraordinary PTB meeting, 5/10/2010 9:00-10:05 Present: Laurence, Morris, Marco, Balazs (notes) Excused: Patrick, not showed up: John The SAGA question was the single topic at the meeting. Balazs gave a summary of the SAGA-SD product team and the two components (SAGA-SD and SAGA-ISN libraries) that were proposed by Antony Wilson and Steve Fisher (RAL) for EMI software stack inclusion. The proposed PT in nutshell: - manpower approximately 0.4 FTE, Antony Wilson and Steve Fisher - two components, the SAGA-SD and SAGA-ISN libraries - development plan that includes creation of plugins for additional infosystems currently available or planned to be developed within EMI. During the discussion the following statements were made and shared by the PTB members: * A library to cover the complete/full SAGA specification is not part of the discussion. Development, support or integration of such a library is not considered to be part of EMI workplan as of Today. * Only a small subset of the OGF SAGA specification, the Service Discovery is being considered. * The proposed RAL products, initially developed during the EGEE-III, offer a possible implementation of the OGF SAGA-SD specification, including an own extension (the "ISN" part). * Other information discovery libraries can also provide an implementation for the OGF SAGA-SD specification. The RAL product is one of those implementations. * The general usability of the OGF SAGA-SD API as an EMI information system discovery API is yet to be evaluated. The OGF SAGA-SD API may need to be extended, profiled or even replaced. * The SAGA-SD-UK libraries are ready to roll out, the libraries offer useful capabilities in the information system discovery area that are not completely covered by other components. EMI customers will benefit having such a library part of EMI software stack. Based on the above statements the PTB reached the following decision unanimously supported by the PTB members being present: 1) The creation of a SAGA-SD-RAL product team covering the specific SAGA-SD and the SAGA-ISN libraries is endorsed by PTB. SAGA-SD-RAL PT belongs to infra area. 2) The two libraries of the SAGA-SD-RAL product team offer a possible solution for information system discovery functionality. It was noted that there are other solutions for information system discovery already part of the EMI software stack provided by ARC and Unicore PTs. 3) The EMI objective "consolidation and reduction in the number of information system discovery APIs and CLIs" applies to SAGA-SD-RAL products as well. The SAGA-SD-RAL libraries enter into the consolidation on the same level as the other affected components (lcg-info, lcg-infosite, libarcclient, HILA, unicore internal libs, gfal): It could happen that SAGA-SD-RAL libraries will be dropped from EMI stack, just like any of the others. 4) With the inclusion of the SAGA-SD-RAL libraries, the EMI-I release will offer (partially) overlapping solutions within the information system discovery area. EMI customers will have multiple choice. Including several candidates into the release reduces the barrier to trial. The duplications will be resolved by EMI-2 release. 5) In addition to the creation of the SAGA-SD-RAL PT the PTB proposes the establishment of a SAGA liaison, contact person working under the JRA1 standardization task as well. 6) Antony and Steve, as SAGA experts within EMI, are encouraged to join and actively contribute to the ongoing work of the following teams a) EMI service registry PT b) harmonization of the compute client library/cli (JRA1 compute area) c) harmonization of the infosys libraries (JRA1 infra area) in order to make sure SAGA expertise is taken into account when important EMI interfaces, APIs are defined.