MIP Design

Grid Independent Architecture

Grid Information Providers in the past have been developed for specific grids. Porting these information providers between grids has proven difficult and costly. Furthermore, these information providers handle similar information sources for the same Grid Information Services. This duplication of effort is not efficient and may encumber grid interoperability.


The Modular Information Provider (MIP) is proposed as a solution that is independent of any grid or grid-related software. MIP accomplishes grid-independence through a modular approach and the use of packages. Each package can be configured for a particular grid, grid-related software, or both! Further information on packages can be found at the Packages webpage.

Modular Architecture

The MIP Config script is used to install and configure MIP. When executed, it will first read the “Easy Edit Config” file. It will extract as much information as possible from this config file. If any values or attributes are missing, the user will be asked questions for the remaining information. Userss answers will be placed in the “Easy Edit Config” file. This removes the need for questions in subsequent executions.


Following the architecture diagram, MIP Config creates a file named “Perl Config”. This file holds the same information as the Easy Edit Config file. But the Perl Config file can be directly 'sourced' from MIP, which increases the execution speed and efficiency of MIP as well as seperates the “user interface” from the backend of MIP.

MIP Core

The MIP Config script is used to install and configure MIP. When executed, it will first read the “Easy Edit Config” file. It will extract as much information as possible from this config file. If any values or attributes are missing, the user will be asked questions for the remaining information. Userss answers will be placed in the “Easy Edit Config” file. This removes the need for questions in subsequent executions.


Following the architecture diagram, MIP Config creates a file named “Perl Config”. This file holds the same information as the Easy Edit Config file. But the Perl Config file can be directly 'sourced' from MIP, which increases the execution speed and efficiency of MIP as well as seperates the “user interface” from the backend of MIP.