EMI Registry (EMIR)

A Service Endpoint Registry conceived during the EMI project. Its main goal is to discover all the Service Endpoints that exist. It consists of a collection of services that enables storing service records in a federated manner. Each of the record contains Service Endpoint Record (SER) according to the GLUE 2.0 standard. The deployment of EMIR (which implies building an EMIR network over WAN) is bipartite: 1) Building a rooted hierarchy with a single EMIR server aggregating all the information within a federation 2) Sharing the information at the root level among peered EMIR servers (using P2P), thus enabling intra-federation discovery.

EMIR documentation

• Architecture and Design
• Administrator and Developer's Guide
• Interface Description
• WHAT is inside Service Endpoint Records (SER)
• HOWTO publish information to EMIR
• HOWTO consume information from EMIR
• Published articles
  • S. Memon, M. Riedel, L. Field, G. Szigeti, I. Marton, "EMIR: An EMI Service Registry for Federated Grid Infrastructures", 2012, 1st European Grid Infrastructure (EGI) Community Forum/ 2nd European Middleware Initiative (EMI) Technical Conference Proc. Muenich, Germany (To Be Published)
• Presentation slides
  • ISGC 2012 - Indico Link
  • EGI-Community Forum, 26.03-30.03-2012, München - Indico Link
  • Towards Integrated Information Systems, 26.03-30.03-2012, München (in conjunction with EGI-CF 2012) - Indico Link
  • Towards Integrated Information Systems, 01.12.2011, Amsterdam - Indico Link
  • EMI 4th AHM, 08.05-11.05.2012, Hamburg - Indico Link
  • EMI 3rd AHM, 17.10-19.10.2011, Padova - Indico Link
  • EMI 2nd AHM, 30.05-01.06.2011, Lund - Indico Link
  • EMI 1st AHM, 22-24.11.2010, Prague - Indico Link

EMIR product (code and binaries)

Source Code

The source code of EMIR is availale on GitHub. There are currently two git (scm) repositories for server and client respectively:

• EMIR Server Code
• EMIR SERP (Service Endpoint Record Publisher) Client Code

Binaries

All the binaries are available from the EMI software repository.

EMIR Server Bundles

• Scientific Linux 5: http://emisoft.web.cern.ch/emisoft/dist/EMI/2/sl5/x86_64/base/repoview/emi-emir.html
• Scientific Linux 6: http://emisoft.web.cern.ch/emisoft/dist/EMI/2/sl6/x86_64/base/repoview/emi-emir.html
• Debian 6: TBD

Each of the above server bundle contains.

• configuration file for setting the authenctication, access control, endpoint, logging, database and p2p/hierarchy
• start, stop, and init scripts

The details about individual configuration is provided in the installation and configuration guide.

EMIR-SERP (formerly called EMIRD) Bundles

• Scientific Linux 5:
  • http://emisoft.web.cern.ch/emisoft/dist/EMI/2/sl5/x86_64/base/repoview/emird.html
  • http://emisoft.web.cern.ch/emisoft/dist/EMI/2/sl5/x86_64/updates/repoview/emir-serp.html
• Scientific Linux 6:
  • http://emisoft.web.cern.ch/emisoft/dist/EMI/2/sl6/x86_64/base/repoview/emird.html
  • http://emisoft.web.cern.ch/emisoft/dist/EMI/2/sl6/x86_64/updates/repoview/emir-serp.html
• Debian 6: TBD

The bundles contains the configuration file for setting the target emir-server and (to be published) service endpoints information

Dependencies

The EMIR server and client dependencies are automatically fetched from the EMI repository while installing the respective binaries. However the following dependencies should be installed, if build and installed from the source code.

EMIR Server: Java (version > 1.6), MongoDB (Version > 2.0.1)

EMIR-SERP: python, python-ldap, python-simplejson

Service Reference Card

• EMIR Server Service Reference Card
• EMIR SERP Service Reference Card

Test results

• certification reports
• performance tests performed

Pilot Deployment

• EMIR testbed
• proposed deployment scenario hybrid scenario where an NGI runs both a DSR (for the local tree) and a GSR (for the full grid) - installation and config instructions for site and NGI level...

User Support & Contact

EMIR is being developed and maintained by the EMIR Product Team. The product team is lead by Shiraz Memon (JUELICH) and has two additional members Ivan Marton (NIIF) and Gabor Szigeti (NIIF)

Mailing List

• Email: emiregistry@googlegroupsNOSPAMPLEASE.com (public), emir@niifNOSPAMPLEASE.hu (broadcast to PT)
• Public Web Forum: https://groups.google.com/d/forum/emiregistry

Feature Requests and Bug Reporting

The feature requests and bugs can be reported on Github Website.

EMIR Server: https://github.com/eu-emi/emiregistry/issues

EMIR-SERP: https://github.com/eu-emi/emir-serp/issues

User Support

https://ggus.eu

TODO

- finish the wiki restructuring

- do not use the Service_Endpoint_URL as a key

- check the version info in the record (to be sync with EMI agreement)

- provide a clean definition of the service_endpoint record (attribute, optional/mandatory, example value)

- cross-check that VO affiliation of a service endpoint is part of the record

- emphasises everywhere oin the documentation that EMIR is a service endpoint registry and not a service registry

- EMIR-SERP: Ivan to finish the implementation of the resource-ldap -> EMIR modul AND documented configuration

- Laurence's script to register all the services of a site-bdii should be shared/distributed

- anonymous query interface

- CANL integration

- new version release (30th July)

- deployment scenario document (12 July)

- complete the "infosys landscape evolution" document explaining the long term evolution of bdii/emir/other indices, the EMI vision of infosys future