Changes between Version 9 and Version 10 of Doc/gLite/WNCloning

Timestamp:

Dec 13, 2009, 9:26:34 AM (16 years ago)

Author:

/O=GRID-FR/C=FR/O=CNRS/OU=LAL/CN=Michel Jouvin

Comment:

--

Doc/gLite/WNCloning

@@ -86 +86 @@
 The important thing to remember when using profile cloning is that some configuration parameters for the node are inherited from the reference node rather than using the node-specific value if it exists. This is particularly true for OS version/architecture selection, kernel version... Also the packages part of the profiles are inherited from the reference nodes, including the OS errata.
 
-To troubleshoot the decision to clone or not clone a profile, enable Pan compiler debugging features with the following command:
+To troubleshoot the decision to clone or not clone a profile, enable Pan compiler [/wiki/Doc/SCDB/Usage#Usingpancdebugging debugging features] with the following command:
 {{{
-ant -Dpan.debug.include=glite/wn/extra/selector
+ant -Dpan.debug.include=glite/wn/cloning/selector
 }}}
+
+== F.A.Q. ==
+
+=== The reference node profile sometimes has an invalid content ===
+
+You need to ensure you don't cross-reference you clusters in the cluster-specific file `cluster.build.properties`. '''This is strongly discouraged'''. When you use profile cloning, this may be the source of undesired side-effects: in particular, if one of the cluster doesn't have the cluster-specific configuration for the profile cloning whereas the other one has one (in particular the definition of a reference node), this may lead to the reference node being rebuilt in the context of the wrong cluster, impacting its OS versions, its gLite parameters...
+
+If you suspect something wrong, use the [#Troubleshooting troubleshooting] procedure describe above to activate debug messages during the compilation.
+
+
+=== Packages or templates provided by the OS not found ===
+
+The cloned node inherit the RPM repository configuration from the reference node. Regarding packages providing by the OS, this means that they will be looked for in the RPM repositories associated with the OS version/architecture of the reference node, whatever is the OS version/architecture explicitly defined for the cloned node.
+
+Even though OS version/architecture is inherited from the reference node, the OS version/architecture selection is replayed in the cloned node to allow to locate templates provided as part of the OS support. A restriction of the current implement is that the information used to configure the ''template loadpath'' is based on the cloned node configuration rather than the reference node configuration. If both don"t match, this may lead to errors like a template or a package that cannot be found. In particular, this may lead to loading a package with the wrong version for the OS version/architecture of the reference node.
+
+This should be improved in a future release.