CEMON / BDII Integrated Server

This process sits on a port and waits for connections from resources. It then saves the data sent to a file in the CEMon consumer's own data space. The file name is that of the hostname reported by the CEMon consumer.

This is just the scanning part of the normal BDII server package. Using a list of sites, it forms ldapsearch commands then executes them. The data returned is saved in a tmp directory and then moved to this feed's local data storage if and only if the ldapsearch completes without error.

This script runs periodically and scan each of the feed's data directories and collects the file timestamp. The most recent data file time is compared to the time of the data currently being served for that resource. If a feed has newer data, that file is accessed and processed to put the site's resource name in the data's DN field with the form of mds-vo-name=SITE_NAME. This daemon also deletes any resource's served data file if it becomes too old. The current maximum age is 10 minutes.

This is the data to be served by the BDII update part of the BDII server package. There is also a parallel storage directory that contains entries denoting the source of the served information as well as it's age.

This is the last part of the bdii-update script. It reaps all the available data and adds the mds-vo-name=local tag to the DN field. The data is then loaded into one of two ldap servers - one ldap server serves data while the other is being loaded. When the process is done, it pauses for a small amount of time then starts again. The typical update time should be about 1 minute.

Each element in the block diagram that needs to know the shortname, hostname, ect. of a resource does so by consulting the master list at each itineration of its cycle. Nothing needs to be restarted to get sites on or off the local listing. Currently, the only blocks that access this information is the BDII Scanner, BDII server, and the daemon.