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
107 <command>info</command>
108 <arg rep="repeat"><replaceable>node</replaceable></arg>
112 Show detailed information about the nodes in the cluster. If you
113 don't give any arguments, all nodes will be shows, otherwise the
114 output will be restricted to the given names.
122 <command>list</command>
123 <arg>--no-headers</arg>
124 <arg>--separator=<replaceable>SEPARATOR</replaceable></arg>
125 <arg>-o <replaceable>FIELD,...</replaceable></arg>
129 Lists the nodes in the cluster. If you give the
130 <option>--ip-info</option> option, the output contains just
131 the node name, primary ip and secondary ip. In case the
132 secondary ip is the same as the primary one, it will be listed
133 as <emphasis>"-"</emphasis>.
137 The <option>--no-headers</option> option will skip the initial
138 header line. The <option>--separator</option> option takes an
139 argument which denotes what will be used between the output
140 fields. Both these options are to help scripting.
144 The <option>-o</option> option takes a comma-separated list of
145 output fields. The available fields and their meaning are:
150 <simpara>the node name</simpara>
156 <simpara>the number of instances having this node as
163 <simpara>the number of instances having this node as a
164 secondary node</simpara>
170 <simpara>the primary ip of this node (used for cluster
171 communication)</simpara>
178 the secondary ip of this node (used for data
179 replication in dual-ip clusters, see <citerefentry>
180 <refentrytitle>gnt-cluster</refentrytitle>
181 <manvolnum>8</manvolnum>
189 <simpara>total disk space in the volume group used for
190 instance disk allocations</simpara>
196 <simpara>available disk space in the volume group</simpara>
202 <simpara>total memory on the physical node</simpara>
208 <simpara>the memory used by the node itself</simpara>
214 <simpara>memory available for instance
215 allocations</simpara>
222 Note that some of this fields are known from the configuration
223 of the cluster (<simplelist type="inline">
224 <member>name</member> <member>pinst</member>
225 <member>sinst</member> <member>pip</member>
226 <member>sip</member> </simplelist> and thus the master does
227 not need to contact the node for this data (making the listing
228 fast if only fields from this set are selected), whereas the
229 other fields are "live" fields and we need to make a query to
234 Depending on the virtualization type and implementation
235 details, the mtotal, mnode and mfree may have slighly varying
236 meanings. For example, some solutions share the node memory
237 with the pool of memory used for instances
238 (<acronym>UML</acronym>), whereas others have separate memory
239 for the node and for the instances (Xen).
244 <title>REMOVE</title>
247 <command>remove</command>
248 <arg choice="req"><replaceable>nodename</replaceable></arg>
252 Removes a node from the cluster. Instances must be removed or
253 migrated to another cluster before.
259 # gnt-node remove node5.example.com
270 <!-- Keep this comment at the end of the file
275 sgml-minimize-attributes:nil
276 sgml-always-quote-attributes:t
279 sgml-parent-document:nil
280 sgml-default-dtd-file:nil
281 sgml-exposed-tags:nil
282 sgml-local-catalogs:nil
283 sgml-local-ecat-files:nil