diff --git a/doc/Pacemaker_Explained/en-US/Ch-Nodes.txt b/doc/Pacemaker_Explained/en-US/Ch-Nodes.txt index c8d826f168..16bf13d9c7 100644 --- a/doc/Pacemaker_Explained/en-US/Ch-Nodes.txt +++ b/doc/Pacemaker_Explained/en-US/Ch-Nodes.txt @@ -1,220 +1,220 @@ = Cluster Nodes = == Defining a Cluster Node == Each node in the cluster will have an entry in the nodes section containing its UUID, uname, and type. .Example Heartbeat cluster node entry ====== [source,XML] ====== .Example Corosync cluster node entry ====== [source,XML] ====== In normal circumstances, the admin should let the cluster populate this information automatically from the communications and membership data. However for Heartbeat, one can use the `crm_uuid` tool to read an existing UUID or define a value before the cluster starts. [[s-node-name]] == Where Pacemaker Gets the Node Name == Traditionally, Pacemaker required nodes to be referred to by the value returned by `uname -n`. This can be problematic for services that require the `uname -n` to be a specific value (ie. for a licence file). Since version 2.0.0 of Pacemaker, this requirement has been relaxed for clusters using Corosync 2.0 or later. The name Pacemaker uses is: . The value stored in 'corosync.conf' under +ring0_addr+ in the +nodelist+, if it does not contain an IP address; otherwise . The value stored in 'corosync.conf' under +name+ in the +nodelist+; otherwise . The value of `uname -n` Pacemaker provides the `crm_node -n` command which displays the name used by a running cluster. If a Corosync nodelist is used, `crm_node --name-for-id $number` is also available to display the name used by the node with the corosync +nodeid+ of '$number', for example: `crm_node --name-for-id 2`. [[s-node-attributes]] == Describing a Cluster Node == indexterm:[Node,attribute] Beyond the basic definition of a node the administrator can also describe the node's attributes, such as how much RAM, disk, what OS or kernel version it has, perhaps even its physical location. This information can then be used by the cluster when deciding where to place resources. For more information on the use of node attributes, see <>. Node attributes can be specified ahead of time or populated later, when the cluster is running, using `crm_attribute`. Below is what the node's definition would look like if the admin ran the command: .The result of using crm_attribute to specify which kernel pcmk-1 is running ====== [source,C] ------- # crm_attribute --type nodes --node-uname pcmk-1 --attr-name kernel --attr-value `uname -r` ------- [source,XML] ------- ------- ====== A simpler way to determine the current value of an attribute is to use `crm_attribute` command again: [source,C] # crm_attribute --type nodes --node-uname pcmk-1 --attr-name kernel --get-value By specifying `--type nodes` the admin tells the cluster that this attribute is persistent. There are also transient attributes which are kept in the status section which are "forgotten" whenever the node rejoins the cluster. The cluster uses this area to store a record of how many times a resource has failed on that node but administrators can also read and write to this section by specifying `--type status`. == Corosync == === Adding a New Corosync Node === indexterm:[Corosync,Add Cluster Node] indexterm:[Add Cluster Node,Corosync] Adding a new node is as simple as installing Corosync and Pacemaker, -and copying '/etc/corosync/corosync.conf' and '/etc/ais/authkey' (if +and copying '/etc/corosync/corosync.conf' and '/etc/corosync/authkey' (if it exists) from an existing node. You may need to modify the +mcastaddr+ option to match the new node's IP address. If a log message containing "Invalid digest" appears from Corosync, the keys are not consistent between the machines. === Removing a Corosync Node === indexterm:[Corosync,Remove Cluster Node] indexterm:[Remove Cluster Node,Corosync] Because the messaging and membership layers are the authoritative source for cluster nodes, deleting them from the CIB is not a reliable solution. First one must arrange for corosync to forget about the node (_pcmk-1_ in the example below). On the host to be removed: . Stop the cluster: `/etc/init.d/corosync stop` Next, from one of the remaining active cluster nodes: . Tell Pacemaker to forget about the removed host: + [source,C] # crm_node -R pcmk-1 + This includes deleting the node from the CIB [NOTE] ====== This proceedure only works for versions after 1.1.8 ====== === Replacing a Corosync Node === indexterm:[Corosync,Replace Cluster Node] indexterm:[Replace Cluster Node,Corosync] The five-step guide to replacing an existing cluster node: . Make sure the old node is completely stopped . Give the new machine the same hostname and IP address as the old one . Install the cluster software :-) -. Copy '/etc/corosync/corosync.conf' and '/etc/ais/authkey' (if it exists) to the new node +. Copy '/etc/corosync/corosync.conf' and '/etc/corosync/authkey' (if it exists) to the new node . Start the new cluster node If a log message containing "Invalid digest" appears from Corosync, the keys are not consistent between the machines. == CMAN == === Adding a New CMAN Node === indexterm:[CMAN,Add Cluster Node] indexterm:[Add Cluster Node,CMAN] === Removing a CMAN Node === indexterm:[CMAN,Remove Cluster Node] indexterm:[Remove Cluster Node,CMAN] == Heartbeat == === Adding a New Heartbeat Node === indexterm:[Heartbeat,Add Cluster Node] indexterm:[Add Cluster Node,Heartbeat] Provided you specified +autojoin any+ in 'ha.cf', adding a new node is as simple as installing heartbeat and copying 'ha.cf' and 'authkeys' from an existing node. If you don't want to use +autojoin+, then after setting up 'ha.cf' and 'authkeys', you must use `hb_addnode` before starting the new node. === Removing a Heartbeat Node === indexterm:[Heartbeat,Remove Cluster Node] indexterm:[Remove Cluster Node,Heartbeat] Because the messaging and membership layers are the authoritative source for cluster nodes, deleting them from the CIB is not a reliable solution. First one must arrange for Heartbeat to forget about the node (pcmk-1 in the example below). On the host to be removed: . Stop the cluster: `/etc/init.d/corosync stop` Next, from one of the remaining active cluster nodes: . Tell Heartbeat the node should be removed [source,C] # hb_delnode pcmk-1 . Tell Pacemaker to forget about the removed host: [source,C] # crm_node -R pcmk-1 [NOTE] ====== This proceedure only works for versions after 1.1.8 ====== === Replacing a Heartbeat Node === indexterm:[Heartbeat,Replace Cluster Node] indexterm:[Replace Cluster Node,Heartbeat] The seven-step guide to replacing an existing cluster node: . Make sure the old node is completely stopped . Give the new machine the same hostname as the old one . Go to an active cluster node and look up the UUID for the old node in '/var/lib/heartbeat/hostcache' . Install the cluster software . Copy 'ha.cf' and 'authkeys' to the new node . On the new node, populate it's UUID using `crm_uuid -w` and the UUID from step 2 . Start the new cluster node diff --git a/doc/Pacemaker_Explained/it-IT/Ch-Nodes.po b/doc/Pacemaker_Explained/it-IT/Ch-Nodes.po index 2621ce8da8..ab7ae7610d 100644 --- a/doc/Pacemaker_Explained/it-IT/Ch-Nodes.po +++ b/doc/Pacemaker_Explained/it-IT/Ch-Nodes.po @@ -1,318 +1,318 @@ # # AUTHOR , YEAR. # msgid "" msgstr "" "Project-Id-Version: 0\n" "POT-Creation-Date: 2012-10-17T05:19:02\n" "PO-Revision-Date: 2011-04-26 14:39+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 "Cluster Nodes" msgstr "Nodi del cluster" #. Tag: title #, no-c-format msgid "Defining a Cluster Node" msgstr "Definire un nodo del cluster" #. Tag: para #, fuzzy, no-c-format msgid "Each node in the cluster will have an entry in the nodes section containing its UUID, uname, and type." msgstr "Ad ogni nodo nel cluster corrisponderà una entry nella sezione nodi contenente il relativo UUID, il valore di uname ed il tipo." #. Tag: title #, no-c-format msgid "Example cluster node entry" msgstr "Esempio di una entry relativa ad un nodo cluster" #. Tag: programlisting #, fuzzy, no-c-format msgid "<node id=\"1186dc9a-324d-425a-966e-d757e693dc86\" uname=\"pcmk-1\" type=\"normal\"/>" msgstr "" "\n" " <node id="1186dc9a-324d-425a-966e-d757e693dc86" uname="pcmk-1" type="normal"/>\n" "\t" #. Tag: para #, fuzzy, no-c-format msgid "In normal circumstances, the admin should let the cluster populate this information automatically from the communications and membership data. However one can use the crm_uuid tool to read an existing UUID or define a value before the cluster starts." msgstr "In circostanze normali, l'amministratore dovrebbe lasciar popolare le informazioni automaticamente al cluster in base ai dati di communication e membership. Ad ogni modo è possibile utilizzare lo strumento crm_uuid per leggere un UUID esistente o definire un valore prima che il cluster si avii." #. Tag: title #, no-c-format msgid "Describing a Cluster Node" msgstr "Descrivere un nodo del cluster" #. Tag: para #, fuzzy, no-c-format msgid " Nodeattribute attribute Beyond the basic definition of a node the administrator can also describe the node’s attributes, such as how much RAM, disk, what OS or kernel version it has, perhaps even its physical location. This information can then be used by the cluster when deciding where to place resources. For more information on the use of node attributes, see ." msgstr "Al di la della definizione base di un nodo, l'amministratore può inoltre descriverne gli attributi, come ad esempio quanta RAM, disco, quale sistema operativo o versione di kernel monta, forse anche la locazione fisica. Queste informazioni possono quindi essere utilizzate dal cluster nel momento in cui viene deciso dove porre le risorse. Per ulteriori informazioni sull'uso degli attributi del nodo, vedere la sezione ." #. Tag: para #, fuzzy, no-c-format msgid "Node attributes can be specified ahead of time or populated later, when the cluster is running, using crm_attribute." msgstr "Gli attributi dei nodi possono essere specificati a priori o popolate in seguito, quando il cluster sta funzionando, utilizzando crm_attribute." #. Tag: para #, fuzzy, no-c-format msgid "Below is what the node’s definition would look like if the admin ran the command:" msgstr "Ecco riportato come sarà la definzione del nodo se l'amministratore lancia il comando:" #. Tag: title #, no-c-format msgid "The result of using crm_attribute to specify which kernel pcmk-1 is running" msgstr "Risultato dell'utilizzo di crm_attribute per specificare quale kernel sta funzionando su pcmk-1" #. Tag: programlisting #, fuzzy, no-c-format msgid "# crm_attribute --type nodes --node-uname pcmk-1 --attr-name kernel --attr-value `uname -r`" msgstr " crm_attribute --type nodes --node-uname pcmk-1 --attr-name kernel --get-value" #. Tag: programlisting #, fuzzy, no-c-format msgid "" "<node uname=\"pcmk-1\" type=\"normal\" id=\"1186dc9a-324d-425a-966e-d757e693dc86\">\n" " <instance_attributes id=\"nodes-1186dc9a-324d-425a-966e-d757e693dc86\">\n" " <nvpair id=\"kernel-1186dc9a-324d-425a-966e-d757e693dc86\" name=\"kernel\" value=\"2.6.16.46-0.4-default\"/>\n" " </instance_attributes>\n" "</node>" msgstr "" "\n" " crm_attribute --type nodes --node-uname pcmk-1 --attr-name kernel --attr-value `uname -r` \n" "\n" " <node uname="pcmk-1" type="normal" id="1186dc9a-324d-425a-966e-d757e693dc86">\n" " <instance_attributes id="nodes-1186dc9a-324d-425a-966e-d757e693dc86">\n" " <nvpair id="kernel-1186dc9a-324d-425a-966e-d757e693dc86" name="kernel" value="2.6.16.46-0.4-default"/>\n" " </instance_attributes>\n" " </node>\n" "\n" "\t" #. Tag: para #, fuzzy, no-c-format msgid "A simpler way to determine the current value of an attribute is to use crm_attribute command again:" msgstr "Una via più semplice per determinare il valore corrente di un attributo è di utilizzare nuovamente il comando crm_attribute:" #. Tag: programlisting #, fuzzy, no-c-format msgid "# crm_attribute --type nodes --node-uname pcmk-1 --attr-name kernel --get-value" msgstr " crm_attribute --type nodes --node-uname pcmk-1 --attr-name kernel --get-value" #. Tag: para #, fuzzy, no-c-format msgid "By specifying --type nodes the admin tells the cluster that this attribute is persistent. There are also transient attributes which are kept in the status section which are \"forgotten\" whenever the node rejoins the cluster. The cluster uses this area to store a record of how many times a resource has failed on that node but administrators can also read and write to this section by specifying --type status." msgstr "Specificando --type nodes, l'amministratore comunica al cluster che l'attributo è persistente. Esistono inoltre attributi transitori presenti nella sezione status che sono "dimenticati" ogni volta che il nodo diventa parte nuovamente del cluster. Il cluster utilizza quest'area per registrare il valore relativo a quante volte una risorsa è fallita su quel nodo, ma gli amministratoripossono inoltre leggere e scrivere in questa sezione specificando --type status." #. Tag: title #, no-c-format msgid "Adding a New Cluster Node" msgstr "Aggiungere un nuovo nodo al cluster" #. Tag: title #, no-c-format msgid "Corosync" msgstr "Corosync" #. Tag: para #, no-c-format -msgid " CorosyncAdd Cluster Node Add Cluster Node Add Cluster NodeCorosync Corosync Adding a new node is as simple as installing Corosync and Pacemaker, and copying /etc/corosync/corosync.conf and /etc/ais/authkey (if it exists) from an existing node. You may need to modify the mcastaddr option to match the new node’s IP address." +msgid " CorosyncAdd Cluster Node Add Cluster Node Add Cluster NodeCorosync Corosync Adding a new node is as simple as installing Corosync and Pacemaker, and copying /etc/corosync/corosync.conf and /etc/corosync/authkey (if it exists) from an existing node. You may need to modify the mcastaddr option to match the new node’s IP address." msgstr "" #. Tag: para #, fuzzy, no-c-format msgid "If a log message containing \"Invalid digest\" appears from Corosync, the keys are not consistent between the machines." msgstr "Se appare tra i log di Corosync un messaggio contenente "Invalid digest", le chiavi tra le due macchine non sono consistenti." #. Tag: title #, no-c-format msgid "Heartbeat" msgstr "Heartbeat" #. Tag: para #, no-c-format msgid " HeartbeatAdd Cluster Node Add Cluster Node Add Cluster NodeHeartbeat Heartbeat Provided you specified autojoin any in ha.cf, adding a new node is as simple as installing heartbeat and copying ha.cf and authkeys from an existing node." msgstr "" #. Tag: para #, fuzzy, no-c-format msgid "If you don’t want to use autojoin, then after setting up ha.cf and authkeys, you must use the hb_addnode command before starting the new node." msgstr "Se l'opzione autojoin non è stata specificata, allora dopo aver modificato ha.cf e authkeys, sarà necessario utilizzare il comando bh_addnode prima di avviare il nuovo nodo." #. Tag: title #, no-c-format msgid "Removing a Cluster Node" msgstr "Rimuovere un nodo" #. Tag: para #, fuzzy, no-c-format msgid " CorosyncRemove Cluster Node Remove Cluster Node Remove Cluster NodeCorosync Corosync Because the messaging and membership layers are the authoritative source for cluster nodes, deleting them from the CIB is not a reliable solution. First one must arrange for heartbeat to forget about the node (pcmk-1 in the example below)." msgstr "Poiché il livello di messaging e membership sono sorgenti autoritative per i nodi del cluster, la loro cancellazione dal CIB non è una via percorribile. Prima quindi è necessario fare in modo che heartbeat dimentichi il nodo in questione (pcmk-1 nell'esempio sottostante)." #. Tag: para #, no-c-format msgid "On the host to be removed:" msgstr "Sull'host da rimuovere:" #. Tag: para #, fuzzy, no-c-format msgid "Find and record the node’s Corosync id: crm_node -i" msgstr "Trova e registra l'id Corosync del nodo: crm_node -i" #. Tag: para #, fuzzy, no-c-format msgid "Stop the cluster: /etc/init.d/corosync stop" msgstr "Stop del cluster: /etc/init.d/corosync stop" #. Tag: para #, no-c-format msgid "Next, from one of the remaining active cluster nodes:" msgstr "Quindi, da uno dei nodi rimasti attivi:" #. Tag: para #, no-c-format msgid "Tell the cluster to forget about the removed host:" msgstr "" #. Tag: programlisting #, no-c-format msgid "# crm_node -R $COROSYNC_ID" msgstr "" #. Tag: para #, no-c-format msgid "Only now is it safe to delete the node from the CIB with:" msgstr "Solamente ora è sicuro rimuovere il nodo dal CIB mediante:" #. Tag: programlisting #, no-c-format msgid "" "# cibadmin --delete --obj_type nodes --crm_xml '<node uname=\"_pcmk-1_\"/>'\n" "# cibadmin --delete --obj_type status --crm_xml '<node_state uname=\"_pcmk-1_\"/>'" msgstr "" #. Tag: para #, no-c-format msgid " HeartbeatRemove Cluster Node Remove Cluster Node Remove Cluster NodeHeartbeat Heartbeat Because the messaging and membership layers are the authoritative source for cluster nodes, deleting them from the CIB is not a reliable solution." msgstr "" #. Tag: para #, fuzzy, no-c-format msgid "First one must arrange for heartbeat to forget about the node (pcmk-1 in the example below). To do this, shut down heartbeat on the node and then, from one of the remaining active cluster nodes, run:" msgstr "Poiché i livelli di messaging e membership sono le sorgenti autoritative per i nodi del cluster, cancellarli dal CIB non è una soluzione percorribile. Prima quindi è necessario fare in modo che heartbeat dimentichi il nodo (pcmk-1 in the example below). Per fare questo, è sufficiente fermare heartbeat sul nodo interessato e successivamente, sul nodo rimasto attivo nel cluster, lanciare:" #. Tag: programlisting #, fuzzy, no-c-format msgid "# hb_delnode pcmk-1" msgstr "hb_delnode pcmk-1" #. Tag: para #, no-c-format msgid "Only then is it safe to delete the node from the CIB with:" msgstr "Solo a questo punto è sicuro rimuovere il nodo dal CIB con:" #. Tag: programlisting #, no-c-format msgid "" "# cibadmin --delete --obj_type nodes --crm_xml '<node uname=\"pcmk-1\"/>'\n" "# cibadmin --delete --obj_type status --crm_xml '<node_state uname=\"pcmk-1\"/>'" msgstr "" #. Tag: title #, no-c-format msgid "Replacing a Cluster Node" msgstr "Rimpiazzare un nodo del cluster" #. Tag: para #, no-c-format msgid " CorosyncReplace Cluster Node Replace Cluster Node Replace Cluster NodeCorosync Corosync The five-step guide to replacing an existing cluster node:" msgstr "" #. Tag: para #, no-c-format msgid "Make sure the old node is completely stopped" msgstr "Assicurarsi che il vecchio nodo sia completamente stoppato" #. Tag: para #, no-c-format msgid "Give the new machine the same hostname and IP address as the old one" msgstr "Assegnare alla nuova macchina lo stesso hostname ed indirizzo IP della vecchia macchina" #. Tag: para #, no-c-format msgid "Install the cluster software :-)" msgstr "Installare il software del cluster :-)" #. Tag: para #, fuzzy, no-c-format -msgid "Copy /etc/corosync/corosync.conf and /etc/ais/authkey (if it exists) to the new node" -msgstr "Copiare /etc/corosync/corosync.conf e /etc/ais/authkey (se esiste) nel nuovo nodo" +msgid "Copy /etc/corosync/corosync.conf and /etc/corosync/authkey (if it exists) to the new node" +msgstr "Copiare /etc/corosync/corosync.conf e /etc/corosync/authkey (se esiste) nel nuovo nodo" #. Tag: para #, no-c-format msgid "Start the new cluster node" msgstr "Avviare il nuovo nodo del cluster" #. Tag: para #, no-c-format msgid " HeartbeatReplace Cluster Node Replace Cluster Node Replace Cluster NodeHeartbeat Heartbeat The seven-step guide to replacing an existing cluster node:" msgstr "" #. Tag: para #, no-c-format msgid "Give the new machine the same hostname as the old one" msgstr "Dare alla nuova macchina lo stesso hostname della vecchia" #. Tag: para #, fuzzy, no-c-format msgid "Go to an active cluster node and look up the UUID for the old node in /var/lib/heartbeat/hostcache" msgstr "Su un nodo attivo del cluster localizzale l'UUID del vecchio nodo in /var/lib/heartbeat/hostcache" #. Tag: para #, no-c-format msgid "Install the cluster software" msgstr "Installare il software del cluster" #. Tag: para #, fuzzy, no-c-format msgid "Copy ha.cf and authkeys to the new node" msgstr "Copiare ha.cf ed authkeys nel nuovo nodo" #. Tag: para #, fuzzy, no-c-format msgid "On the new node, populate it’s UUID using crm_uuid -w and the UUID from step 2" msgstr "Sul vecchio nodo, popolare il file con il valore UUID utilizzando crm_uuid -w ed il valore UUID ricavato nel passo 2" -#~ msgid "Adding a new is as simple as installing Corosync and Pacemaker, and copying /etc/corosync/corosync.conf and /etc/ais/authkey (if it exists) from an existing node. You may need to modify the mcastaddr option to match the new node's IP address." -#~ msgstr "Aggiungere un nuovo nodo è fattibile installando Corosync e Pacemaker, e copiando /etc/corosync/corosync.conf e /etc/ais/authkey (se esiste) da un nodo esistente. Potrebbe essere necessario modificare l'opzione mcastaddr in modo che corrisponda all'indirizzo IP del nuovo nodo." +#~ msgid "Adding a new is as simple as installing Corosync and Pacemaker, and copying /etc/corosync/corosync.conf and /etc/corosync/authkey (if it exists) from an existing node. You may need to modify the mcastaddr option to match the new node's IP address." +#~ msgstr "Aggiungere un nuovo nodo è fattibile installando Corosync e Pacemaker, e copiando /etc/corosync/corosync.conf e /etc/corosync/authkey (se esiste) da un nodo esistente. Potrebbe essere necessario modificare l'opzione mcastaddr in modo che corrisponda all'indirizzo IP del nuovo nodo." #~ msgid "Provided you specified autojoin any in ha.cf, adding a new is as simple as installing heartbeat and copying ha.cf and authkeys from an existing node." #~ msgstr "A condizione che si sia specificato autojon any all'interno del file ha.cf, aggiungere un nuovo nodo è possibile semplicemente installando heartbeat e copiando i file ha.cf e authkeys da un nodo esistente." #~ msgid "Tell the cluster to forget about the removed host: crm_node -R COROSYNC_ID" #~ msgstr "Comunica al cluster di dimenticare gli host rimossi: crm_node -R COROSYNC_ID" #~ msgid "cibadmin --delete --obj_type nodes --crm_xml '<node uname="pcmk-1"/>'" #~ msgstr "cibadmin --delete --obj_type nodes --crm_xml '<node uname="pcmk-1"/>'" #~ msgid "cibadmin --delete --obj_type status --crm_xml '<node_state uname="pcmk-1"/>'" #~ msgstr "cibadmin --delete --obj_type status --crm_xml '<node_state uname="pcmk-1"/>'" #~ msgid "cibadmin --delete --obj_type nodes --crm_xml '<node uname="pcmk-1"/>'" #~ msgstr "cibadmin --delete --obj_type nodes --crm_xml '<node uname="pcmk-1"/>'" #~ msgid "cibadmin --delete --obj_type status --crm_xml '<node_state uname="pcmk-1"/>'" #~ msgstr "cibadmin --delete --obj_type status --crm_xml '<node_state uname="pcmk-1"/>'" #~ msgid "The five-step guide to replacing an existing cluster node:" #~ msgstr "Guida in cinque passi per rimpiazzare un nodo esistente del cluster:" #~ msgid "The seven-step guide to replacing an existing cluster node:" #~ msgstr "Guida in sette passi per rimpiazzare un nodo del cluster esistente:" diff --git a/doc/Pacemaker_Explained/ro-RO/Ch-Nodes.po b/doc/Pacemaker_Explained/ro-RO/Ch-Nodes.po index b507973fae..94858093d8 100644 --- a/doc/Pacemaker_Explained/ro-RO/Ch-Nodes.po +++ b/doc/Pacemaker_Explained/ro-RO/Ch-Nodes.po @@ -1,307 +1,307 @@ 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 "Cluster Nodes" msgstr "Nodurile Clusterului" #. Tag: title #, no-c-format msgid "Defining a Cluster Node" msgstr "Definirea unui Nod de Cluster" #. Tag: para #, no-c-format msgid "Each node in the cluster will have an entry in the nodes section containing its UUID, uname, and type." msgstr "Fiecare nod în cluster va avea o intrare în secţiunea de noduri conţinând UUID-ul, uname-ul şi tipul acestuia." #. Tag: title #, no-c-format msgid "Example cluster node entry" msgstr "Exemplu de intrare de nod de cluster" #. Tag: programlisting #, fuzzy, no-c-format msgid "<node id=\"1186dc9a-324d-425a-966e-d757e693dc86\" uname=\"pcmk-1\" type=\"normal\"/>" msgstr "" "<node id=\"1186dc9a-324d-425a-966e-d757e693dc86\" uname=\"pcmk-1\" type=\"normal\"/>\n" "\t" #. Tag: para #, fuzzy, no-c-format msgid "In normal circumstances, the admin should let the cluster populate this information automatically from the communications and membership data. However one can use the crm_uuid tool to read an existing UUID or define a value before the cluster starts." msgstr "În circumstanţe normale, admin-ul ar trebui să lase clusterul să populeze această informaţie în mod automat din datele de comunicare şi apartenenţă. Totuşi cineva poate folosi utilitarul crm_uuid pentru a citi un UUID existent sau pentru a defini o valoare înainte să pornească clusterul." #. Tag: title #, no-c-format msgid "Describing a Cluster Node" msgstr "Descrierea unui Nod de Cluster" #. Tag: para #, fuzzy, no-c-format msgid " Nodeattribute attribute Beyond the basic definition of a node the administrator can also describe the node’s attributes, such as how much RAM, disk, what OS or kernel version it has, perhaps even its physical location. This information can then be used by the cluster when deciding where to place resources. For more information on the use of node attributes, see ." msgstr "Dincolo de definiţia de bază a unui nod, administratorul poate descrie de asemenea şi atributele nodului, cum ar fi cât de mult RAM, disc are, care OS sau versiune de kernel are, poate chiar şi locaţia fizică. Această informaţie poate fi utilizată mai apoi de către cluster când va decide unde să plaseze resursele. Pentru mai multe informaţii referitoare la folosirea atributelor nodului, vedeţi secţiunea despre ." #. Tag: para #, fuzzy, no-c-format msgid "Node attributes can be specified ahead of time or populated later, when the cluster is running, using crm_attribute." msgstr "Atributele nodului pot fi specificate în avans sau populate ulterior, când clusterul rulează, folosind crm_attribute." #. Tag: para #, fuzzy, no-c-format msgid "Below is what the node’s definition would look like if the admin ran the command:" msgstr "Mai jos este prezentat cum ar arăta definiţia nodului dacă administratorul ar executa comanda:" #. Tag: title #, no-c-format msgid "The result of using crm_attribute to specify which kernel pcmk-1 is running" msgstr "Rezultatul folosirii crm_attribute pentru a specifica pe ce kernel rulează pcmk-1" #. Tag: programlisting #, fuzzy, no-c-format msgid "# crm_attribute --type nodes --node-uname pcmk-1 --attr-name kernel --attr-value `uname -r`" msgstr " crm_attribute --type nodes --node-uname pcmk-1 --attr-name kernel --get-value" #. Tag: programlisting #, fuzzy, no-c-format msgid "" "<node uname=\"pcmk-1\" type=\"normal\" id=\"1186dc9a-324d-425a-966e-d757e693dc86\">\n" " <instance_attributes id=\"nodes-1186dc9a-324d-425a-966e-d757e693dc86\">\n" " <nvpair id=\"kernel-1186dc9a-324d-425a-966e-d757e693dc86\" name=\"kernel\" value=\"2.6.16.46-0.4-default\"/>\n" " </instance_attributes>\n" "</node>" msgstr "" "crm_attribute --type nodes --node-uname pcmk-1 --attr-name kernel --attr-value `uname -r` \n" "\n" " <node uname=\"pcmk-1\" type=\"normal\" id=\"1186dc9a-324d-425a-966e-d757e693dc86\">\n" " <instance_attributes id=\"nodes-1186dc9a-324d-425a-966e-d757e693dc86\">\n" " <nvpair id=\"kernel-1186dc9a-324d-425a-966e-d757e693dc86\" name=\"kernel\" value=\"2.6.16.46-0.4-default\"/>\n" " </instance_attributes>\n" " </node> " #. Tag: para #, fuzzy, no-c-format msgid "A simpler way to determine the current value of an attribute is to use crm_attribute command again:" msgstr "O metodă mai simplă de a determina valoarea curentă a unui atribut este de a folosi comanda crm_attribute din nou:" #. Tag: programlisting #, fuzzy, no-c-format msgid "# crm_attribute --type nodes --node-uname pcmk-1 --attr-name kernel --get-value" msgstr " crm_attribute --type nodes --node-uname pcmk-1 --attr-name kernel --get-value" #. Tag: para #, fuzzy, no-c-format msgid "By specifying --type nodes the admin tells the cluster that this attribute is persistent. There are also transient attributes which are kept in the status section which are \"forgotten\" whenever the node rejoins the cluster. The cluster uses this area to store a record of how many times a resource has failed on that node but administrators can also read and write to this section by specifying --type status." msgstr "Prin specificarea --type noduri administratorul îi spune clusterului că acest atribut este persistent. Există de asemenea atribute tranzitive care sunt păstrate în secţiunea de status şi care sunt \"uitate\" oricând nodul se realătură clusterului. Clusterul foloseşte această zonă pentru a stoca o înregistrare despre de câte ori a eşuat o resursă pe acel nod însâ administratorii pot citi şi scrie în această secţiune prin specificarea a --type status." #. Tag: title #, no-c-format msgid "Adding a New Cluster Node" msgstr "Adăugarea unui Nou Nod în Cluster" #. Tag: title #, no-c-format msgid "Corosync" msgstr "Corosync" #. Tag: para #, fuzzy, no-c-format -msgid " CorosyncAdd Cluster Node Add Cluster Node Add Cluster NodeCorosync Corosync Adding a new node is as simple as installing Corosync and Pacemaker, and copying /etc/corosync/corosync.conf and /etc/ais/authkey (if it exists) from an existing node. You may need to modify the mcastaddr option to match the new node’s IP address." -msgstr "Adăugarea unui nou nod este la fel de simplă ca instalarea Corosync şi Pacemaker şi copierea /etc/corosync/corosync.conf şi a /etc/ais/authkey (dacă există) de pe un nod existent. Ar putea fi necesar să modificaţi opţiunea mcastaddr pentru a se potrivi cu adresa IP a noului nod." +msgid " CorosyncAdd Cluster Node Add Cluster Node Add Cluster NodeCorosync Corosync Adding a new node is as simple as installing Corosync and Pacemaker, and copying /etc/corosync/corosync.conf and /etc/corosync/authkey (if it exists) from an existing node. You may need to modify the mcastaddr option to match the new node’s IP address." +msgstr "Adăugarea unui nou nod este la fel de simplă ca instalarea Corosync şi Pacemaker şi copierea /etc/corosync/corosync.conf şi a /etc/corosync/authkey (dacă există) de pe un nod existent. Ar putea fi necesar să modificaţi opţiunea mcastaddr pentru a se potrivi cu adresa IP a noului nod." #. Tag: para #, no-c-format msgid "If a log message containing \"Invalid digest\" appears from Corosync, the keys are not consistent between the machines." msgstr "Dacă apare în log-uri un mesaj de la Corosync conţinând \"Invalid digest\", cheile nu sunt consistente între maşini." #. Tag: title #, no-c-format msgid "Heartbeat" msgstr "Heartbeat" #. Tag: para #, no-c-format msgid " HeartbeatAdd Cluster Node Add Cluster Node Add Cluster NodeHeartbeat Heartbeat Provided you specified autojoin any in ha.cf, adding a new node is as simple as installing heartbeat and copying ha.cf and authkeys from an existing node." msgstr "" #. Tag: para #, fuzzy, no-c-format msgid "If you don’t want to use autojoin, then after setting up ha.cf and authkeys, you must use the hb_addnode command before starting the new node." msgstr "În caz contrar, după setarea ha.cf şi a authkeys, trebuie să folosiţi comanda hb_addnode înainte de a porni noul nod." #. Tag: title #, no-c-format msgid "Removing a Cluster Node" msgstr "Înlăturarea unui Nod din Cluster" #. Tag: para #, fuzzy, no-c-format msgid " CorosyncRemove Cluster Node Remove Cluster Node Remove Cluster NodeCorosync Corosync Because the messaging and membership layers are the authoritative source for cluster nodes, deleting them from the CIB is not a reliable solution. First one must arrange for heartbeat to forget about the node (pcmk-1 in the example below)." msgstr "Datorită faptului că straturile de mesagerie şi apartenenţă sunt surse autoritative pentru nodurile clusterului, ştergerea acestoa din CIB nu este o soluţie de încredere. Întâi cineva trebuie să facă astfel încât heartbeat să uite de nod (pcmk-1 în exemplul de mai jos)." #. Tag: para #, no-c-format msgid "On the host to be removed:" msgstr "Pe gazda care va fi înlăturată:" #. Tag: para #, fuzzy, no-c-format msgid "Find and record the node’s Corosync id: crm_node -i" msgstr "Găsiţi şi înregistraţi id-ul Corosync al nodului: crm_node -i" #. Tag: para #, fuzzy, no-c-format msgid "Stop the cluster: /etc/init.d/corosync stop" msgstr "Opriţi clusterul: /etc/init.d/corosync stop" #. Tag: para #, no-c-format msgid "Next, from one of the remaining active cluster nodes:" msgstr "Ulterior, de pe unul din nodurile rămase active ale clusterului:" #. Tag: para #, no-c-format msgid "Tell the cluster to forget about the removed host:" msgstr "" #. Tag: programlisting #, no-c-format msgid "# crm_node -R $COROSYNC_ID" msgstr "" #. Tag: para #, no-c-format msgid "Only now is it safe to delete the node from the CIB with:" msgstr "Doar acum este în siguranţă să ştergeţi nodul din CIB cu:" #. Tag: programlisting #, fuzzy, no-c-format msgid "" "# cibadmin --delete --obj_type nodes --crm_xml '<node uname=\"_pcmk-1_\"/>'\n" "# cibadmin --delete --obj_type status --crm_xml '<node_state uname=\"_pcmk-1_\"/>'" msgstr "" "cibadmin --delete --obj_type nodes --crm_xml '<node uname=\"pcmk-1\"/>'\n" "\tcibadmin --delete --obj_type status --crm_xml '<node_state uname=\"pcmk-1\"/>'" #. Tag: para #, no-c-format msgid " HeartbeatRemove Cluster Node Remove Cluster Node Remove Cluster NodeHeartbeat Heartbeat Because the messaging and membership layers are the authoritative source for cluster nodes, deleting them from the CIB is not a reliable solution." msgstr "" #. Tag: para #, fuzzy, no-c-format msgid "First one must arrange for heartbeat to forget about the node (pcmk-1 in the example below). To do this, shut down heartbeat on the node and then, from one of the remaining active cluster nodes, run:" msgstr "Datorită faptului că straturile de mesagerie şi apartenenţă sunt surse autoritative pentru nodurile clusterului, ştergerea acestoa din CIB nu este o soluţie de încredere. Întâi cineva trebuie să facă astfel încât heartbeat să uite de nod (pcmk-1 în exemplul de mai jos). Pentru a realiza acest lucru, opriţi heartbeat pe nod şi apoi, de pe unul din nodurile rămase active în cluster, rulaţi:" #. Tag: programlisting #, fuzzy, no-c-format msgid "# hb_delnode pcmk-1" msgstr "hb_delnode pcmk-1" #. Tag: para #, no-c-format msgid "Only then is it safe to delete the node from the CIB with:" msgstr "Doar acum este în siguranţă să ştergeţi nodul din CIB cu:" #. Tag: programlisting #, fuzzy, no-c-format msgid "" "# cibadmin --delete --obj_type nodes --crm_xml '<node uname=\"pcmk-1\"/>'\n" "# cibadmin --delete --obj_type status --crm_xml '<node_state uname=\"pcmk-1\"/>'" msgstr "" "cibadmin --delete --obj_type nodes --crm_xml '<node uname=\"pcmk-1\"/>'\n" "\tcibadmin --delete --obj_type status --crm_xml '<node_state uname=\"pcmk-1\"/>'" #. Tag: title #, no-c-format msgid "Replacing a Cluster Node" msgstr "Înlocuirea unui Nod din Cluster" #. Tag: para #, no-c-format msgid " CorosyncReplace Cluster Node Replace Cluster Node Replace Cluster NodeCorosync Corosync The five-step guide to replacing an existing cluster node:" msgstr "" #. Tag: para #, no-c-format msgid "Make sure the old node is completely stopped" msgstr "Asiguraţi-vă că nodul vechi este oprit de tot." #. Tag: para #, no-c-format msgid "Give the new machine the same hostname and IP address as the old one" msgstr "Daţi maşinii noi acelaşi hostname şi adresă IP ca celei vechi" #. Tag: para #, no-c-format msgid "Install the cluster software :-)" msgstr "Instalaţi soft-ul de cluster :-)" #. Tag: para #, fuzzy, no-c-format -msgid "Copy /etc/corosync/corosync.conf and /etc/ais/authkey (if it exists) to the new node" -msgstr "Copiaţi /etc/corosync/corosync.conf şi /etc/ais/authkey (dacă există) pe nodul nou" +msgid "Copy /etc/corosync/corosync.conf and /etc/corosync/authkey (if it exists) to the new node" +msgstr "Copiaţi /etc/corosync/corosync.conf şi /etc/corosync/authkey (dacă există) pe nodul nou" #. Tag: para #, no-c-format msgid "Start the new cluster node" msgstr "Porniţi noul nod în cluster" #. Tag: para #, no-c-format msgid " HeartbeatReplace Cluster Node Replace Cluster Node Replace Cluster NodeHeartbeat Heartbeat The seven-step guide to replacing an existing cluster node:" msgstr "" #. Tag: para #, no-c-format msgid "Give the new machine the same hostname as the old one" msgstr "Daţi maşinii noi acelaşi hostname ca şi celei vechi" #. Tag: para #, fuzzy, no-c-format msgid "Go to an active cluster node and look up the UUID for the old node in /var/lib/heartbeat/hostcache" msgstr "Mergeţi pe un nod activ din cluster şi căutaţi UUID-ul nodului vechi în /var/lib/heartbeat/hostcache" #. Tag: para #, no-c-format msgid "Install the cluster software" msgstr "Instalaţi soft-ul de cluster" #. Tag: para #, fuzzy, no-c-format msgid "Copy ha.cf and authkeys to the new node" -msgstr "Copiaţi /etc/corosync/corosync.conf şi /etc/ais/authkey (dacă există) pe nodul nou" +msgstr "Copiaţi /etc/corosync/corosync.conf şi /etc/corosync/authkey (dacă există) pe nodul nou" #. Tag: para #, fuzzy, no-c-format msgid "On the new node, populate it’s UUID using crm_uuid -w and the UUID from step 2" msgstr "Pe nodul nou, populaţi UUID-ul acestuia folosind crm_uuid -w şi UUID-ul prelevat de la pasul 2" #~ msgid "Provided you specified autojoin any in ha.cf, adding a new node is as simple as installing heartbeat and copying ha.cf and authkeys from an existing node." #~ msgstr "Dacă aţi specificat autojoin any în ha.cf, adăugarea unui nod nou este la fel de simpla ca şi instalarea Heartbeat şi copierea ha.cf şi a authkeys de pe un nod existent." #~ msgid "Tell the cluster to forget about the removed host: crm_node -R COROSYNC_ID" #~ msgstr "Comunicaţi clusterului să uite despre gazda înlăturată: crm_node -R COROSYNC_ID" #~ msgid "" #~ "cibadmin --delete --obj_type nodes --crm_xml '<node uname=\"pcmk-1\"/>'\n" #~ "\t cibadmin --delete --obj_type status --crm_xml '<node_state uname=\"pcmk-1\"/>'" #~ msgstr "" #~ "cibadmin --delete --obj_type nodes --crm_xml '<node uname=\"pcmk-1\"/>'\n" #~ "\t cibadmin --delete --obj_type status --crm_xml '<node_state uname=\"pcmk-1\"/>'" #~ msgid "The five-step guide to replacing an existing cluster node:" #~ msgstr "Ghidul în cinci paşi pentru înlocuirea unui nod existent din cluster:" #~ msgid "The seven-step guide to replacing an existing cluster node:" #~ msgstr "Ghidul în şapte paşi pentru înlocuirea unui nod existent din cluster"