Changes between Version 14 and Version 15 of Doc/gLite/WNCloning


Ignore:
Timestamp:
Dec 22, 2009, 3:45:58 PM (16 years ago)
Author:
/O=GRID-FR/C=FR/O=CNRS/OU=LAL/CN=Michel Jouvin
Comment:

--

Legend:

Unmodified
Added
Removed
Modified

  • Doc/gLite/WNCloning

    v14 v15  
    3535By default, the profile name is considered as matching the node name. If this is not the case, in particular if you use a prefix like `profile_` for your profile names, you need to define it with the variable `PROFILE_PREFIX`.
    3636
    37 === Miscellaneous Configuration Options ===
     37=== Miscellaneous Configuration Options === #MiscConfOptions
    3838
    3939Profile cloning is configured at a very early stage of the compilation process. As a result, it doesn't have access to the variables defined by the standard configuration process but needs to access directly some of specific site templates. If you don't use the standard names for these profiles, you should define the following variables (that are used by the standard configuration process and have the same defaults):
    … …  
    6666It is harmless to define this variable on a node which is not cloned.
    6767
    68 === Conditional Configuration ==
     68=== Conditional Configuration == #ConditionalActions
    6969
    7070If a site-specific template is executed in the context of profile cloning (as part of the configuration replayed on every node), it may test the variable `PROFILE_CLONING_CLONED_NODE` to do (or ignore) some actions in the context of profile cloning. This variable has the value `true` when the profile is cloned rather than rebuilt.
    … …  
    102102=== two (or more) children have the same name in merge() ===
    103103
    104 If you have some site-specific actions done after the `inlcude { 'machine-types/wn' }` and involving `npush` operations (or an explicit call to function `merge`), you may have the following error during cloning:
     104If you have some site-specific actions done after the `include { 'machine-types/wn' }` and involving `npush` operations (or an explicit call to function `merge`), you may have the following error during cloning:
    105105{{{
    106106two (or more) children have the same name in merge()
    107107}}}
    108108
     109This may also happen with actions done in [#MiscConfOptions CLUSTER_INFO_TEMPLATE] or [#MiscConfOptions SITE_CONFIG_TEMPLATE], which are reexecuted after cloning the reference profile.
     110
    109111This error results from the fact the entry you try to add to the nlist is already present in the reference profile and cannot be added twice. There are several workarounds possible to this problem:
    110112 * Use `WN_CONFIG_SITE` (specific to WN) or `GLITE_BASE_CONFIG_SITE` (executed for all gLite machines) to execute a template containing all the site specific actions. This template will not be reexecuted when profile is cloned. This is the recommended and the most efficient method.
    111  * Conditionally execute site-specific action by testing variable `PROFILE_CLONING_CLONED_NODE`.
     113 * Conditionally execute site-specific action by testing variable [#ConditionalActions PROFILE_CLONING_CLONED_NODE].
    112114 * Use a direct assignment to the nlist rather than using `npush` to overwrite the entry in the reference node rather than add a new one. This is the least recommended method as it can be pretty inefficient. To do it, use Pan code like:
    113115{{{