pacemaker/doc/Pacemaker_Explained/pot/Ap-Upgrade-Config.pot - actifio - Git at Google

 #
 # 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 &gt; 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 ""
	#
	# 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 ""