X-Git-Url: https://code.grnet.gr/git/ganeti-local/blobdiff_plain/48c4dfa88692d86045075cc83e6fc39b182facaa..1b54fc6c2fd92b614c029cc5312d02f9f1526253:/man/gnt-node.sgml diff --git a/man/gnt-node.sgml b/man/gnt-node.sgml index 9664fd2..f00440d 100644 --- a/man/gnt-node.sgml +++ b/man/gnt-node.sgml @@ -2,7 +2,7 @@ - June 20, 2007"> + February 12, 2009"> 8"> @@ -21,6 +21,7 @@ 2006 2007 2008 + 2009 Google Inc. &dhdate; @@ -29,7 +30,7 @@ &dhucpackage; &dhsection; - ganeti 1.2 + ganeti 2.0 &dhpackage; @@ -94,8 +95,12 @@ - In case you're readding a node after hardware failure, you - can use the parameter. + In case you're readding a node after hardware failure, you can + use the parameter. In this case, you + don't need to pass the secondary IP again, it will reused from + the cluster. Also, the drained and + offline flags of the node will be cleared + before re-adding it. @@ -138,21 +143,39 @@ evacuate -f - source_node - destination_node + + --iallocator NAME + --new-secondary destination_node + + node - This command will change the secondary node from the source - node to the destination node for all instances having the - source node as secondary. It works only for instances having - a remote_raid1 or drbd disk layout. + This command will move all secondary instances away from the + given node. It works only for instances having a drbd disk + template. + + + + The new location for the instances can be specified in two ways: + + + as a single node for all instances, via the + option + + + or via the option, + giving a script name as parameter, so each instance will + be in turn placed on the (per the script) optimal + node + + Example: - # gnt-node evacuate node1.example.com node2.example.com + # gnt-node evacuate -I dumb node3.example.com @@ -170,7 +193,7 @@ This command will fail over all instances having the given node as primary to their secondary nodes. This works only for - instances having a remote raid disk layout. + instances having a drbd disk template. @@ -208,17 +231,19 @@ list + --sync + --no-headers --separator=SEPARATOR + + --units=UNITS -o [+]FIELD,... + + node - Lists the nodes in the cluster. If you give the - option, the output contains just - the node name, primary ip and secondary ip. In case the - secondary ip is the same as the primary one, it will be listed - as "-". + Lists the nodes in the cluster. @@ -229,6 +254,24 @@ + The units used to display the numeric values in the output + varies, depending on the options given. By default, the values + will be formatted in the most appropriate unit. If the + option is given, then the values + are shown in mebibytes to allow parsing by scripts. In both + cases, the option can be used to + enforce a given output unit. + + + + By default, the query of nodes will be done in parallel with + any running jobs. This might give inconsistent results for the + free disk/memory. The can be used to + grab locks for all the nodes and ensure consistent view of the + cluster (but this might stall the query for a long time). + + + The option takes a comma-separated list of output fields. The available fields and their meaning are: @@ -326,6 +369,60 @@ changes in this value) + + tags + + comma-separated list of the node's + tags + + + + serial_no + + the so called 'serial number' of the instance; + this is a numeric field that is incremented each time + the instance is modified, and it can be used to detect + modifications + + + + ctotal + + the toal number of logical processors + + + + cnodes + + the number of NUMA domains on the node, if the + hypervisor can export this information + + + + csockets + + the number of physical CPU sockets, if the + hypervisor can export this information + + + + master_candidate + + whether the node is a master candidate or not + + + + drained + + whether the node is drained or not + + + + offline + + whether the node is offline or not + + @@ -339,7 +436,7 @@ Note that some of this fields are known from the configuration - of the cluster ( + of the cluster (e.g. name pinst sinst pip sip and thus the master does @@ -354,9 +451,14 @@ details, the mtotal, mnode and mfree may have slighly varying meanings. For example, some solutions share the node memory with the pool of memory used for instances - (UML), whereas others have separate memory + (KVM), whereas others have separate memory for the node and for the instances (Xen). + + + If no node names are given, then all nodes are + queried. Otherwise, only the given nodes will be listed. + @@ -371,6 +473,81 @@ + MIGRATE + + migrate + -f + --non-live + node + + + + This command will migrate all instances having the given + node as primary to their secondary nodes. This works only for + instances having a drbd disk template. + + + + As for the gnt-instance migrate command, + the option can be given to do a + non-live migration. + + + + Example: + + # gnt-node migrate node1.example.com + + + + + + + MODIFY + + modify + -f + --submit + --master-candidate= + --drained= + --offline= + node + + + + This command changes the role of the node. Each options takes + either a literal yes or + no, and only one option should be given as + yes. The meaning of the roles are described + in the manpage + ganeti 7 + . + + + + In case a node is demoted from the master candidate role, but + there are not enough new nodes for this case, the operation + will be refused. To override this check, pass the + option. + + + + Example (setting a node offline, which will demote it from + master candidate role if is in that role): + +# gnt-node modify --offline=yes node1.example.com + + + + Example (setting the node back to online and master candidate): + +# gnt-node modify --offline=no --master-candidate=yes node1.example.com + + + + + + REMOVE @@ -441,6 +618,16 @@ + The units used to display the numeric values in the output + varies, depending on the options given. By default, the values + will be formatted in the most appropriate unit. If the + option is given, then the values + are shown in mebibytes to allow parsing by scripts. In both + cases, the option can be used to + enforce a given output unit. + + + The option takes a comma-separated list of output fields. The available fields and their meaning are: @@ -497,6 +684,36 @@ node1.example.com /dev/hdc1 xenvg instance1.example.com-sda_11001.data 256 inst + + POWERCYCLE + + + powercycle + + + node + + + + This commands (tries to) forcefully reboot a node. It is a + command that can be used if the node environemnt is broken, + such that the admin can no longer login over ssh, but the + ganeti node daemon is still working. + + + + Note that this command is not guaranteed to work; it depends + on the hypervisor how effective is the reboot attempt. For + Linux, this command require that the kernel option + CONFIG_MAGIC_SYSRQ is enabled. + + + + The option can be used to skip + confirmation, while the option is + needed if the target node is the master node. + + &footer;