EMI 1 Release Notes

EMI 1 (Kebnekaise) Overview

The European Middleware Initiative (EMI) project aims to deliver a consolidated set of middleware components based on the four major middleware providers in Europe - ARC, dCache, gLite and UNICORE. EMI 1 (codename Kebnekaise) is the first step towards a stable integrated distribution of compute and data management services that will deliver a broad suite of technologies for deployment in distributed computing infrastructures in Europe and beyond.

The first EMI release is focused primarily on laying the foundations for the distribution, increasing the level of integration among the original middleware stacks, improving the compatibility with mainstream operating systemsí guidelines and extending the compliance with existing standards.

EMI 1 components follow more closely packaging guidelines and policies defined by Fedora, introduce widespread compliance with the File Hierarchy Standard (FHS), make extensive use of off-the-shelf packages from the OS distribution or major downstream repositories like EPEL, reduce the dependency on less standard technologies and protocols.

EMI 1 introduces a number of changes and new functionality in response to existing user requirements. The major highlights are:

  • Security - Replacement of GSI with SSL in the security components, most notably VOMS; REST-based interface for obtaining X.509 attribute certificates in VOMS Admin; initial integration of ARGUS with middleware services (e.g. CREAM)

  • Compute - Full support for the CLUSTER service in CREAM; initial support for GLUE 2 in all CEs; integration of ARGUS in CREAM; initial implementation of common MPI methods across the different compute services

  • Data - Adoption of pNFS4.1 and WebDAV standards (dCache); preview version of a messaging-based Storage Element-File Catalog synchronization service (SEMsg)

  • Information Systems - ARC CE, UNICORE WS, CREAM, dCache, DPM expose a richer set of information via the experimental adoption of the GLUE2 information model standard.

EMI 1 Release Content

EMI 1 is fully supported on SL5/x86_64, with partial suport for SL5/i386.

The EMI 1 release consists in 59 products that meet the EMI Acceptance Criteria:

  • 333 EMI packages
  • 192 external dependencies:
    • 172 from SL5/EPEL
    • 20 managed by EMI

Installation Notes

All EMI products are distributed from a single repository having the following structure:

  • EMI production (stable): dist/EMI/1/sl5/<basearch>/{base|updates}
    • stable and signed, well tested software components, recommended to be installed on production-sites

  • EMI testing: dist/EMI/2/testing/<platform>/<basearch>
    • packages that will become part of the next stable distribution; passed the certification and validation phase and are available for technical-previews

  • Third-party: dist/EMI/1/<platform>/<basearch>/third-party
    • packages that are not part of EMI, but are currently not part of the base OS or EPEL

<basearch> can be currently i386, x86_64, SRPMS, tgz

All EMI packages are signed with the EMI gpg key. The public key can be downloaded from here, and the fingerprint from here

A package is also available containing the key and preconfigured YUM repo files.

To understand how to install and configure individual EMI products either refer to the EMI 1 Generic Installation & Configuration Guide or to each individual product documentation.


Most complex software contains bugs, we are not an exception. One of the features of free and open source software is the ability to report bugs, helping to fix or improve the software you use.

EMI uses the GGUS (Global Grid User Support) tool as its user support system.It provides EMI with sophisticated search functionality, report generation, interfaces to bug tracking systems used by different middleware components, and automatic ticket reminder including escalation indication.

You can have more details on how to report problems at EMI Support.


Anyone can help us improve by participating to discussions on our User Forums, the place where developers, system administrators and users can discuss, ask questions, post comments, solutions and suggestions.

-- DoinaCristinaAiftimiei - 12-May-2011

Topic attachments
I Attachment History Action Size Date Who Comment
Unknown file formatasc EMI_key_fingerprint.asc r1 manage 0.2 K 2011-05-12 - 10:29 DoinaCristinaAiftimiei EMi key fingerprint
PDFpdf GenericInstallationConfiguration_EMI1_v_1_0_0.pdf r1 manage 92.0 K 2011-05-12 - 10:16 DoinaCristinaAiftimiei Generic Installation & Configuration for EMI 1
JPEGjpg arch_overview_1.jpg r1 manage 80.0 K 2011-05-12 - 07:41 DoinaCristinaAiftimiei EMI 1 Architecture Overview
Edit | Attach | Watch | Print version | History: r7 < r6 < r5 < r4 < r3 | Backlinks | Raw View | WYSIWYG | More topic actions
Topic revision: r7 - 2011-05-12 - DoinaCristinaAiftimiei
    • 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-2021 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
or Ideas, requests, problems regarding TWiki? use Discourse or Send feedback