diff --git a/doc/Pacemaker_Explained/en-US/Ap-Upgrade-Config.xml b/doc/Pacemaker_Explained/en-US/Ap-Upgrade-Config.xml index 8a7ff366d7..d9177d1230 100644 --- a/doc/Pacemaker_Explained/en-US/Ap-Upgrade-Config.xml +++ b/doc/Pacemaker_Explained/en-US/Ap-Upgrade-Config.xml @@ -1,93 +1,93 @@ Upgrading the Configuration from 0.6
Preparation Download the latest DTD from and ensure your configuration validates.
Perform the upgrade
Upgrade the software Refer to the appendix:
Upgrade the Configuration As XML is not the friendliest of languages, it is common for cluster administrators to have scripted some of their activities. In such cases, it is likely that those scripts will not work with the new 1.0 syntax. In order to support such environments, it is actually possible to continue using the old 0.6 syntax. The downside however, is that not all the new features will be available and there is a performance impact since the cluster must do a non-persistent configuration upgrade before each transition. So while using the old syntax is possible, it is not advisable to continue using it indefinitely. Even if you wish to continue using the old syntax, it is advisable to follow the upgrade procedure to ensure that the cluster is able to use your existing configuration (since it will perform much the same task internally). Create a shadow copy to work with crm_shadow --create upgrade06 Verify the configuration is valid crm_verify --live-check Fix any errors or warnings Perform the upgrade cibadmin --upgrade If this step fails, there are three main possibilities The configuration was not valid to start with - go back to step 2 The transformation failed - report a bug or email the project at pacemaker@oss.clusterlabs.org The transformation was successful but produced an invalid result The most common reason is ID values being repeated or invalid. Pacemaker 1.0 is much stricter regarding this type of validation If the result of the transformation is invalid, you may see a number of errors from the validation library. If these are not helpful, visit and/or try the following procedure described below under . Check the changes crm_shadow --diff If at this point there is anything about the upgrade that you wish to fine-tune (for example, to change some of the automatic IDs) now is the time to do so. Since the shadow configuration is not in use by the cluster, it is safe to edit the file manually: crm_shadow --edit Will open the configuration in your favorite editor (or whichever one is specified by the standard EDITOR environment variable). Preview how the cluster will react Test what the cluster will do when you upload the new configuration ptest -VVVVV --live-check --save-dotfile upgrade06.dot graphviz upgrade06.dot Verify that either no resource actions will occur or that you are happy with any that are scheduled. If the output contains actions you do not expect (possibly due to changes to the score calculations), you may need to make further manual changes. See for further details on how to interpret the output of ptest. Upload the changes crm_shadow --commit upgrade06 --force If this step fails, something really strange has occurred. You should report a bug.
Manually Upgrading the Configuration It is also possible to perform the configuration upgrade steps manually. To do this Locate the upgrade06.xsl conversion script or download the latest version from version control - xsltproc /path/tp/upgrade06.xsl config06.xml > config10.xml + xsltproc /path/to/upgrade06.xsl config06.xml > config10.xml Locate the pacemaker.rng script. - xmllint --relaxng /path/tp/pacemaker.rng config10.xml + xmllint --relaxng /path/to/pacemaker.rng config10.xml The advantage of this method is that it can be performed without the cluster running and any validation errors should be more informative (despite being generated by the same library!) since they include line numbers.