EMI 1 Kebnekaise EMI 1 Kebnekaise

EMI 1 - Kebnekaise released !

The EMI project is pleased to announce the availability of the EMI 1 (Kebnekaise) release.

This release features for the first time a complete and consolidated set of middleware components from ARC, dCache, gLite and UNICORE. The services, managed in the past by separate providers, and now developed, built and tested in collaboration, follow well established open-source practices and are distributed from a single reference repository. The reference platform for EMI 1 is Scientific Linux 5 64 bit..

Kebnekaise will be supported for 18 months, with 6 additional months of support for security issues.    

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.

Release Notes

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

  • 367 EMI packages
  • 192 external dependencies:
    • 165 from SL5/EPEL
    • 27 managed by EMI
  • All components are fully supported on  Scientific Linux 5 / 64 bit 
    • supported package formats: tar.gz, src.tar.gz, rpm, src.rpm - list available here.
    • the upgrade path from the existing gLite, ARC, UNICORE and dCache installations to EMI-1 is not supported and hasn´t been tested. Therefore only clean installations are recommended. Please refer to individual products Release Notes for more information.
  • one single EMI repository for all components
  • components follow common packaging guidelines and policies defined by Fedora, EPEL and Debian

Find here the full list of EMI 1 products, with detailed release notes  and instructions for their installation/configuration.

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/testing/{1|2|3}/<platform>/<basearch>
    • packages that will become part of the next stable distribution; in the certification and validation phase and 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.

It is strongly recommended the use of the lastest version of the emi-release package containing the public key and the yum .repo files, that ensures the precedence of EMI repositories over EPEL

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


EMI 1 software can be downloaded from EMI 1 repository.


Please find EMI 1 documentation here


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.