#
# AUTHOR <EMAIL@ADDRESS>, YEAR.
#
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
"POT-Creation-Date: 2012-10-17T05:19:02\n"
"PO-Revision-Date: 2011-05-03 15:38+0100\n"
"Last-Translator: RaSca <rasca@miamammausalinux.org>\n"
"Language-Team: None\n"
"Language: \n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
#. Tag: title
#, no-c-format
msgid "Resource Constraints"
msgstr "Vincoli delle risorse"
#. Tag: para
#, no-c-format
msgid "<indexterm> <primary>Resource</primary><secondary>Constraints</secondary> </indexterm> <indexterm> <primary>Constraints</primary> </indexterm>"
msgstr ""
#. Tag: title
#, no-c-format
msgid "Scores"
msgstr "Punteggi"
#. Tag: para
#, no-c-format
msgid "Scores of all kinds are integral to how the cluster works. Practically everything from moving a resource to deciding which resource to stop in a degraded cluster is achieved by manipulating scores in some way."
msgstr "Nel funzionamento del cluster sono integrati punteggi di ogni tipo. Praticamente qualsiasi decisione, dallo spostamento di una risorsa sino a quale risorsa fermare in un cluster degradato, è ottenuta manipolando in qualche forma i punteggi."
#. Tag: para
#, fuzzy, no-c-format
msgid "Scores are calculated on a per-resource basis and any node with a negative score for a resource can’t run that resource. After calculating the scores for a resource, the cluster then chooses the node with the highest one."
msgstr "I punteggi sono calcolati sulla base per l'erogazione di ogni risorsa e qualsiasi nodo con un punteggio negativo non può erogare la risorsa associata. Dopo aver calcolato i punteggi per una risorsa il cluster sceglie il nodo con il punteggio più alto."
#. Tag: title
#, no-c-format
msgid "Infinity Math"
msgstr "Il valore INFINITY"
#. Tag: para
#, fuzzy, no-c-format
msgid "<literal>INFINITY</literal> is currently defined as 1,000,000 and addition/subtraction with it follows these three basic rules:"
msgstr "<literal>INFINITY</literal> viene attualmente definito come 1,000,000 ed addizioni/sottrazioni ad esso seguono queste 3 regole base:"
#. Tag: para
#, no-c-format
msgid "Any value + <literal>INFINITY</literal> = <literal>INFINITY</literal>"
msgstr "Qualsiasi valore + <literal>INFINITY</literal> = <literal>INFINITY</literal>"
#. Tag: para
#, no-c-format
msgid "Any value - <literal>INFINITY</literal> = -<literal>INFINITY</literal>"
msgstr "Qualsiasi valore - <literal>INFINITY</literal> = -<literal>INFINITY</literal>"
#. Tag: para
#, no-c-format
msgid "<literal>INFINITY</literal> - <literal>INFINITY</literal> = -<literal>INFINITY</literal>"
msgstr "<literal>INFINITY</literal> - <literal>INFINITY</literal> = -<literal>INFINITY</literal>"
#. Tag: title
#, no-c-format
msgid "Deciding Which Nodes a Resource Can Run On"
msgstr "Decidere quale nodo può erogare una risorsa"
#. Tag: para
#, fuzzy, no-c-format
msgid "<indexterm> <primary>Location Constraints</primary> </indexterm> <indexterm> <primary>Resource</primary><secondary>Constraints</secondary><tertiary>Location</tertiary> </indexterm> <indexterm> <primary>Constraints</primary><secondary>Location</secondary> </indexterm> <indexterm> <primary>Location</primary> </indexterm> There are two alternative strategies for specifying which nodes a resources can run on. One way is to say that by default they can run anywhere and then create location constraints for nodes that are not allowed. The other option is to have nodes \"opt-in\"… to start with nothing able to run anywhere and selectively enable allowed nodes."
msgstr "Esistono due strategie alternative per specificare su quali nodi può funzionare una risorsa. Una via è quella di dire che di default la risorsa può funzionare ovunque e poi create dei vincoli posizionali (location constraints) per i nodi da escludere. L'altra via è quella di avere nodi che vengano avviati come inabili ad erogare risorse ed fare in modo che questi vengano abilitati selettivamente."
#. Tag: title
#, no-c-format
msgid "Options"
msgstr "Opzioni"
#. Tag: title
#, no-c-format
msgid "Options for Simple Location Constraints"
msgstr "Opzioni per semplici vincoli di locazione (location constraints)"
#. Tag: entry
#, no-c-format
msgid "Field"
msgstr "Campo"
#. Tag: entry
#, no-c-format
msgid "Description"
msgstr "Descrizione"
#. Tag: para
#, no-c-format
msgid "<literal>id</literal>"
msgstr ""
#. Tag: para
#, no-c-format
msgid "A unique name for the constraint <indexterm> <primary>id</primary><secondary>Location Constraints</secondary> </indexterm> <indexterm> <primary>Location Constraints</primary> </indexterm> <indexterm> <primary>Constraints</primary><secondary>Location</secondary><tertiary>id</tertiary> </indexterm> <indexterm> <primary>Location</primary><secondary>id</secondary> </indexterm> <indexterm> <primary>id</primary> </indexterm>"
msgstr ""
#. Tag: para
#, no-c-format
msgid "<literal>rsc</literal>"
msgstr ""
#. Tag: para
#, no-c-format
msgid "A resource name <indexterm> <primary>rsc</primary><secondary>Location Constraints</secondary> </indexterm> <indexterm> <primary>Location Constraints</primary> </indexterm> <indexterm> <primary>Constraints</primary><secondary>Location</secondary><tertiary>rsc</tertiary> </indexterm> <indexterm> <primary>Location</primary><secondary>rsc</secondary> </indexterm> <indexterm> <primary>rsc</primary> </indexterm>"
msgstr ""
#. Tag: para
#, no-c-format
msgid "<literal>node</literal>"
msgstr ""
#. Tag: para
#, no-c-format
msgid "A node’s name <indexterm> <primary>node</primary><secondary>Location Constraints</secondary> </indexterm> <indexterm> <primary>Location Constraints</primary> </indexterm> <indexterm> <primary>Constraints</primary><secondary>Location</secondary><tertiary>node</tertiary> </indexterm> <indexterm> <primary>Location</primary><secondary>node</secondary> </indexterm> <indexterm> <primary>node</primary> </indexterm>"
msgstr ""
#. Tag: para
#, no-c-format
msgid "<literal>score</literal>"
msgstr ""
#. Tag: para
#, fuzzy, no-c-format
msgid "Positive values indicate the resource should run on this node. Negative values indicate the resource should not run on this node."
msgstr "Valori positivi indicano che la risorsa può funzionare su questo nodo. Valori negativi indicano che la risorsa non può funzionare su questo nodo. Valori di +/- <literal>INFINITY</literal> modificano "può" in "deve"."
#. Tag: para
#, no-c-format
msgid "Values of +/- <literal>INFINITY</literal> change \"should\"/\"should not\" to \"must\"/\"must not\". <indexterm> <primary>score</primary><secondary>Location Constraints</secondary> </indexterm> <indexterm> <primary>Location Constraints</primary> </indexterm> <indexterm> <primary>Constraints</primary><secondary>Location</secondary><tertiary>score</tertiary> </indexterm> <indexterm> <primary>Location</primary><secondary>score</secondary> </indexterm> <indexterm> <primary>score</primary> </indexterm>"
msgstr ""
#. Tag: title
#, fuzzy, no-c-format
msgid "Asymmetrical \"Opt-In\" Clusters"
msgstr "Cluster "Opt-In" asimmetrici"
#. Tag: para
#, no-c-format
msgid "<indexterm> <primary>Asymmetrical Opt-In Clusters</primary> </indexterm> <indexterm> <primary>Cluster Type</primary><secondary>Asymmetrical Opt-In</secondary> </indexterm> <indexterm> <primary>Asymmetrical Opt-In</primary> </indexterm>"
msgstr ""
#. Tag: para
#, no-c-format
msgid "To create an opt-in cluster, start by preventing resources from running anywhere by default:"
msgstr ""
#. Tag: programlisting
#, no-c-format
msgid "# crm_attribute --attr-name symmetric-cluster --attr-value false"
msgstr ""
#. Tag: para
#, no-c-format
msgid "Then start enabling nodes. The following fragment says that the web server prefers <literal>sles-1</literal>, the database prefers <literal>sles-2</literal> and both can fail over to <literal>sles-3</literal> if their most preferred node fails."
msgstr ""
#. Tag: title
#, no-c-format
msgid "Example set of opt-in location constraints"
msgstr ""
#. Tag: programlisting
#, no-c-format
msgid ""
"<constraints>\n"
" <rsc_location id=\"loc-1\" rsc=\"Webserver\" node=\"sles-1\" score=\"200\"/>\n"
" <rsc_location id=\"loc-2\" rsc=\"Webserver\" node=\"sles-3\" score=\"0\"/>\n"
" <rsc_location id=\"loc-3\" rsc=\"Database\" node=\"sles-2\" score=\"200\"/>\n"
" <rsc_location id=\"loc-4\" rsc=\"Database\" node=\"sles-3\" score=\"0\"/>\n"
"</constraints>"
msgstr ""
#. Tag: title
#, fuzzy, no-c-format
msgid "Symmetrical \"Opt-Out\" Clusters"
msgstr "Cluster "Opt-In" asimmetrici"
#. Tag: para
#, no-c-format
msgid "<indexterm> <primary>Symmetrical Opt-Out Clusters</primary> </indexterm> <indexterm> <primary>Cluster Type</primary><secondary>Symmetrical Opt-Out</secondary> </indexterm> <indexterm> <primary>Symmetrical Opt-Out</primary> </indexterm>"
msgstr ""
#. Tag: para
#, no-c-format
msgid "To create an opt-out cluster, start by allowing resources to run anywhere by default:"
msgstr ""
#. Tag: programlisting
#, no-c-format
msgid "# crm_attribute --attr-name symmetric-cluster --attr-value true"
msgstr ""
#. Tag: para
#, no-c-format
msgid "Then start disabling nodes. The following fragment is the equivalent of the above opt-in configuration."
msgstr ""
#. Tag: title
#, no-c-format
msgid "Example set of opt-out location constraints"
msgstr ""
#. Tag: programlisting
#, no-c-format
msgid ""
"<constraints>\n"
" <rsc_location id=\"loc-1\" rsc=\"Webserver\" node=\"sles-1\" score=\"200\"/>\n"
" <rsc_location id=\"loc-2-dont-run\" rsc=\"Webserver\" node=\"sles-2\" score=\"-INFINITY\"/>\n"
" <rsc_location id=\"loc-3-dont-run\" rsc=\"Database\" node=\"sles-1\" score=\"-INFINITY\"/>\n"
" <rsc_location id=\"loc-4\" rsc=\"Database\" node=\"sles-2\" score=\"200\"/>\n"
"</constraints>"
msgstr ""
#. Tag: para
#, no-c-format
msgid "Whether you should choose opt-in or opt-out depends both on your personal preference and the make-up of your cluster. If most of your resources can run on most of the nodes, then an opt-out arrangement is likely to result in a simpler configuration. On the other-hand, if most resources can only run on a small subset of nodes an opt-in configuration might be simpler."
msgstr ""
#. Tag: title
#, no-c-format
msgid "What if Two Nodes Have the Same Score"
msgstr ""
#. Tag: para
#, no-c-format
msgid "If two nodes have the same score, then the cluster will choose one. This choice may seem random and may not be what was intended, however the cluster was not given enough information to know any better."
msgstr ""
#. Tag: title
#, no-c-format
msgid "Example of two resources that prefer two nodes equally"
msgstr ""
#. Tag: programlisting
#, no-c-format
msgid ""
"<constraints>\n"
" <rsc_location id=\"loc-1\" rsc=\"Webserver\" node=\"sles-1\" score=\"INFINITY\"/>\n"
" <rsc_location id=\"loc-2\" rsc=\"Webserver\" node=\"sles-2\" score=\"INFINITY\"/>\n"
" <rsc_location id=\"loc-3\" rsc=\"Database\" node=\"sles-1\" score=\"500\"/>\n"
" <rsc_location id=\"loc-4\" rsc=\"Database\" node=\"sles-2\" score=\"300\"/>\n"
" <rsc_location id=\"loc-5\" rsc=\"Database\" node=\"sles-2\" score=\"200\"/>\n"
"</constraints>"
msgstr ""
#. Tag: para
#, no-c-format
msgid "In the example above, assuming no other constraints and an inactive cluster, Webserver would probably be placed on sles-1 and Database on sles-2. It would likely have placed Webserver based on the node’s uname and Database based on the desire to spread the resource load evenly across the cluster. However other factors can also be involved in more complex configurations."
msgstr ""
#. Tag: title
#, no-c-format
msgid "Specifying in which Order Resources Should Start/Stop"
msgstr ""
#. Tag: para
#, no-c-format
msgid "<indexterm> <primary>Resource</primary><secondary>Constraints</secondary><tertiary>Ordering</tertiary> </indexterm> <indexterm> <primary>Constraints</primary><secondary>Ordering</secondary> </indexterm> <indexterm> <primary>Ordering</primary> </indexterm> <indexterm> <primary>Resource</primary><secondary>Start Order</secondary> </indexterm> <indexterm> <primary>Start Order</primary> </indexterm> <indexterm> <primary>Ordering Constraints</primary> </indexterm> The way to specify the order in which resources should start is by creating <literal>rsc_order</literal> constraints."
msgstr ""
#. Tag: title
#, no-c-format
msgid "Properties of an Ordering Constraint"
msgstr ""
#. Tag: para
#, no-c-format
msgid "A unique name for the constraint <indexterm> <primary>id</primary><secondary>Ordering Constraints</secondary> </indexterm> <indexterm> <primary>Ordering Constraints</primary> </indexterm> <indexterm> <primary>Constraints</primary><secondary>Ordering</secondary><tertiary>id</tertiary> </indexterm> <indexterm> <primary>Ordering</primary><secondary>id</secondary> </indexterm> <indexterm> <primary>id</primary> </indexterm>"
msgstr ""
#. Tag: para
#, no-c-format
msgid "<literal>first</literal>"
msgstr ""
#. Tag: para
#, no-c-format
msgid "The name of a resource that must be started before the <literal>then</literal> resource is allowed to. <indexterm> <primary>first</primary><secondary>Ordering Constraints</secondary> </indexterm> <indexterm> <primary>Ordering Constraints</primary> </indexterm> <indexterm> <primary>Constraints</primary><secondary>Ordering</secondary><tertiary>first</tertiary> </indexterm> <indexterm> <primary>Ordering</primary><secondary>first</secondary> </indexterm> <indexterm> <primary>first</primary> </indexterm>"
msgstr ""
#. Tag: para
#, no-c-format
msgid "<literal>then</literal>"
msgstr ""
#. Tag: para
#, no-c-format
msgid "The name of a resource. This resource will start after the <literal>first</literal> resource. <indexterm> <primary>then</primary><secondary>Ordering Constraints</secondary> </indexterm> <indexterm> <primary>Ordering Constraints</primary> </indexterm> <indexterm> <primary>Constraints</primary><secondary>Ordering</secondary><tertiary>then</tertiary> </indexterm> <indexterm> <primary>Ordering</primary><secondary>then</secondary> </indexterm> <indexterm> <primary>then</primary> </indexterm>"
msgstr ""
#. Tag: para
#, no-c-format
msgid "<literal>kind</literal>"
msgstr ""
#. Tag: para
#, no-c-format
msgid "How to enforce the constraint. (<emphasis>Since 1.1.2</emphasis>)"
msgstr ""
#. Tag: para
#, no-c-format
msgid "* Optional - Just a suggestion. Only applies if both resources are starting/stopping."
msgstr ""
#. Tag: para
#, no-c-format
msgid "* Mandatory - Always. If <emphasis>first</emphasis> is stopping or cannot be started, <emphasis>then</emphasis> must be stopped."
msgstr ""
#. Tag: para
#, no-c-format
msgid "* Serialize - Ensure that no two stop/start actions occur concurrently for a set of resources."
msgstr ""
#. Tag: para
#, no-c-format
msgid "<indexterm> <primary>kind</primary><secondary>Ordering Constraints</secondary> </indexterm> <indexterm> <primary>Ordering Constraints</primary> </indexterm> <indexterm> <primary>Constraints</primary><secondary>Ordering</secondary><tertiary>kind</tertiary> </indexterm> <indexterm> <primary>Ordering</primary><secondary>kind</secondary> </indexterm> <indexterm> <primary>kind</primary> </indexterm>"
msgstr ""
#. Tag: para
#, no-c-format
msgid "<literal>symmetrical</literal>"
msgstr ""
#. Tag: para
#, no-c-format
msgid "If true, which is the default, stop the resources in the reverse order. Default value: <emphasis>true</emphasis> <indexterm> <primary>symmetrical</primary><secondary>Ordering Constraints</secondary> </indexterm> <indexterm> <primary>Ordering Constraints</primary> </indexterm> <indexterm> <primary>Ordering Constraints</primary><secondary>symmetrical</secondary> </indexterm> <indexterm> <primary>symmetrical</primary> </indexterm>"
msgstr ""
#. Tag: title
#, no-c-format
msgid "Mandatory Ordering"
msgstr ""
#. Tag: para
#, no-c-format
msgid "When the <literal>then</literal> resource cannot run without the <literal>first</literal> resource being active, one should use mandatory constraints. To specify a constraint is mandatory, use scores greater than zero. This will ensure that the then resource will react when the first resource changes state."
msgstr ""
#. Tag: para
#, no-c-format
msgid "If the <literal>first</literal> resource was running and is stopped, the <literal>then</literal> resource will also be stopped (if it is running)."
msgstr ""
#. Tag: para
#, no-c-format
msgid "If the <literal>first</literal> resource was not running and cannot be started, the <literal>then</literal> resource will be stopped (if it is running)."
msgstr ""
#. Tag: para
#, no-c-format
msgid "If the <literal>first</literal> resource is (re)started while the <literal>then</literal> resource is running, the <literal>then</literal> resource will be stopped and restarted."
msgstr ""
#. Tag: title
#, no-c-format
msgid "Advisory Ordering"
msgstr ""
#. Tag: para
#, no-c-format
msgid "On the other hand, when <literal>score=\"0\"</literal> is specified for a constraint, the constraint is considered optional and only has an effect when both resources are stopping and/or starting. Any change in state by the <literal>first</literal> resource will have no effect on the <literal>then</literal> resource."
msgstr ""
#. Tag: title
#, no-c-format
msgid "Example of an optional and mandatory ordering constraint"
msgstr ""
#. Tag: programlisting
#, no-c-format
msgid ""
"<constraints>\n"
" <rsc_order id=\"order-1\" first=\"Database\" then=\"Webserver\" />\n"
" <rsc_order id=\"order-2\" first=\"IP\" then=\"Webserver\" score=\"0\"/>\n"
"</constraints>"
msgstr ""
#. Tag: para
#, no-c-format
msgid "Some additional information on ordering constraints can be found in the document <ulink url=\"http://clusterlabs.org/doc/Ordering_Explained.pdf\">Ordering Explained</ulink>."
msgstr ""
#. Tag: title
#, no-c-format
msgid "Placing Resources Relative to other Resources"
msgstr ""
#. Tag: para
#, no-c-format
msgid "<indexterm> <primary>Resource</primary><secondary>Constraints</secondary><tertiary>Colocation</tertiary> </indexterm> <indexterm> <primary>Constraints</primary><secondary>Colocation</secondary> </indexterm> <indexterm> <primary>Colocation</primary> </indexterm> <indexterm> <primary>Resource</primary><secondary>Location Relative to other Resources</secondary> </indexterm> <indexterm> <primary>Location Relative to other Resources</primary> </indexterm> When the location of one resource depends on the location of another one, we call this colocation."
msgstr ""
#. Tag: para
#, no-c-format
msgid "There is an important side-effect of creating a colocation constraint between two resources: it affects the order in which resources are assigned to a node. If you think about it, it’s somewhat obvious. You can’t place A relative to B unless you know where B is. <footnote><para> While the human brain is sophisticated enough to read the constraint in any order and choose the correct one depending on the situation, the cluster is not quite so smart. Yet. </para></footnote>"
msgstr ""
#. Tag: para
#, no-c-format
msgid "So when you are creating colocation constraints, it is important to consider whether you should colocate A with B or B with A."
msgstr ""
#. Tag: para
#, no-c-format
msgid "Another thing to keep in mind is that, assuming A is collocated with B, the cluster will also take into account A’s preferences when deciding which node to choose for B."
msgstr ""
#. Tag: para
#, no-c-format
msgid "For a detailed look at exactly how this occurs, see the <ulink url=\"http://www.clusterlabs.org/mediawiki/images/6/61/Colocation_Explained.pdf\">Colocation Explained</ulink> document."
msgstr ""
#. Tag: title
#, no-c-format
msgid "Properties of a Collocation Constraint"
msgstr ""
#. Tag: para
#, no-c-format
msgid "A unique name for the constraint. <indexterm> <primary>id</primary><secondary>Colocation Constraints</secondary> </indexterm> <indexterm> <primary>Colocation Constraints</primary> </indexterm> <indexterm> <primary>Constraints</primary><secondary>Colocation</secondary><tertiary>id</tertiary> </indexterm> <indexterm> <primary>Colocation</primary><secondary>id</secondary> </indexterm> <indexterm> <primary>id</primary> </indexterm>"
msgstr ""
#. Tag: para
#, no-c-format
msgid "The colocation source. If the constraint cannot be satisfied, the cluster may decide not to allow the resource to run at all. <indexterm> <primary>rsc</primary><secondary>Colocation Constraints</secondary> </indexterm> <indexterm> <primary>Colocation Constraints</primary> </indexterm> <indexterm> <primary>Constraints</primary><secondary>Colocation</secondary><tertiary>rsc</tertiary> </indexterm> <indexterm> <primary>Colocation</primary><secondary>rsc</secondary> </indexterm> <indexterm> <primary>rsc</primary> </indexterm>"
msgstr ""
#. Tag: para
#, no-c-format
msgid "<literal>with-rsc</literal>"
msgstr ""
#. Tag: para
#, no-c-format
msgid "The colocation target. The cluster will decide where to put this resource first and then decide where to put the resource in the <literal>rsc</literal> field. <indexterm> <primary>with-rsc</primary><secondary>Colocation Constraints</secondary> </indexterm> <indexterm> <primary>Colocation Constraints</primary> </indexterm> <indexterm> <primary>Constraints</primary><secondary>Colocation</secondary><tertiary>with-rsc</tertiary> </indexterm> <indexterm> <primary>Colocation</primary><secondary>with-rsc</secondary> </indexterm> <indexterm> <primary>with-rsc</primary> </indexterm>"
msgstr ""
#. Tag: para
#, no-c-format
msgid "Positive values indicate the resource should run on the same node. Negative values indicate the resources should not run on the same node. Values of +/- <literal>INFINITY</literal> change \"should\" to \"must\". <indexterm> <primary>score</primary><secondary>Colocation Constraints</secondary> </indexterm> <indexterm> <primary>Colocation Constraints</primary> </indexterm> <indexterm> <primary>Constraints</primary><secondary>Colocation</secondary><tertiary>score</tertiary> </indexterm> <indexterm> <primary>Colocation</primary><secondary>score</secondary> </indexterm> <indexterm> <primary>score</primary> </indexterm>"
msgstr ""
#. Tag: title
#, no-c-format
msgid "Mandatory Placement"
msgstr ""
#. Tag: para
#, no-c-format
msgid "Mandatory placement occurs any time the constraint’s score is <literal>+INFINITY</literal> or <literal>-INFINITY</literal>. In such cases, if the constraint can’t be satisfied, then the <literal>rsc</literal> resource is not permitted to run. For <literal>score=INFINITY</literal>, this includes cases where the <literal>with-rsc</literal> resource is not active."
msgstr ""
#. Tag: para
#, no-c-format
msgid "If you need <literal>resource1</literal> to always run on the same machine as <literal>resource2</literal>, you would add the following constraint:"
msgstr ""
#. Tag: title
#, no-c-format
msgid "An example colocation constraint"
msgstr ""
#. Tag: programlisting
#, no-c-format
msgid "<rsc_colocation id=\"colocate\" rsc=\"resource1\" with-rsc=\"resource2\" score=\"INFINITY\"/>"
msgstr ""
#. Tag: para
#, no-c-format
msgid "Remember, because <literal>INFINITY</literal> was used, if <literal>resource2</literal> can’t run on any of the cluster nodes (for whatever reason) then <literal>resource1</literal> will not be allowed to run."
msgstr ""
#. Tag: para
#, no-c-format
msgid "Alternatively, you may want the opposite… that <literal>resource1</literal> cannot run on the same machine as <literal>resource2</literal>. In this case use <literal>score=\"-INFINITY\"</literal>"
msgstr ""
#. Tag: title
#, no-c-format
msgid "An example anti-colocation constraint"
msgstr ""
#. Tag: programlisting
#, no-c-format
msgid "<rsc_colocation id=\"anti-colocate\" rsc=\"resource1\" with-rsc=\"resource2\" score=\"-INFINITY\"/>"
msgstr ""
#. Tag: para
#, no-c-format
msgid "Again, by specifying <literal>-INFINTY</literal>, the constraint is binding. So if the only place left to run is where <literal>resource2</literal> already is, then <literal>resource1</literal> may not run anywhere."
msgstr ""
#. Tag: title
#, no-c-format
msgid "Advisory Placement"
msgstr ""
#. Tag: para
#, no-c-format
msgid "If mandatory placement is about \"must\" and \"must not\", then advisory placement is the \"I’d prefer if\" alternative. For constraints with scores greater than <literal>-INFINITY</literal> and less than <literal>INFINITY</literal>, the cluster will try and accommodate your wishes but may ignore them if the alternative is to stop some of the cluster resources."
msgstr ""
#. Tag: para
#, no-c-format
msgid "Like in life, where if enough people prefer something it effectively becomes mandatory, advisory colocation constraints can combine with other elements of the configuration to behave as if they were mandatory."
msgstr ""
#. Tag: title
#, no-c-format
msgid "An example advisory-only colocation constraint"
msgstr ""
#. Tag: programlisting
#, no-c-format
msgid "<rsc_colocation id=\"colocate-maybe\" rsc=\"resource1\" with-rsc=\"resource2\" score=\"500\"/>"
msgstr ""
#. Tag: title
#, no-c-format
msgid "Ordering Sets of Resources"
msgstr ""
#. Tag: para
#, no-c-format
msgid "A common situation is for an administrator to create a chain of ordered resources, such as:"
msgstr ""
#. Tag: title
#, no-c-format
msgid "A chain of ordered resources"
msgstr ""
#. Tag: programlisting
#, no-c-format
msgid ""
"<constraints>\n"
" <rsc_order id=\"order-1\" first=\"A\" then=\"B\" />\n"
" <rsc_order id=\"order-2\" first=\"B\" then=\"C\" />\n"
" <rsc_order id=\"order-3\" first=\"C\" then=\"D\" />\n"
"</constraints>"
msgstr ""
#. Tag: title
#, no-c-format
msgid "Ordered Set"
msgstr ""
#. Tag: title
#, no-c-format
msgid "Visual representation of the four resources' start order for the above constraints"
msgstr ""
#. Tag: phrase
#, no-c-format
msgid "Ordered set"
msgstr ""
#. Tag: para
#, no-c-format
msgid "To simplify this situation, there is an alternate format for ordering constraints:"
msgstr ""
#. Tag: title
#, no-c-format
msgid "A chain of ordered resources expressed as a set"
msgstr ""
#. Tag: programlisting
#, no-c-format
msgid ""
"<constraints>\n"
" <rsc_order id=\"order-1\">\n"
" <resource_set id=\"ordered-set-example\" sequential=\"true\">\n"
" <resource_ref id=\"A\"/>\n"
" <resource_ref id=\"B\"/>\n"
" <resource_ref id=\"C\"/>\n"
" <resource_ref id=\"D\"/>\n"
" </resource_set>\n"
" </rsc_order>\n"
"</constraints>"
msgstr ""
#. Tag: para
#, no-c-format
msgid "Resource sets have the same ordering semantics as groups."
msgstr ""
#. Tag: title
#, no-c-format
msgid "A group resource with the equivalent ordering rules"
msgstr ""
#. Tag: programlisting
#, no-c-format
msgid ""
"<group id=\"dummy\">\n"
" <primitive id=\"A\" .../>\n"
" <primitive id=\"B\" .../>\n"
" <primitive id=\"C\" .../>\n"
" <primitive id=\"D\" .../>\n"
"</group>"
msgstr ""
#. Tag: para
#, no-c-format
msgid "While the set-based format is not less verbose, it is significantly easier to get right and maintain. It can also be expanded to allow ordered sets of (un)ordered resources. In the example below, <literal>rscA</literal> and <literal>rscB</literal> can both start in parallel, as can <literal>rscC</literal> and <literal>rscD</literal>, however <literal>rscC</literal> and <literal>rscD</literal> can only start once <emphasis>both</emphasis> <literal>rscA</literal> <emphasis>and</emphasis> <literal>rscB</literal> are active."
msgstr ""
#. Tag: title
#, no-c-format
msgid "Ordered sets of unordered resources"
msgstr ""
#. Tag: programlisting
#, no-c-format
msgid ""
"<constraints>\n"
" <rsc_order id=\"order-1\">\n"
" <resource_set id=\"ordered-set-1\" sequential=\"false\">\n"
" <resource_ref id=\"A\"/>\n"
" <resource_ref id=\"B\"/>\n"
" </resource_set>\n"
" <resource_set id=\"ordered-set-2\" sequential=\"false\">\n"
" <resource_ref id=\"C\"/>\n"
" <resource_ref id=\"D\"/>\n"
" </resource_set>\n"
" </rsc_order>\n"
" </constraints>"
msgstr ""
#. Tag: title
#, no-c-format
msgid "Two Sets of Unordered Resources"
msgstr ""
#. Tag: title
#, no-c-format
msgid "Visual representation of the start order for two ordered sets of unordered resources"
msgstr ""
#. Tag: phrase
#, no-c-format
msgid "Two ordered sets"
msgstr ""
#. Tag: para
#, no-c-format
msgid "Of course either set — or both sets — of resources can also be internally ordered (by setting <literal>sequential=\"true\"</literal>) and there is no limit to the number of sets that can be specified."
msgstr ""
#. Tag: title
#, no-c-format
msgid "Advanced use of set ordering - Three ordered sets, two of which are internally unordered"
msgstr ""
#. Tag: programlisting
#, no-c-format
msgid ""
"<constraints>\n"
" <rsc_order id=\"order-1\">\n"
" <resource_set id=\"ordered-set-1\" sequential=\"false\">\n"
" <resource_ref id=\"A\"/>\n"
" <resource_ref id=\"B\"/>\n"
" </resource_set>\n"
" <resource_set id=\"ordered-set-2\" sequential=\"true\">\n"
" <resource_ref id=\"C\"/>\n"
" <resource_ref id=\"D\"/>\n"
" </resource_set>\n"
" <resource_set id=\"ordered-set-3\" sequential=\"false\">\n"
" <resource_ref id=\"E\"/>\n"
" <resource_ref id=\"F\"/>\n"
" </resource_set>\n"
" </rsc_order>\n"
"</constraints>"
msgstr ""
#. Tag: title
#, no-c-format
msgid "Three Resources Sets"
msgstr ""
#. Tag: title
#, no-c-format
msgid "Visual representation of the start order for the three sets defined above"
msgstr ""
#. Tag: phrase
#, no-c-format
msgid "Three ordered sets"
msgstr ""
#. Tag: title
#, no-c-format
msgid "Collocating Sets of Resources"
msgstr ""
#. Tag: para
#, no-c-format
msgid "Another common situation is for an administrator to create a set of collocated resources. Previously this was possible either by defining a resource group (See <xref linkend=\"group-resources\" />) which could not always accurately express the design; or by defining each relationship as an individual constraint, causing a constraint explosion as the number of resources and combinations grew."
msgstr ""
#. Tag: title
#, no-c-format
msgid "A chain of collocated resources"
msgstr ""
#. Tag: programlisting
#, no-c-format
msgid ""
"<constraints>\n"
" <rsc_colocation id=\"coloc-1\" rsc=\"B\" with-rsc=\"A\" score=\"INFINITY\"/>\n"
" <rsc_colocation id=\"coloc-2\" rsc=\"C\" with-rsc=\"B\" score=\"INFINITY\"/>\n"
" <rsc_colocation id=\"coloc-3\" rsc=\"D\" with-rsc=\"C\" score=\"INFINITY\"/>\n"
"</constraints>"
msgstr ""
#. Tag: para
#, no-c-format
msgid "To make things easier, we allow an alternate form of colocation constraints using <literal>resource_sets</literal>. Just like the expanded version, a resource that can’t be active also prevents any resource that must be collocated with it from being active. For example, if <literal>B was</literal> not able to run, then both <literal>C (+and by inference +D)</literal> must also remain stopped."
msgstr ""
#. Tag: title
#, no-c-format
msgid "The equivalent colocation chain expressed using <literal>resource_sets</literal>"
msgstr ""
#. Tag: programlisting
#, no-c-format
msgid ""
"<constraints>\n"
" <rsc_colocation id=\"coloc-1\" score=\"INFINITY\" >\n"
" <resource_set id=\"collocated-set-example\" sequential=\"true\">\n"
" <resource_ref id=\"A\"/>\n"
" <resource_ref id=\"B\"/>\n"
" <resource_ref id=\"C\"/>\n"
" <resource_ref id=\"D\"/>\n"
" </resource_set>\n"
" </rsc_colocation>\n"
"</constraints>"
msgstr ""
#. Tag: para
#, no-c-format
msgid "Resource sets have the same colocation semantics as groups."
msgstr ""
#. Tag: title
#, no-c-format
msgid "A group resource with the equivalent colocation rules"
msgstr ""
#. Tag: para
#, no-c-format
msgid "This notation can also be used in this context to tell the cluster that a set of resources must all be located with a common peer, but have no dependencies on each other. In this scenario, unlike the previous, <literal>B would</literal> be allowed to remain active even if <literal>A or</literal> <literal>C</literal> (or both) were inactive."
msgstr ""
#. Tag: title
#, no-c-format
msgid "Using colocation sets to specify a common peer."
msgstr ""
#. Tag: programlisting
#, no-c-format
msgid ""
"<constraints>\n"
" <rsc_colocation id=\"coloc-1\" score=\"INFINITY\" >\n"
" <resource_set id=\"collocated-set-1\" sequential=\"false\">\n"
" <resource_ref id=\"A\"/>\n"
" <resource_ref id=\"B\"/>\n"
" <resource_ref id=\"C\"/>\n"
" </resource_set>\n"
" <resource_set id=\"collocated-set-2\" sequential=\"true\">\n"
" <resource_ref id=\"D\"/>\n"
" </resource_set>\n"
" </rsc_colocation>\n"
"</constraints>"
msgstr ""
#. Tag: para
#, no-c-format
msgid "Of course there is no limit to the number and size of the sets used. The only thing that matters is that in order for any member of set N to be active, all the members of set N+1 must also be active (and naturally on the same node); and if a set has <literal>sequential=\"true\"</literal>, then in order for member M to be active, member M+1 must also be active. You can even specify the role in which the members of a set must be in using the set’s role attribute."
msgstr ""
#. Tag: title
#, no-c-format
msgid "A colocation chain where the members of the middle set have no inter-dependencies and the last has master status."
msgstr ""
#. Tag: programlisting
#, no-c-format
msgid ""
"<constraints>\n"
" <rsc_colocation id=\"coloc-1\" score=\"INFINITY\" >\n"
" <resource_set id=\"collocated-set-1\" sequential=\"true\">\n"
" <resource_ref id=\"A\"/>\n"
" <resource_ref id=\"B\"/>\n"
" </resource_set>\n"
" <resource_set id=\"collocated-set-2\" sequential=\"false\">\n"
" <resource_ref id=\"C\"/>\n"
" <resource_ref id=\"D\"/>\n"
" <resource_ref id=\"E\"/>\n"
" </resource_set>\n"
" <resource_set id=\"collocated-set-2\" sequential=\"true\" role=\"Master\">\n"
" <resource_ref id=\"F\"/>\n"
" <resource_ref id=\"G\"/>\n"
" </resource_set>\n"
" </rsc_colocation>\n"
"</constraints>"
msgstr ""
#. Tag: title
#, no-c-format
msgid "Another Three Resources Sets"
msgstr ""
#. Tag: title
#, no-c-format
msgid "Visual representation of a colocation chain where the members of the middle set have no inter-dependencies"
msgstr ""
#. Tag: phrase
#, no-c-format
msgid "Colocation chain"
msgstr ""
#~ msgid "id"
#~ msgstr "id"
#~ msgid "A unique name for the constraint"
#~ msgstr "Nome univoco per il vincolo (constraint)"
#~ msgid "rsc"
#~ msgstr "rsc"
#~ msgid "A resource name"
#~ msgstr "Nome della risorsa"
#~ msgid "node"
#~ msgstr "node"
#~ msgid "A node's uname"
#~ msgstr "uname del nodo"
#~ msgid "score"
#~ msgstr "punteggio"