Top-level BDII configuration file generator service

The tool is available as an RPM in the SAM repository and downloadable from CVS as well.

Software

Insatllation, layout

The software is located in /opt/lcg/bdiiconf-gen/ by default. The directory structure is explained below:

/bin

main executables $ /conf:

• bdii-additional.conf: This file contains a static list of URLs that should be added to the list further than the URLs coming from GOCDB
• bdii-exclude.conf: This file contains a static list of URLs that should be added to the list further than the URLs coming from GOCDB
• dbaccess.conf: definitions for DB connnection in the following format

              $ENV{'ORACLE_HOME'} = "";
              $ENV{'TNS_ADMIN'} = "";
              $user="";
              $password="";
              $database="";
          

/cron

Wrapper script to be invoked by cron job

/log

log file

/www

directory for the HTTP accessible BDII config file(s)

How does it work

It's basically a perl script that connects to GOCBD, and collects the LDAB URLs of site BDIIs that belong to the categories specified in the command-line parameters. There is a wrapper script that makes it easier to invoke the main executeable. This script should be invoked by cron, as below:

• 3,13,23,33,43,53 * * * * root /opt/lcg/bdiiconf-gen/cron/bdiiconf-gen-cronscript.sh 2>> /opt/lcg/bdiiconf-gen/log/bdiiconf-gen-cron.log 2>&1

The list of OSG sites is provied both for production and PPS on the web instead of coming from GOCDB.

• Prod OSG sites: http://vors.grid.iu.edu/cgi-bin/show_ldap_info.cgi
• PPS OSG sites: http://vors.grid.iu.edu/cgi-bin/show_ldap_info_pps.cgi

There is a script in the /bin directory to collect OSG information. If preferred, these URLs can be concatenated to the list coming from GOCDB. In order to keep the OSG list that's cached on the server up-to-date, a wrapper script is provided as in the previous case, so it could be invoked by a cron job as below:

• 0,10,20,30,40,50 * * * * root /opt/lcg/bdiiconf-gen/cron/get-osgsites-cron.sh 2>> /opt/lcg/bdiiconf-gen/log/get-osgsites-cron.log 2>&1

HTTP access to the output

The output of the script have to be available for all top-level BDIIs to download. Therefore additional httpd configuration is necessary. Something like below (an example httpd config file is available in the /conf directory)

        NameVirtualHost monb004.cern.ch:80

        NameVirtualHost monb004.cern.ch:80


        <VirtualHost monb004.cern.ch:80>
            Alias /bdii-conf /opt/lcg/bdiiconf-gen/www

            ServerName lcg-bdii-conf.cern.ch


            <Directory "/opt/lcg/bdiiconf-gen/www">
                Allow from all

                Order allow,deny

            </Directory>
        </VirtualHost>

-- JuditNovak - 24 Sep 2007