PDT:MOU advancement

MoU Advancement

Late Milestones

• IGE M5.2: Report on services for extension of accounting mechanisms for recording service usage (June 2011) Content of report provided being reviewed - To effect also EMI M1.5
• StratusLab M6.1: Establish agreement for delivery of StratusLab software for UMD (May 2011)
• StratusLab M6.2: Input to UMD Roadmap (June 2011)
• CHAIN M3.1 Survey of the current middleware platforms used in Regional Grid Infrastructures and the current adoption of open standards (July 2011)
• CHAIN M2.1: A roadmap to improve the integration of operational tools supported by EGI that are used in the different Regional Grid Infrastructures Oct 2011)
• CHAIN M6.1 Report to CHAIN about the identification of research groups that are part of EGI VRCs and active in CHAIN’s regions of interest (Sept 2011)
• CHAIN M1.1 Roadmap for interoperation and integration aligned with the EGI Model and based on CHAIN’s understanding of Regional Grid Infrastructures (Sept 2011)

Dec 2011

Expected

• MAPPER M2.4: EGI to provide monitoring infrastructure needed to check status of deployed services. MAPPER delivers EGI compatible monitoring connectors (Dec 2011)
• MAPPER M8.1: Training material published by MAPPER on the EGI Training Marketplace (Dec 2011)
• e-ScienceTalk M2.1: Brief dissemination report (Dec 2011)
• CHAIN M7.1 Report from CHAIN to EGI-InSPIRE on: 1) identification of new and emerging NGIs that could interoperate with EGI; 2) NGI guidelines documentation (Dec 2011)
• SAGA M1.1 (update) Report listing the inputs to the UMD Roadmap for the EGI-InSPIRE deliverable due in Jan 2012 (Dec 2011)
• SAGA M5.1 Requires a survey to evaluate the user base for SAGA software in EGI (Dec 2011)
• IGE M1.1 Update: Input to UMD Roadmap (Dec 2011)
• ScalaLife M1.4: Report analysing the VRC integration plans for or of ScalaLife (Dec 2011)
• Meraka M3.1: Resource Infrastructure Provider OLA is released and approved

Nov 2011

Expected

• StratusLab M7.1: Requires a report on dissemination activities (report led by Catherine Gater, EGI.eu)
• MAPPER M5.1: Deliver MAPPER D5.2 vertical integration plan (Nov 2011)
• DECIDE M4.1: DECIDE Sustainability Plan (Nov 2011)
• CHAIN M3.1 Gap analysis on existing issues and other barriers that prevent the adoption of open standards identified in the EGI Standards Roadmap (Nov 2011)
• CHAIN M4.3 Requires a report on dissemination activities including the list of publications issued by CHAIN that benefited from the usage of EGI (Nov 2011)
• SAGA M4.2 Requires a report on dissemination activities (Nov 2011)
• IGE M4.2: Report on dissemination activities (Nov 2011)
• SIENA M2.1: EGI-InSPIRE provides contribution to development of the SIENA cloud standards profile (Nov 2011)

Achieved

• ScalaLife M1.1: Community information exchange (Sept 2011)
• ScalaLife M1.3: Initial list of requirements from the EGI Life Science community for ScalaLife (Nov 2011)

Oct 2011

Expected

• HMRC A.2: List of applications and services that HMRC can offer to the EGI community (Oct 2011)
• HMRC A.3: Feedback from EGI on progress on requirements (Oct 2011
• MAPPER M1.2: EGI-InSPIRE to provide feedback to MAPPER on the status of the supplied requirements (Oct 2011)
• DECIDE M3.1: Help desk integration (Sept 2011)
• DECIDE M2.1: List of applications and services needed and offered by DECIDE (Sept 2011)
• DECIDE M3.1(b): Report analysing VRC integration plans (Sept 2011)
• HMRC A.1: Outline HMRC’s areas of expertise (Sept 2011)
• HMRC A.2: List of applications and services needed by HMRC from the EGI community (Sept 2011)
• MAPPER M2.2: EGI to provide list of candidates interested in running/supporting MAPPER middleware extensions & application tools (Sept 2011)
• MAPPER M2.3: EGI to provide access to GOCDB for info on resource centres/services accessible to MAPPER (Sept 2011)
• MAPPER M2.1: Access to EGI Community Repository and EGI Help desk (GGUS) given to MAPPER (Aug 2011)
• Meraka M4.1: SAgrid starts operations as an EGI integrated production infrastructure
• Meraka: subscription of Meraka security representatives to SPG group and relevant mailing lists

Achieved

• LSGC M2.1: List of applications and services needed by LSGC from the EGI community (July 2011)
• LSGC M2.2: List of applications and services that LSGC can offer to the EGI community (Aug 2011)
• SIENA M1.1: Published announcement regarding the signed MoU (Sept 2011)

Sept 2011

Expected

• GISELA M1.3 (A.1) Organize a joint activity at EGI Technical Forum
• GISELA M4.1 (A.4) Requires a report analysing VRC coordination
• StratusLab M4.3: Deployment of Standards-based software on EGI sites
• StratusLab M7.1: Establish GGUS support team to support sites running StratusLab (May 2011) All information provided. Support Unit to go online with next release (end of Sept)
• gSLM M5.1: Input collection from VO Managers based on gSLM User Survey and report analysing results of survey
• gSLM M4.2: Report on the outcome of the training session

Achieved

• MAPPER M7.1: Start of collaboration advertised on each Party’s website with dedicated static page, article and/or press releases (July 2011)
• MAPPER M1.1: Deliver MAPPER D4.1 Review on applications, users, software and e-Infrastructures (June 2011)
• MAPPER M6.1: Deliver MAPPER D3.1 Policy framework resource providers need & D6.3 Support Process Definition (June 2011)
• LSGC A.4: Feedback from EGI on progress on requirements progress (Every 3 months from June'11)
• LSGC M1.1: Outline LSGC's areas of expertise (June 2011)
• WeNMR A.4: Feedback from EGI on progress on requirements progress (Every 3 months from May'11)
• ScalaLife M2.1: Both parties announce the agreement on their web sites (Aug 2011)
• SIENA M3.1: SIENA holds Roadmapping workshop at EGI Technical Forum 2011 (Sept 2011)
• CHAIN M4.2 Joint session at EGI Technical Forum (Sept 2011)

Aug 2011

Achieved

• SAGA M2.1 Requires a report listing standards relevant to both projects and a roadmap for delivery to be used as input to the EGI-InSPIRE Standards Roadmap deliverable due in Sept (Aug 2011)
• EMI M2.1: Report listing standards relevant to both projects and a roadmap for their delivery to be used as input to the standards roadmap
• EMI M1.1 (update): Report listing the inputs to the UMD Roadmap for the EGI-InSPIRE deliverable (June 2011)
• WeNMR A.3: Participation in UCB Alexandre Bonvin attended the meeting and is documented in the 23 Aug UCB
• LSGC A.3: Participation in UCB Tristan Glatard attended the meeting and is documented in the 23 Aug UCB
• StratusLab M4.2: Description of software components support standards-based interfaces to be released by StratusLab (June 2011)
• HMRC A.4: Both parties announce collaboration agreement on their web sites (Aug 2011)
• IGE M2.1: Standards report (Aug 2011)

Jul 2011

Achieved

• gSLM M2.1: Report proposing alignments of EGI terminology as in use within ITSM (July 2011)
• e-ScienceTalk M1: Published announcement on the signed MoU and section of collaboration overview on each other’s project website (July 2011)
• WeNMR A.3: Participation in UCB Alexandre Bonvin attended the meeting and is documented in the 15 July UCB
• LSGC A.3: Participation in UCB Franck Michel and Tristan Glatard attended the meeting and is documented in the 15 July UCB
• DECIDE M5.1: Both parties announcement agreement on websites (July 2011)

Jun 2011

Achieved

• LSGC M6.1: Announce the collaboration agreement on project websites
• gSLM M4.1: Submit a proposal for tutorial at the EGI TF 2011
• SAGA M4.1 The milestone is achieved by advertising the start of the collaboration (April 2011)
• SAGA M1.1: Requires a report listing the inputs to the UMD Roadmap for the EGI-InSPIRE deliverable due in July 2011
• EMI М1.3: Report defining the strategy for managing software releases and repositories
• WeNMR A.5: A.3 Participation in UCB Alexandre Bonvin attended the meeting and is documented in the 14 June Minutes
• StratusLab M4.1: Definition of prioritised list of standards
• IGE M1.1 (update): Input to UMD Roadmap (June 2011)

May 2011

Achieved

• UFRJ M1.1: Appointment of a UFRJ Operations Manager, subscription of UFRJ operations representatives to relevant EGI.eu groups and mailing lists are completed
• UFRJ M4.1: UFRJ starts operations as an EGI integrated production infrastructure
• GISELA M1.1: The milestone is achieved by advertising the start of the collaboration in the EGI.eu and GISELA websites (April 2011)
• GISELA M1.2 (A.1) Organize joint event at EGI User Forum
• EMI M1.1: Report listing the inputs to the UMD Roadmap for the EGI-InSPIRE deliverable
• EMI M4.1: Advertising the start of the collaboration
• EMI M5.1: Report analysing sustainability of EMI middleware
• EMI M3.1: Signing the SLA
• EMI М5.2: Report with inventory of existing software components to provide initial assessment of usage, install base and opportunities for uptake/support outside EGI community
• IGE M1.1: Input to UMD Roadmap
• IGE M4.1: Advertise start of collaboration
• IGE M3.1: Sign SLA
• IGE M5.1: Inventory and assessment report of existing software components
• SAGA M3.1: The milestone is achieved by signing the SLA
• StratusLab M3.1: Joint dissemination sessions at EGI and StratusLab events
• StratusLab M2.1: User Training session at EGI User Forum 2011
• StratusLab M1.2: Technical meeting at EGI User Virtualisation Workshop
• WeNMR A.6: Both parties to announce the collaboration agreement on their web sites
• WeNMR A.1: Outline VRC’s areas of expertise
• WeNMR A.1: Help desk integration (VRC & EGI)
• WeNMR A.2: List of applications and services needed by the VRC
• WeNMR A.2: List of applications and services that the VRC can offer
• WeNMR A.5: VRC sustainability plan – description of the Sustainability work package of WeNMR
• WeNMR A.5: A.3 Participation in UCB Alexandre Bonvin attended the meeting and is documented in the UCB Minutes

Others

• StratusLab M1.1: Technical meeting on grid-cloud integration at EGI UF 2011 (April 2011)

This activity will not be done as there is another milestone to hold this kind of meeting at the TF, therefore, this one cannot be moved to there. StratusLab held a workshop and a training course as well as participated in the UVW in May, but each had a specified milestone marked as "achieved".

MoU Status

• MoU Status (Signed, Negotiation Phase, Planned, DocDB link, Process Owner, etc.)