Difference: GIP (3 vs. 4)

Revision 42008-01-23 - LaurenceField

Line: 1 to 1
 
META TOPICPARENT name="EGEEMiddlewareSupport"

Generic Information Provider

Overview

The Generic Information Provider, GIP, is a framework which simplifies the creation and deployment of information providers. The GIP enables smaller plugins to be used which makes it easier to support new systems by separating static and dynamic information. It can be used in conjunction with other LDAP based grid information system components to inject information into the system.
Changed:
<
<
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. There are usually only a few attributes that have to be found dynamically from a specific system. To avoid the creation of many different information providers that duplicate much of thier functionality, the GIP uses a plugin mechanism to obtain these dynamic values from the specific system.
>
>
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. There are usually only a few attributes that have to be found dynamically from a specific system. To avoid the creation of many different information providers that duplicate much of their functionality, the GIP uses a plugin mechanism to obtain these dynamic values from the specific system.
 
Changed:
<
<
The GIP reads in all the LDIF files from the static directory. Depending on the state of the cache, the information providers in the providers directory and dynamic plug-ins found in the_plugin_ directory are run and the output stored in a temporary directory before updating the cache. When the providers or plugins are executed, a lock file is placed in the lock directory to stop multiple instances being spawned. The dn is used to identify attributes and values from the same entry entry. The cached entries resulting from ruining information providers will overwrite entries from the static files. The cached values from the dynamic plug-ins will overwrite the values from static files and/or information providers. The resulting LDIF is then printed to standard out. Instead of putting plugins and providers directly into the directories, symbolic links or wrapper scripts can be used. This enables them to be turned on and off without having to uninstall them.
>
>
The GIP reads in all the LDIF files from the static directory. Depending on the state of the cache, the information providers in the providers directory and dynamic plug-ins found in the_plugin_ directory are run and the output stored in a temporary directory before updating the cache. When the providers or plugins are executed, a lock file is placed in the lock directory to stop multiple instances being spawned. The dn is used to identify attributes and values from the same entry entry. The cached entries resulting from running information providers will overwrite entries from the static files. The cached values from the dynamic plug-ins will overwrite the values from static files and/or information providers. The resulting LDIF is then printed to standard out. Instead of putting plugins and providers directly into the directories, symbolic links or wrapper scripts can be used. This enables them to be turned on and off without having to uninstall them.
  gip.png
 
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