The tool uses the same library as the live cluster to show what it
would have done given the supplied input. It's output, in addition to
a significant amount of logging, is stored in two files +tmp.graph+
and +tmp.dot+, both are representations of the same thing -- the
cluster's response to your changes.
In the graph file is stored the complete transition, containing a list
of all the actions, their parameters and their pre-requisites.
Because the transition graph is not terribly easy to read, the tool
also generates a Graphviz dot-file representing the same information.
== Interpreting the Graphviz output ==
* Arrows indicate ordering dependencies
* Dashed-arrows indicate dependencies that are not present in the transition graph
* Actions with a dashed border of any color do not form part of the transition graph
* Actions with a green border form part of the transition graph
* Actions with a red border are ones the cluster would like to execute but cannot run
* Actions with a blue border are ones the cluster does not feel need to be executed
* Actions with orange text are pseudo/pretend actions that the cluster uses to simplify the graph
* Actions with black text are sent to the LRM
* Resource actions have text of the form pass:[<replaceable>rsc</replaceable>]_pass:[<replaceable>action</replaceable>]_pass:[<replaceable>interval</replaceable>] pass:[<replaceable>node</replaceable>]
* Any action depending on an action with a red border will not be able to execute.
* Loops are _really_ bad. Please report them to the development team.
=== Small Cluster Transition ===
image::images/Policy-Engine-small.png["An example transition graph as represented by Graphviz",width="16cm",height="6cm",align="center"]
In the above example, it appears that a new node, +node2+, has come
online and that the cluster is checking to make sure +rsc1+, +rsc2+
and +rsc3+ are not already running there (Indicated by the
+*_monitor_0+ entries). Once it did that, and assuming the resources
were not active there, it would have liked to stop +rsc1+ and +rsc2+
on +node1+ and move them to +node2+. However, there appears to be
some problem and the cluster cannot or is not permitted to perform the
stop actions which implies it also cannot perform the start actions.
For some reason the cluster does not want to start +rsc3+ anywhere.
For information on the options supported by ptest, use
pass:[<command>ptest --help</command>].
=== Complex Cluster Transition ===
image::images/Policy-Engine-big.png["Another, slightly more complex, transition graph that you're not expected to be able to read",width="16cm",height="20cm",align="center"]
== Do I Need to Update the Configuration on all Cluster Nodes? ==
No. Any changes are immediately synchronized to the other active
members of the cluster.
To reduce bandwidth, the cluster only broadcasts the incremental
updates that result from your changes and uses MD5 checksums to ensure
msgid "The cluster is written using XML notation and divided into two main sections: configuration and status."
msgstr ""
#. Tag: para
#, no-c-format
msgid "The status section contains the history of each resource on each node and based on this data, the cluster can construct the complete current state of the cluster. The authoritative source for the status section is the local resource manager (lrmd) process on each cluster node and the cluster will occasionally repopulate the entire section. For this reason it is never written to disk and administrators are advised against modifying it in any way."
msgstr ""
#. Tag: para
#, no-c-format
msgid "The configuration section contains the more traditional information like cluster options, lists of resources and indications of where they should be placed. The configuration section is the primary focus of this document."
msgstr ""
#. Tag: para
#, no-c-format
msgid "The configuration section itself is divided into four parts:"
msgid "Before one starts to configure a cluster, it is worth explaining how to view the finished product. For this purpose we have created the <command>crm_mon</command> utility that will display the current state of an active cluster. It can show the cluster status by node or by resource and can be used in either single-shot or dynamically-updating mode. There are also modes for displaying a list of the operations performed (grouped by node and resource) as well as information about failures."
msgstr ""
#. Tag: para
#, no-c-format
msgid "Using this tool, you can examine the state of the cluster for irregularities and see how it responds when you cause or simulate failures."
msgstr ""
#. Tag: para
#, no-c-format
msgid "Details on all the available options can be obtained using the <command>crm_mon --help</command> command."
msgstr ""
#. Tag: title
#, no-c-format
msgid "Sample output from crm_mon"
msgstr ""
#. Tag: screen
#, no-c-format
msgid " ============\n"
" Last updated: Fri Nov 23 15:26:13 2007\n"
" Current DC: sles-3 (2298606a-6a8c-499a-9d25-76242f7006ec)\n"
" child_DoFencing:2 (stonith:external/vmware): Started sles-1"
msgstr ""
#. Tag: para
#, no-c-format
msgid "The DC (Designated Controller) node is where all the decisions are made and if the current DC fails a new one is elected from the remaining cluster nodes. The choice of DC is of no significance to an administrator beyond the fact that its logs will generally be more interesting."
msgstr ""
#. Tag: title
#, no-c-format
msgid "How Should the Configuration be Updated?"
msgstr ""
#. Tag: para
#, no-c-format
msgid "There are three basic rules for updating the cluster configuration:"
msgstr ""
#. Tag: para
#, no-c-format
msgid "Rule 1 - Never edit the cib.xml file manually. Ever. I’m not making this up."
msgstr ""
#. Tag: para
#, no-c-format
msgid "Rule 2 - Read Rule 1 again."
msgstr ""
#. Tag: para
#, no-c-format
msgid "Rule 3 - The cluster will notice if you ignored rules 1 & 2 and refuse to use the configuration."
msgstr ""
#. Tag: para
#, no-c-format
msgid "Now that it is clear how NOT to update the configuration, we can begin to explain how you should."
msgstr ""
#. Tag: para
#, no-c-format
msgid "The most powerful tool for modifying the configuration is the <literal>cibadmin</literal> command which talks to a running cluster. With <literal>cibadmin</literal>, the user can query, add, remove, update or replace any part of the configuration; all changes take effect immediately, so there is no need to perform a reload-like operation."
msgstr ""
#. Tag: para
#, no-c-format
msgid "The simplest way of using cibadmin is to use it to save the current configuration to a temporary file, edit that file with your favorite text or XML editor and then upload the revised configuration."
msgstr ""
#. Tag: programlisting
#, no-c-format
msgid "# cibadmin --query > tmp.xml\n"
"# vi tmp.xml\n"
"# cibadmin --replace --xml-file tmp.xml"
msgstr ""
#. Tag: para
#, no-c-format
msgid "Some of the better XML editors can make use of a Relax NG schema to help make sure any changes you make are valid. The schema describing the configuration can normally be found in <filename>/usr/lib/heartbeat/pacemaker.rng</filename> on most systems."
msgstr ""
#. Tag: para
#, no-c-format
msgid "If you only wanted to modify the resources section, you could instead do"
msgid "Next identify the resource’s tag name and id (in this case we’ll choose <literal>primitive</literal> and <literal>child_DoFencing</literal>). Then simply execute:"
msgid "Often it is desirable to preview the effects of a series of changes before updating the configuration atomically. For this purpose we have created <command>crm_shadow</command> which creates a \"shadow\" copy of the configuration and arranges for all the command line tools to use it."
msgstr ""
#. Tag: para
#, no-c-format
msgid "To begin, simply invoke <command>crm_shadow</command> and give it the name of a configuration to create <footnote><para>Shadow copies are identified with a name, making it possible to have more than one.</para></footnote> ; be sure to follow the simple on-screen instructions."
msgstr ""
#. Tag: para
#, no-c-format
msgid "Read the above carefully, failure to do so could result in you destroying the cluster’s active configuration!</warning>"
msgstr ""
#. Tag: programlisting
#, no-c-format
msgid " # crm_shadow --create test\n"
" Setting up shadow instance\n"
" Type Ctrl-D to exit the crm_shadow shell\n"
" shadow[test]:\n"
" shadow[test] # crm_shadow --which\n"
" test"
msgstr ""
#. Tag: para
#, no-c-format
msgid "From this point on, all cluster commands will automatically use the shadow copy instead of talking to the cluster’s active configuration. Once you have finished experimenting, you can either commit the changes, or discard them as shown below. Again, be sure to follow the on-screen instructions carefully."
msgstr ""
#. Tag: para
#, no-c-format
msgid "For a full list of <command>crm_shadow</command> options and commands, invoke it with the <parameter>--help</parameter> option."
msgid "Making changes in a sandbox and verifying the real configuration is untouched"
msgstr ""
#. Tag: title
#, no-c-format
msgid "Testing Your Configuration Changes"
msgstr ""
#. Tag: para
#, no-c-format
msgid "We saw previously how to make a series of changes to a \"shadow\" copy of the configuration. Before loading the changes back into the cluster (eg. <command>crm_shadow --commit mytest --force</command>), it is often advisable to simulate the effect of the changes with <literal>ptest</literal>, eg."
msgid "The tool uses the same library as the live cluster to show what it would have done given the supplied input. It’s output, in addition to a significant amount of logging, is stored in two files <literal>tmp.graph</literal> and <literal>tmp.dot</literal>, both are representations of the same thing — the cluster’s response to your changes."
msgstr ""
#. Tag: para
#, no-c-format
msgid "In the graph file is stored the complete transition, containing a list of all the actions, their parameters and their pre-requisites. Because the transition graph is not terribly easy to read, the tool also generates a Graphviz dot-file representing the same information."
msgstr ""
#. Tag: title
#, no-c-format
msgid "Interpreting the Graphviz output"
msgstr ""
#. Tag: para
#, no-c-format
msgid "Arrows indicate ordering dependencies"
msgstr ""
#. Tag: para
#, no-c-format
msgid "Dashed-arrows indicate dependencies that are not present in the transition graph"
msgstr ""
#. Tag: para
#, no-c-format
msgid "Actions with a dashed border of any color do not form part of the transition graph"
msgstr ""
#. Tag: para
#, no-c-format
msgid "Actions with a green border form part of the transition graph"
msgstr ""
#. Tag: para
#, no-c-format
msgid "Actions with a red border are ones the cluster would like to execute but cannot run"
msgstr ""
#. Tag: para
#, no-c-format
msgid "Actions with a blue border are ones the cluster does not feel need to be executed"
msgstr ""
#. Tag: para
#, no-c-format
msgid "Actions with orange text are pseudo/pretend actions that the cluster uses to simplify the graph"
msgstr ""
#. Tag: para
#, no-c-format
msgid "Actions with black text are sent to the LRM"
msgstr ""
#. Tag: para
#, no-c-format
msgid "Resource actions have text of the form <replaceable>rsc</replaceable>_<replaceable>action</replaceable>_<replaceable>interval</replaceable> <replaceable>node</replaceable>"
msgstr ""
#. Tag: para
#, no-c-format
msgid "Any action depending on an action with a red border will not be able to execute."
msgstr ""
#. Tag: para
#, no-c-format
msgid "Loops are <emphasis>really</emphasis> bad. Please report them to the development team."
msgstr ""
#. Tag: title
#, no-c-format
msgid "Small Cluster Transition"
msgstr ""
#. Tag: phrase
#, no-c-format
msgid "An example transition graph as represented by Graphviz"
msgstr ""
#. Tag: para
#, no-c-format
msgid "In the above example, it appears that a new node, <literal>node2</literal>, has come online and that the cluster is checking to make sure <literal>rsc1</literal>, <literal>rsc2</literal> and <literal>rsc3</literal> are not already running there (Indicated by the <literal>*_monitor_0</literal> entries). Once it did that, and assuming the resources were not active there, it would have liked to stop <literal>rsc1</literal> and <literal>rsc2</literal> on <literal>node1</literal> and move them to <literal>node2</literal>. However, there appears to be some problem and the cluster cannot or is not permitted to perform the stop actions which implies it also cannot perform the start actions. For some reason the cluster does not want to start <literal>rsc3</literal> anywhere."
msgstr ""
#. Tag: para
#, no-c-format
msgid "For information on the options supported by ptest, use <command>ptest --help</command>."
msgstr ""
#. Tag: title
#, no-c-format
msgid "Complex Cluster Transition"
msgstr ""
#. Tag: phrase
#, no-c-format
msgid "Another, slightly more complex, transition graph that you're not expected to be able to read"
msgstr ""
#. Tag: title
#, no-c-format
msgid "Do I Need to Update the Configuration on all Cluster Nodes?"
msgstr ""
#. Tag: para
#, no-c-format
msgid "No. Any changes are immediately synchronized to the other active members of the cluster."
msgstr ""
#. Tag: para
#, no-c-format
msgid "To reduce bandwidth, the cluster only broadcasts the incremental updates that result from your changes and uses MD5 checksums to ensure that each copy is completely consistent."
msgid "The cluster is written using XML notation and divided into two main sections: configuration and status."
msgstr "Clusterul este scris folosind notaţie XML şi este împărţit în două secţiuni principale: configurare şi status."
#. Tag: para
#, no-c-format
msgid "The status section contains the history of each resource on each node and based on this data, the cluster can construct the complete current state of the cluster. The authoritative source for the status section is the local resource manager (lrmd) process on each cluster node and the cluster will occasionally repopulate the entire section. For this reason it is never written to disk and administrators are advised against modifying it in any way."
msgstr "Secţiunea de status conţine istoricul fiecărei resurse de pe fiecare nod şi pe baza acestor date, clusterul poate construi starea curentă completă a clusterului. Sursa autoritativă pentru secţiunea de status este procesul managerului de resurse local (lrmd) pe fiecare nod din cluster iar clusterul va repopula în mod ocazional întreaga secţiune. Din acest motiv nu este scris niciodată pe disc iar administratorii sunt sfătuiţi împotriva modificării în orice fel a acestuia."
#. Tag: para
#, no-c-format
msgid "The configuration section contains the more traditional information like cluster options, lists of resources and indications of where they should be placed. The configuration section is the primary focus of this document."
msgstr "Secţiunea de configurare conţine informaţiile mai tradiţionale precum opţiuni ale clusterului, liste de resurse şi indicaţii despre unde ar trebui acestea plasate. Secţiunea de configurare este scopul primar al acestui document."
#. Tag: para
#, no-c-format
msgid "The configuration section itself is divided into four parts:"
msgstr "Secţiunea de configurare în sine este împărţită în patru părţi:"
msgid "Before one starts to configure a cluster, it is worth explaining how to view the finished product. For this purpose we have created the <command>crm_mon</command> utility that will display the current state of an active cluster. It can show the cluster status by node or by resource and can be used in either single-shot or dynamically-updating mode. There are also modes for displaying a list of the operations performed (grouped by node and resource) as well as information about failures."
msgstr "Înainte de a începe să configurăm clusterul, merită explicat cum să vizualizăm produsul finit. Pentru acest scop am creat utilitarul <command>crm_mon</command> care va arăta starea curentă a unui cluster activ. Poate arăta statusul clusterului după nod sau după resurse şi poate fi folosit fie în mod single-shot (o singură listare) sau dynamically-updating (updatându-se dinamic). Sunt de asemenea moduri pentru prezentarea unei liste de operaţiuni efectuate (grupată după nod si resursă) precum şi informaţii despre eşecuri."
#. Tag: para
#, no-c-format
msgid "Using this tool, you can examine the state of the cluster for irregularities and see how it responds when you cause or simulate failures."
msgstr "Folosind acest utilitar, puteţi examina starea clusterului pentru neconcordanţe şi pentru a vedea cum răspunde atunci când provocaţi sau simulaţi eşecuri."
#. Tag: para
#, no-c-format
msgid "Details on all the available options can be obtained using the <command>crm_mon --help</command> command."
msgstr "Detalii despre toate opţiunile disponibile pot fi obţinute folosind comanda <command>crm_mon --help</command>."
#. Tag: title
#, no-c-format
msgid "Sample output from crm_mon"
msgstr "Exemplu de rezultat obţinut din crm_mon"
#. Tag: screen
#, no-c-format
msgid "<command># crm_mon</command>\n"
" ============\n"
" Last updated: Fri Nov 23 15:26:13 2007\n"
" Current DC: sles-3 (2298606a-6a8c-499a-9d25-76242f7006ec)\n"
" child_DoFencing:2 (stonith:external/vmware): Started sles-1"
#. Tag: para
#, no-c-format
msgid "The DC (Designated Controller) node is where all the decisions are made and if the current DC fails a new one is elected from the remaining cluster nodes. The choice of DC is of no significance to an administrator beyond the fact that its logs will generally be more interesting."
msgstr "Nodul DC (Designated Controller - Controller Desemnat) este locul unde toate deciziile sunt luate şi dacă DC-ul curent eşuează unul nou este ales din nodurile rămase în cluster. Alegerea unui DC nu are nici o semnificaţie pentru administrator dincolo de faptul că logurile acestuia vor fi în general mai interesante."
#. Tag: title
#, no-c-format
msgid "How Should the Configuration be Updated?"
msgstr "Cum Ar Trebui să fie Actualizată Configuraţia"
#. Tag: para
#, no-c-format
msgid "There are three basic rules for updating the cluster configuration:"
msgstr "Sunt trei reguli de bază pentru actualizarea configuraţiei clusterului:"
#. Tag: para
#, no-c-format
msgid "Rule 1 - Never edit the cib.xml file manually. Ever. I'm not making this up."
msgstr "Regula 1 - Nu editaţi niciodată fişierul cib.xml manual. Niciodată. Nu inventez acest lucru."
#. Tag: para
#, no-c-format
msgid "Rule 2 - Read Rule 1 again."
msgstr "Regula 2 - Citiţi Regula 1 din nou."
#. Tag: para
#, no-c-format
msgid "Rule 3 - The cluster will notice if you ignored rules 1 & 2 and refuse to use the configuration."
msgstr "Regula 3 - Clusterul va detecta că aţi ignorat regulile 1 & 2 şi va refuza să folosească configuraţia."
#. Tag: para
#, no-c-format
msgid "Now that it is clear how NOT to update the configuration, we can begin to explain how you should."
msgstr "Acum că este clar cum să NU actualizăm configuraţia, putem începe să explicăm cum ar trebui să realizăm acest lucru."
#. Tag: para
#, no-c-format
msgid "The most powerful tool for modifying the configuration is the <literal>cibadmin</literal> command which talks to a running cluster. With <literal>cibadmin</literal>, the user can query, add, remove, update or replace any part of the configuration; all changes take effect immediately, so there is no need to perform a reload-like operation."
msgstr "Cea mai puternică unealtă pentru modificarea configuraţiei este comanda <literal>cibadmin</literal> care comunică cu un cluster funcţional. Cu <literal>cibadmin</literal>, utilizatorul poate interoga, adăuga, înlătura, actualiza sau înlocui orice parte a configuraţiei; toate modificările iau efect imediat aşa că nu este necesar să executaţi operaţiuni de tip reîncărcare."
#. Tag: para
#, no-c-format
msgid "The simplest way of using cibadmin is to use it to save the current configuration to a temporary file, edit that file with your favorite text or XML editor and then upload the revised configuration."
msgstr "Cel mai simplu mod de a folosi cibadmin este de a-l folosi pentru a salva configuraţia curentă într-un fişier temporar, să editaţi acel fişier cu editorul de text sau XML favorit şi apoi să încărcaţi configuraţia revizuită."
#. Tag: title
#, no-c-format
msgid "Safely using an editor to modify the cluster configuration"
msgstr "Folosind cu siguranţă un editor pentru a modifica configuraţia clusterului"
msgid "Some of the better XML editors can make use of a Relax NG schema to help make sure any changes you make are valid. The schema describing the configuration can normally be found in <filename>/usr/lib/heartbeat/pacemaker.rng</filename> on most systems."
msgstr "Unele dintre editoarele mai bune de XML pot folosi schema Relax NG pentru a vă ajuta să fiţi siguri că modificările pe care le realizaţi sunt valide. Schema care descrie configuraţia poate fi găsită în mod normal în <filename>/usr/lib/heartbeat/pacemaker.rng</filename> pe majoritatea sistemelor."
#. Tag: para
#, no-c-format
msgid "If you only wanted to modify the resources section, you could instead do"
msgstr "Dacă aţi dorit să modificaţi doar secţiunea de resurse, aţi putea alternativ să executaţi"
#. Tag: title
#, no-c-format
msgid "Safely using an editor to modify a subsection of the cluster configuration"
msgstr "Folosind cu siguranţă un editor pentru a modifica o subsecţiune din configuraţia clusterlui"
msgid "Next identify the resource's tag name and id (in this case we'll choose <literal>primitive</literal> and <literal>child_DoFencing</literal>). Then simply execute:"
msgstr "Apoi identificaţi numele tag-ului resursei şi id-ul (în acest caz vom alege <literal>primitive</literal> şi <literal>child_DoFencing</literal>). Apoi executaţi:"
msgstr "Realizând Modificări de Configurare într-un Sandbox"
#. Tag: para
#, no-c-format
msgid "Often it is desirable to preview the effects of a series of changes before updating the configuration atomically. For this purpose we have created <command>crm_shadow</command> which creates a \"shadow\" copy of the configuration and arranges for all the command line tools to use it."
msgstr "Deseori este de dorit să previzualizaţi efectele unei serii de modificări înainte să actualizaţi configuraţia în mod atomic. Pentru acest scop am creat <command>crm_shadow</command> care creează o copie \"ascunsă\" a configuraţiei şi aranjează astfel încât toate utilitarele din linia de comandă să o folosească."
#. Tag: para
#, no-c-format
msgid "To begin, simply invoke <command>crm_shadow</command> and give it the name of a configuration to create<footnote> <para>Shadow copies are identified with a name, making it possible to have more than one.</para> </footnote>; be sure to follow the simple on-screen instructions."
msgstr "Pentru a începe, invocaţi pur şi simplu <command>crm_shadow</command> şi daţi-i numele unei configuraţii pe care să o creeze<footnote> <para>Copiile ascunse sunt identificate cu un nume, fiind posibil să avem mai mult de una.</para> </footnote>; asiguraţi-vă că urmaţi simplele instrucţiuni de pe ecran."
#. Tag: para
#, no-c-format
msgid "Read the above carefully, failure to do so could result in you destroying the cluster's active configuration!"
msgstr "Citiţi cele de mai sus cu atenţie, nerespectarea acestora poate rezulta în distrugerea de către voi a configuraţiei active a clusterului!"
#. Tag: title
#, no-c-format
msgid "Creating and displaying the active sandbox"
msgstr "Crearea şi prezentarea sandbox-ului activ"
msgid "From this point on, all cluster commands will automatically use the shadow copy instead of talking to the cluster's active configuration. Once you have finished experimenting, you can either commit the changes, or discard them as shown below. Again, be sure to follow the on-screen instructions carefully."
msgstr "Din acest punct înainte, toate comenzile clusterului vor folosi în mod automat copia ascunsă în loc să comunice cu copia activă a configuraţiei clusterului. Odată ce aţi terminat de experimentat, puteţi fie să aplicaţi modificările sau să le înlăturaţi după cum este prezentat mai jos. Din nou, asiguraţi-vă că urmaţi instrucţiunile de pe ecran cu grijă."
#. Tag: para
#, no-c-format
msgid "For a full list of <command>crm_shadow</command> options and commands, invoke it with the <parameter>--help</parameter> option."
msgstr "Pentru o listă completă de opţiuni şi comenzi ale <command>crm_shadow</command>, apelaţi-l cu opţiunea <parameter>--help</parameter>."
#. Tag: title
#, no-c-format
msgid "Using a sandbox to make multiple changes atomically"
msgstr "Folosirea unui sandbox pentru a realiza mai multe modificări în mod atomic"
msgid "Making changes in a sandbox and verifying the real configuration is untouched"
msgstr "Realizarea de modificări într-un sandbox şi apoi verificarea că, configuraţia reală nu este atinsă."
#. Tag: title
#, no-c-format
msgid "Testing Your Configuration Changes"
msgstr "Testarea Modificărilor Voastre de Configurare"
#. Tag: para
#, no-c-format
msgid "We saw previously how to make a series of changes to a \"shadow\" copy of the configuration. Before loading the changes back into the cluster (eg. <command>crm_shadow --commit mytest --force</command>), it is often advisable to simulate the effect of the changes with <literal>ptest</literal>, eg."
msgstr "Am văzut anterior cum să realizăm o serie de modificări într-o copie \"ascunsă\" a configuraţiei. Înainte de a încărca modificările înapoi în cluster (ex. <command>crm_shadow --commit mytest --force</command>), este adeseori recomandat să simulaţi efectul modificărilor cu <literal>ptest</literal>, ex."
msgid "The tool uses the same library as the live cluster to show what it would have done given the supplied input. It's output, in addition to a significant amount of logging, is stored in two files <filename>tmp.graph</filename> and <filename>tmp.dot</filename>, both are representations of the same thing -- the cluster's response to your changes. In the graph file is stored the complete transition, containing a list of all the actions, their parameters and their pre-requisites. Because the transition graph is not terribly easy to read, the tool also generates a Graphviz dot-file representing the same information."
msgstr "Utilitarul foloseşte aceeaşi bibliotecă precum clusterul activ pentru a arăta ce ar fi realizat cu informaţiile primite. Rezultatul de ieşire, suplimentar la o cantitate semnificativă de loguri, este stocat în două fişiere <filename>tmp.graph</filename> şi <filename>tmp.dot</filename>, ambele sunt reprezentări ale aceluiaşi lucru -- răspunsul clusterului la modificările voastre. În fişierul graf este stocată tranziţia completă, conţinând o listă cu toate acţiunile, parametrii acestora şi cerinţele premergătoare ale acestora. Pentru că graful de tranziţie nu este foarte uşor de citit, utilitarul generează un fişier Graphviz dot de asemenea reprezentând aceleaşi informaţii."
#. Tag: title
#, no-c-format
msgid "Small Cluster Transition"
msgstr "Tranziţia unui Cluster Mic"
#. Tag: caption
#, no-c-format
msgid "An example transition graph as represented by Graphviz"
msgstr "Un exemplu de graf de tranziţie aşa cum este reprezentat de Graphviz"
#. Tag: title
#, no-c-format
msgid "Interpreting the Graphviz output"
msgstr "Interpretarea rezultatului de ieşire al Graphviz"
#. Tag: para
#, no-c-format
msgid "Arrows indicate ordering dependencies"
msgstr "Săgeţile indică dependinţele de ordonare"
#. Tag: para
#, no-c-format
msgid "Dashed-arrows indicate dependencies that are not present in the transition graph"
msgstr "Săgeţile întrerupte de cratime indică dependinţe care nu sunt prezente în graful de tranziţie"
#. Tag: para
#, no-c-format
msgid "Actions with a dashed border of any color do not form part of the transition graph"
msgstr "Acţiunile cu o margine întreruptă cu cratime de orice culoare nu se formează ca parte a grafului de tranziţie"
#. Tag: para
#, no-c-format
msgid "Actions with a green border form part of the transition graph"
msgstr "Acţiunile cu o margine verde se formează ca parte a grafului de tranziţie"
#. Tag: para
#, no-c-format
msgid "Actions with a red border are ones the cluster would like to execute but cannot run"
msgstr "Acţiunile cu o margine roşie sunt cele pe care clusterul ar dori să le execute dar sunt neexecutabile"
#. Tag: para
#, no-c-format
msgid "Actions with a blue border are ones the cluster does not feel need to be executed"
msgstr "Acţiunile cu o margine albastră sunt cele pe care clusterul nu consideră că trebuie executate"
#. Tag: para
#, no-c-format
msgid "Actions with orange text are pseudo/pretend actions that the cluster uses to simplify the graph"
msgstr "Acţiunile cu text portocaliu sunt acţiuni pseudo/de prefacere pe care clusterul le foloseşte pentru a simplifica graful"
#. Tag: para
#, no-c-format
msgid "Actions with black text are sent to the LRM"
msgstr "Acţiunile cu text negru sunt trimise la LRM"
#. Tag: para
#, no-c-format
msgid "Resource actions have text of the form <replaceable>rsc</replaceable>_<replaceable>action</replaceable>_<replaceable>interval</replaceable> <replaceable>node</replaceable>"
msgstr "Acţiunile resurselor au textul de forma <replaceable>rsc</replaceable>_<replaceable>action</replaceable>_<replaceable>interval</replaceable><replaceable>node</replaceable>"
#. Tag: para
#, no-c-format
msgid "Any action depending on an action with a red border will not be able to execute."
msgstr "Orice acţiune care depine de o acţiune cu o margine roşie nu va putea să se execute."
#. Tag: para
#, no-c-format
msgid "Loops are <emphasis>really</emphasis> bad. Please report them to the development team."
msgstr "Buclele de execuţie sunt <emphasis>foarte</emphasis> rele. Vă rugăm să le raportaţi echipei de dezvoltare."
#. Tag: para
#, no-c-format
msgid "In the above example, it appears that a new node, <literal>node2</literal>, has come online and that the cluster is checking to make sure <literal>rsc1</literal>, <literal>rsc2</literal> and <literal>rsc3</literal> are not already running there (Indicated by the <literal>*_monitor_0</literal> entries). Once it did that, and assuming the resources were not active there, it would have liked to stop <literal>rsc1</literal> and <literal>rsc2</literal> on <literal>node1</literal> and move them to <literal>node2</literal>. However, there appears to be some problem and the cluster cannot or is not permitted to perform the stop actions which implies it also cannot perform the start actions. For some reason the cluster does not want to start <literal>rsc3</literal> anywhere."
msgstr "În exemplul de mai sus, se pare că un nod nou, <literal>node2</literal>, a ajuns online şi clusterul verifică să se asigure că <literal>rsc1</literal>, <literal>rsc2</literal> şi <literal>rsc3</literal>, nu rulează deja acolo (aspect indicat de intrările <literal>*_monitor_0</literal>). Odată ce a realizat acest lucru şi mergând pe presupunerea că resursele nu erau active acolo, ar fi preferat să oprească <literal>rsc1</literal> şi <literal>rsc2</literal> pe <literal>node1</literal> şi să le mute pe <literal>node2</literal>. Totuşi se pare că există o problemă şi clusterul nu poate sau nu îi este permis să execute operaţiunile de oprire, fapt care implică neputinţa de a efectua acţiunile de pornire de asemenea. Pentru un motiv anume clusterul nu vrea să pornească <literal>rsc3</literal> nicăieri."
#. Tag: para
#, no-c-format
msgid "For information on the options supported by ptest, use <command>ptest --help</command>."
msgstr "Pentru informaţii legate de opţiunile suportate de ptest, folosiţi <command>ptest --help</command>"
#. Tag: title
#, no-c-format
msgid "Complex Cluster Transition"
msgstr "Tranziţii Complexe ale Clusterului"
#. Tag: caption
#, no-c-format
msgid "Another, slightly more complex, transition graph that you're not expected to be able to read"
msgstr "Un alt graf de tranziţie, ceva mai complex, pe care nu sunteţi aşteaptaţi să îl puteţi citi"
#. Tag: title
#, no-c-format
msgid "Do I Need to Update the Configuration on all Cluster Nodes?"
msgstr "Trebuie să Actualizez Configuraţia pe toate Nodurile Clusterului?"
#. Tag: para
#, no-c-format
msgid "No. Any changes are immediately synchronized to the other active members of the cluster."
msgstr "Nu. Orice modificări sunt sincronizate imediat către ceilalţi membri activi ai clusterului."
#. Tag: para
#, no-c-format
msgid "To reduce bandwidth, the cluster only broadcasts the incremental updates that result from your changes and uses MD5 checksums to ensure that each copy is completely consistent."
msgstr "Pentru a reduce consumul de lăţime de bandă, clusterul transmite numai actualizările incrementale care rezultă din modificările realizate de voi şi foloseşte hash-uri MD5 pentru a se asigura că fiecare copie este complet consistentă."