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>June 20, 2007</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">
23 <holder>Google Inc.</holder>
31 <refmiscinfo>ganeti 1.2</refmiscinfo>
34 <refname>&dhpackage;</refname>
36 <refpurpose>node administration</refpurpose>
40 <command>&dhpackage; </command>
42 <arg choice="req">command</arg>
43 <arg>arguments...</arg>
47 <title>DESCRIPTION</title>
50 The <command>&dhpackage;</command> is used for managing the
51 (physical) nodes in the ganeti system.
56 <title>COMMANDS</title>
62 <command>add</command>
63 <arg>-s <replaceable>secondary_ip</replaceable></arg>
64 <arg choice="req"><replaceable>nodename</replaceable></arg>
68 Adds the given node to the cluster.
72 This command is used to join a new node to the cluster. You
73 will have to provide the password for root of the node to be
74 able to add the node in the cluster. The command needs to be
75 run on the ganeti master.
79 Note that the command is potentially destructive, as it will
80 forcibly join the specified host the cluster, not paying
81 attention to its current status (it could be already in a
86 The <option>-s</option> is used in dual-home clusters and
87 specifies the new node's IP in the secondary network. See the
88 discussion in <citerefentry>
89 <refentrytitle>gnt-cluster</refentrytitle>
90 <manvolnum>8</manvolnum> </citerefentry> for more
97 # gnt-node add node5.example.com
98 # gnt-node add -s 192.168.44.5 node5.example.com
104 <title>ADD-TAGS</title>
107 <command>add-tags</command>
108 <arg choice="opt">--from <replaceable>file</replaceable></arg>
109 <arg choice="req"><replaceable>nodename</replaceable></arg>
111 rep="repeat"><replaceable>tag</replaceable></arg>
115 Add tags to the given node. If any of the tags contains
116 invalid characters, the entire operation will abort.
120 If the <option>--from</option> option is given, the list of
121 tags will be extended with the contents of that file (each
122 line becomes a tag). In this case, there is not need to pass
123 tags on the command line (if you do, both sources will be
124 used). A file name of - will be interpreted as stdin.
129 <title>FAILOVER</title>
132 <command>failover</command>
134 <arg>--ignore-consistency</arg>
135 <arg choice="req"><replaceable>node</replaceable></arg>
139 This command will fail over all instances having the given
140 node as primary to their secondary nodes. This works only for
141 instances having a remote raid disk layout.
145 Normally the failover will check the consistency of the disks
146 before failing over the instance. If you are trying to migrate
147 instances off a dead node, this will fail. Use the
148 <option>--ignore-consistency</option> option for this purpose.
154 # gnt-node failover node1.example.com
163 <command>info</command>
164 <arg rep="repeat"><replaceable>node</replaceable></arg>
168 Show detailed information about the nodes in the cluster. If you
169 don't give any arguments, all nodes will be shows, otherwise the
170 output will be restricted to the given names.
178 <command>list</command>
179 <arg>--no-headers</arg>
180 <arg>--separator=<replaceable>SEPARATOR</replaceable></arg>
181 <arg>-o <replaceable>FIELD,...</replaceable></arg>
185 Lists the nodes in the cluster. If you give the
186 <option>--ip-info</option> option, the output contains just
187 the node name, primary ip and secondary ip. In case the
188 secondary ip is the same as the primary one, it will be listed
189 as <emphasis>"-"</emphasis>.
193 The <option>--no-headers</option> option will skip the initial
194 header line. The <option>--separator</option> option takes an
195 argument which denotes what will be used between the output
196 fields. Both these options are to help scripting.
200 The <option>-o</option> option takes a comma-separated list of
201 output fields. The available fields and their meaning are:
206 <simpara>the node name</simpara>
212 <simpara>the number of instances having this node as
219 <simpara>the number of instances having this node as a
220 secondary node</simpara>
226 <simpara>the primary ip of this node (used for cluster
227 communication)</simpara>
234 the secondary ip of this node (used for data
235 replication in dual-ip clusters, see <citerefentry>
236 <refentrytitle>gnt-cluster</refentrytitle>
237 <manvolnum>8</manvolnum>
245 <simpara>total disk space in the volume group used for
246 instance disk allocations</simpara>
252 <simpara>available disk space in the volume group</simpara>
258 <simpara>total memory on the physical node</simpara>
264 <simpara>the memory used by the node itself</simpara>
270 <simpara>memory available for instance
271 allocations</simpara>
278 Note that some of this fields are known from the configuration
279 of the cluster (<simplelist type="inline">
280 <member>name</member> <member>pinst</member>
281 <member>sinst</member> <member>pip</member>
282 <member>sip</member> </simplelist> and thus the master does
283 not need to contact the node for this data (making the listing
284 fast if only fields from this set are selected), whereas the
285 other fields are "live" fields and we need to make a query to
290 Depending on the virtualization type and implementation
291 details, the mtotal, mnode and mfree may have slighly varying
292 meanings. For example, some solutions share the node memory
293 with the pool of memory used for instances
294 (<acronym>UML</acronym>), whereas others have separate memory
295 for the node and for the instances (Xen).
300 <title>LIST-TAGS</title>
303 <command>list-tags</command>
304 <arg choice="req"><replaceable>nodename</replaceable></arg>
307 <para>List the tags of the given node.</para>
311 <title>REMOVE</title>
314 <command>remove</command>
315 <arg choice="req"><replaceable>nodename</replaceable></arg>
319 Removes a node from the cluster. Instances must be removed or
320 migrated to another cluster before.
326 # gnt-node remove node5.example.com
332 <title>REMOVE-TAGS</title>
334 <command>remove-tags</command>
335 <arg choice="opt">--from <replaceable>file</replaceable></arg>
336 <arg choice="req"><replaceable>nodename</replaceable></arg>
338 rep="repeat"><replaceable>tag</replaceable></arg>
342 Remove tags from the given node. If any of the tags are not
343 existing on the node, the entire operation will abort.
347 If the <option>--from</option> option is given, the list of
348 tags will be extended with the contents of that file (each
349 line becomes a tag). In this case, there is not need to pass
350 tags on the command line (if you do, both sources will be
351 used). A file name of - will be interpreted as stdin.
356 <title>VOLUMES</title>
359 <command>volumes</command>
360 <arg rep="repeat"><replaceable>node</replaceable></arg>
364 Lists all logical volumes and their physical disks from the node(s)
371 # gnt-node volumes node5.example.com
372 Node PhysDev VG Name Size Instance
373 node1.example.com /dev/hdc1 xenvg instance1.example.com-sda_11000.meta 128 instance1.example.com
374 node1.example.com /dev/hdc1 xenvg instance1.example.com-sda_11001.data 256 instance1.example.com
385 <!-- Keep this comment at the end of the file
390 sgml-minimize-attributes:nil
391 sgml-always-quote-attributes:t
394 sgml-parent-document:nil
395 sgml-default-dtd-file:nil
396 sgml-exposed-tags:nil
397 sgml-local-catalogs:nil
398 sgml-local-ecat-files:nil