| | 1 | = QCG-BDII = |
| | 2 | |
| | 3 | The guide describes the process of integration of QCG services with the EGI Information System - Resource BDII. |
| | 4 | |
| | 5 | The integration results in publishing information about the service in a GLUE2 complaint format through the BDII service. |
| | 6 | |
| | 7 | The basics of EGI Information Service are described at [[http://gridinfo.web.cern.ch/introduction|link]]. |
| | 8 | |
| | 9 | |
| | 10 | 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. |
| | 11 | |
| | 12 | |
| | 13 | '''IMPORTANT:''' The documentation is common for all QCG services: QCG-Broker, QCG-Computing and QCG-Notifications and varies only in some points from one service to another. |
| | 14 | = Software repositories = |
| | 15 | |
| | 16 | To install QCG-BDII (BDII for one of QCG services) please configure the system with: |
| | 17 | * one of QCG repositories, containing QCG specific extensions to the EGI information system. The RPMs are availeble for SL5 and SL6. |
| | 18 | * EMI3 (Monte Bianco) repository, which is needed for the `emi-resource-information-service` metapackage, providing the EGI information system base framework. |
| | 19 | To configure aforementioned repositories please follow the instruction: [[http://www.qoscosgrid.org/trac/qcg/wiki/Software%20repositories | QCG Software Repositories]]. |
| | 20 | |
| | 21 | = Installation = |
| | 22 | |
| | 23 | Install the proper package for the selected service: |
| | 24 | |
| | 25 | * for '''QCG-Broker''' service: |
| | 26 | {{{ |
| | 27 | yum install qcg-broker-egi-is-provider |
| | 28 | }}} |
| | 29 | |
| | 30 | |
| | 31 | * for '''QCG-Computing''' service |
| | 32 | {{{ |
| | 33 | yum install qcg-comp-egi-is-provider |
| | 34 | }}} |
| | 35 | |
| | 36 | |
| | 37 | * for '''QCG-Notification''' service |
| | 38 | {{{ |
| | 39 | yum install qcg-ntf-egi-is-provider |
| | 40 | }}} |
| | 41 | |
| | 42 | All the dependency packages will be automatically installed. |
| | 43 | == Configuration == |
| | 44 | All the QCG-BDII packages need to be configured by providing the name of the BDII site, to which they intend to publish service information. |
| | 45 | |
| | 46 | Run the command |
| | 47 | {{{ |
| | 48 | qcg-info-site-config -s <site-ID> |
| | 49 | }}} |
| | 50 | to set appropriate data. |
| | 51 | |
| | 52 | The list of available site-IDs can be found at https://goc.egi.eu/portal/index.php?Page_Type=Sites |
| | 53 | |
| | 54 | Currently configured `site-ID` may be displayed as follows: |
| | 55 | {{{ |
| | 56 | qcg-info-site-config -d |
| | 57 | site-ID=PSNC |
| | 58 | }}} |
| | 59 | |
| | 60 | = Starting service = |
| | 61 | |
| | 62 | '''IMPORTANT:''' Before starting the QCG-BDII please ensure that the QCG service is properly configured and started. |
| | 63 | |
| | 64 | To start the QCG-BDII please run (as a root): |
| | 65 | {{{ |
| | 66 | service bdii start |
| | 67 | }}} |
| | 68 | |
| | 69 | By default the BDII works on port 2170. |
| | 70 | |
| | 71 | == Verification == |
| | 72 | To validate correctness of the published data the glue-validator tool can be used: |
| | 73 | |
| | 74 | {{{ |
| | 75 | glue-validator -H localhost -p 2170 -b o=glue |
| | 76 | }}} |
