Skip to content

EGI-Federation/glite-info-provider-ldap

Repository files navigation

glite-info-provider-ldap

glite-info-provider-ldap enables information to be obtained by querying other BDIIs or LDAP servers. The script requires as input a configuration file containing a list of LDAP URLs of the form ldap://host.domain:2170/mds-vo-name=something,o=grid.

/opt/glite/libexec/glite-info-provider-ldap -c <config file> <options>

Options:

-c The configuration file listing all the LDAP URLs.

-m The mds-vo-name which should be used.

-h Displays this helpful message.

-d This option will change the search filter to only
retrieve the dynamic information. (currently not supported)

-t The timeout of the ldapsearch in seconds.

-v The validity of the cache files in seconds.

-s Maximum file size in megabytes for a single source.

BDII documentation is available at gridinfo documentation site.

Installing from packages

On RHEL-based systems

On RHEL-based systems, it's possible to install packages from EGI UMD packages. The packages are build from this repository, and tested to work with other components part of the Unified Middleware Distribution.

On CentOS 7, some dependencies are in EPEL.

Building packages

The Makefile allows building source tarball and packages.

Building an RPM

The required build dependencies are:

  • rpm-build
  • yum-utils
# Checkout tag to package
$ git clone https://github.com/EGI-Foundation/glite-info-provider-ldap.git
$ cd glite-info-provider-ldap
$ git checkout X.X.X
# Building in a container
$ docker run --rm -v $(pwd):/source -it quay.io/centos/centos:7
[root@8a9d60c61f42 /]# cd /source
[root@8a9d60c61f42 /]# yum install -y rpm-build yum-utils
[root@8a9d60c61f42 /]# yum-builddep -y glite-info-provider-ldap.spec
[root@8a9d60c61f42 /]# make rpm

The RPM will be available into the build/RPMS directory.

Installing from source

This procedure is not for production deployment, please consider using packages.

  • Build dependencies: None
  • Runtime dependencies: bdii.

Get the source by cloning this repository and do a make install.

Preparing a release

  • Prepare a changelog from the last version, including contributors' names
  • Prepare a PR with
  • Merge the PR, then tag and release a new version
    • GitHub Actions build and attach packages to the release page

History

This work started under the EGEE project, and CERN hosted and maintained it for a long time. This is now hosted here on GitHub, maintained by the BDII community with support of members of the EGI Federation.