Commitment statements from current TPs ====================================== Each current Technology Provider (EMI, IGE, StratusLab, PSNC, SAGA, UVACSE) will provide an commitment statement as to where in the evolved TCB ecosystem they see themselves or successors see fit to contribute in the future. The statements will include information about: - the level of desired commitment (community, contributing, integrated), - the role & size of the member (small group, Product Team, Platform Integrator), - target consumers - type of software deployment (e.g. integrated into a specific EGI platform, individual platform) - integration points with other platforms in the EGI ecosystem. Further, these statements will include issues that need addressing for efficient collaboration. These issues will be the topics for discussion for the remainder of the session. The terms are explained in this document: https://indico.egi.eu/indico/materialDisplay.py?sessionId=4&materialId=1&confId=1303 As stated multiple times, EGCF can take up the role IGE has now as TP, however, not for free. EGI would have to pay for this effort. If there is any chance of this happening, then please let us know ASAP so that we can clarify all the legal aspects of this. As long as EGI is not willing to do this, EGCF cannot provide this coordinating function. Instead, EGI then has to engage directly with the IGE product teams. The speaker for EGCF is Michael Krieger . Detailed answer: - the level of desired commitment (community, contributing, integrated), => This will vary from PT to PT. There are some "contributing" (with SLA) and some "community" (without SLA) level engagements. We have already given the complete list to EGI in 2012. - the role & size of the member (small group, Product Team, Platform Integrator), => EGCF offers to take over the role of Platform Integrator for a suitable fee, otherwise EGI must directly engage with the individual product teams. - target consumers => These vary from product to product. The hydro-meteorological community (DRIHM) is using Globus, as well as VERCE and MAPPER. We have received applications for use of Globus resources from * VO moldyngrid * VO enmr.eu (WeNMR) * VO glast.org - type of software deployment => We see the Globus tools as both: a community platform, e.g., through the use of our Globus appliances in EGI's Cloud, and also contributing to the UMD. It is up to the individual product teams (PT) to decide on their level of engagement. - integration points with other platforms in the EGI ecosystem => Referring to Table 3 on p. 18 of EGI's document we see integration points in the form of Globus SW components being used in other platforms with: * Data-intensive HTC * QosCosGrid IGE has the following product teams: * UCM: GridWay * EPCC: OGSA-DAI * LRZ: GSI-SSHTerm; SLURM Batch Adaptor * LRZ: LoadLeveler Batch Adaptor * NIKHEF: LCMAPS * EPCC: Grid-SAFE * PSNC: jGlobus 2.0 * UTCN: Globus Online Clients * UTCN: SHIWA DCI Bridge Adaptor to GT5 * UTCN: GlobusAppliances * GWT: AdHoc * TUDO: BESGRAM * UC (USA): GridFTP * UC (USA): GRAM * UC (USA): Globus Online * NCSA (USA): gsissh(d) * NCSA (USA): myProxy * UU: Native packaging