| | 1 | = Integration with EGI Information Service = |
| | 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 services, the required stuff is distributed as RPM packages, respectively: |
| | 5 | * '''`qcg-comp-egi-is-provider`''' - for QCG-Computing service |
| | 6 | * '''`qcg-ntf-egi-is-provider`''' - for QCG-Notification service |
| | 7 | * '''`qcg-broker-egi-is-provider`''' - for QCG-Broker service |
| | 8 | The RPMs are availeble for SL5 and SL6. |
| | 9 | |
| | 10 | == Requirements == |
| | 11 | 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: |
| | 12 | |
| | 13 | {{{ |
| | 14 | cd /etc/yum.repos.d/ |
| | 15 | wget http://emisoft.web.cern.ch/emisoft/dist/EMI/3/repos/sl6/emi3-base.repo |
| | 16 | wget http://emisoft.web.cern.ch/emisoft/dist/EMI/3/repos/sl6/emi3-updates.repo |
| | 17 | rpm --import http://emisoft.web.cern.ch/emisoft/dist/EMI/3/RPM-GPG-KEY-emi |
| | 18 | |
| | 19 | yum install emi-resource-information-service |
| | 20 | }}} |
| | 21 | |
| | 22 | Next, it also may be needed to configure (in `/etc/bdii` directory) and start the bdii service (`/sbin/service bdii start`). |
| | 23 | |
| | 24 | Please also check if the yum repositories for QCG packages are configured correctly: [http://apps.man.poznan.pl/trac/qcg/wiki/Software%20repositories instruction]. |
| | 25 | |
| | 26 | == Installation == |
| | 27 | The installation of QCG-Notification provider for EGI IS may be done simply by installing the '''`qcg-ntf-egi-is-provider`''' RPM: |
| | 28 | {{{ |
| | 29 | yum install qcg-ntf-egi-is-provider |
| | 30 | }}} |
| | 31 | |
| | 32 | == Configuration == |
| | 33 | 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`''': |
| | 34 | |
| | 35 | {{{ |
| | 36 | Installing : qcg-egi-is-conf-3.2.0-5.noarch 1/2 |
| | 37 | The package requires initial configuration in order to be used by QCG providers. |
| | 38 | Run qcg-info-site-config -s <site-ID> to set appropriate data. |
| | 39 | The list of available site-IDs can be found at https://goc.egi.eu/portal/index.php?Page_Type=Sites |
| | 40 | }}} |
| | 41 | |
| | 42 | According to this information, the requested data may be established with help of '''`qcg-info-site-config`''' command: |
| | 43 | {{{ |
| | 44 | qcg-info-site-config -s PSNC |
| | 45 | }}} |
| | 46 | |
| | 47 | Currently configured `site-ID` may be displayed as follows: |
| | 48 | {{{ |
| | 49 | qcg-info-site-config -d |
| | 50 | site-ID=PSNC |
| | 51 | }}} |
