EMI 2 Matterhorn EMI 2 Matterhorn

EMI 2 - Matterhorn released!

The EMI project is pleased to announce the availability of the EMI 2 (Matterhorn) release.

This release provides many new features and enhancements for many middleware components from ARC, dCache, gLite and UNICORE, including important new services not available in EMI 1. The new functionality includes a new common Service Registry Service (EMIR), the Worker Nodes on Demand Service (WNoDeS), Nagios probes for most services, better integration of the Argus authorization  framework with many services, the initial implementation of the common EMI Execution Service interface and more. 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 near future.

Matterhorn will be fully supported for 12 months until the end of April 2013 with 6 additional months for bug fixes only and a final 6-month period of security updates. 

EMI 2 (Matterhorn) 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 2 (codename Matterhorn) is the second 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 was focused primarily on increasing the level of integration among the original middleware stacks and , improving the compatibility with mainstream operating systems' guidelines. EMI 2 builds on this foundation to provide new services and functionality, while increasing also the compatibility with mainstreams OS with several services distributed also through Fedora/EPEL and Debian. Source RPMS and Debian source packages in Quilt format are also available, with Native format following shortly. All packages follows standard open source policies and can be rebuilt with standard tools like mock and pbuilder, therefore contributions and fixes are always welcome.

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

  • Security - Better integration of the Argus authorization service in the CEs and SEs, a technical preview of a new common EMI security libraries (CANL) for all services, the Pseudoanonymization service
  • Compute - Better support for GLUE 2 in all relevant services, the initial implmentation of the EMI Execution Service interface in all CEs
  • Data - Support for industry-standard protocols for accessing the EMI SEs (NFS4.1, http, webDAV), a messaging-based Storage Element-File Catalog synchronization service (SEMsg)
  • Information Systems and monitoring- the new common Service Registry Service, Nagios probes for most services, better support for the GLUE2 information model standard.

Release Notes:

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

  • 454 (SL5), 447 (SL6), 60 (Deb6) EMI packages
    • 37 (SL5), 28 (SL6), 18 (Deb6) external dependencies managed by EMI
    • 2 (SL5) external contributions
  • 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 products to EMI 2 on SL5 is supported and it is described in the products documentation. For EMI 2/SL6 products versions only clean installations are recommended. Please refer to individual products Release Notes for more information.
  • one single EMI repository for all components

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

Installation:

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

  • EMI production (stable): dist/EMI/2/{sl5,sl6,debian}
    • stable and signed, well tested software components, recommended to be installed on production-sites
  • EMI testing: dist/EMI/testing/2/<platform>/<basearch>
    • 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/2/<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 (for SL 5 & 6), binary-amd64 (for Debian/squeeze)

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

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 & Debian:

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

Software

EMI 2 software can be downloaded from EMI 2 repository.

Documentation

Please find here the EMI 2 products documentation.

Support

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.

Feedback:

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:

http://www.facebook.com/EuropeanMiddlewareInitiative

where you can follow us, and express your opinions.