gLite > gLite 3.2 > glite-BDII  
 
 

 

 

This site is deprecated

The new site for gLite is available under http://cern.ch/grid-deployment/glite-web/.

This web pages are not longer going to be updated and are kept only as an archive of all the previously released versions.

gLite 3.2

gLite BDII


This metapackage has been obsoleted and replaced by glite-BDII_site and glite-BDII_top. Please refer to this metapackages in the future.


Description

The Berkeley Database Information Index (BDII) consists of two or more standard LDAP databases that are populated by an update process. Port forwarding is used to enable one database to serve data while the other is refreshing. The update process obtains LDIF from either doing an ldapsearch on LDAP URLs or by running a local script that generates LDIF. The LDIF is then inserted into the LDAP database. Options exist to update the the list of LDAP URLs from a web page and to use an LDIF file from a web page to modify the data before inserting it into the database.

Documentation
For a quick overview on the Information System, please check the Information System Overview.

For further details on the BDII, please check the Berkeley Database Information Index twiki page.

For a technical summary of the BDII service, please check the BDII service reference card

Known Issues
Please pay attention to the known issues.

If you are having problems you may want to check the Troubleshooting pages.



Supported platform
The gLite 3.2 software stack is supported on Scientific Linux 5 (SL5).


Installation
The gLite BDII is available in RPM format. The recommended installation is via the gLite YUM repository. You can find the installation instructions here.

Due to the critical nature of the information system with respect to the operation of the grid, the BDII should be installed as a stand-alone service to ensure that problems with other services do not affect the BDII. In no circumstances should the BDII be co-hosted with a service which has the potential to generate a high load. To achieve the desired scalability, multiple BDII  instances should be deployed behind a round-robin DNS alias in order to provide a load balanced BDII service.



RPM Installation via YUM
The yum-module name is glite-BDII.

More information about gLite 3.2 Installation and Configuration can be found here.


Installation via individual RPMs
For the list of RPMs needed to install the BDII Node, please see individual version below.

Released Versions

Version Date Priority Update details List of RPMs
3.2.9-0.sl5 26.08.2010 High Details RPM list
3.2.8-0.sl5 27.04.2010 High Details RPM list
3.2.6-0 24.03.2010 Normal Details RPM list
3.2.5-0 08.02.2010 Normal Details RPM list
3.2.4-0 07.01.2010 Normal Details RPM list
3.2.3-0 22.09.2009 Normal Details RPM list
3.2.2-0 27.07.2009 High Details RPM list
3.2.1-0 29.06.09 Normal Details RPM list