EMI Collaboration Programs

Works with EMI

The Works with EMI program is a managed collaboration program dedicated to software providers developing applications making use of EMI middleware services or producing additional middleware or distributed computing services extending or complementing the functionality of the EMI services.

The goal of this collaboration program is to establish technical relationships of mutual benefit for EMI and relevant development projects. On one hand, software providers participating in the ‘Works with EMI’ program have access to technical previews of new or modified EMI services early in their development lifecycle, dedicated support channels and joint dissemination and training activities. On the other hand, EMI receives early feedback on its services and requirements to extend and improve their functionality. Together EMI and interested technical partners make sure that the user experience when using applications or services based on EMI is coherent and consistent.

The program builds on the successful EGEE RESPECT program , with a more formal set of commitments and a mutual technical collaboration aspect. Technical partners joining the program must commit to adhere to the quality levels EMI strives to achieve during its development process. In Technical partners must also implement a certification process able to document the level of testing performed. Access to the EMI software engineering platform and certification testbeds in order to perform tests in the same environment where EMI itself is developed and tested is available to technical partners, if required.

The list of technical partners and their software products complying with the ‘Works with EMI’ are published on the EMI web site and can use the EMI web site to advertise their products and achievements within the scope of this collaboration program. These products will be tagged with the ‘Works with EMI’ logo, as testament to the products’ adherence to EMI quality metrics and certification process.

The collaboration is based on the establishment of a Memorandum of Understanding between EMI and the technical partner joining the program. The MoU, which specifies the framework of collaboration between EMI and the technical partner, includes the joint work plan, benefits for the parties involved, roles, responsibilities and timeline of collaboration.

In addition to the MoU, the Work with EMI program foresees the signature of an Operational Level Agreement in case the program partner decides to distribute software as part of the EMI distributions. The OLA ensures that the contributors provide the same service levels to customer and users of the EMI distribution as EMI itslef. The advantage for the contributor is the possibility of using the established and proven support structure of EMI without having to define independent SLAs and support structures.

Memorandum of Understanding

What is an MoU?

An Memorandum of Understanding (MoU) is a written agreement that clarifies relationships and responsibilities between two or more parties that share services, clients, and resources.

Why EMI is establishing an MoU with other projects?

EMI will establish MoUs with other projects to facilitate and strengthen the collaboration between them. The MoU will identify areas of collaboration, clarify roles and commitments from parties involved and agree on a joint programme of work.

A number of MoUs have been signed or are in the process of being finalised with the following specific objectives:

Project Joint Activities Contact Person
D4Science-II Finalised November 2010
* To provide D4science-II access to the EMI-managed ETICS Production Service
* To facilitate preview of EMI release
* To adopt EMI releases
* To provide EMI with timely feedback on the services and functionality under development
Donatella Castelli
Pasquale Pagano
EGI Finalised January 2011
* To provide robust, well-designed, user-centric services to scientific user communities
* To define and monitor SLA for third-level support on incidents and requests
* To accelerate the development of standards within production grid infrastructures
* To disseminate the results of this collaboration within the remit of each project’ s dissemination and communication activities such as joint events
* To exchange ideas and collaborate on the definition of sustainability models
* To collaborate in business relationships development
Status of milestones
Steven Newhouse
WeNMR Finalised April 2011
* To facilitate preview of EMI release
* To adopt EMI releases
* To provide EMI with timely feedback on the services and functionality under development
Alexandre Bonvin
Marco Verlato
eScienceTalk Finalised May 2011
* Disseminating new applications of relevance through the e-ScienceTalk dissemination channels
* Disseminating the outputs of EMI in e-ScienceTalk publications
* Raising the awareness of other potential users and decision makers, through the presentation of the results of [PROJECT], about the usefulness of e-Infrastructures for e-Science.
* EMI will provide content and information about the project and applications of relevance to their community to e-ScienceTalk publications such as iSGTW and the policy documents, the GridBriefings
* EMI will promote e-ScienceTalk’s products to its communities and contacts, for example by offering registrants to events the opportunity to subscribe to iSGTW
* EMI will offer e-ScienceTalk the opportunity to act as media sponsors for events that it organises, including adding the e-ScienceTalk logos and links to e-ScienceTalk products to the event website, in return for promotional activities for the event
Catherine Gater
EDGI Finalised August 2011
* To support the development of ‘bridge middleware’ federating service grids with desktop grids
* To facilitate early access to EMI releases
* Setup an OLA between EMI and EDGI
Peter Kacsuk
Jozsef Kovacs
Zoltan Farkas
Alejandro Rivero
DECIDE Finalised September 2011
* To facilitate the adoption and exploitation of EMI services by DECIDE infrastructure
* To increase the usability of EMI services to meet the requirements of DECIDE community
Roberto Barbera
Andrea Schenone
Ivan Porro
Livia Torterolo
Marco Fargetta
Gianluca Passaro
EUIndiaGrid-II Finalised September 2011
* Transfer of know-how on best practices in configuration and deployment of production services (this may cover release and change management, quality assurance guidelines, operational procedures, certification guidelines, etc)
* Participation of EU-IndiaGrid2 sites in the large scale pre-deployment testing of EMI 1 release candidates (if you agree with this, the testing period is Mar-April 2011)
* Upgrade of EU-IndiaGrid gLite sites to the latest versions included in the EMI 1 release
* Dissemination of the progress and final results of the collaboration within EU-IndiaGrid2 and EMI communities.
Alberto Masoni
ERINA+ Finalised September 2011
* ERINA+ main activities depend on the involvement of e-Infrastructure funded projects to evaluate the impact of e-Infrastructure investments. Feedback from cooperating projects will also enable the team to develop a sound self assessment methodology by the end of the project lifetime.
* EMI will benefit from the cooperation with a team of experts in impact assessment both on the social and economic point of view. The cooperation gives EMI the opportunity to:
- Be trained for the collection of sound quantitative and qualitative indicators which can then be used by EMI to prepare a sustainability and/or exploitation plan as expected by the EC.
- Have visibility towards the European Commission as one of the projects which has cooperated with ERINA+ in the definition of a common methodology for the evaluation of impact of e-Infrastructures investments.
- Have visibility during dissemination activities performed by the ERINA+ team.
Isabel Matranga
Andrea Manieri
iMarine Finalised February 2012
* To provide iMarine access to EMI build services.
* To facilitate preview and support adoption of EMI releases.
* To provide EMI with timely feedback on its pre-production and production services.
Andrea Manzi
Pasquale Pagano
IGE Finalised March 2012
* To facilitate the delivery of Globus-related requirements from EMI to IGE, for example in the areas of standard installation and deployment procedures
* To collaborate on standardisation and interoperability in the areas of Compute and Data Management for DCI middleware
* To exploit the collaboration's successes through the remit of each of the Parties' dissemination and communication activities
Stephen Crouch
DCore Finalized June 2012
* Collaborate in identifying which EMI technologies are suitable candidates to be integrated with DCore services.
* Collaborate in establishing and facilitating direct contacts between DCore (or its subsidiaries) and EMI partners. Any subsequent agreement between DCore and any of the EMI partner is left to them to discuss outside the terms of this MoU. EMI management can provide administrative, technical or logistical support, but it’s not a party in any direct agreement.
* Contribute to identifying and addressing requirements for the EMI software products based on input collected by DCore during the development, deployment and support of its applications.
* Collaborate in establishing a community of developers and users of open source software to act as technical coordination network. The specific form of this initiative is not defined by this MoU and will be discussed as part of the collaboration.
Robert Harakaly
GISELA EMI and GISELA will continue to work together in leveraging EMI services within GISELA: upgrade to the latest EMI releases and EMI-OurGrid interoperability. As agreed with involved parties, there is no need to formalise this with an MoU.
 
PRACE Finalized February 2013
* To provide robust, well-designed, user-centric services to scientific user communities
* To define a common understanding for third-level support on incidents and problems;
* To guarantee the development of specific open standards which are necessary to enable the interoperability with other e-infrastructures (i.e. the XSEDE infrastructure); to disseminate the results of this collaboration.
Giuseppe Fiameni

Restricted access to MoU documents Lock

For more information, contact the EMI Project Office at emi-po@cernNOSPAMPLEASE.ch . You will find here the EMI MoU template.

DCI Collaboration Program

As a result of an open call that closed in November 2009, six projects are being granted with nearly €50M by the European Commission’s 7th Framework Programme in the area of Distributed Computing Infrastructures. Together these projects will provide a pan-European production infrastructure built from federated distributed resources, ensure the continued support, maintenance and development of the middlewares (gLite, ARC, UNICORE and Globus) that are in common use in Europe, explore how grid sites and different applications can be hosted sustainably in commercial, public, publicly procured and private ‘cloud computing’ environments, and provide desktop resources to the European research community. Distributed Computing Infrastructure (DCI) Collaborative Roadmap form a common text agreed by
  • EGI-InSPIRE: Federation of national and domain specific resource providers into a European Grid Infrastructure for multi-disciplinary use.
  • European Middleware Initiative (EMI): Continued support, development and harmonisation of the European middleware stacks from gLite, ARC, UNICORE and dCache.
  • Initiative for Globus in Europe (IGE): Dedicated support for the European Globus community.
  • European Desktop Grid Initiative (EDGI): To deploy desktop grids and cloud computing services for European user communities.
  • StratusLab: Exploration of running production grid services in a cloud environment and providing cloud resources to research user communities.
  • VENUS-C: Will explore and demonstrate the applicability of private and public cloud computing environments to different scientific applications to speeding up e-Science built on the sustainable public procurement of computing and storage resources on the cloud market.

Service Level Agreeement

Service Level Agreements (SLA) are a key method within ITIL and IT Service Management (ITSM) for setting out how two parties have agreed that a specific service (usually, but not necessarily, IT-related) will be delivered by one to the other, and the standards or levels to which it will be delivered. EMI provides a standard SLA with infrastructures and users that can be used as the basis for negotiation of the expected service levels. Currently EMI has one SLA in place with the European Grid Infrastructure.

Operational Level Agreeement

Operational Level Agreements (OLA) is =internal agreements used to define the relationship of two units of the same organization when providing services to customers or users. EMI uses OLAs to define how middleware contributors have to support their software products that are distributed as part of the EMI distribution. Currently EMI has one OLA in place with the EDGI project.

Collaboration with PRACE

PRACE is a very specific e-Infrastructure and collaboration with EMI relies in various distinct activities.

Collection (draft version)

1. Exploitation of EMI components The first step of this was to provide the tarballs in an easy to find location such as our main repository page. This was done by Cristina on 4/10/2012, and can be seen here: http://emisoft.web.cern.ch/emisoft/index.html

2. Evolution of UNICORE components to foster the interoperability with other e-infrastructures (e.g. XSEDE) Question for PEB. My understanding is that this is about standards, so perhaps it is being done by keeping some standards such as BES/JDSL, so the TB should know about this.

3. Evolution of the EMI Security Token Service (STS) I think we are doing this, but again the PEB / TB should confirm.

4. Evolution of EMI components I have no knowledge of EMI listening to requirements from PRACE, but there may be some items in savannah that relate to this.

5. Operational Support This was supposed to be established by an SLA, which is not going to happen. It is possible that there are tickets in GGUS for UNICORE components, but I wouldn't know if they can be classified as PRACE-related operational support.

6. Dissemination and Training EMI has not attended the PRACE events, but we did attend all the ISC events. In terms of training, EMI always does training for its UNICORE components, FWIW.

Topic attachments
I Attachment History Action Size Date Who Comment
Microsoft Word filedoc EMI-MoU-Template-May2011.doc r1 manage 95.0 K 2011-05-05 - 12:04 UnknownUser  
PDFpdf EMI-MoU-Template-May2011.pdf r1 manage 390.3 K 2011-05-05 - 12:04 UnknownUser  
Edit | Attach | Watch | Print version | History: r28 < r27 < r26 < r25 < r24 | Backlinks | Raw View | WYSIWYG | More topic actions
Topic revision: r28 - 2013-04-03 - unknown
 
    • Cern Search Icon Cern Search
    • TWiki Search Icon TWiki Search
    • Google Search Icon Google Search

    EMI All webs login

This site is powered by the TWiki collaboration platform Powered by PerlCopyright &© 2008-2020 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding TWiki? Send feedback