How To Publish Service Information into EMIR

These instructions explain how to publish service information into the testbed Domain Service Registry (DSR). As a prerequisite an EMI Resource Information Service needs to be installed.

The examples below are for SL6, but the packages are also available for Debian and SL5 and the configuration is very similar too. Manually built packages for all of the supported platforms can be found on the project github site this page. It's important to use at least version 1.2.0 (1.2.1 in case of SL5)!

Install the service publisher

Since EMI3 is still not out, it's highly recommended to add ETICS repository to yum repos and install the emir service publisher (EMIR-SERP) from there:

wget http://etics-repository.cern.ch:8080/repository/pm/registered/repomd/global/emi/sl6_x86_64_gcc446EPEL/etics-registered-emi.repo -O /etc/yum.repos.d/etics-registered-emi.repo
yum update
yum install emir-serp

OR download and install EMIR-SERP manually (after resolving the dependency)

yum install python-simplejson
wget --no-check-certificate  http://twiki.cern.ch/twiki/pub/EMI/SERP/emir-serp-1.2.2-0.el6.noarch.rpm
rpm -i emir-serp-1.2.2-0.el6.noarch.rpm

Configure the service publisher

Edit the file /etc/emi/emir-serp/emir-serp.ini and set the url for the EMIR DSR.

url = http://emitbdsr1.cern.ch:9126

Set your resource_bdii_url in a separated ini section just like in the commented example in the default configuration file:

[servicesFromResourceBDII]
resource_bdii_url = ldap://your.domain.com:2170

Start/Stop registration

Start the service: as a result the service record should appear in the configured EMIR

service emir-serp start

Stop the service: as a result the service record should be removed from the configured EMIR

service emir-serp stop

Test the service registration in EMIR

Check the expected services are published/removed:

http://emitbdsr1.cern.ch:9126/services

WARNING: Please check the published value of the "QualityLevel" attribute (production, pre-production, testing, development) so that it corresponds to the actual deployment state of the service. If necessary the values can be changed via configuration of the resource information system (e.g. YAIM).

Troubleshooting

General Tips

Check the following log file.

/var/log/emi/emir-serp/emir-serp.log

If you have any questions, just let us know: emir@niifNOSPAMPLEASE.hu

-- IvanMarton - 05-Nov-2012

• emir-serp_1.2.2-1_all.deb: EMIR SERP v1.2.2 packages for different operating systems

• emir-serp-1.2.2-0.el5.noarch.rpm: EMIR SERP v1.2.2 packages for different operating systems

• emir-serp-1.2.2-0.el6.noarch.rpm: EMIR SERP v1.2.2 packages for different operating systems