| 625 | | ''Note : in QWG templates for gLite 3.0 and gLite-3.1 until [milestone:gLite-3.1.0-4 gLite-3.1.0-4], MAUI variables described here, except `MAUI_WN_PART` and `MAUI_WN_PART_DEF`, are not available and the complete MAUI configuration must be provided into variable `MAUI_CONFIG`.'' |
| | 625 | In addition to the variable to configure MAUI itself, there is one variable related to resource publishing into the BDII. The default plugin provided with gLite uses Torque to retrieve the number of job slots configured, the number of free slots... This doesn't allow to reflect correctly a configuration where advanced MAUI features like ''standing reservations'' are used. An alternative plugin, based on MAUI, is available and distributed with QWG templates (even though it is totally independent). To use this MAUI-based plugin instead of the Torque-based one, define the following variable in your [source:templates/trunk/sites/example/site/glite/config.tpl gLite parameters] (this variable is ignored if the LRMS used in not Torque): |
| | 626 | {{{ |
| | 627 | variable GIP_CE_USE_MAUI ?= true; |
| | 628 | }}} |
| | 638 | |
| | 639 | === CE Publishing into BDII === |
| | 640 | |
| | 641 | When using Torque/MAUI, the default plugin provided with gLite to retrieve the number of job slots configured and the number of free slots is using Torque. This doesn't allow to reflect correctly a configuration where advanced MAUI features like ''standing reservations'' are used. An alternative plugin, based on MAUI, is available and distributed with QWG templates (even though it is totally independent). To use this MAUI-based plugin instead of the Torque-based one, define the following variable in your [source:templates/trunk/sites/example/site/glite/config.tpl gLite parameters] (this variable is ignored if the LRMS used in not Torque): |
| | 642 | {{{ |
| | 643 | variable GIP_CE_USE_MAUI ?= true; |
| | 644 | }}} |
| | 645 | |
| | 646 | This variable is `true` by default in QWG templates. Set it to `false` if you want to use the standard plugin. |
| | 647 | |
| | 648 | Another specific feature provided by QWG templates with respect to CE publishing into the BDII is the ability to run plugins in charge of updating CE dynamic information as a cron job on the LRMS host and to cache their outputs for later use by GIP itself. This is generally necessary in a multiple CE configuration and this is mandatory with MAUI-based plugins when using Torque/MAUI as MAUI commands can be executed only on the MAUI server. This ''cache mode'' is also lowering the polling rate on the batch system and protects again temporary failure of the LRMS to respond to the inquiry command (this is quite usual with MAUI when it is overloaded). To activiate this feature, you need to define the following variable in your [source:templates/trunk/sites/example/site/glite/config.tpl gLite parameters]: |
| | 649 | {{{ |
| | 650 | variable GIP_CE_USE_CACHE ?= true; |
| | 651 | }}} |
| | 652 | |
| | 653 | This variable default depends on the number of CE configured. When there is only one CE, it is `false` for backward compatibility, else it is `true`. But it is recommended to set it to `true` inconditionally. |
| | 654 | |
| | 655 | ''Note: cache mode, even though it is essentially independent of the LRMS, is currently implemented only for MAUI. Defining this variable for unsupported LRMS has no effect.'' |
| | 656 | |
| | 657 | |
| | 658 | |
