X-Git-Url: https://code.grnet.gr/git/ganeti-local/blobdiff_plain/f69dab6d3a2b5eb3488bf3a8ae88ced091c0f221..1645d22dc118ee1df0a82a318c50d59861474627:/man/gnt-node.sgml
diff --git a/man/gnt-node.sgml b/man/gnt-node.sgml
index d44847b..836fc5d 100644
--- a/man/gnt-node.sgml
+++ b/man/gnt-node.sgml
@@ -2,7 +2,7 @@
- June 20, 2007">
+ February 12, 2009">
8">
@@ -20,6 +20,8 @@
20062007
+ 2008
+ 2009Google Inc.
&dhdate;
@@ -28,7 +30,7 @@
&dhucpackage;
&dhsection;
- ganeti 1.2
+ ganeti 2.0&dhpackage;
@@ -60,6 +62,7 @@
add
+ --readd-s secondary_ipnodename
@@ -88,7 +91,16 @@
discussion in gnt-cluster8 for more
- informations.
+ information.
+
+
+
+ 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.
@@ -131,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 raid 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
@@ -163,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.
@@ -201,17 +231,19 @@
list
+ --sync
+ --no-headers--separator=SEPARATOR
- -o FIELD,...
+
+ --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.
@@ -222,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:
@@ -232,20 +282,34 @@
- pinst
+ pinst_cntthe number of instances having this node as
primary
- sinst
+ pinst_list
+
+ the list of instances having this node as
+ primary, comma separated
+
+
+
+ sinst_cntthe number of instances having this node as a
secondary node
+ sinst_list
+
+ the list of instances having this node as a
+ secondary node, comma separated
+
+
+ pipthe primary ip of this node (used for cluster
@@ -296,12 +360,154 @@
allocations
+
+ bootid
+
+ the node bootid value; this is a linux specific
+ feature that assigns a new UUID to the node at each boot
+ and can be use to detect node reboots (by tracking
+ changes in this value)
+
+
+
+ tags
+
+ comma-separated list of the node's
+ tags
+
+
+
+ serial_no
+
+ the so called 'serial number' of the node;
+ this is a numeric field that is incremented each time
+ the node is modified, and it can be used to detect
+ modifications
+
+
+
+ ctime
+
+
+ the creation time of the node; note that this field
+ contains spaces and as such it's harder to parse
+
+
+ if this attribute is not present (e.g. when upgrading
+ from older versions), then "N/A" will be shown instead
+
+
+
+
+ mtime
+
+
+ the last modification time of the node; note that this
+ field contains spaces and as such it's harder to parse
+
+
+ if this attribute is not present (e.g. when upgrading
+ from older versions), then "N/A" will be shown instead
+
+
+
+
+ uuid
+
+ Show the UUID of the node (generated
+ automatically by Ganeti)
+
+
+
+
+ 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; the cluster
+ still communicates with drained nodes but excludes them
+ from allocation operations
+
+
+
+ offline
+
+ whether the node is offline or not; if offline,
+ the cluster does not communicate with offline nodes;
+ useful for nodes that are not reachable in order to
+ avoid delays
+
+
+
+ role
+
+
+ A condensed version of the node flags; this field will
+ output a one-character field, with the following
+ possible values:
+
+
+ M for the master
+ node
+
+
+ C for a master
+ candidate
+
+
+ R for a regular
+ node
+
+
+ D for a drained
+ node
+
+
+ O for an offline
+ node
+
+
+
+
+
+ If the value of the option starts with the character
+ +, the new fields will be added to the
+ default list. This allows to quickly see the default list plus
+ a few other fields, instead of retyping the entire list of
+ fields.
+
+
+
Note that some of this fields are known from the configuration
- of the cluster (
+ of the cluster (e.g. namepinstsinstpipsip and thus the master does
@@ -316,9 +522,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.
+
@@ -333,6 +544,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
+ ganeti7
+ .
+
+
+
+ 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
@@ -403,6 +689,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:
@@ -459,6 +755,204 @@ node1.example.com /dev/hdc1 xenvg instance1.example.com-sda_11001.data 256 inst
+
+ PHYSICAL-VOLUMES
+
+
+ physical-volumes
+ --no-headers
+ --human-readable
+ --separator=SEPARATOR
+ --storage-type=STORAGE_TYPE
+ --output=FIELDS
+
+ node
+
+
+
+ Lists all physical volumes and their details from the node(s) provided.
+
+
+
+ The option will skip the initial header
+ line. The option takes an argument which
+ denotes what will be used between the output fields. Both these options
+ are to help scripting.
+
+
+
+ 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 can be used to choose a
+ storage unit type. Possible choices are lvm-pv,
+ lvm-vg or file. Depending on the
+ storage type, the available output fields change.
+
+
+
+ The option takes a comma-separated list of
+ output fields. The available fields and their meaning are:
+
+
+ node
+
+ the node name on which the volume exists
+
+
+
+ name
+
+ the physical drive name
+
+
+
+ size
+
+
+ the physical drive size
+ (lvm-pv and lvm-vg only)
+
+
+
+
+ used
+
+
+ used disk space
+ (lvm-pv and file only)
+
+
+
+
+ free
+
+
+ available disk space
+ (lvm-pv and file only)
+
+
+
+
+ allocatable
+
+
+ whether physical volume is allocatable
+ (lvm-pv only)
+
+
+
+
+
+
+
+ Example:
+
+# gnt-node physical-volumes node5.example.com
+Node Name Size Used Free
+node5.example.com /dev/sda7 673.8G 0M 673.8G
+node5.example.com /dev/sdb1 698.6G 1.3G 697.4G
+
+
+
+
+
+ MODIFY-VOLUME
+
+
+ modify-volume
+
+
+ node
+ storage-type
+ volume-name
+
+
+
+ Modifies storage volumes on a node. Only LVM physical volumes can be
+ modified at the moment. They have a storage type of lvm-pv.
+
+
+
+ Example:
+
+# gnt-node modify-volume --allocatable no node5.example.com lvm-pv /dev/sdb1
+
+
+
+
+
+ REPAIR-VOLUME
+
+
+ repair-volume
+ node
+ storage-type
+ volume-name
+
+
+
+ Repairs a storage volume on a node. Only LVM volume groups can be
+ repaired at this time. They have the storage type
+ lvm-vg.
+
+
+
+ On LVM volume groups, repair-volume runs
+ vgreduce --removemissing.
+
+
+
+
+ Running this command can lead to data loss. Use it with care.
+
+
+
+
+ Example:
+
+# gnt-node repair-volume node5.example.com lvm-vg xenvg
+
+
+
+
+
+ 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;