TWiki> EGEE Web>EGEEMiddlewareSupport>GIP (revision 1)EditAttachPDF

Generic Information Provider

The Generic Information Provider, GIP, is a highly configurable information provider that makes a separation between static and dynamic information. It can be used to produce any kind of information for use with LDAP based grid information systems.

An information provider in its simplest form is a script that prints an LDIF file to standard out. The LDIF file should conform to the schema used in the GIP. The problem is with dynamic information. It is for this reason that there currently exists many different information providers written by many different people and that require many different methods of configuration. Usually there are only a few attributes that have to be found dynamically. The idea with the GIP is to use dynamic plug-ins to obtain these values and use a common framework for everything else.

The GIP configuration file contains all the configuration parameters for the GIP.

temp_dir

The directory to use as the GIPs cache.

plugin_dir

The directory where to put links to the dynamic plugins.

static_dir

The directory where to put inks to the static ldif files.

provider_dir

The directory where to put links to the information providers.

freshness

How long to use the cache before running the dynamic plugins again.

cache_ttl

How long the cache is valid.

response

How long the GIP will wait for dynamic plugins before continuing.

timeout

Timeout for the dynamic plugins in seconds.

The GIP script reads in all the ldif files from the static_dir and run all the providers in the plugin_dir. It will then run any dynamic plug-ins found in the plugin_dir to obtain the dynamic values. It will print the LDIF to standard out but use the any dynamic values found from the plugins. Plugins and providers should not be put directly into the directory, insted a symbolic link or wrapper script should be used. This enables us to turn them on and off without having to remove the software.

The advantage of this framework is that it reduces the number of packages, lines of code, different configuration methods etc. To use new dynamics sources only a new dynamic plug-in is required.

-- LaurenceField - 31 Aug 2006

Edit | Attach | Watch | Print version | History: r5 | r4 < r3 < r2 < r1 | Backlinks | Raw View | Raw edit | More topic actions...
Topic revision: r1 - 2006-08-31 - LaurenceField
 
    • Cern Search Icon Cern Search
    • TWiki Search Icon TWiki Search
    • Google Search Icon Google Search

    EGEE All webs login

This site is powered by the TWiki collaboration platform Powered by Perl This site is powered by the TWiki collaboration platformCopyright & by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding TWiki? Ask a support question or Send feedback