| 2 | | The basics of EGI Information Service are described at [[http://gridinfo.web.cern.ch/introduction|link]]. |
| 3 | | |
| 4 | | In general, information about a grid service is produced by a service provider and transfered into the closest BDII (LDAP) instance (typically co-allocated with the service).This procedure is significantly simplified with the help of tools offered by EMI Resource Information Service (`emi-resource-information-service`). Consequently, the integration of new services was limited to the provisioning of a few script and configuration files. In case of QCG-Notification, the required stuff is distributed within the package: '''`qcg-ntf-egi-is-provider`''', available for SL5 and SL6. |
| 5 | | |
| 6 | | == Requirements == |
| 7 | | The integration of QCG-Notification with the EGI IS is based on tools enclosed in the `emi-resource-information-service` metapackage (including, among others `glite-info-provider-service` and `bdii`). The packages may be obtained from the EMI repo, which should be added to the yum in prior the installation: |
| 8 | | |
| 9 | | {{{ |
| 10 | | cd /etc/yum.repos.d/ |
| 11 | | wget http://emisoft.web.cern.ch/emisoft/dist/EMI/3/repos/sl6/emi3-base.repo |
| 12 | | wget http://emisoft.web.cern.ch/emisoft/dist/EMI/3/repos/sl6/emi3-updates.repo |
| 13 | | rpm --import http://emisoft.web.cern.ch/emisoft/dist/EMI/3/RPM-GPG-KEY-emi |
| 14 | | |
| 15 | | yum install emi-resource-information-service |
| 16 | | }}} |
| 17 | | |
| 18 | | Next, it also may be needed to configure (in `/etc/bdii` directory) and start the bdii service (`/sbin/service bdii start`). |
| 19 | | |
| 20 | | Please also check if the yum repositories for QCG packages are configured correctly: [http://apps.man.poznan.pl/trac/qcg/wiki/Software%20repositories instruction]. |
| 21 | | |
| 22 | | == Installation == |
| 23 | | The installation of QCG-Notification provider for EGI IS may be done simply by installing the '''`qcg-ntf-egi-is-provider`''' RPM: |
| 24 | | {{{ |
| 25 | | yum install qcg-ntf-egi-is-provider |
| 26 | | }}} |
| 27 | | |
| 28 | | == Configuration == |
| 29 | | All the QCG EGI IS providers depend on the '''`qcg-egi-is-conf`''' package that is used for configuration of common data for all QCG services installed on the same resource. After the first installation of `qcg-egi-is-conf`, the installator will ask for configuration of the '''`site-ID`''': |
| 30 | | |
| 31 | | {{{ |
| 32 | | Installing : qcg-egi-is-conf-3.2.0-5.noarch 1/2 |
| 33 | | The package requires initial configuration in order to be used by QCG providers. |
| 34 | | Run qcg-info-site-config -s <site-ID> to set appropriate data. |
| 35 | | The list of available site-IDs can be found at https://goc.egi.eu/portal/index.php?Page_Type=Sites |
| 36 | | }}} |
| 37 | | |
| 38 | | According to this information, the requested data may be established with help of '''`qcg-info-site-config`''' command: |
| 39 | | {{{ |
| 40 | | qcg-info-site-config -s PSNC |
| 41 | | }}} |
| 42 | | |
| 43 | | Currently configured `site-ID` may be displayed as follows: |
| 44 | | {{{ |
| 45 | | qcg-info-site-config -d |
| 46 | | site-ID=PSNC |
| 47 | | }}} |
| | 2 | Please look at [[http://www.qoscosgrid.org/trac/qcg/wiki/QCG-EGI-IS]]. |
