diff --git a/doc/Pacemaker_Explained/en-US/Ch-Constraints.txt b/doc/Pacemaker_Explained/en-US/Ch-Constraints.txt index b1cc47c426..7f5aa61aa0 100644 --- a/doc/Pacemaker_Explained/en-US/Ch-Constraints.txt +++ b/doc/Pacemaker_Explained/en-US/Ch-Constraints.txt @@ -1,650 +1,650 @@ = Resource Constraints = indexterm:[Resource,Constraints] == Scores == 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. 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. === Infinity Math === +INFINITY+ is currently defined as 1,000,000 and addition/subtraction with it follows these three basic rules: * Any value + +INFINITY+ = +INFINITY+ * Any value - +INFINITY+ = -+INFINITY+ * +INFINITY+ - +INFINITY+ = -+INFINITY+ == Deciding Which Nodes a Resource Can Run On == indexterm:[Location Constraints] indexterm:[Resource,Constraints,Location] 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. === Options === .Options for Simple Location Constraints [width="95%",cols="2m,5<",options="header",align="center"] |========================================================= |Field |Description |id |A unique name for the constraint indexterm:[id,Location Constraints] indexterm:[Constraints,Location,id] |rsc |A resource name indexterm:[rsc,Location Constraints] indexterm:[Constraints,Location,rsc] |node |A node's name indexterm:[node,Location Constraints] indexterm:[Constraints,Location,node] |score |Positive values indicate the resource should run on this node. Negative values indicate the resource should not run on this node. Values of \+/- +INFINITY+ change "should"/"should not" to "must"/"must not". indexterm:[score,Location Constraints] indexterm:[Constraints,Location,score] |========================================================= === Asymmetrical "Opt-In" Clusters === indexterm:[Asymmetrical Opt-In Clusters] indexterm:[Cluster Type,Asymmetrical Opt-In] To create an opt-in cluster, start by preventing resources from running anywhere by default: [source,C] # crm_attribute --attr-name symmetric-cluster --attr-value false Then start enabling nodes. The following fragment says that the web server prefers +sles-1+, the database prefers +sles-2+ and both can fail over to +sles-3+ if their most preferred node fails. .Example set of opt-in location constraints ====== [source,XML] ------- ------- ====== === Symmetrical "Opt-Out" Clusters === indexterm:[Symmetrical Opt-Out Clusters] indexterm:[Cluster Type,Symmetrical Opt-Out] To create an opt-out cluster, start by allowing resources to run anywhere by default: [source,C] # crm_attribute --attr-name symmetric-cluster --attr-value true Then start disabling nodes. The following fragment is the equivalent of the above opt-in configuration. .Example set of opt-out location constraints ====== [source,XML] ------- ------- ====== 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. [[node-score-equal]] === What if Two Nodes Have the Same Score === 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. .Example of two resources that prefer two nodes equally ====== [source,XML] ------- ------- ====== 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. [[s-resource-ordering]] == Specifying in which Order Resources Should Start/Stop == indexterm:[Resource,Constraints,Ordering] indexterm:[Resource,Start Order] indexterm:[Ordering Constraints] The way to specify the order in which resources should start is by creating +rsc_order+ constraints. .Properties of an Ordering Constraint [width="95%",cols="2m,5<",options="header",align="center"] |========================================================= |Field |Description |id |A unique name for the constraint indexterm:[id,Ordering Constraints] indexterm:[Constraints,Ordering,id] |first |The name of a resource that must be started before the +then+ resource is allowed to. indexterm:[first,Ordering Constraints] indexterm:[Constraints,Ordering,first] |then |The name of a resource. This resource will start after the +first+ resource. indexterm:[then,Ordering Constraints] indexterm:[Constraints,Ordering,then] |kind |How to enforce the constraint. ('Since 1.1.2') * Optional - Just a suggestion. Only applies if both resources are starting/stopping. * Mandatory - Always. If 'first' is stopping or cannot be started, 'then' must be stopped. * Serialize - Ensure that no two stop/start actions occur concurrently for a set of resources. indexterm:[kind,Ordering Constraints] indexterm:[Constraints,Ordering,kind] |symmetrical |If true, which is the default, stop the resources in the reverse order. Default value: _true_ indexterm:[symmetrical,Ordering Constraints] indexterm:[Ordering Constraints,symmetrical] |========================================================= === Mandatory Ordering === When the +then+ resource cannot run without the +first+ 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. * If the +first+ resource was running and is stopped, the +then+ resource will also be stopped (if it is running). * If the +first+ resource was not running and cannot be started, the +then+ resource will be stopped (if it is running). * If the +first+ resource is (re)started while the +then+ resource is running, the +then+ resource will be stopped and restarted. === Advisory Ordering === On the other hand, when +score="0"+ 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 +first+ resource will have no effect on the +then+ resource. .Example of an optional and mandatory ordering constraint ====== [source,XML] ------- ------- ====== Some additional information on ordering constraints can be found in -the document http://www.clusterlabs.org/mediawiki/images/d/d6/Ordering_Explained.pdf[Ordering Explained]. +the document http://clusterlabs.org/doc/Ordering_Explained.pdf[Ordering Explained]. [[s-resource-colocation]] == Placing Resources Relative to other Resources == indexterm:[Resource,Constraints,Colocation] indexterm:[Resource,Location Relative to other Resources] When the location of one resource depends on the location of another one, we call this colocation. 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:[ 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. ] So when you are creating colocation constraints, it is important to consider whether you should colocate A with B or B with A. 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. For a detailed look at exactly how this occurs, see the http://www.clusterlabs.org/mediawiki/images/6/61/Colocation_Explained.pdf[Colocation Explained] document. === Options === .Properties of a Collocation Constraint [width="95%",cols="2m,5<",options="header",align="center"] |========================================================= |Field |Description |id |A unique name for the constraint. indexterm:[id,Colocation Constraints] indexterm:[Constraints,Colocation,id] |rsc |The colocation source. If the constraint cannot be satisfied, the cluster may decide not to allow the resource to run at all. indexterm:[rsc,Colocation Constraints] indexterm:[Constraints,Colocation,rsc] |with-rsc |The colocation target. The cluster will decide where to put this resource first and then decide where to put the resource in the +rsc+ field. indexterm:[with-rsc,Colocation Constraints] indexterm:[Constraints,Colocation,with-rsc] |score |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 \+/- +INFINITY+ change "should" to "must". indexterm:[score,Colocation Constraints] indexterm:[Constraints,Colocation,score] |========================================================= === Mandatory Placement === Mandatory placement occurs any time the constraint's score is ++INFINITY+ or +-INFINITY+. In such cases, if the constraint can't be satisfied, then the +rsc+ resource is not permitted to run. For +score=INFINITY+, this includes cases where the +with-rsc+ resource is not active. If you need +resource1+ to always run on the same machine as +resource2+, you would add the following constraint: .An example colocation constraint [source,XML] Remember, because +INFINITY+ was used, if +resource2+ can't run on any of the cluster nodes (for whatever reason) then +resource1+ will not be allowed to run. Alternatively, you may want the opposite... that +resource1+ cannot run on the same machine as +resource2+. In this case use +score="-INFINITY"+ .An example anti-colocation constraint [source,XML] Again, by specifying +-INFINTY+, the constraint is binding. So if the only place left to run is where +resource2+ already is, then +resource1+ may not run anywhere. === Advisory Placement === 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 +-INFINITY+ and less than +INFINITY+, the cluster will try and accommodate your wishes but may ignore them if the alternative is to stop some of the cluster resources. 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. .An example advisory-only colocation constraint [source,XML] [[s-resource-sets-ordering]] == Ordering Sets of Resources == A common situation is for an administrator to create a chain of ordered resources, such as: .A chain of ordered resources ====== [source,XML] ------- ------- ====== == Ordered Set == .Visual representation of the four resources' start order for the above constraints image::images/resource-set.png["Ordered set",width="16cm",height="2.5cm",align="center"] To simplify this situation, there is an alternate format for ordering constraints: .A chain of ordered resources expressed as a set ====== [source,XML] ------- ------- ====== [NOTE] Resource sets have the same ordering semantics as groups. .A group resource with the equivalent ordering rules ====== [source,XML] ------- ------- ====== 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, +rscA+ and +rscB+ can both start in parallel, as can +rscC+ and +rscD+, however +rscC+ and +rscD+ can only start once _both_ +rscA+ _and_ +rscB+ are active. .Ordered sets of unordered resources ====== [source,XML] ------- ------- ====== == Two Sets of Unordered Resources == .Visual representation of the start order for two ordered sets of unordered resources image::images/two-sets.png["Two ordered sets",width="13cm",height="7.5cm",align="center"] Of course either set -- or both sets -- of resources can also be internally ordered (by setting +sequential="true"+) and there is no limit to the number of sets that can be specified. .Advanced use of set ordering - Three ordered sets, two of which are internally unordered ====== [source,XML] ------- ------- ====== == Three Resources Sets == .Visual representation of the start order for the three sets defined above image::images/three-sets.png["Three ordered sets",width="16cm",height="7.5cm",align="center"] == Resource Set OR Logic == The unordered set logic discussed so far has all been "AND" logic. To illustrate this take the 3 resource set figure in the previous section. Those sets can be expressed, +(A and B) then (C) then (D) then (E and F)+ Say for example we want change the first set, (A and B), to use "OR" logic so the sets look like this, +(A or B) then (C) then (D) then (E and F)+. This functionality can be achieved through the use of the +require-all+ option. By default this option is 'require-all=true' which is why the "AND" logic is used by default. Changing +require-all=false+ means only one resource in the set needs to be started before continuing on to the next set. Note that the 'require-all=false' option only makes sense to use in conjunction with unordered sets, 'sequential=false'. Think of it like this, 'sequential=false' modifies the set to be an unordered set that uses "AND" logic by default, by adding 'require-all=false' the unordered set's "AND" logic is flipped to "OR" logic. .Resource Set "OR" logic. Three ordered sets, where the first set is internally unordered with "OR" logic. ====== [source,XML] ------- ------- ====== [[s-resource-sets-collocation]] == Collocating Sets of Resources == 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 <>) 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. .A chain of collocated resources ====== [source,XML] ------- ------- ====== To make things easier, we allow an alternate form of colocation constraints using +resource_sets+. 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 +B was+ not able to run, then both +C+ (and by inference +D+) must also remain stopped. .The equivalent colocation chain expressed using +resource_sets+ ====== [source,XML] ------- ------- ====== [NOTE] Resource sets have the same colocation semantics as groups. .A group resource with the equivalent colocation rules [source,XML] ------- ------- 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, +B would+ be allowed to remain active even if +A or+ +C+ (or both) were inactive. .Using colocation sets to specify a common peer. ====== [source,XML] ------- ------- ====== 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 +sequential="true"+, 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. .A colocation chain where the members of the middle set have no inter-dependencies and the last has master status. ====== [source,XML] ------- ------- ====== == Another Three Resources Sets == .Visual representation of a colocation chain where the members of the middle set have no inter-dependencies image::images/three-sets-complex.png["Colocation chain",width="16cm",height="9cm",align="center"] diff --git a/doc/Pacemaker_Explained/it-IT/Ch-Constraints.po b/doc/Pacemaker_Explained/it-IT/Ch-Constraints.po index 2358886a6f..e80d416ed1 100644 --- a/doc/Pacemaker_Explained/it-IT/Ch-Constraints.po +++ b/doc/Pacemaker_Explained/it-IT/Ch-Constraints.po @@ -1,856 +1,856 @@ # # AUTHOR , 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 \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 " ResourceConstraints Constraints " 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 "INFINITY is currently defined as 1,000,000 and addition/subtraction with it follows these three basic rules:" msgstr "INFINITY 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 + INFINITY = INFINITY" msgstr "Qualsiasi valore + INFINITY = INFINITY" #. Tag: para #, no-c-format msgid "Any value - INFINITY = -INFINITY" msgstr "Qualsiasi valore - INFINITY = -INFINITY" #. Tag: para #, no-c-format msgid "INFINITY - INFINITY = -INFINITY" msgstr "INFINITY - INFINITY = -INFINITY" #. 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 " Location Constraints ResourceConstraintsLocation ConstraintsLocation Location 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 "id" msgstr "" #. Tag: para #, no-c-format msgid "A unique name for the constraint idLocation Constraints Location Constraints ConstraintsLocationid Locationid id " msgstr "" #. Tag: para #, no-c-format msgid "rsc" msgstr "" #. Tag: para #, no-c-format msgid "A resource name rscLocation Constraints Location Constraints ConstraintsLocationrsc Locationrsc rsc " msgstr "" #. Tag: para #, no-c-format msgid "node" msgstr "" #. Tag: para #, no-c-format msgid "A node’s name nodeLocation Constraints Location Constraints ConstraintsLocationnode Locationnode node " msgstr "" #. Tag: para #, no-c-format msgid "score" 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 +/- INFINITY modificano "può" in "deve"." #. Tag: para #, no-c-format msgid "Values of +/- INFINITY change \"should\"/\"should not\" to \"must\"/\"must not\". scoreLocation Constraints Location Constraints ConstraintsLocationscore Locationscore score " msgstr "" #. Tag: title #, fuzzy, no-c-format msgid "Asymmetrical \"Opt-In\" Clusters" msgstr "Cluster "Opt-In" asimmetrici" #. Tag: para #, no-c-format msgid " Asymmetrical Opt-In Clusters Cluster TypeAsymmetrical Opt-In Asymmetrical Opt-In " 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 sles-1, the database prefers sles-2 and both can fail over to sles-3 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 " Symmetrical Opt-Out Clusters Cluster TypeSymmetrical Opt-Out Symmetrical Opt-Out " 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 " ResourceConstraintsOrdering ConstraintsOrdering Ordering ResourceStart Order Start Order Ordering Constraints The way to specify the order in which resources should start is by creating rsc_order 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 idOrdering Constraints Ordering Constraints ConstraintsOrderingid Orderingid id " msgstr "" #. Tag: para #, no-c-format msgid "first" msgstr "" #. Tag: para #, no-c-format msgid "The name of a resource that must be started before the then resource is allowed to. firstOrdering Constraints Ordering Constraints ConstraintsOrderingfirst Orderingfirst first " msgstr "" #. Tag: para #, no-c-format msgid "then" msgstr "" #. Tag: para #, no-c-format msgid "The name of a resource. This resource will start after the first resource. thenOrdering Constraints Ordering Constraints ConstraintsOrderingthen Orderingthen then " msgstr "" #. Tag: para #, no-c-format msgid "kind" msgstr "" #. Tag: para #, no-c-format msgid "How to enforce the constraint. (Since 1.1.2)" 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 first is stopping or cannot be started, then 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 " kindOrdering Constraints Ordering Constraints ConstraintsOrderingkind Orderingkind kind " msgstr "" #. Tag: para #, no-c-format msgid "symmetrical" msgstr "" #. Tag: para #, no-c-format msgid "If true, which is the default, stop the resources in the reverse order. Default value: true symmetricalOrdering Constraints Ordering Constraints Ordering Constraintssymmetrical symmetrical " msgstr "" #. Tag: title #, no-c-format msgid "Mandatory Ordering" msgstr "" #. Tag: para #, no-c-format msgid "When the then resource cannot run without the first 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 first resource was running and is stopped, the then resource will also be stopped (if it is running)." msgstr "" #. Tag: para #, no-c-format msgid "If the first resource was not running and cannot be started, the then resource will be stopped (if it is running)." msgstr "" #. Tag: para #, no-c-format msgid "If the first resource is (re)started while the then resource is running, the then 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 score=\"0\" 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 first resource will have no effect on the then 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 Ordering Explained." +msgid "Some additional information on ordering constraints can be found in the document Ordering Explained." msgstr "" #. Tag: title #, no-c-format msgid "Placing Resources Relative to other Resources" msgstr "" #. Tag: para #, no-c-format msgid " ResourceConstraintsColocation ConstraintsColocation Colocation ResourceLocation Relative to other Resources Location Relative to other Resources 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. 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. " 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 Colocation Explained 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. idColocation Constraints Colocation Constraints ConstraintsColocationid Colocationid id " 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. rscColocation Constraints Colocation Constraints ConstraintsColocationrsc Colocationrsc rsc " msgstr "" #. Tag: para #, no-c-format msgid "with-rsc" 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 rsc field. with-rscColocation Constraints Colocation Constraints ConstraintsColocationwith-rsc Colocationwith-rsc with-rsc " 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 +/- INFINITY change \"should\" to \"must\". scoreColocation Constraints Colocation Constraints ConstraintsColocationscore Colocationscore score " 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 +INFINITY or -INFINITY. In such cases, if the constraint can’t be satisfied, then the rsc resource is not permitted to run. For score=INFINITY, this includes cases where the with-rsc resource is not active." msgstr "" #. Tag: para #, no-c-format msgid "If you need resource1 to always run on the same machine as resource2, 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 INFINITY was used, if resource2 can’t run on any of the cluster nodes (for whatever reason) then resource1 will not be allowed to run." msgstr "" #. Tag: para #, no-c-format msgid "Alternatively, you may want the opposite… that resource1 cannot run on the same machine as resource2. In this case use score=\"-INFINITY\"" 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 -INFINTY, the constraint is binding. So if the only place left to run is where resource2 already is, then resource1 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 -INFINITY and less than INFINITY, 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, rscA and rscB can both start in parallel, as can rscC and rscD, however rscC and rscD can only start once both rscA and rscB 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 sequential=\"true\") 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 ) 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 resource_sets. 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 B was not able to run, then both C (+and by inference +D) must also remain stopped." msgstr "" #. Tag: title #, no-c-format msgid "The equivalent colocation chain expressed using resource_sets" 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, B would be allowed to remain active even if A or C (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 sequential=\"true\", 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" diff --git a/doc/Pacemaker_Explained/pot/Ch-Constraints.pot b/doc/Pacemaker_Explained/pot/Ch-Constraints.pot index 898c5e5174..8abc38fffe 100644 --- a/doc/Pacemaker_Explained/pot/Ch-Constraints.pot +++ b/doc/Pacemaker_Explained/pot/Ch-Constraints.pot @@ -1,822 +1,822 @@ # # AUTHOR , YEAR. # msgid "" msgstr "" "Project-Id-Version: 0\n" "POT-Creation-Date: 2012-10-17T05:19:02\n" "PO-Revision-Date: 2012-10-17T05:19:02\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 "Resource Constraints" msgstr "" #. Tag: para #, no-c-format msgid " ResourceConstraints Constraints " msgstr "" #. Tag: title #, no-c-format msgid "Scores" msgstr "" #. 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 "" #. Tag: para #, 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 "" #. Tag: title #, no-c-format msgid "Infinity Math" msgstr "" #. Tag: para #, no-c-format msgid "INFINITY is currently defined as 1,000,000 and addition/subtraction with it follows these three basic rules:" msgstr "" #. Tag: para #, no-c-format msgid "Any value + INFINITY = INFINITY" msgstr "" #. Tag: para #, no-c-format msgid "Any value - INFINITY = -INFINITY" msgstr "" #. Tag: para #, no-c-format msgid "INFINITY - INFINITY = -INFINITY" msgstr "" #. Tag: title #, no-c-format msgid "Deciding Which Nodes a Resource Can Run On" msgstr "" #. Tag: para #, no-c-format msgid " Location Constraints ResourceConstraintsLocation ConstraintsLocation Location 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 "" #. Tag: title #, no-c-format msgid "Options" msgstr "" #. Tag: title #, no-c-format msgid "Options for Simple Location Constraints" msgstr "" #. Tag: entry #, no-c-format msgid "Field" msgstr "" #. Tag: entry #, no-c-format msgid "Description" msgstr "" #. Tag: para #, no-c-format msgid "id" msgstr "" #. Tag: para #, no-c-format msgid "A unique name for the constraint idLocation Constraints Location Constraints ConstraintsLocationid Locationid id " msgstr "" #. Tag: para #, no-c-format msgid "rsc" msgstr "" #. Tag: para #, no-c-format msgid "A resource name rscLocation Constraints Location Constraints ConstraintsLocationrsc Locationrsc rsc " msgstr "" #. Tag: para #, no-c-format msgid "node" msgstr "" #. Tag: para #, no-c-format msgid "A node’s name nodeLocation Constraints Location Constraints ConstraintsLocationnode Locationnode node " msgstr "" #. Tag: para #, no-c-format msgid "score" msgstr "" #. Tag: para #, 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 "" #. Tag: para #, no-c-format msgid "Values of +/- INFINITY change \"should\"/\"should not\" to \"must\"/\"must not\". scoreLocation Constraints Location Constraints ConstraintsLocationscore Locationscore score " msgstr "" #. Tag: title #, no-c-format msgid "Asymmetrical \"Opt-In\" Clusters" msgstr "" #. Tag: para #, no-c-format msgid " Asymmetrical Opt-In Clusters Cluster TypeAsymmetrical Opt-In Asymmetrical Opt-In " 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 sles-1, the database prefers sles-2 and both can fail over to sles-3 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 #, no-c-format msgid "Symmetrical \"Opt-Out\" Clusters" msgstr "" #. Tag: para #, no-c-format msgid " Symmetrical Opt-Out Clusters Cluster TypeSymmetrical Opt-Out Symmetrical Opt-Out " 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 " ResourceConstraintsOrdering ConstraintsOrdering Ordering ResourceStart Order Start Order Ordering Constraints The way to specify the order in which resources should start is by creating rsc_order 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 idOrdering Constraints Ordering Constraints ConstraintsOrderingid Orderingid id " msgstr "" #. Tag: para #, no-c-format msgid "first" msgstr "" #. Tag: para #, no-c-format msgid "The name of a resource that must be started before the then resource is allowed to. firstOrdering Constraints Ordering Constraints ConstraintsOrderingfirst Orderingfirst first " msgstr "" #. Tag: para #, no-c-format msgid "then" msgstr "" #. Tag: para #, no-c-format msgid "The name of a resource. This resource will start after the first resource. thenOrdering Constraints Ordering Constraints ConstraintsOrderingthen Orderingthen then " msgstr "" #. Tag: para #, no-c-format msgid "kind" msgstr "" #. Tag: para #, no-c-format msgid "How to enforce the constraint. (Since 1.1.2)" 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 first is stopping or cannot be started, then 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 " kindOrdering Constraints Ordering Constraints ConstraintsOrderingkind Orderingkind kind " msgstr "" #. Tag: para #, no-c-format msgid "symmetrical" msgstr "" #. Tag: para #, no-c-format msgid "If true, which is the default, stop the resources in the reverse order. Default value: true symmetricalOrdering Constraints Ordering Constraints Ordering Constraintssymmetrical symmetrical " msgstr "" #. Tag: title #, no-c-format msgid "Mandatory Ordering" msgstr "" #. Tag: para #, no-c-format msgid "When the then resource cannot run without the first 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 first resource was running and is stopped, the then resource will also be stopped (if it is running)." msgstr "" #. Tag: para #, no-c-format msgid "If the first resource was not running and cannot be started, the then resource will be stopped (if it is running)." msgstr "" #. Tag: para #, no-c-format msgid "If the first resource is (re)started while the then resource is running, the then 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 score=\"0\" 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 first resource will have no effect on the then 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 Ordering Explained." +msgid "Some additional information on ordering constraints can be found in the document Ordering Explained." msgstr "" #. Tag: title #, no-c-format msgid "Placing Resources Relative to other Resources" msgstr "" #. Tag: para #, no-c-format msgid " ResourceConstraintsColocation ConstraintsColocation Colocation ResourceLocation Relative to other Resources Location Relative to other Resources 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. 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. " 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 Colocation Explained 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. idColocation Constraints Colocation Constraints ConstraintsColocationid Colocationid id " 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. rscColocation Constraints Colocation Constraints ConstraintsColocationrsc Colocationrsc rsc " msgstr "" #. Tag: para #, no-c-format msgid "with-rsc" 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 rsc field. with-rscColocation Constraints Colocation Constraints ConstraintsColocationwith-rsc Colocationwith-rsc with-rsc " 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 +/- INFINITY change \"should\" to \"must\". scoreColocation Constraints Colocation Constraints ConstraintsColocationscore Colocationscore score " 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 +INFINITY or -INFINITY. In such cases, if the constraint can’t be satisfied, then the rsc resource is not permitted to run. For score=INFINITY, this includes cases where the with-rsc resource is not active." msgstr "" #. Tag: para #, no-c-format msgid "If you need resource1 to always run on the same machine as resource2, 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 INFINITY was used, if resource2 can’t run on any of the cluster nodes (for whatever reason) then resource1 will not be allowed to run." msgstr "" #. Tag: para #, no-c-format msgid "Alternatively, you may want the opposite… that resource1 cannot run on the same machine as resource2. In this case use score=\"-INFINITY\"" 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 -INFINTY, the constraint is binding. So if the only place left to run is where resource2 already is, then resource1 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 -INFINITY and less than INFINITY, 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, rscA and rscB can both start in parallel, as can rscC and rscD, however rscC and rscD can only start once both rscA and rscB 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 sequential=\"true\") 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 ) 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 resource_sets. 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 B was not able to run, then both C (+and by inference +D) must also remain stopped." msgstr "" #. Tag: title #, no-c-format msgid "The equivalent colocation chain expressed using resource_sets" 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, B would be allowed to remain active even if A or C (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 sequential=\"true\", 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 "" diff --git a/doc/Pacemaker_Explained/ro-RO/Ch-Constraints.po b/doc/Pacemaker_Explained/ro-RO/Ch-Constraints.po index f2c34e16c1..5cd5af1945 100644 --- a/doc/Pacemaker_Explained/ro-RO/Ch-Constraints.po +++ b/doc/Pacemaker_Explained/ro-RO/Ch-Constraints.po @@ -1,1030 +1,1030 @@ msgid "" msgstr "" "Project-Id-Version: Pacemaker 1.1\n" "POT-Creation-Date: 2012-10-17T05:19:02\n" "PO-Revision-Date: 2012-01-01T17:48:32\n" "Last-Translator: Dan Frîncu \n" "Language-Team: None\n" "Language: \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 "Resource Constraints" msgstr "Restricţiile Resurselor" #. Tag: para #, fuzzy, no-c-format msgid " ResourceConstraints Constraints " msgstr "scorCâmp de Restricție Constraint Fieldscor scor" #. Tag: title #, no-c-format msgid "Scores" msgstr "Scoruri" #. 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 "Scorurile de toate tipurile sunt parte integrală din cum funcţionează clusterul. Practic orice de la mutarea unei resurse la a decide care resursă să fie oprită într-un cluster degradat este atinsă prin manipularea scorurilor în vreun fel." #. 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 "Scorurile sunt calculate la nivel de resursă şi orice nod cu un scor negativ pentru o resursă nu poate rula acea resursă. După calcularea scorurilor pentru o resursă, clusterul alege mai apoi nodul cu scorul cel mai mare." #. Tag: title #, no-c-format msgid "Infinity Math" msgstr "Matematica Infinitului" #. Tag: para #, no-c-format msgid "INFINITY is currently defined as 1,000,000 and addition/subtraction with it follows these three basic rules:" msgstr "INFINITY este definit în mod curent ca 1,000,000 şi adunarea/scăderea din acesta urmează următoarele 3 reguli de bază:" #. Tag: para #, no-c-format msgid "Any value + INFINITY = INFINITY" msgstr "Orice valoare + INFINITY = INFINITY " #. Tag: para #, no-c-format msgid "Any value - INFINITY = -INFINITY" msgstr "Orice valoare - INFINITY = -INFINITY" #. Tag: para #, no-c-format msgid "INFINITY - INFINITY = -INFINITY" msgstr "INFINITY - INFINITY = -INFINITY" #. Tag: title #, no-c-format msgid "Deciding Which Nodes a Resource Can Run On" msgstr "Decizând pe Care Noduri Poate Rula o Resursă" #. Tag: para #, fuzzy, no-c-format msgid " Location Constraints ResourceConstraintsLocation ConstraintsLocation Location 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 "Sunt două strategii alternative pentru specificarea nodurilor pe care poate rula o resursă. Un mod este acela de a spune că în mod implicit acestea pot rula oriunde şi apoi să se creeze restricţii de locaţie pentru nodurile pe care acestea nu sunt permise. Cealaltă opţiune este cea de a avea noduri care să \"opt-in\"... de a porni fără a permite la nimic de a rula nicăieri şi de a activa în mod selectiv nodurile permise." #. Tag: title #, no-c-format msgid "Options" msgstr "Opţiuni" #. Tag: title #, no-c-format msgid "Options for Simple Location Constraints" msgstr "Opţiuni pentru Restricţii Simple de Locaţie" #. Tag: entry #, no-c-format msgid "Field" msgstr "Câmp" #. Tag: entry #, no-c-format msgid "Description" msgstr "Descriere" #. Tag: para #, no-c-format msgid "id" msgstr "" #. Tag: para #, no-c-format msgid "A unique name for the constraint idLocation Constraints Location Constraints ConstraintsLocationid Locationid id " msgstr "" #. Tag: para #, no-c-format msgid "rsc" msgstr "" #. Tag: para #, no-c-format msgid "A resource name rscLocation Constraints Location Constraints ConstraintsLocationrsc Locationrsc rsc " msgstr "" #. Tag: para #, no-c-format msgid "node" msgstr "" #. Tag: para #, no-c-format msgid "A node’s name nodeLocation Constraints Location Constraints ConstraintsLocationnode Locationnode node " msgstr "" #. Tag: para #, no-c-format msgid "score" 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 "Valorile pozitive indică faptul că resursa ar trebui să ruleze pe acelaşi nod. Valorile negative indică faptul că resursele ar trebui să nu ruleze pe acelaşi nod. Valorile +/- INFINITY schimbâ \"ar trebui\" în \"trebuie\"." #. Tag: para #, no-c-format msgid "Values of +/- INFINITY change \"should\"/\"should not\" to \"must\"/\"must not\". scoreLocation Constraints Location Constraints ConstraintsLocationscore Locationscore score " msgstr "" #. Tag: title #, no-c-format msgid "Asymmetrical \"Opt-In\" Clusters" msgstr "" #. Tag: para #, fuzzy, no-c-format msgid " Asymmetrical Opt-In Clusters Cluster TypeAsymmetrical Opt-In Asymmetrical Opt-In " msgstr "Clustere Opt-In Asimetrice Tip de ClusterOpt-In Asimetric Clustere \"Opt-In\" Asimetrice" #. Tag: para #, no-c-format msgid "To create an opt-in cluster, start by preventing resources from running anywhere by default:" msgstr "Pentru a crea un cluster opt-in, porniţi prin a împiedica resursele din a rula oriunde în mod implicit:" #. Tag: programlisting #, fuzzy, no-c-format msgid "# crm_attribute --attr-name symmetric-cluster --attr-value false" msgstr "crm_attribute --attr-name symmetric-cluster --attr-value false" #. Tag: para #, no-c-format msgid "Then start enabling nodes. The following fragment says that the web server prefers sles-1, the database prefers sles-2 and both can fail over to sles-3 if their most preferred node fails." msgstr "Apoi începeţi să activaţi noduri. Fragmentul următor spune că serverul web preferă sles-1, baza de date preferă sles-2 şi ambele pot face failover pe sles-3 dacă nodul lor cu cea mai mare preferinţă eşuează." #. Tag: title #, no-c-format msgid "Example set of opt-in location constraints" msgstr "Exemplu de restricţii de locaţie opt-in" #. Tag: programlisting #, fuzzy, 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 "" "<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> " #. Tag: title #, no-c-format msgid "Symmetrical \"Opt-Out\" Clusters" msgstr "" #. Tag: para #, fuzzy, no-c-format msgid " Symmetrical Opt-Out Clusters Cluster TypeSymmetrical Opt-Out Symmetrical Opt-Out " msgstr "Clustere Opt-Out Simetrice Tip de ClusterOpt-Out Simetrice Clustere \"Opt-Out\" Simetrice" #. Tag: para #, fuzzy, no-c-format msgid "To create an opt-out cluster, start by allowing resources to run anywhere by default:" msgstr "Pentru a crea un cluster opt-out, începeţi prin a permite resurselor să ruleze oriunde în mod implicit" #. Tag: programlisting #, fuzzy, no-c-format msgid "# crm_attribute --attr-name symmetric-cluster --attr-value true" msgstr "crm_attribute --attr-name symmetric-cluster --attr-value true" #. Tag: para #, no-c-format msgid "Then start disabling nodes. The following fragment is the equivalent of the above opt-in configuration." msgstr "Apoi începeţi să dezactivaţi noduri. Următorul fragment este echivalentul configuraţiei opt-in de mai sus." #. Tag: title #, no-c-format msgid "Example set of opt-out location constraints" msgstr "Exemplu de restricţii de locaţie opt-out" #. Tag: programlisting #, fuzzy, 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 "" " <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> " #. 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 "Fie că ar trebui să alegeţi opt-in sau opt-out depinde atât de preferinţele voastre personale cât şi de structura clusterului vostru. Dacă majoritatea resurselor pot rula pe majoritatea nodurilor, atunci un aranjament opt-out va rezulta într-o configuraţie mai simplă. Pe partea cealaltă, dacă majoritatea resurselor pot rula doar pe un subset mic de noduri o configuraţie opt-in ar putea fi mai simplă." #. Tag: title #, no-c-format msgid "What if Two Nodes Have the Same Score" msgstr "Dacă Două Noduri Au Acelaşi Scor" #. 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 "Dacă două noduri au acelaşi scor, atunci clusterul va alege unul. Această alegere poate părea aleatorie şi ar putea să nu fie ceea ce s-a intenţionat, în schimb clusterului nu i-a fost dată suficientă informaţie pentru a şti care a fost intenţia." #. Tag: title #, no-c-format msgid "Example of two resources that prefer two nodes equally" msgstr "Exemplu de două resurse care preferă două noduri în mod egal" #. Tag: programlisting #, fuzzy, 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 "" " <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> " #. Tag: para #, fuzzy, 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 "În exemplul de mai sus, mergând pe presupunerea că nu sunt alte restricţii şi un cluster inactiv, Webserver ar fi probabil plasat pe sles-1 şi Database pe sles-2. Este probabil să fi plasat Webserver pe baza uname-ului nodului şi Database bazat pe dorinţa de a împrăştia încărcarea cu resurse în mod egal de-a lungul clusterului. Totuşi alţi factori pot fi implicaţi de asemenea în configuraţii mai complexe." #. Tag: title #, no-c-format msgid "Specifying in which Order Resources Should Start/Stop" msgstr "Specificând Ordinea în care Resursele ar Trebui să Pornească/Oprească" #. Tag: para #, no-c-format msgid " ResourceConstraintsOrdering ConstraintsOrdering Ordering ResourceStart Order Start Order Ordering Constraints The way to specify the order in which resources should start is by creating rsc_order constraints." msgstr "" #. Tag: title #, no-c-format msgid "Properties of an Ordering Constraint" msgstr "Proprietăţile unei Restricţii de Ordonare" #. Tag: para #, no-c-format msgid "A unique name for the constraint idOrdering Constraints Ordering Constraints ConstraintsOrderingid Orderingid id " msgstr "" #. Tag: para #, no-c-format msgid "first" msgstr "" #. Tag: para #, no-c-format msgid "The name of a resource that must be started before the then resource is allowed to. firstOrdering Constraints Ordering Constraints ConstraintsOrderingfirst Orderingfirst first " msgstr "" #. Tag: para #, no-c-format msgid "then" msgstr "" #. Tag: para #, no-c-format msgid "The name of a resource. This resource will start after the first resource. thenOrdering Constraints Ordering Constraints ConstraintsOrderingthen Orderingthen then " msgstr "" #. Tag: para #, no-c-format msgid "kind" msgstr "" #. Tag: para #, no-c-format msgid "How to enforce the constraint. (Since 1.1.2)" 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 first is stopping or cannot be started, then 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 " kindOrdering Constraints Ordering Constraints ConstraintsOrderingkind Orderingkind kind " msgstr "" #. Tag: para #, no-c-format msgid "symmetrical" msgstr "" #. Tag: para #, no-c-format msgid "If true, which is the default, stop the resources in the reverse order. Default value: true symmetricalOrdering Constraints Ordering Constraints Ordering Constraintssymmetrical symmetrical " msgstr "" #. Tag: title #, no-c-format msgid "Mandatory Ordering" msgstr "Ordonarea Obligatorie" #. Tag: para #, no-c-format msgid "When the then resource cannot run without the first 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 "Când resursa then nu poate rula fără ca resursa first să fie activă, ar trebui să folosiţi restricţii obligatorii. Pentru a specifica faptul că o restricţie este obligatorie, folosiţi scoruri mai mari decât zero. Acest lucru va asigura că resursa \"then\" va reacţiona atunci când resursa \"first\" îşi schimbă starea." #. Tag: para #, no-c-format msgid "If the first resource was running and is stopped, the then resource will also be stopped (if it is running)." msgstr "Dacâ resursa first rula şi este oprită, resursa then va fi oprită de asemenea (dacă rulează)" #. Tag: para #, no-c-format msgid "If the first resource was not running and cannot be started, the then resource will be stopped (if it is running)." msgstr "Dacă resursa first nu rula şi nu poate fi pornită, resursa then va fi oprită (dacă rulează)" #. Tag: para #, no-c-format msgid "If the first resource is (re)started while the then resource is running, the then resource will be stopped and restarted." msgstr "Dacă resursa first este (re)pornită în timp ce resursa then rulează, resursa then va fi oprită şi repornită" #. Tag: title #, no-c-format msgid "Advisory Ordering" msgstr "Ordonare Recomandată" #. Tag: para #, no-c-format msgid "On the other hand, when score=\"0\" 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 first resource will have no effect on the then resource." msgstr "Pe altă parte, când score=\"0\" este specificat pentru o restricţie, restricţia este considerată opţională şi are efect doar când ambele resurse sunt oprite sau pornite. Orice modificare a stării resursei first nu va avea nici un efect asupra resursei then." #. Tag: title #, no-c-format msgid "Example of an optional and mandatory ordering constraint" msgstr "Exemplu de restricţie de ordonare obligatorie şi recomandată" #. Tag: programlisting #, fuzzy, 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 "" " <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> " #. Tag: para #, no-c-format -msgid "Some additional information on ordering constraints can be found in the document Ordering Explained." -msgstr "Informaţii adiţionale despre restricţiile de ordonare pot fi găsite în documentul Ordonarea Explicată" +msgid "Some additional information on ordering constraints can be found in the document Ordering Explained." +msgstr "Informaţii adiţionale despre restricţiile de ordonare pot fi găsite în documentul Ordonarea Explicată" #. Tag: title #, no-c-format msgid "Placing Resources Relative to other Resources" msgstr "Plasarea Resurselor Relativă la alte Resurse" #. Tag: para #, no-c-format msgid " ResourceConstraintsColocation ConstraintsColocation Colocation ResourceLocation Relative to other Resources Location Relative to other Resources When the location of one resource depends on the location of another one, we call this colocation." msgstr "" #. Tag: para #, fuzzy, 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. 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. " msgstr "Există un efect secundar important ca urmare a creării unei restricţii de colocare între două resurse, şi anume acela că afectează ordinea în care resursele sunt asignate unui nod. Dacă stai să te gândeşti, este oarecum evident. Nu poţi plasa A relativ la B decât dacă ştii unde B este În timp ce creierul uman este destul de sofisticat pentru a citi o restricţie în orice ordine şi de a alege pe cea corectă în funcţie de situaţie, clusterul nu este atât de inteligent. Încă. . Aşa că atunci când creaţi restricţii de colocare, este important să ţineţi cont de dacă vreţi să colocaţi A cu B sau B cu A." #. 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 #, fuzzy, 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 "Un alt aspect care merită reţinut este acela că, presupunând că A este colocat cu B, clusterul va lua în considerare preferinţele lui A când va decide care nod să aleagă pentru B. Pentru o vedere detaliată asupra modului exact în care se întâmplă acest lucru, vedeţi documentul Colocarea Explicată." #. Tag: para #, fuzzy, no-c-format msgid "For a detailed look at exactly how this occurs, see the Colocation Explained document." msgstr "Un alt aspect care merită reţinut este acela că, presupunând că A este colocat cu B, clusterul va lua în considerare preferinţele lui A când va decide care nod să aleagă pentru B. Pentru o vedere detaliată asupra modului exact în care se întâmplă acest lucru, vedeţi documentul Colocarea Explicată." #. Tag: title #, no-c-format msgid "Properties of a Collocation Constraint" msgstr "Proprietăţile unei Restricţii de Colocare" #. Tag: para #, no-c-format msgid "A unique name for the constraint. idColocation Constraints Colocation Constraints ConstraintsColocationid Colocationid id " 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. rscColocation Constraints Colocation Constraints ConstraintsColocationrsc Colocationrsc rsc " msgstr "" #. Tag: para #, no-c-format msgid "with-rsc" 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 rsc field. with-rscColocation Constraints Colocation Constraints ConstraintsColocationwith-rsc Colocationwith-rsc with-rsc " 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 +/- INFINITY change \"should\" to \"must\". scoreColocation Constraints Colocation Constraints ConstraintsColocationscore Colocationscore score " msgstr "" #. Tag: title #, no-c-format msgid "Mandatory Placement" msgstr "Plasament Obligatoriu" #. Tag: para #, fuzzy, no-c-format msgid "Mandatory placement occurs any time the constraint’s score is +INFINITY or -INFINITY. In such cases, if the constraint can’t be satisfied, then the rsc resource is not permitted to run. For score=INFINITY, this includes cases where the with-rsc resource is not active." msgstr "Plasamentul obligatoriu se întâmplă oricând scorul restricţiei este +INFINITY sau -INFINITY. În astfel de cazuri, dacă restricţia poate fi satisfăcută, atunci resursei rsc nu îi este permis să ruleze. Pentru scor=INFINITY, acest aspect include cazuri în care resursa with-rsc nu este activă." #. Tag: para #, no-c-format msgid "If you need resource1 to always run on the same machine as resource2, you would add the following constraint:" msgstr "Dacă aveţi nevoie ca resource1 să ruleze întotdeauna pe aceeaşi maşină ca şi resource2, aţi adăuga următoarea restricţie:" #. Tag: title #, no-c-format msgid "An example colocation constraint" msgstr "Un exemplu de restricţie de colocare" #. Tag: programlisting #, fuzzy, no-c-format msgid "<rsc_colocation id=\"colocate\" rsc=\"resource1\" with-rsc=\"resource2\" score=\"INFINITY\"/>" msgstr "" " <rsc_colocation id=\"colocate\" rsc=\"resource1\" with-rsc=\"resource2\" score=\"INFINITY\"/>\n" "\t " #. Tag: para #, fuzzy, no-c-format msgid "Remember, because INFINITY was used, if resource2 can’t run on any of the cluster nodes (for whatever reason) then resource1 will not be allowed to run." msgstr "Ţineţi minte, datorită faptului că INFINITY a fost folosit, dacă resource2 nu poate rula pe nici unul din nodurile clusterului (indiferent de motiv) atunci resource1 nu îi va fi permis să ruleze." #. Tag: para #, fuzzy, no-c-format msgid "Alternatively, you may want the opposite… that resource1 cannot run on the same machine as resource2. In this case use score=\"-INFINITY\"" msgstr "Alternativ, aţi putea dori opusul... ca resource1 să nu poată rula pe aceeaşi maşină ca resource2. În acest caz folosiţi scor=\"-INFINITY\"" #. Tag: title #, no-c-format msgid "An example anti-colocation constraint" msgstr "Un exemplu de restricţie anti-colocare" #. Tag: programlisting #, fuzzy, no-c-format msgid "<rsc_colocation id=\"anti-colocate\" rsc=\"resource1\" with-rsc=\"resource2\" score=\"-INFINITY\"/>" msgstr "" "<rsc_colocation id=\"anti-colocate\"\n" " rsc=\"resource1\" with-rsc=\"resource2\" score=\"-INFINITY\"/> \n" "\t " #. Tag: para #, no-c-format msgid "Again, by specifying -INFINTY, the constraint is binding. So if the only place left to run is where resource2 already is, then resource1 may not run anywhere." msgstr "Din nou, specificând -INFINTY, restricţia este imutabilă. Deci singurul loc rămas pentru a rula este cel unde resource2 este deja, atunci resource1 nu poate rula nicăieri." #. Tag: title #, no-c-format msgid "Advisory Placement" msgstr "Plasament Recomandat" #. Tag: para #, fuzzy, 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 -INFINITY and less than INFINITY, the cluster will try and accommodate your wishes but may ignore them if the alternative is to stop some of the cluster resources." msgstr "Dacă plasamentul obligatoriu se referă la \"trebuie\" şi \"nu trebuie\", atunci plasamentul recomandat este alternativa \"aş prefera dacă\". Pentru restricţii cu scoruri mai mari decât -INFINITY şi mai mici decât INFINITY, clusterul va încerca să acomodeze dorinţele voastre dar le-ar putea ignora dacă alternativa este să oprească unele din resursele clusterului." #. 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 "Ca şi în viaţă, unde dacă destule persoane preferă ceva acest lucru devine obligatoriu, restricţiile de colocare recomandate se pot combina cu alte elemente ale configuraţiei pentru a se comporta ca şi cum ar fi obligatorii." #. Tag: title #, no-c-format msgid "An example advisory-only colocation constraint" msgstr "Un exemplu de restricţie de colocare doar recomandată" #. Tag: programlisting #, fuzzy, no-c-format msgid "<rsc_colocation id=\"colocate-maybe\" rsc=\"resource1\" with-rsc=\"resource2\" score=\"500\"/>" msgstr "" "<rsc_colocation id=\"colocate-maybe\" rsc=\"resource1\" with-rsc=\"resource2\" score=\"500\"/>\n" "\t " #. Tag: title #, no-c-format msgid "Ordering Sets of Resources" msgstr "Ordonarea Seturilor de Resurse" #. Tag: para #, no-c-format msgid "A common situation is for an administrator to create a chain of ordered resources, such as:" msgstr "O situaţie comună este ca un administrator să creeze un lanţ de resurse ordonate, precum:" #. Tag: title #, no-c-format msgid "A chain of ordered resources" msgstr "Un lanţ de resurse ordonate" #. Tag: programlisting #, fuzzy, 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 "" " <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> " #. Tag: title #, no-c-format msgid "Ordered Set" msgstr "Set Ordonat" #. Tag: title #, no-c-format msgid "Visual representation of the four resources' start order for the above constraints" msgstr "Reprezentarea vizuală a ordinii de pornire a celor patru resurse pentru restricţiile de mai sus" #. Tag: phrase #, fuzzy, no-c-format msgid "Ordered set" msgstr "Set Ordonat" #. Tag: para #, no-c-format msgid "To simplify this situation, there is an alternate format for ordering constraints:" msgstr "Pentru a simplifica această situaţie, există un format alternativ pentru ordonarea restricţiilor" #. Tag: title #, no-c-format msgid "A chain of ordered resources expressed as a set" msgstr "Un lanţ de resurse ordonate exprimate ca un set" #. Tag: programlisting #, fuzzy, 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 "" " <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> " #. Tag: para #, no-c-format msgid "Resource sets have the same ordering semantics as groups." msgstr "Seturile de resurse au aceeaşi semantică de ordonare ca şi grupurile." #. Tag: title #, no-c-format msgid "A group resource with the equivalent ordering rules" msgstr "Un grup de resurse cu regulile de ordonare echivalente" #. Tag: programlisting #, fuzzy, 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 "" " <group id=\"dummy\">\n" " <primitive id=\"A\" .../>\n" " <primitive id=\"B\" .../>\n" " <primitive id=\"C\" .../>\n" " <primitive id=\"D\" .../>\n" " </group> " #. 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, rscA and rscB can both start in parallel, as can rscC and rscD, however rscC and rscD can only start once both rscA and rscB are active." msgstr "În timp ce formatul bazat pe seturi nu este mai puţin verbose, este semnificativ mai uşor de a nimeri şi menţine. Poate fi extins pentru a permite seturi ordonate de resurse (ne)ordonate. În exemplul de mai jos, rscA şi rscB pot porni ambele în paralel, la fel pot si rscC şi rscD, însă rscC şi rscD pot porni doar odată ce ambele rscA şi rscB sunt active." #. Tag: title #, no-c-format msgid "Ordered sets of unordered resources" msgstr "Seturi ordonate de resurse neordonate" #. Tag: programlisting #, fuzzy, 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 "" " <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> " #. Tag: title #, no-c-format msgid "Two Sets of Unordered Resources" msgstr "Două Seturi de Resurse Neordonate" #. Tag: title #, no-c-format msgid "Visual representation of the start order for two ordered sets of unordered resources" msgstr "Reprezentarea vizuală a ordinii de pornire pentru două seturi de resurse neordonate" #. Tag: phrase #, fuzzy, no-c-format msgid "Two ordered sets" msgstr "Set Ordonat" #. Tag: para #, fuzzy, no-c-format msgid "Of course either set — or both sets — of resources can also be internally ordered (by setting sequential=\"true\") and there is no limit to the number of sets that can be specified." msgstr "Desigur că oricare set -- sau ambele seturi -- de resurse pot de asemenea să fie ordonate intern (prin setarea sequential=\"true\") şi nu este nici o limită asupra numărului de seturi care poate fi specificat." #. Tag: title #, no-c-format msgid "Advanced use of set ordering - Three ordered sets, two of which are internally unordered" msgstr "Utilizări avansate ale ordonării seturilor - Trei seturi ordonate, două din care sunt neordonate intern" #. Tag: programlisting #, fuzzy, 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 "" " <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> " #. Tag: title #, no-c-format msgid "Three Resources Sets" msgstr "Trei Seturi de Resurse" #. Tag: title #, no-c-format msgid "Visual representation of the start order for the three sets defined above" msgstr "Reprezentarea vizuală a ordinii de pornire pentru cele trei seturi definite mai sus" #. Tag: phrase #, fuzzy, no-c-format msgid "Three ordered sets" msgstr "Trei Seturi de Resurse" #. Tag: title #, no-c-format msgid "Collocating Sets of Resources" msgstr "Colocarea Seturilor de Resurse" #. 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 ) 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 "O altă situaţie comună este ca un administrator să creeze un set de resurse colocate. Anterior acest lucru era posibil fie prin definirea unui grup de resurse (Vedeţi ) care nu putea întotdeauna să exprime designul în mod corect; sau prin definirea fiecărei relaţii ca o restricţie individuală, cauzând o explozie de restricţii pe măsură ce numărul resurselor şi al combinaţiilor creştea." #. Tag: title #, no-c-format msgid "A chain of collocated resources" msgstr "Un lanţ de resurse colocate" #. Tag: programlisting #, fuzzy, 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 "" " <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> " #. Tag: para #, fuzzy, no-c-format msgid "To make things easier, we allow an alternate form of colocation constraints using resource_sets. 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 B was not able to run, then both C (+and by inference +D) must also remain stopped." msgstr "Pentru a face lucrurile mai uşoare, permitem o altă formă de restricţii de colocare folosind resource_sets (seturi de resurse). La fel ca şi versiunea extinsă, o resursă care nu poate fi activă împiedică de asemenea orice resursă care trebuie colocată cu aceasta de a fi activă. De exemplu dacă B nu era capabil să ruleze, atunci atât C (şi prin alianţă D) trebuie să rămână oprite." #. Tag: title #, no-c-format msgid "The equivalent colocation chain expressed using resource_sets" msgstr "Lanţul echivalent de restricţii de colocare exprimat folosind resource_sets" #. Tag: programlisting #, fuzzy, 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 "" " <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> " #. Tag: para #, no-c-format msgid "Resource sets have the same colocation semantics as groups." msgstr "Seturile de resurse au aceleaşi restricţii semantice ca şi grupurile." #. Tag: title #, no-c-format msgid "A group resource with the equivalent colocation rules" msgstr "O resursă de grup cu regulile echivalente de colocare" #. Tag: para #, fuzzy, 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, B would be allowed to remain active even if A or C (or both) were inactive." msgstr "Această notaţie poate fi folosită de asemenea în acest context pentru a spune clusterului că un set de resurse trebuie să fie toate amplasate pe un nod comun, dar că nu au dependinţe unele de altele. În acest scenariu, contrar faţă de cel anterior, lui B i-ar fi permis să rămână activă chiar dacă A sau C (sau ambele) ar fi fost inactive." #. Tag: title #, no-c-format msgid "Using colocation sets to specify a common peer." msgstr "Folosirea seturilor de colocare pentru a specifica un nod comun." #. Tag: programlisting #, fuzzy, 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 "" " <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> " #. Tag: para #, fuzzy, 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 sequential=\"true\", 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 "Desigur nu există nici o limită asupra numărului şi mărimii seturilor folosite. Singurul lucru care contează este ca pentru orice membru al setului N să fie activ, toţi membrii setului N+1 trebuie să fie activi de asemenea (şi evident pe acelaşi nod) şi dacă un set are sequential=\"true\", atunci pentru ca membrul M să fie activ, membrul M+1 trebuie să fie activ de asemenea. Puteţi specifica chiar rolul în care membrii unui set trebuie să fie folosind atributele de rol ale setului." #. 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 "Un lanţ de colocare unde membrii setului mijlociu nu au interdependenţe şi ultimul are statusul de master." #. Tag: programlisting #, fuzzy, 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 "" " <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> " #. Tag: title #, no-c-format msgid "Another Three Resources Sets" msgstr "Încă Trei Seturi de Resurse" #. Tag: title #, no-c-format msgid "Visual representation of a colocation chain where the members of the middle set have no inter-dependencies" msgstr "Reprezentarea vizuală a unui lanţ de colocare unde membrii setului mijlociu nu au interdependenţe" #. Tag: phrase #, no-c-format msgid "Colocation chain" msgstr "" #~ msgid "ResourceConstraints" #~ msgstr "RestricțiileResurselor" #~ msgid "Constraintsfor Resources" #~ msgstr "Restricțiipentru Resurse" #~ msgid "idConstraint Field Constraint Fieldid entry>id" #~ msgstr "idCâmp de Restricție Câmp de Restricțieid entry>id" #~ msgid "A unique name for the constraint" #~ msgstr "Un nume unic pentru restricţie" #~ msgid "rsc Constraint Field Constraint Fieldrsc rsc" #~ msgstr "rsc Câmp de Restricție Constraint Fieldrsc rsc" #~ msgid "A resource name" #~ msgstr "Un nume de resursă" #~ msgid "NodeConstraint Field Constraint Fieldnode node" #~ msgstr "NodCâmp de Restricție Constraint Fieldnod nod" #~ msgid "A node's uname" #~ msgstr "uname-ul unui nod" #~ msgid "Positive values indicate the resource should run on this node. Negative values indicate the resource should not run on this node. Values of +/- INFINITY change \"should\"/\"should not\" to \"must\"/\"must not\"." #~ msgstr "Valorile pozitive indică faptul că resursa ar trebui să ruleze pe acelaşi nod. Valorile negative indică faptul că resursele ar trebui să nu ruleze pe acelaşi nod. Valorile +/- INFINITY schimbă \"ar putea\"/\"nu ar putea\" în \"trebuie\"/\"nu trebuie\"." #~ msgid "The way to specify the order in which resources should start is by creating rsc_order constraints." #~ msgstr "Modul în care se poate specifica ordinea în care resursele ar trebui să pornească este prin crearea de restricţii rsc_order" #~ msgid "id" #~ msgstr "id" #~ msgid "first" #~ msgstr "first" #~ msgid "The name of a resource that must be started before the then resource is allowed to." #~ msgstr "Numele unei resurse care trebuie pornită înainte de a îi permite resursei then să pornească" #~ msgid "then" #~ msgstr "then" #~ msgid "The name of a resource. This resource will start after the first resource." #~ msgstr "Numele unei resurse. Această resursă va porni după resursa first." #~ msgid "score" #~ msgstr "scor" #~ msgid "If greater than zero, the constraint is mandatory. Otherwise it is only a suggestion. Default value: INFINITY" #~ msgstr "Dacă este mai mare decât zero, restricţia este obligatorie. Altfel este doar o sugestie. Valoarea implicită: INFINITY" #~ msgid "symmetrical" #~ msgstr "simetric" #~ msgid "If true, which is the default, stop the resources in the reverse order. Default value: true" #~ msgstr "Dacă este adevărat, care este şi valoarea implicită, opreşte resursele în ordine inversă. Valoarea implicită: true" #~ msgid "When the location of one resource depends on the location of another one, we call this colocation." #~ msgstr "Când locaţia unei resurse depinde de locaţia altei resurse, numim acest lucru colocare." #~ msgid "A unique name for the constraint." #~ msgstr "Un nume unic pentru restricţie" #~ msgid "rsc" #~ msgstr "rsc" #~ msgid "The colocation source. If the constraint cannot be satisfied, the cluster may decide not to allow the resource to run at all." #~ msgstr "Sursa colocării. Dacă restricţia nu poate fi satisfăcută, clusterul poate decide să nu permită resursei să ruleze deloc." #~ msgid "with-rsc" #~ msgstr "with-rsc" #~ msgid "The colocation target. The cluster will decide where to put this resource first and then decide where to put the resource in the rsc field." #~ msgstr "Destinaţia colocării. Clusterul va decide unde să plaseze această resursă mai întâi şi apoi va decide unde să plaseze resursa din câmpul rsc"