EMI 3  Monte Bianco EMI 3 Monte Bianco

EMI 3 - MonteBianco released!

The EMI project is pleased to announce the availability of the EMI 3 (Monte Bianco) release.

This release is the third EMI major release and brings new important services, like STS, the final implementation of common specifications and standards, like EMI-ES, GLUE2 and StAR, wider integration with the CANL library, and many enhancements and bug fixes.

All services are available for Scientific Linux 5 64 bit  and Scientific Linux 6 64 bit. A subset of services is also available for Debian 6 64bit and more will be released in the future. All packages can be found at http://emisoft.web.cern.ch/emisoft

Several packages are also directly available from EPEL and Debian.Source RPMS and Debian source packages are available in the repository. All packages follow open source policies and can be rebuilt with standard tools like mock and pbuilder, therefore contributions and fixes are always welcome.

One of the major goals of EMI is to create a true open source community around our software. As the EMI project gets to its conclusion in April 2013, we are building a longer-term collaboration that will strive to support and innovate even more the EMI services. Monte Bianco will be supported by the EMI Product Teams and the EMI collaboration at least for 12 months until the end of April 2014.

EMI 3 (MonteBianco) 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 3 (codename MonteBianco) is the third 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 third EMI release builds on the solid foundation provided by the previous two releases to provide a stable stack of integrated middleware services compliant with mainstream operating systems' guidelines. EMI 3 provides new services and functionality that increase the integration among its components and enhance the efficiency of distributed research infrastructures through improved security features, more dynamic information services and increased standardization.
The major highlights are:
  • Security - The first release of the EMI Security Token Service (STS) that eases the use of x509-based infrastructures for end-users; wider adoption of the Common Authentication Library (CAnL)
  • Compute - Implementation of the EMI ES specifications across all compute element services
  • Data: - consistent support for secure HTTP access in preparation of EMI HTTP federation service; adoption of StAR specifications; new FTS3 service (with EMI 3 first update)
  • Information Systems and monitoring - Improved version of the EMIR service registry with all EMI services being able to send registration records.; full set of NAGIOS probes for all supported services; completion of the messaging-based (SSM2) accounting probes for EMI CEs and SEs supporting CAR and StAR stadard accounting record formats.

Release Notes:

The EMI 3 release consists in 62 products that meet the EMI 3 Acceptance Criteria

  • 480 (SL5), 474 (SL6), 233 (Deb6) EMI packages
    • 74 (SL5), 67 (SL6), 24 (Deb6) external dependencies managed by EMI
  • All components are fully supported on Scientific Linux 5 / 64 bit & Scientific Linux 6 /64 bit
    • supported package formats, list available here.:
      • tar.gz, src.tar.gz, rpm, src.rpm
      • deb, dsc, orig.tar.gz, debian.tar.gz, tar.gz
    • the upgrade path from the EMI 1 or EMI 2 products to EMI 3 is supported and it is described in the products documentation. Please refer to individual products Release Notes for more information.
  • one single EMI repository for all components

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


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

  • EMI production (stable): dist/EMI/3/{sl5,sl6,debian}
    • stable and signed, well tested software components, recommended to be installed on production-sites
  • EMI testing: dist/EMI/testing/3//
    • packages that will become part of the next stable distribution; in the certification and validation phase and available for beta-testing & technical-previews
  • Third-party: dist/EMI/3///third-party
    • packages that are not part of EMI, but are currently not part of the base OS or EPEL

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 http://emisoft.web.cern.ch/emisoft/dist/EMI/3/RPM-GPG-KEY-emi, and the fingerprint from http://emisoft.web.cern.ch/emisoft/dist/EMI/3/EMI_key_fingerprint.asc.

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

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


EMI 3 software can be downloaded from EMI 3 repository.


Please have a look at each individual product to see their available documentation. You will find here the list of the EMI 3 products.


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.

We have created also a Facebook presence:


where you can follow us, and express your opinions.