1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
|
#
# AUTHOR <EMAIL@ADDRESS>, YEAR.
#
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
"POT-Creation-Date: 2016-05-03 17:45-0500\n"
"PO-Revision-Date: 2016-05-03 17:45-0500\n"
"Last-Translator: Automatically generated\n"
"Language-Team: None\n"
"MIME-Version: 1.0\n"
"Content-Type: application/x-publican; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
#. Tag: title
#, no-c-format
msgid "Upgrading the Configuration"
msgstr ""
#. Tag: para
#, no-c-format
msgid "This process was originally written for the upgrade from 0.6.<emphasis>x</emphasis> to 1.<emphasis>y</emphasis>, but the concepts should apply for any upgrade involving a change in the XML schema version."
msgstr ""
#. Tag: para
#, no-c-format
msgid "<indexterm> <primary>Upgrading the Configuration</primary> </indexterm> <indexterm> <primary>Configuration</primary><secondary>Upgrading</secondary> </indexterm> <indexterm> <primary>Upgrading</primary> </indexterm>"
msgstr ""
#. Tag: title
#, no-c-format
msgid "Perform the upgrade"
msgstr ""
#. Tag: title
#, no-c-format
msgid "Upgrade the software"
msgstr ""
#. Tag: para
#, no-c-format
msgid "Refer to the appendix: <xref linkend=\"ap-upgrade\" />"
msgstr ""
#. Tag: title
#, no-c-format
msgid "Upgrade the Configuration"
msgstr ""
#. Tag: para
#, no-c-format
msgid "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 XML syntax."
msgstr ""
#. Tag: para
#, no-c-format
msgid "In order to support such environments, it is actually possible to continue using the old XML syntax."
msgstr ""
#. Tag: para
#, no-c-format
msgid "The downside is, however, 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."
msgstr ""
#. Tag: para
#, no-c-format
msgid "Even if you wish to continue using the old syntax, it is advisable to follow the upgrade procedure (except for the last step) to ensure that the cluster is able to use your existing configuration (since it will perform much the same task internally)."
msgstr ""
#. Tag: para
#, no-c-format
msgid "Create a shadow copy to work with"
msgstr ""
#. Tag: screen
#, no-c-format
msgid "# crm_shadow --create upgrade06"
msgstr ""
#. Tag: para
#, no-c-format
msgid "Verify the configuration is valid <indexterm> <primary>Configuration</primary><secondary>Verify</secondary> </indexterm> <indexterm> <primary>Verify</primary> </indexterm><indexterm> <primary>Verify</primary><secondary>Configuration</secondary> </indexterm> <indexterm> <primary>Configuration</primary> </indexterm>"
msgstr ""
#. Tag: screen
#, no-c-format
msgid "# crm_verify --live-check"
msgstr ""
#. Tag: para
#, no-c-format
msgid "Fix any errors or warnings"
msgstr ""
#. Tag: para
#, no-c-format
msgid "Perform the upgrade:"
msgstr ""
#. Tag: screen
#, no-c-format
msgid "# cibadmin --upgrade"
msgstr ""
#. Tag: para
#, no-c-format
msgid "If this step fails, there are three main possibilities:"
msgstr ""
#. Tag: para
#, no-c-format
msgid "The configuration was not valid to start with - go back to step 2"
msgstr ""
#. Tag: para
#, no-c-format
msgid "The transformation failed - report a bug or <ulink url=\"mailto:pacemaker@oss.clusterlabs.org?subject=Transformation%20failed%20during%20upgrade\">email the project</ulink>"
msgstr ""
#. Tag: para
#, no-c-format
msgid "The transformation was successful but produced an invalid result <footnote><para> The most common reason is ID values being repeated or invalid. Pacemaker 1.0 is much stricter regarding this type of validation. </para></footnote>"
msgstr ""
#. Tag: para
#, no-c-format
msgid "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 the <ulink url=\"http://clusterlabs.org/wiki/Validation_FAQ\">Validation FAQ wiki page</ulink> and/or try the procedure described below under <xref linkend=\"s-upgrade-config-manual\" />"
msgstr ""
#. Tag: para
#, no-c-format
msgid "Check the changes"
msgstr ""
#. Tag: screen
#, no-c-format
msgid "# crm_shadow --diff"
msgstr ""
#. Tag: para
#, no-c-format
msgid "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:"
msgstr ""
#. Tag: screen
#, no-c-format
msgid "# crm_shadow --edit"
msgstr ""
#. Tag: para
#, no-c-format
msgid "This will open the configuration in your favorite editor (whichever is specified by the standard <emphasis role=\"strong\">$EDITOR</emphasis> environment variable)"
msgstr ""
#. Tag: para
#, no-c-format
msgid "Preview how the cluster will react:"
msgstr ""
#. Tag: screen
#, no-c-format
msgid "# crm_simulate --live-check --save-dotfile upgrade06.dot -S\n"
"# graphviz upgrade06.dot"
msgstr ""
#. Tag: para
#, no-c-format
msgid "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 <xref linkend=\"s-config-testing-changes\" /> for further details on how to interpret the output of <literal>crm_simulate</literal> and <literal>graphviz</literal>."
msgstr ""
#. Tag: para
#, no-c-format
msgid "Upload the changes"
msgstr ""
#. Tag: screen
#, no-c-format
msgid "# crm_shadow --commit upgrade06 --force"
msgstr ""
#. Tag: para
#, no-c-format
msgid "In the unlikely event this step fails, please report a bug."
msgstr ""
#. Tag: title
#, no-c-format
msgid "Manually Upgrading the Configuration"
msgstr ""
#. Tag: para
#, no-c-format
msgid "<indexterm> <primary>Configuration</primary><secondary>Upgrade manually</secondary> </indexterm> <indexterm> <primary>Upgrade manually</primary> </indexterm> It is also possible to perform the configuration upgrade steps manually:"
msgstr ""
#. Tag: para
#, no-c-format
msgid "Locate the <literal>upgrade06.xsl</literal> conversion script provided with the source code (the <ulink url=\"https://github.com/ClusterLabs/pacemaker/tree/master/xml/upgrade06.xsl\">latest version</ulink> is available via git)."
msgstr ""
#. Tag: para
#, no-c-format
msgid "Convert the XML blob: <indexterm> <primary>XML</primary><secondary>Convert</secondary> </indexterm> <indexterm> <primary>Convert</primary> </indexterm>"
msgstr ""
#. Tag: screen
#, no-c-format
msgid "# xsltproc /path/to/upgrade06.xsl config06.xml > config10.xml"
msgstr ""
#. Tag: para
#, no-c-format
msgid "Locate the <literal>pacemaker.rng</literal> script."
msgstr ""
#. Tag: para
#, no-c-format
msgid "Check the XML validity: <indexterm> <primary>Validate Configuration</primary> </indexterm><indexterm> <primary>Configuration</primary><secondary>Validate XML</secondary> </indexterm> <indexterm> <primary>Validate XML</primary> </indexterm>"
msgstr ""
#. Tag: screen
#, no-c-format
msgid "# xmllint --relaxng /path/to/pacemaker.rng config10.xml"
msgstr ""
#. Tag: para
#, no-c-format
msgid "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."
msgstr ""
|
