1 <!doctype refentry PUBLIC "-//OASIS//DTD DocBook V4.1//EN" [
3 <!-- Fill in your name for FIRSTNAME and SURNAME. -->
4 <!-- Please adjust the date whenever revising the manpage. -->
5 <!ENTITY dhdate "<date>February 12, 2009</date>">
6 <!-- SECTION should be 1-8, maybe w/ subsection other parameters are
7 allowed: see man(7), man(1). -->
8 <!ENTITY dhsection "<manvolnum>8</manvolnum>">
9 <!ENTITY dhucpackage "<refentrytitle>gnt-node</refentrytitle>">
10 <!ENTITY dhpackage "gnt-node">
12 <!ENTITY debian "<productname>Debian</productname>">
13 <!ENTITY gnu "<acronym>GNU</acronym>">
14 <!ENTITY gpl "&gnu; <acronym>GPL</acronym>">
15 <!ENTITY footer SYSTEM "footer.sgml">
25 <holder>Google Inc.</holder>
33 <refmiscinfo>ganeti 2.0</refmiscinfo>
36 <refname>&dhpackage;</refname>
38 <refpurpose>node administration</refpurpose>
42 <command>&dhpackage; </command>
44 <arg choice="req">command</arg>
45 <arg>arguments...</arg>
49 <title>DESCRIPTION</title>
52 The <command>&dhpackage;</command> is used for managing the
53 (physical) nodes in the ganeti system.
58 <title>COMMANDS</title>
64 <command>add</command>
66 <arg>-s <replaceable>secondary_ip</replaceable></arg>
67 <arg choice="req"><replaceable>nodename</replaceable></arg>
71 Adds the given node to the cluster.
75 This command is used to join a new node to the cluster. You
76 will have to provide the password for root of the node to be
77 able to add the node in the cluster. The command needs to be
78 run on the ganeti master.
82 Note that the command is potentially destructive, as it will
83 forcibly join the specified host the cluster, not paying
84 attention to its current status (it could be already in a
89 The <option>-s</option> is used in dual-home clusters and
90 specifies the new node's IP in the secondary network. See the
91 discussion in <citerefentry>
92 <refentrytitle>gnt-cluster</refentrytitle>
93 <manvolnum>8</manvolnum> </citerefentry> for more
98 In case you're readding a node after hardware failure, you can
99 use the <option>--readd</option> parameter. In this case, you
100 don't need to pass the secondary IP again, it will reused from
101 the cluster. Also, the <literal>drained</literal> and
102 <literal>offline</literal> flags of the node will be cleared
109 # gnt-node add node5.example.com
110 # gnt-node add -s 192.168.44.5 node5.example.com
116 <title>ADD-TAGS</title>
119 <command>add-tags</command>
120 <arg choice="opt">--from <replaceable>file</replaceable></arg>
121 <arg choice="req"><replaceable>nodename</replaceable></arg>
123 rep="repeat"><replaceable>tag</replaceable></arg>
127 Add tags to the given node. If any of the tags contains
128 invalid characters, the entire operation will abort.
132 If the <option>--from</option> option is given, the list of
133 tags will be extended with the contents of that file (each
134 line becomes a tag). In this case, there is not need to pass
135 tags on the command line (if you do, both sources will be
136 used). A file name of - will be interpreted as stdin.
141 <title>EVACUATE</title>
144 <command>evacuate</command>
147 <arg>--iallocator <replaceable>NAME</replaceable></arg>
148 <arg>--new-secondary <replaceable>destination_node</replaceable></arg>
150 <arg choice="req"><replaceable>node</replaceable></arg>
154 This command will move all secondary instances away from the
155 given node. It works only for instances having a drbd disk
160 The new location for the instances can be specified in two ways:
163 <simpara>as a single node for all instances, via the
164 <option>--new-secondary</option> option</simpara>
167 <simpara>or via the <option>--iallocator</option> option,
168 giving a script name as parameter, so each instance will
169 be in turn placed on the (per the script) optimal
178 # gnt-node evacuate -I dumb node3.example.com
184 <title>FAILOVER</title>
187 <command>failover</command>
189 <arg>--ignore-consistency</arg>
190 <arg choice="req"><replaceable>node</replaceable></arg>
194 This command will fail over all instances having the given
195 node as primary to their secondary nodes. This works only for
196 instances having a drbd disk template.
200 Normally the failover will check the consistency of the disks
201 before failing over the instance. If you are trying to migrate
202 instances off a dead node, this will fail. Use the
203 <option>--ignore-consistency</option> option for this purpose.
209 # gnt-node failover node1.example.com
218 <command>info</command>
219 <arg rep="repeat"><replaceable>node</replaceable></arg>
223 Show detailed information about the nodes in the cluster. If you
224 don't give any arguments, all nodes will be shows, otherwise the
225 output will be restricted to the given names.
233 <command>list</command>
236 <arg>--no-headers</arg>
237 <arg>--separator=<replaceable>SEPARATOR</replaceable></arg>
239 <arg>--units=<replaceable>UNITS</replaceable></arg>
240 <arg>-o <replaceable>[+]FIELD,...</replaceable></arg>
242 <arg rep="repeat">node</arg>
246 Lists the nodes in the cluster.
250 The <option>--no-headers</option> option will skip the initial
251 header line. The <option>--separator</option> option takes an
252 argument which denotes what will be used between the output
253 fields. Both these options are to help scripting.
257 The units used to display the numeric values in the output
258 varies, depending on the options given. By default, the values
259 will be formatted in the most appropriate unit. If the
260 <option>--separator</option> option is given, then the values
261 are shown in mebibytes to allow parsing by scripts. In both
262 cases, the <option>--units</option> option can be used to
263 enforce a given output unit.
267 By default, the query of nodes will be done in parallel with
268 any running jobs. This might give inconsistent results for the
269 free disk/memory. The <option>--sync</option> can be used to
270 grab locks for all the nodes and ensure consistent view of the
271 cluster (but this might stall the query for a long time).
275 The <option>-o</option> option takes a comma-separated list of
276 output fields. The available fields and their meaning are:
281 <simpara>the node name</simpara>
285 <term>pinst_cnt</term>
287 <simpara>the number of instances having this node as
292 <term>pinst_list</term>
294 <simpara>the list of instances having this node as
295 primary, comma separated</simpara>
299 <term>sinst_cnt</term>
301 <simpara>the number of instances having this node as a
302 secondary node</simpara>
306 <term>sinst_list</term>
308 <simpara>the list of instances having this node as a
309 secondary node, comma separated</simpara>
315 <simpara>the primary ip of this node (used for cluster
316 communication)</simpara>
323 the secondary ip of this node (used for data
324 replication in dual-ip clusters, see <citerefentry>
325 <refentrytitle>gnt-cluster</refentrytitle>
326 <manvolnum>8</manvolnum>
334 <simpara>total disk space in the volume group used for
335 instance disk allocations</simpara>
341 <simpara>available disk space in the volume group</simpara>
347 <simpara>total memory on the physical node</simpara>
353 <simpara>the memory used by the node itself</simpara>
359 <simpara>memory available for instance
360 allocations</simpara>
366 <simpara>the node bootid value; this is a linux specific
367 feature that assigns a new UUID to the node at each boot
368 and can be use to detect node reboots (by tracking
369 changes in this value)</simpara>
375 <simpara>comma-separated list of the node's
380 <term>serial_no</term>
382 <simpara>the so called 'serial number' of the instance;
383 this is a numeric field that is incremented each time
384 the instance is modified, and it can be used to detect
385 modifications</simpara>
391 <simpara>the toal number of logical processors</simpara>
397 <simpara>the number of NUMA domains on the node, if the
398 hypervisor can export this information</simpara>
402 <term>csockets</term>
404 <simpara>the number of physical CPU sockets, if the
405 hypervisor can export this information</simpara>
409 <term>master_candidate</term>
411 <simpara>whether the node is a master candidate or not</simpara>
417 <simpara>whether the node is drained or not; the cluster
418 still communicates with drained nodes but excludes them
419 from allocation operations</simpara>
425 <simpara>whether the node is offline or not; if offline,
426 the cluster does not communicate with offline nodes;
427 useful for nodes that are not reachable in order to
428 avoid delays</simpara>
435 A condensed version of the node flags; this field will
436 output a one-character field, with the following
440 <simpara><emphasis>M</emphasis> for the master
444 <simpara><emphasis>C</emphasis> for a master
448 <simpara><emphasis>R</emphasis> for a regular
452 <simpara><emphasis>D</emphasis> for a drained
456 <simpara><emphasis>O</emphasis> for an offline
467 If the value of the option starts with the character
468 <constant>+</constant>, the new fields will be added to the
469 default list. This allows to quickly see the default list plus
470 a few other fields, instead of retyping the entire list of
475 Note that some of this fields are known from the configuration
476 of the cluster (e.g. <simplelist type="inline">
477 <member>name</member> <member>pinst</member>
478 <member>sinst</member> <member>pip</member>
479 <member>sip</member> </simplelist> and thus the master does
480 not need to contact the node for this data (making the listing
481 fast if only fields from this set are selected), whereas the
482 other fields are "live" fields and we need to make a query to
487 Depending on the virtualization type and implementation
488 details, the mtotal, mnode and mfree may have slighly varying
489 meanings. For example, some solutions share the node memory
490 with the pool of memory used for instances
491 (<acronym>KVM</acronym>), whereas others have separate memory
492 for the node and for the instances (Xen).
496 If no node names are given, then all nodes are
497 queried. Otherwise, only the given nodes will be listed.
502 <title>LIST-TAGS</title>
505 <command>list-tags</command>
506 <arg choice="req"><replaceable>nodename</replaceable></arg>
509 <para>List the tags of the given node.</para>
513 <title>MIGRATE</title>
515 <command>migrate</command>
517 <arg>--non-live</arg>
518 <arg choice="req"><replaceable>node</replaceable></arg>
522 This command will migrate all instances having the given
523 node as primary to their secondary nodes. This works only for
524 instances having a drbd disk template.
528 As for the <command>gnt-instance migrate</command> command,
529 the <option>--no-live</option> option can be given to do a
536 # gnt-node migrate node1.example.com
543 <title>MODIFY</title>
545 <command>modify</command>
548 <arg>--master-candidate=<option>yes|no</option></arg>
549 <arg>--drained=<option>yes|no</option></arg>
550 <arg>--offline=<option>yes|no</option></arg>
551 <arg choice="req"><replaceable>node</replaceable></arg>
555 This command changes the role of the node. Each options takes
556 either a literal <literal>yes</literal> or
557 <literal>no</literal>, and only one option should be given as
558 <literal>yes</literal>. The meaning of the roles are described
559 in the manpage <citerefentry>
560 <refentrytitle>ganeti</refentrytitle> <manvolnum>7</manvolnum>
565 In case a node is demoted from the master candidate role, but
566 there are not enough new nodes for this case, the operation
567 will be refused. To override this check, pass the
568 <option>--force</option> option.
572 Example (setting a node offline, which will demote it from
573 master candidate role if is in that role):
575 # gnt-node modify --offline=yes node1.example.com
579 <para>Example (setting the node back to online and master candidate):
581 # gnt-node modify --offline=no --master-candidate=yes node1.example.com
588 <title>REMOVE</title>
591 <command>remove</command>
592 <arg choice="req"><replaceable>nodename</replaceable></arg>
596 Removes a node from the cluster. Instances must be removed or
597 migrated to another cluster before.
603 # gnt-node remove node5.example.com
609 <title>REMOVE-TAGS</title>
611 <command>remove-tags</command>
612 <arg choice="opt">--from <replaceable>file</replaceable></arg>
613 <arg choice="req"><replaceable>nodename</replaceable></arg>
615 rep="repeat"><replaceable>tag</replaceable></arg>
619 Remove tags from the given node. If any of the tags are not
620 existing on the node, the entire operation will abort.
624 If the <option>--from</option> option is given, the list of
625 tags will be extended with the contents of that file (each
626 line becomes a tag). In this case, there is not need to pass
627 tags on the command line (if you do, both sources will be
628 used). A file name of - will be interpreted as stdin.
633 <title>VOLUMES</title>
636 <command>volumes</command>
637 <arg>--no-headers</arg>
638 <arg>--human-readable</arg>
639 <arg>--separator=<replaceable>SEPARATOR</replaceable></arg>
640 <arg>--output=<replaceable>FIELDS</replaceable></arg>
642 <arg rep="repeat"><replaceable>node</replaceable></arg>
646 Lists all logical volumes and their physical disks from the node(s)
651 The <option>--no-headers</option> option will skip the initial
652 header line. The <option>--separator</option> option takes an
653 argument which denotes what will be used between the output
654 fields. Both these options are to help scripting.
658 The units used to display the numeric values in the output
659 varies, depending on the options given. By default, the values
660 will be formatted in the most appropriate unit. If the
661 <option>--separator</option> option is given, then the values
662 are shown in mebibytes to allow parsing by scripts. In both
663 cases, the <option>--units</option> option can be used to
664 enforce a given output unit.
668 The <option>-o</option> option takes a comma-separated list of
669 output fields. The available fields and their meaning are:
674 <simpara>the node name on which the volume exists</simpara>
680 <simpara>the physical drive (on which the LVM physical
681 volume lives)</simpara>
687 <simpara>the volume group name</simpara>
693 <simpara>the logical volume name</simpara>
699 <simpara>the logical volume size</simpara>
703 <term>instance</term>
705 <simpara>The name of the instance to which this volume
706 belongs, or (in case it's an orphan volume) the
707 character <quote>-</quote></simpara>
716 # gnt-node volumes node5.example.com
717 Node PhysDev VG Name Size Instance
718 node1.example.com /dev/hdc1 xenvg instance1.example.com-sda_11000.meta 128 instance1.example.com
719 node1.example.com /dev/hdc1 xenvg instance1.example.com-sda_11001.data 256 instance1.example.com
730 <!-- Keep this comment at the end of the file
735 sgml-minimize-attributes:nil
736 sgml-always-quote-attributes:t
739 sgml-parent-document:nil
740 sgml-default-dtd-file:nil
741 sgml-exposed-tags:nil
742 sgml-local-catalogs:nil
743 sgml-local-ecat-files:nil