1 gnt-instance(8) Ganeti | Version @GANETI_VERSION@
2 =================================================
7 gnt-instance - Ganeti instance administration
12 **gnt-instance** {command} [arguments...]
17 The **gnt-instance** command is used for instance administration in
23 Creation/removal/querying
24 ~~~~~~~~~~~~~~~~~~~~~~~~~
30 | {-t|\--disk-template {diskless | file \| plain \| drbd \| rbd}}
31 | {\--disk=*N*: {size=*VAL* \| adopt=*LV*}[,options...]
32 | \| {size=*VAL*,provider=*PROVIDER*}[,param=*value*... ][,options...]
33 | \| {-s|\--os-size} *SIZE*}
34 | [\--no-ip-check] [\--no-name-check] [\--no-conflicts-check]
35 | [\--no-start] [\--no-install]
36 | [\--net=*N* [:options...] \| \--no-nics]
37 | [{-B|\--backend-parameters} *BEPARAMS*]
38 | [{-H|\--hypervisor-parameters} *HYPERVISOR* [: option=*value*... ]]
39 | [{-O|\--os-parameters} *param*=*value*... ]
40 | [\--file-storage-dir *dir\_path*] [\--file-driver {loop \| blktap}]
41 | {{-n|\--node} *node[:secondary-node]* \| {-I|\--iallocator} *name*}
42 | {{-o|\--os-type} *os-type*}
47 Creates a new instance on the specified host. The *instance* argument
48 must be in DNS, but depending on the bridge/routing setup, need not be
49 in the same network as the nodes in the cluster.
51 The ``disk`` option specifies the parameters for the disks of the
52 instance. The numbering of disks starts at zero, and at least one disk
53 needs to be passed. For each disk, either the size or the adoption
54 source needs to be given. The size is interpreted (when no unit is
55 given) in mebibytes. You can also use one of the suffixes *m*, *g* or
56 *t* to specify the exact the units used; these suffixes map to
57 mebibytes, gibibytes and tebibytes. Each disk can also take these
58 parameters (all optional):
61 The access mode. Either ``ro`` (read-only) or the default ``rw``
65 this option specifies a name for the disk, which can be used as a disk
66 identifier. An instance can not have two disks with the same name.
69 The LVM volume group. This works only for LVM and DRBD devices.
72 This options specifies a different VG for the metadata device. This
73 works only for DRBD devices
75 When creating ExtStorage disks, also arbitrary parameters can be passed,
76 to the ExtStorage provider. Those parameters are passed as additional
77 comma separated options. Therefore, an ExtStorage disk provided by
78 provider ``pvdr1`` with parameters ``param1``, ``param2`` would be
79 passed as ``--disk 0:size=10G,provider=pvdr1,param1=val1,param2=val2``.
81 When using the ``adopt`` key in the disk definition, Ganeti will
82 reuse those volumes (instead of creating new ones) as the
83 instance's disks. Ganeti will rename these volumes to the standard
84 format, and (without installing the OS) will use them as-is for the
85 instance. This allows migrating instances from non-managed mode
86 (e.g. plain KVM with LVM) to being managed via Ganeti. Please note that
87 this works only for the \`plain' disk template (see below for
90 Alternatively, a single-disk instance can be created via the ``-s``
91 option which takes a single argument, the size of the disk. This is
92 similar to the Ganeti 1.2 version (but will only create one disk).
94 The minimum disk specification is therefore ``--disk 0:size=20G`` (or
95 ``-s 20G`` when using the ``-s`` option), and a three-disk instance
96 can be specified as ``--disk 0:size=20G --disk 1:size=4G --disk
99 The minimum information needed to specify an ExtStorage disk are the
100 ``size`` and the ``provider``. For example:
101 ``--disk 0:size=20G,provider=pvdr1``.
103 The ``--no-ip-check`` skips the checks that are done to see if the
104 instance's IP is not already alive (i.e. reachable from the master
107 The ``--no-name-check`` skips the check for the instance name via
108 the resolver (e.g. in DNS or /etc/hosts, depending on your setup).
109 Since the name check is used to compute the IP address, if you pass
110 this option you must also pass the ``--no-ip-check`` option.
112 If you don't want the instance to automatically start after
113 creation, this is possible via the ``--no-start`` option. This will
114 leave the instance down until a subsequent **gnt-instance start**
117 The NICs of the instances can be specified via the ``--net``
118 option. By default, one NIC is created for the instance, with a
119 random MAC, and set up according the the cluster level NIC
120 parameters. Each NIC can take these parameters (all optional):
123 either a value or 'generate' to generate a new unique MAC
126 specifies the IP address assigned to the instance from the Ganeti
127 side (this is not necessarily what the instance will use, but what
128 the node expects the instance to use). Note that if an IP in the
129 range of a network configured with **gnt-network**\(8) is used,
130 and the NIC is not already connected to it, this network has to be
131 passed in the **network** parameter if this NIC is meant to be
132 connected to the said network. ``--no-conflicts-check`` can be used
133 to override this check. The special value **pool** causes Ganeti to
134 select an IP from the the network the NIC is or will be connected to.
137 specifies the connection mode for this NIC: routed, bridged or
141 in bridged or openvswitch mode specifies the interface to attach
142 this NIC to, in routed mode it's intended to differentiate between
143 different routing tables/instance groups (but the meaning is
144 dependent on the network script, see **gnt-cluster**\(8) for more
145 details). Note that openvswitch support is also hypervisor
149 derives the mode and the link from the settings of the network
150 which is identified by its name. If the network option is chosen,
151 link and mode must not be specified. Note that the mode and link
152 depend on the network-to-nodegroup connection, thus allowing
153 different nodegroups to be connected to the same network in
157 this option specifies a name for the NIC, which can be used as a NIC
158 identifier. An instance can not have two NICs with the same name.
161 Of these "mode" and "link" are NIC parameters, and inherit their
162 default at cluster level. Alternatively, if no network is desired for
163 the instance, you can prevent the default of one NIC with the
164 ``--no-nics`` option.
166 The ``-o (--os-type)`` option specifies the operating system to be
167 installed. The available operating systems can be listed with
168 **gnt-os list**. Passing ``--no-install`` will however skip the OS
169 installation, allowing a manual import if so desired. Note that the
170 no-installation mode will automatically disable the start-up of the
171 instance (without an OS, it most likely won't be able to start-up
174 The ``-B (--backend-parameters)`` option specifies the backend
175 parameters for the instance. If no such parameters are specified, the
176 values are inherited from the cluster. Possible parameters are:
179 the maximum memory size of the instance; as usual, suffixes can be
180 used to denote the unit, otherwise the value is taken in mebibytes
183 the minimum memory size of the instance; as usual, suffixes can be
184 used to denote the unit, otherwise the value is taken in mebibytes
187 the number of VCPUs to assign to the instance (if this value makes
188 sense for the hypervisor)
191 whether the instance is considered in the N+1 cluster checks
192 (enough redundancy in the cluster to survive a node failure)
195 ``True`` or ``False``, whether the instance must be failed over
196 (shut down and rebooted) always or it may be migrated (briefly
199 Note that before 2.6 Ganeti had a ``memory`` parameter, which was the
200 only value of memory an instance could have. With the
201 ``maxmem``/``minmem`` change Ganeti guarantees that at least the minimum
202 memory is always available for an instance, but allows more memory to be
203 used (up to the maximum memory) should it be free.
205 The ``-H (--hypervisor-parameters)`` option specified the hypervisor
206 to use for the instance (must be one of the enabled hypervisors on the
207 cluster) and optionally custom parameters for this instance. If not
208 other options are used (i.e. the invocation is just -H *NAME*) the
209 instance will inherit the cluster options. The defaults below show the
210 cluster defaults at cluster creation time.
212 The possible hypervisor options are as follows:
215 Valid for the Xen HVM and KVM hypervisors.
217 A string value denoting the boot order. This has different meaning
218 for the Xen HVM hypervisor and for the KVM one.
220 For Xen HVM, The boot order is a string of letters listing the boot
221 devices, with valid device letters being:
235 The default is not to set an HVM boot order, which is interpreted
238 For KVM the boot order is either "floppy", "cdrom", "disk" or
239 "network". Please note that older versions of KVM couldn't netboot
240 from virtio interfaces. This has been fixed in more recent versions
241 and is confirmed to work at least with qemu-kvm 0.11.1. Also note
242 that if you have set the ``kernel_path`` option, that will be used
243 for booting, and this setting will be silently ignored.
246 Valid for the Xen HVM and PVM hypervisors.
248 Relevant to non-pvops guest kernels, in which the disk device names
249 are given by the host. Allows one to specify 'xvd', which helps run
250 Red Hat based installers, driven by anaconda.
253 Valid for the KVM hypervisor.
255 The path to a floppy disk image to attach to the instance. This
256 is useful to install Windows operating systems on Virt/IO disks
257 because you can specify here the floppy for the drivers at
261 Valid for the Xen HVM and KVM hypervisors.
263 The path to a CDROM image to attach to the instance.
266 Valid for the KVM hypervisor.
268 The path to a second CDROM image to attach to the instance.
269 **NOTE**: This image can't be used to boot the system. To do that
270 you have to use the 'cdrom\_image\_path' option.
273 Valid for the Xen HVM and KVM hypervisors.
275 This parameter determines the way the network cards are presented
276 to the instance. The possible options are:
278 - rtl8139 (default for Xen HVM) (HVM & KVM)
279 - ne2k\_isa (HVM & KVM)
280 - ne2k\_pci (HVM & KVM)
286 - paravirtual (default for KVM) (HVM & KVM)
289 Valid for the Xen HVM hypervisor.
291 This parameter specifies the vif type of the nic configuration
292 of the instance. Unsetting the value leads to no type being specified
293 in the configuration. Note that this parameter only takes effect when
294 the 'nic_type' is not set. The possible options are:
300 Valid for the Xen HVM and KVM hypervisors.
302 This parameter determines the way the disks are presented to the
303 instance. The possible options are:
305 - ioemu [default] (HVM & KVM)
314 Valid for the KVM hypervisor.
316 This parameter determines the way the cdroms disks are presented
317 to the instance. The default behavior is to get the same value of
318 the earlier parameter (disk_type). The possible options are:
329 Valid for the Xen HVM and KVM hypervisors.
331 Specifies the address that the VNC listener for this instance
332 should bind to. Valid values are IPv4 addresses. Use the address
333 0.0.0.0 to bind to all available interfaces (this is the default)
334 or specify the address of one of the interfaces on the node to
335 restrict listening to that interface.
338 Valid for the KVM hypervisor.
340 A boolean option that controls whether the VNC connection is
344 Valid for the KVM hypervisor.
346 If ``vnc_tls`` is enabled, this options specifies the path to the
347 x509 certificate to use.
350 Valid for the KVM hypervisor.
353 Valid for the KVM hypervisor.
355 Specifies the address or interface on which the SPICE server will
356 listen. Valid values are:
358 - IPv4 addresses, including 0.0.0.0 and 127.0.0.1
359 - IPv6 addresses, including :: and ::1
360 - names of network interfaces
362 If a network interface is specified, the SPICE server will be bound
363 to one of the addresses of that interface.
366 Valid for the KVM hypervisor.
368 Specifies which version of the IP protocol should be used by the
371 It is mainly intended to be used for specifying what kind of IP
372 addresses should be used if a network interface with both IPv4 and
373 IPv6 addresses is specified via the ``spice_bind`` parameter. In
374 this case, if the ``spice_ip_version`` parameter is not used, the
375 default IP version of the cluster will be used.
377 spice\_password\_file
378 Valid for the KVM hypervisor.
380 Specifies a file containing the password that must be used when
381 connecting via the SPICE protocol. If the option is not specified,
382 passwordless connections are allowed.
384 spice\_image\_compression
385 Valid for the KVM hypervisor.
387 Configures the SPICE lossless image compression. Valid values are:
396 spice\_jpeg\_wan\_compression
397 Valid for the KVM hypervisor.
399 Configures how SPICE should use the jpeg algorithm for lossy image
400 compression on slow links. Valid values are:
406 spice\_zlib\_glz\_wan\_compression
407 Valid for the KVM hypervisor.
409 Configures how SPICE should use the zlib-glz algorithm for lossy image
410 compression on slow links. Valid values are:
416 spice\_streaming\_video
417 Valid for the KVM hypervisor.
419 Configures how SPICE should detect video streams. Valid values are:
425 spice\_playback\_compression
426 Valid for the KVM hypervisor.
428 Configures whether SPICE should compress audio streams or not.
431 Valid for the KVM hypervisor.
433 Specifies that the SPICE server must use TLS to encrypt all the
434 traffic with the client.
437 Valid for the KVM hypervisor.
439 Specifies a list of comma-separated ciphers that SPICE should use
440 for TLS connections. For the format, see man **cipher**\(1).
443 Valid for the KVM hypervisor.
445 Enables or disables passing mouse events via SPICE vdagent.
448 Valid for the KVM hypervisor.
450 This parameter determines the emulated cpu for the instance. If this
451 parameter is empty (which is the default configuration), it will not
454 Be aware of setting this parameter to ``"host"`` if you have nodes
455 with different CPUs from each other. Live migration may stop working
458 For more information please refer to the KVM manual.
461 Valid for the Xen HVM and KVM hypervisors.
463 A boolean option that specifies if the hypervisor should enable
464 ACPI support for this instance. By default, ACPI is disabled.
467 Valid for the Xen HVM and KVM hypervisors.
469 A boolean option that specifies if the hypervisor should enabled
470 PAE support for this instance. The default is false, disabling PAE
474 Valid for the Xen HVM and KVM hypervisors.
476 A boolean option that specifies if the instance should be started
477 with its clock set to the localtime of the machine (when true) or
478 to the UTC (When false). The default is false, which is useful for
479 Linux/Unix machines; for Windows OSes, it is recommended to enable
483 Valid for the Xen PVM and KVM hypervisors.
485 This option specifies the path (on the node) to the kernel to boot
486 the instance with. Xen PVM instances always require this, while for
487 KVM if this option is empty, it will cause the machine to load the
488 kernel from its disks (and the boot will be done accordingly to
492 Valid for the Xen PVM and KVM hypervisors.
494 This options specifies extra arguments to the kernel that will be
495 loaded. device. This is always used for Xen PVM, while for KVM it
496 is only used if the ``kernel_path`` option is also specified.
498 The default setting for this value is simply ``"ro"``, which
499 mounts the root disk (initially) in read-only one. For example,
500 setting this to single will cause the instance to start in
504 Valid for the Xen PVM and KVM hypervisors.
506 This option specifies the path (on the node) to the initrd to boot
507 the instance with. Xen PVM instances can use this always, while
508 for KVM if this option is only used if the ``kernel_path`` option
509 is also specified. You can pass here either an absolute filename
510 (the path to the initrd) if you want to use an initrd, or use the
511 format no\_initrd\_path for no initrd.
514 Valid for the Xen PVM and KVM hypervisors.
516 This options specifies the name of the root device. This is always
517 needed for Xen PVM, while for KVM it is only used if the
518 ``kernel_path`` option is also specified.
520 Please note, that if this setting is an empty string and the
521 hypervisor is Xen it will not be written to the Xen configuration
525 Valid for the KVM hypervisor.
527 This boolean option specifies whether to emulate a serial console
528 for the instance. Note that some versions of KVM have a bug that
529 will make an instance hang when configured to use the serial console
530 unless a connection is made to it within about 2 seconds of the
531 instance's startup. For such case it's recommended to disable this
532 option, which is enabled by default.
535 Valid for the KVM hypervisor.
537 This integer option specifies the speed of the serial console.
538 Common values are 9600, 19200, 38400, 57600 and 115200: choose the
539 one which works on your system. (The default is 38400 for historical
540 reasons, but newer versions of kvm/qemu work with 115200)
543 Valid for the KVM hypervisor.
545 The disk cache mode. It can be either default to not pass any
546 cache option to KVM, or one of the KVM cache modes: none (for
547 direct I/O), writethrough (to use the host cache but report
548 completion to the guest only when the host has committed the
549 changes to disk) or writeback (to use the host cache and report
550 completion as soon as the data is in the host cache). Note that
551 there are special considerations for the cache mode depending on
552 version of KVM used and disk type (always raw file under Ganeti),
553 please refer to the KVM documentation for more details.
556 Valid for the KVM hypervisor.
558 The security model for kvm. Currently one of *none*, *user* or
559 *pool*. Under *none*, the default, nothing is done and instances
560 are run as the Ganeti daemon user (normally root).
562 Under *user* kvm will drop privileges and become the user
563 specified by the security\_domain parameter.
565 Under *pool* a global cluster pool of users will be used, making
566 sure no two instances share the same user on the same node. (this
567 mode is not implemented yet)
570 Valid for the KVM hypervisor.
572 Under security model *user* the username to run the instance
573 under. It must be a valid username existing on the host.
575 Cannot be set under security model *none* or *pool*.
578 Valid for the KVM hypervisor.
580 If *enabled* the -enable-kvm flag is passed to kvm. If *disabled*
581 -disable-kvm is passed. If unset no flag is passed, and the
582 default running mode for your kvm binary will be used.
585 Valid for the KVM hypervisor.
587 This option passes the -mem-path argument to kvm with the path (on
588 the node) to the mount point of the hugetlbfs file system, along
589 with the -mem-prealloc argument too.
592 Valid for the KVM hypervisor.
594 This boolean option determines whether to run the KVM instance in a
597 If it is set to ``true``, an empty directory is created before
598 starting the instance and its path is passed via the -chroot flag
599 to kvm. The directory is removed when the instance is stopped.
601 It is set to ``false`` by default.
604 Valid for the KVM hypervisor.
606 The maximum amount of time (in ms) a KVM instance is allowed to be
607 frozen during a live migration, in order to copy dirty memory
608 pages. Default value is 30ms, but you may need to increase this
609 value for busy instances.
611 This option is only effective with kvm versions >= 87 and qemu-kvm
615 Valid for the Xen, KVM and LXC hypervisors.
617 The processes belonging to the given instance are only scheduled
618 on the specified CPUs.
620 The format of the mask can be given in three forms. First, the word
621 "all", which signifies the common case where all VCPUs can live on
622 any CPU, based on the hypervisor's decisions.
624 Second, a comma-separated list of CPU IDs or CPU ID ranges. The
625 ranges are defined by a lower and higher boundary, separated by a
626 dash, and the boundaries are inclusive. In this form, all VCPUs of
627 the instance will be mapped on the selected list of CPUs. Example:
628 ``0-2,5``, mapping all VCPUs (no matter how many) onto physical CPUs
631 The last form is used for explicit control of VCPU-CPU pinnings. In
632 this form, the list of VCPU mappings is given as a colon (:)
633 separated list, whose elements are the possible values for the
634 second or first form above. In this form, the number of elements in
635 the colon-separated list _must_ equal the number of VCPUs of the
642 # Map the entire instance to CPUs 0-2
643 gnt-instance modify -H cpu_mask=0-2 my-inst
645 # Map vCPU 0 to physical CPU 1 and vCPU 1 to CPU 3 (assuming 2 vCPUs)
646 gnt-instance modify -H cpu_mask=1:3 my-inst
648 # Pin vCPU 0 to CPUs 1 or 2, and vCPU 1 to any CPU
649 gnt-instance modify -H cpu_mask=1-2:all my-inst
651 # Pin vCPU 0 to any CPU, vCPU 1 to CPUs 1, 3, 4 or 5, and CPU 2 to
652 # CPU 0 (backslashes for escaping the comma)
653 gnt-instance modify -H cpu_mask=all:1\\,3-5:0 my-inst
655 # Pin entire VM to CPU 0
656 gnt-instance modify -H cpu_mask=0 my-inst
658 # Turn off CPU pinning (default setting)
659 gnt-instance modify -H cpu_mask=all my-inst
662 Valid for the Xen hypervisor.
664 Set the maximum amount of cpu usage by the VM. The value is a percentage
665 between 0 and (100 * number of VCPUs). Default cap is 0: unlimited.
668 Valid for the Xen hypervisor.
670 Set the cpu time ratio to be allocated to the VM. Valid values are
671 between 1 and 65535. Default weight is 256.
674 Valid for the KVM hypervisor.
676 This option specifies the usb mouse type to be used. It can be
677 "mouse" or "tablet". When using VNC it's recommended to set it to
681 Valid for the KVM hypervisor.
683 This option specifies the keyboard mapping to be used. It is only
684 needed when using the VNC console. For example: "fr" or "en-gb".
687 Valid for Xen PVM, Xen HVM and KVM hypervisors.
689 Normally if an instance reboots, the hypervisor will restart it. If
690 this option is set to ``exit``, the hypervisor will treat a reboot
691 as a shutdown instead.
693 It is set to ``reboot`` by default.
696 Valid for the KVM hypervisor.
698 Number of emulated CPU cores.
701 Valid for the KVM hypervisor.
703 Number of emulated CPU threads.
706 Valid for the KVM hypervisor.
708 Number of emulated CPU sockets.
711 Valid for the KVM hypervisor.
713 Comma separated list of emulated sounds cards, or "all" to enable
714 all the available ones.
717 Valid for the KVM hypervisor.
719 Comma separated list of usb devices. These can be emulated devices
720 or passthrough ones, and each one gets passed to kvm with its own
721 ``-usbdevice`` option. See the **qemu**\(1) manpage for the syntax
722 of the possible components.
725 Valid for the KVM hypervisor.
727 Emulated vga mode, passed the the kvm -vga option.
730 Valid for the KVM hypervisor.
732 Any other option to the KVM hypervisor, useful tweaking anything
733 that Ganeti doesn't support.
736 Valid for the KVM hypervisor.
738 Use in case an instance must be booted with an exact type of
739 machine version (due to e.g. outdated drivers). In case it's not set
740 the default version supported by your version of kvm is used.
743 Valid for the KVM hypervisor.
745 Path to the userspace KVM (or qemu) program.
747 The ``-O (--os-parameters)`` option allows customisation of the OS
748 parameters. The actual parameter names and values depends on the OS
749 being used, but the syntax is the same key=value. For example, setting
750 a hypothetical ``dhcp`` parameter to yes can be achieved by::
752 gnt-instance add -O dhcp=yes ...
754 The ``-I (--iallocator)`` option specifies the instance allocator plugin
755 to use (``.`` means the default allocator). If you pass in this option
756 the allocator will select nodes for this instance automatically, so you
757 don't need to pass them with the ``-n`` option. For more information
758 please refer to the instance allocator documentation.
760 The ``-t (--disk-template)`` options specifies the disk layout type
761 for the instance. The available choices are:
764 This creates an instance with no disks. Its useful for testing only
765 (or other special cases).
768 Disk devices will be regular files.
771 Disk devices will be regulare files on a shared directory.
774 Disk devices will be logical volumes.
777 Disk devices will be drbd (version 8.x) on top of lvm volumes.
780 Disk devices will be rbd volumes residing inside a RADOS cluster.
783 Disk devices will be adopted pre-existent block devices.
786 Disk devices will be provided by external shared storage,
787 through the ExtStorage Interface using ExtStorage providers.
789 The optional second value of the ``-n (--node)`` is used for the drbd
790 template type and specifies the remote node.
792 If you do not want gnt-instance to wait for the disk mirror to be
793 synced, use the ``--no-wait-for-sync`` option.
795 The ``--file-storage-dir`` specifies the relative path under the
796 cluster-wide file storage directory to store file-based disks. It is
797 useful for having different subdirectories for different
798 instances. The full path of the directory where the disk files are
799 stored will consist of cluster-wide file storage directory + optional
800 subdirectory + instance name. Example:
801 ``@RPL_FILE_STORAGE_DIR@/mysubdir/instance1.example.com``. This
802 option is only relevant for instances using the file storage backend.
804 The ``--file-driver`` specifies the driver to use for file-based
805 disks. Note that currently these drivers work with the xen hypervisor
806 only. This option is only relevant for instances using the file
807 storage backend. The available choices are:
810 Kernel loopback driver. This driver uses loopback devices to
811 access the filesystem within the file. However, running I/O
812 intensive applications in your instance using the loop driver
813 might result in slowdowns. Furthermore, if you use the loopback
814 driver consider increasing the maximum amount of loopback devices
815 (on most systems it's 8) using the max\_loop param.
818 The blktap driver (for Xen hypervisors). In order to be able to
819 use the blktap driver you should check if the 'blktapctrl' user
820 space disk agent is running (usually automatically started via
821 xend). This user-level disk I/O interface has the advantage of
822 better performance. Especially if you use a network file system
823 (e.g. NFS) to store your instances this is the recommended choice.
825 If ``--ignore-ipolicy`` is given any instance policy violations occuring
826 during this operation are ignored.
828 See **ganeti**\(7) for a description of ``--submit`` and other common
833 # gnt-instance add -t file --disk 0:size=30g -B maxmem=512 -o debian-etch \
834 -n node1.example.com --file-storage-dir=mysubdir instance1.example.com
835 # gnt-instance add -t plain --disk 0:size=30g -B maxmem=1024,minmem=512 \
836 -o debian-etch -n node1.example.com instance1.example.com
837 # gnt-instance add -t plain --disk 0:size=30g --disk 1:size=100g,vg=san \
838 -B maxmem=512 -o debian-etch -n node1.example.com instance1.example.com
839 # gnt-instance add -t drbd --disk 0:size=30g -B maxmem=512 -o debian-etch \
840 -n node1.example.com:node2.example.com instance2.example.com
841 # gnt-instance add -t rbd --disk 0:size=30g -B maxmem=512 -o debian-etch \
842 -n node1.example.com instance1.example.com
843 # gnt-instance add -t ext --disk 0:size=30g,provider=pvdr1 -B maxmem=512 \
844 -o debian-etch -n node1.example.com instance1.example.com
845 # gnt-instance add -t ext --disk 0:size=30g,provider=pvdr1,param1=val1 \
846 --disk 1:size=40g,provider=pvdr2,param2=val2,param3=val3 -B maxmem=512 \
847 -o debian-etch -n node1.example.com instance1.example.com
853 **batch-create** {instances\_file.json}
855 This command (similar to the Ganeti 1.2 **batcher** tool) submits
856 multiple instance creation jobs based on a definition file. The
857 instance configurations do not encompass all the possible options for
858 the **add** command, but only a subset.
860 The instance file should be a valid-formed JSON file, containing a
861 dictionary with instance name and instance parameters. The accepted
865 The size of the disks of the instance.
868 The disk template to use for the instance, the same as in the
872 A dictionary of backend parameters.
875 A dictionary with a single key (the hypervisor name), and as value
876 the hypervisor options. If not passed, the default hypervisor and
877 hypervisor options will be inherited.
880 Specifications for the one NIC that will be created for the
881 instance. 'bridge' is also accepted as a backwards compatible
885 List of NICs that will be created for the instance. Each entry
886 should be a dict, with mac, ip, mode and link as possible keys.
887 Please don't provide the "mac, ip, mode, link" parent keys if you
888 use this method for specifying NICs.
890 primary\_node, secondary\_node
891 The primary and optionally the secondary node to use for the
892 instance (in case an iallocator script is not used).
895 Instead of specifying the nodes, an iallocator script can be used
896 to automatically compute them.
899 whether to start the instance
902 Skip the check for already-in-use instance; see the description in
903 the **add** command for details.
906 Skip the name check for instances; see the description in the
907 **add** command for details.
909 file\_storage\_dir, file\_driver
910 Configuration for the file disk type, see the **add** command for
914 A simple definition for one instance can be (with most of the
915 parameters taken from the cluster defaults)::
921 "disk_size": ["25G"],
927 "disk_size": ["25G"],
928 "iallocator": "dumb",
929 "hypervisor": "xen-hvm",
930 "hvparams": {"acpi": true},
931 "backend": {"maxmem": 512, "minmem": 256}
935 The command will display the job id for each submitted instance, as
938 # gnt-instance batch-create instances.json
945 **remove** [\--ignore-failures] [\--shutdown-timeout=*N*] [\--submit]
946 [\--force] {*instance*}
948 Remove an instance. This will remove all data from the instance and
949 there is *no way back*. If you are not sure if you use an instance
950 again, use **shutdown** first and leave it in the shutdown state for a
953 The ``--ignore-failures`` option will cause the removal to proceed
954 even in the presence of errors during the removal of the instance
955 (e.g. during the shutdown or the disk removal). If this option is not
956 given, the command will stop at the first error.
958 The ``--shutdown-timeout`` is used to specify how much time to wait
959 before forcing the shutdown (e.g. ``xm destroy`` in Xen, killing the
960 kvm process for KVM, etc.). By default two minutes are given to each
963 The ``--force`` option is used to skip the interactive confirmation.
965 See **ganeti**\(7) for a description of ``--submit`` and other common
970 # gnt-instance remove instance1.example.com
977 | [\--no-headers] [\--separator=*SEPARATOR*] [\--units=*UNITS*] [-v]
978 | [{-o|\--output} *[+]FIELD,...*] [\--filter] [instance...]
980 Shows the currently configured instances with memory usage, disk
981 usage, the node they are running on, and their run status.
983 The ``--no-headers`` option will skip the initial header line. The
984 ``--separator`` option takes an argument which denotes what will be
985 used between the output fields. Both these options are to help
988 The units used to display the numeric values in the output varies,
989 depending on the options given. By default, the values will be
990 formatted in the most appropriate unit. If the ``--separator`` option
991 is given, then the values are shown in mebibytes to allow parsing by
992 scripts. In both cases, the ``--units`` option can be used to enforce
995 The ``-v`` option activates verbose mode, which changes the display of
996 special field states (see **ganeti**\(7)).
998 The ``-o (--output)`` option takes a comma-separated list of output
999 fields. The available fields and their meaning are:
1001 @QUERY_FIELDS_INSTANCE@
1003 If the value of the option starts with the character ``+``, the new
1004 field(s) will be added to the default list. This allows one to quickly
1005 see the default list plus a few other fields, instead of retyping the
1006 entire list of fields.
1008 There is a subtle grouping about the available output fields: all
1009 fields except for ``oper_state``, ``oper_ram``, ``oper_vcpus`` and
1010 ``status`` are configuration value and not run-time values. So if you
1011 don't select any of the these fields, the query will be satisfied
1012 instantly from the cluster configuration, without having to ask the
1013 remote nodes for the data. This can be helpful for big clusters when
1014 you only want some data and it makes sense to specify a reduced set of
1017 If exactly one argument is given and it appears to be a query filter
1018 (see **ganeti**\(7)), the query result is filtered accordingly. For
1019 ambiguous cases (e.g. a single field name as a filter) the ``--filter``
1020 (``-F``) option forces the argument to be treated as a filter (e.g.
1021 ``gnt-instance list -F admin_state``).
1023 The default output field list is: ``name``, ``os``, ``pnode``,
1024 ``admin_state``, ``oper_state``, ``oper_ram``.
1030 **list-fields** [field...]
1032 Lists available fields for instances.
1038 **info** [-s \| \--static] [\--roman] {\--all \| *instance*}
1040 Show detailed information about the given instance(s). This is
1041 different from **list** as it shows detailed data about the instance's
1042 disks (especially useful for the drbd disk template).
1044 If the option ``-s`` is used, only information available in the
1045 configuration file is returned, without querying nodes, making the
1048 Use the ``--all`` to get info about all instances, rather than
1049 explicitly passing the ones you're interested in.
1051 The ``--roman`` option can be used to cause envy among people who like
1052 ancient cultures, but are stuck with non-latin-friendly cluster
1053 virtualization technologies.
1059 | [{-H|\--hypervisor-parameters} *HYPERVISOR\_PARAMETERS*]
1060 | [{-B|\--backend-parameters} *BACKEND\_PARAMETERS*]
1061 | [{-m|\--runtime-memory} *SIZE*]
1062 | [\--net add[:options...] \|
1063 | \--net [*N*:]add[,options...] \|
1064 | \--net [*ID*:]remove \|
1065 | \--net *ID*:modify[,options...]]
1066 | [\--disk add:size=*SIZE*[,options...] \|
1067 | \--disk *N*:add,size=*SIZE*[,options...] \|
1068 | \--disk *N*:add,size=*SIZE*,provider=*PROVIDER*[,options...][,param=*value*... ] \|
1069 | \--disk *ID*:modify[,options...]
1070 | \--disk [*ID*:]remove]
1071 | [{-t|\--disk-template} plain | {-t|\--disk-template} drbd -n *new_secondary*] [\--no-wait-for-sync]
1072 | [\--new-primary=*node*]
1073 | [\--os-type=*OS* [\--force-variant]]
1074 | [{-O|\--os-parameters} *param*=*value*... ]
1075 | [\--offline \| \--online]
1077 | [\--ignore-ipolicy]
1080 Modifies the memory size, number of vcpus, ip address, MAC address
1081 and/or NIC parameters for an instance. It can also add and remove
1082 disks and NICs to/from the instance. Note that you need to give at
1083 least one of the arguments, otherwise the command complains.
1085 The ``-H (--hypervisor-parameters)``, ``-B (--backend-parameters)``
1086 and ``-O (--os-parameters)`` options specifies hypervisor, backend and
1087 OS parameter options in the form of name=value[,...]. For details
1088 which options can be specified, see the **add** command.
1090 The ``-t (--disk-template)`` option will change the disk template of
1091 the instance. Currently only conversions between the plain and drbd
1092 disk templates are supported, and the instance must be stopped before
1093 attempting the conversion. When changing from the plain to the drbd
1094 disk template, a new secondary node must be specified via the ``-n``
1095 option. The option ``--no-wait-for-sync`` can be used when converting
1096 to the ``drbd`` template in order to make the instance available for
1097 startup before DRBD has finished resyncing.
1099 The ``-m (--runtime-memory)`` option will change an instance's runtime
1100 memory to the given size (in MB if a different suffix is not specified),
1101 by ballooning it up or down to the new value.
1103 The ``--disk add:size=*SIZE*,[options..]`` option adds a disk to the
1104 instance, and ``--disk *N*:add:size=*SIZE*,[options..]`` will add a disk
1105 to the the instance at a specific index. The available options are the
1106 same as in the **add** command(``mode``, ``name``, ``vg``, ``metavg``).
1107 When adding an ExtStorage disk the ``provider=*PROVIDER*`` option is
1108 also mandatory and specifies the ExtStorage provider. Also, for
1109 ExtStorage disks arbitrary parameters can be passed as additional comma
1110 separated options, same as in the **add** command. -The ``--disk remove``
1111 option will remove the last disk of the instance. Use
1112 ``--disk `` *ID*``:remove`` to remove a disk by its identifier. *ID*
1113 can be the index of the disk, the disks's name or the disks's UUID. The
1114 ``--disk *ID*:modify[,options...]`` wil change the options of the disk.
1115 Available options are:
1118 The access mode. Either ``ro`` (read-only) or the default ``rw`` (read-write).
1121 this option specifies a name for the disk, which can be used as a disk
1122 identifier. An instance can not have two disks with the same name.
1124 The ``--net *N*:add[,options..]`` will add a new network interface to
1125 the instance. The available options are the same as in the **add**
1126 command (``mac``, ``ip``, ``link``, ``mode``, ``network``). The
1127 ``--net *ID*,remove`` will remove the intances' NIC with *ID* identifier,
1128 which can be the index of the NIC, the NIC's name or the NIC's UUID.
1129 The ``--net *ID*:modify[,options..]`` option will change the parameters of
1130 the instance network interface with the *ID* identifier.
1132 The option ``-o (--os-type)`` will change the OS name for the instance
1133 (without reinstallation). In case an OS variant is specified that is
1134 not found, then by default the modification is refused, unless
1135 ``--force-variant`` is passed. An invalid OS will also be refused,
1136 unless the ``--force`` option is given.
1138 The option ``--new-primary`` will set the new primary node of an instance
1139 assuming the disks have already been moved manually. Unless the ``--force``
1140 option is given, it is verified that the instance is no longer running
1141 on its current primary node.
1143 The ``--online`` and ``--offline`` options are used to transition an
1144 instance into and out of the ``offline`` state. An instance can be
1145 turned offline only if it was previously down. The ``--online`` option
1146 fails if the instance was not in the ``offline`` state, otherwise it
1147 changes instance's state to ``down``. These modifications take effect
1150 If ``--ignore-ipolicy`` is given any instance policy violations occuring
1151 during this operation are ignored.
1153 See **ganeti**\(7) for a description of ``--submit`` and other common
1156 Most of the changes take effect at the next restart. If the instance is
1157 running, there is no effect on the instance.
1162 | **reinstall** [{-o|\--os-type} *os-type*] [\--select-os] [-f *force*]
1163 | [\--force-multiple]
1164 | [\--instance \| \--node \| \--primary \| \--secondary \| \--all]
1165 | [{-O|\--os-parameters} *OS\_PARAMETERS*] [\--submit] {*instance*...}
1167 Reinstalls the operating system on the given instance(s). The
1168 instance(s) must be stopped when running this command. If the ``-o
1169 (--os-type)`` is specified, the operating system is changed.
1171 The ``--select-os`` option switches to an interactive OS reinstall.
1172 The user is prompted to select the OS template from the list of
1173 available OS templates. OS parameters can be overridden using ``-O
1174 (--os-parameters)`` (more documentation for this option under the
1177 Since this is a potentially dangerous command, the user will be
1178 required to confirm this action, unless the ``-f`` flag is passed.
1179 When multiple instances are selected (either by passing multiple
1180 arguments or by using the ``--node``, ``--primary``, ``--secondary``
1181 or ``--all`` options), the user must pass the ``--force-multiple``
1182 options to skip the interactive confirmation.
1184 See **ganeti**\(7) for a description of ``--submit`` and other common
1190 | **rename** [\--no-ip-check] [\--no-name-check] [\--submit]
1191 | {*instance*} {*new\_name*}
1193 Renames the given instance. The instance must be stopped when running
1194 this command. The requirements for the new name are the same as for
1195 adding an instance: the new name must be resolvable and the IP it
1196 resolves to must not be reachable (in order to prevent duplicate IPs
1197 the next time the instance is started). The IP test can be skipped if
1198 the ``--no-ip-check`` option is passed.
1200 Note that you can rename an instance to its same name, to force
1201 re-executing the os-specific rename script for that instance, if
1204 The ``--no-name-check`` skips the check for the new instance name via
1205 the resolver (e.g. in DNS or /etc/hosts, depending on your setup) and
1206 that the resolved name matches the provided name. Since the name check
1207 is used to compute the IP address, if you pass this option you must also
1208 pass the ``--no-ip-check`` option.
1210 See **ganeti**\(7) for a description of ``--submit`` and other common
1213 Starting/stopping/connecting to console
1214 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1220 | [\--force] [\--ignore-offline]
1221 | [\--force-multiple] [\--no-remember]
1222 | [\--instance \| \--node \| \--primary \| \--secondary \| \--all \|
1223 | \--tags \| \--node-tags \| \--pri-node-tags \| \--sec-node-tags]
1224 | [{-H|\--hypervisor-parameters} ``key=value...``]
1225 | [{-B|\--backend-parameters} ``key=value...``]
1226 | [\--submit] [\--paused]
1229 Starts one or more instances, depending on the following options. The
1230 four available modes are:
1233 will start the instances given as arguments (at least one argument
1234 required); this is the default selection
1237 will start the instances who have the given node as either primary
1241 will start all instances whose primary node is in the list of nodes
1242 passed as arguments (at least one node required)
1245 will start all instances whose secondary node is in the list of
1246 nodes passed as arguments (at least one node required)
1249 will start all instances in the cluster (no arguments accepted)
1252 will start all instances in the cluster with the tags given as
1256 will start all instances in the cluster on nodes with the tags
1260 will start all instances in the cluster on primary nodes with the
1261 tags given as arguments
1264 will start all instances in the cluster on secondary nodes with the
1265 tags given as arguments
1267 Note that although you can pass more than one selection option, the
1268 last one wins, so in order to guarantee the desired result, don't pass
1269 more than one such option.
1271 Use ``--force`` to start even if secondary disks are failing.
1272 ``--ignore-offline`` can be used to ignore offline primary nodes and
1273 mark the instance as started even if the primary is not available.
1275 The ``--force-multiple`` will skip the interactive confirmation in the
1276 case the more than one instance will be affected.
1278 The ``--no-remember`` option will perform the startup but not change
1279 the state of the instance in the configuration file (if it was stopped
1280 before, Ganeti will still think it needs to be stopped). This can be
1281 used for testing, or for a one shot-start where you don't want the
1282 watcher to restart the instance if it crashes.
1284 The ``-H (--hypervisor-parameters)`` and ``-B (--backend-parameters)``
1285 options specify temporary hypervisor and backend parameters that can
1286 be used to start an instance with modified parameters. They can be
1287 useful for quick testing without having to modify an instance back and
1290 # gnt-instance start -H kernel_args="single" instance1
1291 # gnt-instance start -B maxmem=2048 instance2
1294 The first form will start the instance instance1 in single-user mode,
1295 and the instance instance2 with 2GB of RAM (this time only, unless
1296 that is the actual instance memory size already). Note that the values
1297 override the instance parameters (and not extend them): an instance
1298 with "kernel\_args=ro" when started with -H kernel\_args=single will
1299 result in "single", not "ro single".
1301 The ``--paused`` option is only valid for Xen and kvm hypervisors. This
1302 pauses the instance at the start of bootup, awaiting ``gnt-instance
1303 console`` to unpause it, allowing the entire boot process to be
1304 monitored for debugging.
1306 See **ganeti**\(7) for a description of ``--submit`` and other common
1311 # gnt-instance start instance1.example.com
1312 # gnt-instance start --node node1.example.com node2.example.com
1313 # gnt-instance start --all
1321 | [\--force] [\--force-multiple] [\--ignore-offline] [\--no-remember]
1322 | [\--instance \| \--node \| \--primary \| \--secondary \| \--all \|
1323 | \--tags \| \--node-tags \| \--pri-node-tags \| \--sec-node-tags]
1327 Stops one or more instances. If the instance cannot be cleanly stopped
1328 during a hardcoded interval (currently 2 minutes), it will forcibly
1329 stop the instance (equivalent to switching off the power on a physical
1332 The ``--timeout`` is used to specify how much time to wait before
1333 forcing the shutdown (e.g. ``xm destroy`` in Xen, killing the kvm
1334 process for KVM, etc.). By default two minutes are given to each
1337 The ``--instance``, ``--node``, ``--primary``, ``--secondary``,
1338 ``--all``, ``--tags``, ``--node-tags``, ``--pri-node-tags`` and
1339 ``--sec-node-tags`` options are similar as for the **startup** command
1340 and they influence the actual instances being shutdown.
1342 ``--ignore-offline`` can be used to ignore offline primary nodes and
1343 force the instance to be marked as stopped. This option should be used
1344 with care as it can lead to an inconsistent cluster state.
1346 Use ``--force`` to be able to shutdown an instance even when it's marked
1347 as offline. This is useful is an offline instance ends up in the
1348 ``ERROR_up`` state, for example.
1350 The ``--no-remember`` option will perform the shutdown but not change
1351 the state of the instance in the configuration file (if it was running
1352 before, Ganeti will still thinks it needs to be running). This can be
1353 useful for a cluster-wide shutdown, where some instances are marked as
1354 up and some as down, and you don't want to change the running state:
1355 you just need to disable the watcher, shutdown all instances with
1356 ``--no-remember``, and when the watcher is activated again it will
1357 restore the correct runtime state for all instances.
1359 See **ganeti**\(7) for a description of ``--submit`` and other common
1364 # gnt-instance shutdown instance1.example.com
1365 # gnt-instance shutdown --all
1372 | [{-t|\--type} *REBOOT-TYPE*]
1373 | [\--ignore-secondaries]
1374 | [\--shutdown-timeout=*N*]
1375 | [\--force-multiple]
1376 | [\--instance \| \--node \| \--primary \| \--secondary \| \--all \|
1377 | \--tags \| \--node-tags \| \--pri-node-tags \| \--sec-node-tags]
1381 Reboots one or more instances. The type of reboot depends on the value
1382 of ``-t (--type)``. A soft reboot does a hypervisor reboot, a hard reboot
1383 does a instance stop, recreates the hypervisor config for the instance
1384 and starts the instance. A full reboot does the equivalent of
1385 **gnt-instance shutdown && gnt-instance startup**. The default is
1388 For the hard reboot the option ``--ignore-secondaries`` ignores errors
1389 for the secondary node while re-assembling the instance disks.
1391 The ``--instance``, ``--node``, ``--primary``, ``--secondary``,
1392 ``--all``, ``--tags``, ``--node-tags``, ``--pri-node-tags`` and
1393 ``--sec-node-tags`` options are similar as for the **startup** command
1394 and they influence the actual instances being rebooted.
1396 The ``--shutdown-timeout`` is used to specify how much time to wait
1397 before forcing the shutdown (xm destroy in xen, killing the kvm
1398 process, for kvm). By default two minutes are given to each instance
1401 The ``--force-multiple`` will skip the interactive confirmation in the
1402 case the more than one instance will be affected.
1404 See **ganeti**\(7) for a description of ``--submit`` and other common
1409 # gnt-instance reboot instance1.example.com
1410 # gnt-instance reboot --type=full instance1.example.com
1416 **console** [\--show-cmd] {*instance*}
1418 Connects to the console of the given instance. If the instance is not
1419 up, an error is returned. Use the ``--show-cmd`` option to display the
1420 command instead of executing it.
1422 For HVM instances, this will attempt to connect to the serial console
1423 of the instance. To connect to the virtualized "physical" console of a
1424 HVM instance, use a VNC client with the connection info from the
1427 For Xen/kvm instances, if the instance is paused, this attempts to
1428 unpause the instance after waiting a few seconds for the connection to
1429 the console to be made.
1433 # gnt-instance console instance1.example.com
1442 **replace-disks** [\--submit] [\--early-release] [\--ignore-ipolicy] {-p}
1443 [\--disks *idx*] {*instance*}
1445 **replace-disks** [\--submit] [\--early-release] [\--ignore-ipolicy] {-s}
1446 [\--disks *idx*] {*instance*}
1448 **replace-disks** [\--submit] [\--early-release] [\--ignore-ipolicy]
1449 {{-I\|\--iallocator} *name* \| {{-n|\--new-secondary} *node* } {*instance*}
1451 **replace-disks** [\--submit] [\--early-release] [\--ignore-ipolicy]
1452 {-a\|\--auto} {*instance*}
1454 This command is a generalized form for replacing disks. It is
1455 currently only valid for the mirrored (DRBD) disk template.
1457 The first form (when passing the ``-p`` option) will replace the disks
1458 on the primary, while the second form (when passing the ``-s`` option
1459 will replace the disks on the secondary node. For these two cases (as
1460 the node doesn't change), it is possible to only run the replace for a
1461 subset of the disks, using the option ``--disks`` which takes a list
1462 of comma-delimited disk indices (zero-based), e.g. 0,2 to replace only
1463 the first and third disks.
1465 The third form (when passing either the ``--iallocator`` or the
1466 ``--new-secondary`` option) is designed to change secondary node of the
1467 instance. Specifying ``--iallocator`` makes the new secondary be
1468 selected automatically by the specified allocator plugin (use ``.`` to
1469 indicate the default allocator), otherwise the new secondary node will
1470 be the one chosen manually via the ``--new-secondary`` option.
1472 Note that it is not possible to select an offline or drained node as a
1475 The fourth form (when using ``--auto``) will automatically determine
1476 which disks of an instance are faulty and replace them within the same
1477 node. The ``--auto`` option works only when an instance has only
1478 faulty disks on either the primary or secondary node; it doesn't work
1479 when both sides have faulty disks.
1481 The ``--early-release`` changes the code so that the old storage on
1482 secondary node(s) is removed early (before the resync is completed)
1483 and the internal Ganeti locks for the current (and new, if any)
1484 secondary node are also released, thus allowing more parallelism in
1485 the cluster operation. This should be used only when recovering from a
1486 disk failure on the current secondary (thus the old storage is already
1487 broken) or when the storage on the primary node is known to be fine
1488 (thus we won't need the old storage for potential recovery).
1490 The ``--ignore-ipolicy`` let the command ignore instance policy
1491 violations if replace-disks changes groups and the instance would
1492 violate the new groups instance policy.
1494 See **ganeti**\(7) for a description of ``--submit`` and other common
1500 **activate-disks** [\--submit] [\--ignore-size] [\--wait-for-sync] {*instance*}
1502 Activates the block devices of the given instance. If successful, the
1503 command will show the location and name of the block devices::
1505 node1.example.com:disk/0:/dev/drbd0
1506 node1.example.com:disk/1:/dev/drbd1
1509 In this example, *node1.example.com* is the name of the node on which
1510 the devices have been activated. The *disk/0* and *disk/1* are the
1511 Ganeti-names of the instance disks; how they are visible inside the
1512 instance is hypervisor-specific. */dev/drbd0* and */dev/drbd1* are the
1513 actual block devices as visible on the node.
1515 The ``--ignore-size`` option can be used to activate disks ignoring
1516 the currently configured size in Ganeti. This can be used in cases
1517 where the configuration has gotten out of sync with the real-world
1518 (e.g. after a partially-failed grow-disk operation or due to rounding
1519 in LVM devices). This should not be used in normal cases, but only
1520 when activate-disks fails without it.
1522 The ``--wait-for-sync`` option will ensure that the command returns only
1523 after the instance's disks are synchronised (mostly for DRBD); this can
1524 be useful to ensure consistency, as otherwise there are no commands that
1525 can wait until synchronisation is done. However when passing this
1526 option, the command will have additional output, making it harder to
1527 parse the disk information.
1529 Note that it is safe to run this command while the instance is already
1532 See **ganeti**\(7) for a description of ``--submit`` and other common
1538 **deactivate-disks** [-f] [\--submit] {*instance*}
1540 De-activates the block devices of the given instance. Note that if you
1541 run this command for an instance with a drbd disk template, while it
1542 is running, it will not be able to shutdown the block devices on the
1543 primary node, but it will shutdown the block devices on the secondary
1544 nodes, thus breaking the replication.
1546 The ``-f``/``--force`` option will skip checks that the instance is
1547 down; in case the hypervisor is confused and we can't talk to it,
1548 normally Ganeti will refuse to deactivate the disks, but with this
1549 option passed it will skip this check and directly try to deactivate
1550 the disks. This can still fail due to the instance actually running or
1553 See **ganeti**\(7) for a description of ``--submit`` and other common
1559 | **grow-disk** [\--no-wait-for-sync] [\--submit] [\--absolute]
1560 | {*instance*} {*disk*} {*amount*}
1562 Grows an instance's disk. This is only possible for instances having a
1563 plain, drbd, file, sharedfile, rbd or ext disk template. For the ext
1564 template to work, the ExtStorage provider should also support growing.
1565 This means having a ``grow`` script that actually grows the volume of
1566 the external shared storage.
1568 Note that this command only change the block device size; it will not
1569 grow the actual filesystems, partitions, etc. that live on that
1570 disk. Usually, you will need to:
1572 #. use **gnt-instance grow-disk**
1574 #. reboot the instance (later, at a convenient time)
1576 #. use a filesystem resizer, such as **ext2online**\(8) or
1577 **xfs\_growfs**\(8) to resize the filesystem, or use **fdisk**\(8) to
1578 change the partition table on the disk
1580 The *disk* argument is the index of the instance disk to grow. The
1581 *amount* argument is given as a number which can have a suffix (like the
1582 disk size in instance create); if the suffix is missing, the value will
1583 be interpreted as mebibytes.
1585 By default, the *amount* value represents the desired increase in the
1586 disk size (e.g. an amount of 1G will take a disk of size 3G to 4G). If
1587 the optional ``--absolute`` parameter is passed, then the *amount*
1588 argument doesn't represent the delta, but instead the desired final disk
1589 size (e.g. an amount of 8G will take a disk of size 4G to 8G).
1591 For instances with a drbd template, note that the disk grow operation
1592 might complete on one node but fail on the other; this will leave the
1593 instance with different-sized LVs on the two nodes, but this will not
1594 create problems (except for unused space).
1596 If you do not want gnt-instance to wait for the new disk region to be
1597 synced, use the ``--no-wait-for-sync`` option.
1599 See **ganeti**\(7) for a description of ``--submit`` and other common
1602 Example (increase the first disk for instance1 by 16GiB)::
1604 # gnt-instance grow-disk instance1.example.com 0 16g
1606 Example for increasing the disk size to a certain size::
1608 # gnt-instance grow-disk --absolute instance1.example.com 0 32g
1610 Also note that disk shrinking is not supported; use **gnt-backup
1611 export** and then **gnt-backup import** to reduce the disk size of an
1617 | **recreate-disks** [\--submit]
1618 | [{-n node1:[node2] \| {-I\|\--iallocator *name*}}]
1619 | [\--disk=*N*[:[size=*VAL*][,mode=*ro\|rw*]]] {*instance*}
1621 Recreates all or a subset of disks of the given instance.
1623 Note that this functionality should only be used for missing disks; if
1624 any of the given disks already exists, the operation will fail. While
1625 this is suboptimal, recreate-disks should hopefully not be needed in
1626 normal operation and as such the impact of this is low.
1628 If only a subset should be recreated, any number of ``disk`` options can
1629 be specified. It expects a disk index and an optional list of disk
1630 parameters to change. Only ``size`` and ``mode`` can be changed while
1631 recreating disks. To recreate all disks while changing parameters on
1632 a subset only, a ``--disk`` option must be given for every disk of the
1635 Optionally the instance's disks can be recreated on different
1636 nodes. This can be useful if, for example, the original nodes of the
1637 instance have gone down (and are marked offline), so we can't recreate
1638 on the same nodes. To do this, pass the new node(s) via ``-n`` option,
1639 with a syntax similar to the **add** command. The number of nodes
1640 passed must equal the number of nodes that the instance currently
1641 has. Note that changing nodes is only allowed when all disks are
1642 replaced, e.g. when no ``--disk`` option is passed.
1644 Another method of choosing which nodes to place the instance on is by
1645 using the specified iallocator, passing the ``--iallocator`` option.
1646 The primary and secondary nodes will be chosen by the specified
1647 iallocator plugin, or by the default allocator if ``.`` is specified.
1649 See **ganeti**\(7) for a description of ``--submit`` and other common
1658 | **failover** [-f] [\--ignore-consistency] [\--ignore-ipolicy]
1659 | [\--shutdown-timeout=*N*]
1660 | [{-n|\--target-node} *node* \| {-I|\--iallocator} *name*]
1664 Failover will stop the instance (if running), change its primary node,
1665 and if it was originally running it will start it again (on the new
1666 primary). This works for instances with drbd template (in which case you
1667 can only fail to the secondary node) and for externally mirrored
1668 templates (sharedfile, blockdev, rbd and ext) (in which case you can
1669 fail to any other node).
1671 If the instance's disk template is of type sharedfile, blockdev, rbd or
1672 ext, then you can explicitly specify the target node (which can be any
1673 node) using the ``-n`` or ``--target-node`` option, or specify an
1674 iallocator plugin using the ``-I`` or ``--iallocator`` option. If you
1675 omit both, the default iallocator will be used to specify the target
1678 If the instance's disk template is of type drbd, the target node is
1679 automatically selected as the drbd's secondary node. Changing the
1680 secondary node is possible with a replace-disks operation.
1682 Normally the failover will check the consistency of the disks before
1683 failing over the instance. If you are trying to migrate instances off
1684 a dead node, this will fail. Use the ``--ignore-consistency`` option
1685 for this purpose. Note that this option can be dangerous as errors in
1686 shutting down the instance will be ignored, resulting in possibly
1687 having the instance running on two machines in parallel (on
1688 disconnected DRBD drives).
1690 The ``--shutdown-timeout`` is used to specify how much time to wait
1691 before forcing the shutdown (xm destroy in xen, killing the kvm
1692 process, for kvm). By default two minutes are given to each instance
1695 If ``--ignore-ipolicy`` is given any instance policy violations occuring
1696 during this operation are ignored.
1698 See **ganeti**\(7) for a description of ``--submit`` and other common
1703 # gnt-instance failover instance1.example.com
1705 For externally mirrored templates also ``-n`` is available::
1707 # gnt-instance failover -n node3.example.com instance1.example.com
1713 | **migrate** [-f] [\--allow-failover] [\--non-live]
1714 | [\--migration-mode=live\|non-live] [\--ignore-ipolicy]
1715 | [\--no-runtime-changes] [\--submit]
1716 | [{-n|\--target-node} *node* \| {-I|\--iallocator} *name*] {*instance*}
1718 | **migrate** [-f] \--cleanup [\--submit] {*instance*}
1720 Migrate will move the instance to its secondary node without shutdown.
1721 As with failover, it works for instances having the drbd disk template
1722 or an externally mirrored disk template type such as sharedfile,
1723 blockdev, rbd or ext.
1725 If the instance's disk template is of type sharedfile, blockdev, rbd or
1726 ext, then you can explicitly specify the target node (which can be any
1727 node) using the ``-n`` or ``--target-node`` option, or specify an
1728 iallocator plugin using the ``-I`` or ``--iallocator`` option. If you
1729 omit both, the default iallocator will be used to specify the target
1730 node. Alternatively, the default iallocator can be requested by
1731 specifying ``.`` as the name of the plugin.
1733 If the instance's disk template is of type drbd, the target node is
1734 automatically selected as the drbd's secondary node. Changing the
1735 secondary node is possible with a replace-disks operation.
1737 The migration command needs a perfectly healthy instance for drbd
1738 instances, as we rely on the dual-master capability of drbd8 and the
1739 disks of the instance are not allowed to be degraded.
1741 The ``--non-live`` and ``--migration-mode=non-live`` options will
1742 switch (for the hypervisors that support it) between a "fully live"
1743 (i.e. the interruption is as minimal as possible) migration and one in
1744 which the instance is frozen, its state saved and transported to the
1745 remote node, and then resumed there. This all depends on the
1746 hypervisor support for two different methods. In any case, it is not
1747 an error to pass this parameter (it will just be ignored if the
1748 hypervisor doesn't support it). The option ``--migration-mode=live``
1749 option will request a fully-live migration. The default, when neither
1750 option is passed, depends on the hypervisor parameters (and can be
1751 viewed with the **gnt-cluster info** command).
1753 If the ``--cleanup`` option is passed, the operation changes from
1754 migration to attempting recovery from a failed previous migration. In
1755 this mode, Ganeti checks if the instance runs on the correct node (and
1756 updates its configuration if not) and ensures the instances' disks
1757 are configured correctly. In this mode, the ``--non-live`` option is
1760 The option ``-f`` will skip the prompting for confirmation.
1762 If ``--allow-failover`` is specified it tries to fallback to failover if
1763 it already can determine that a migration won't work (e.g. if the
1764 instance is shut down). Please note that the fallback will not happen
1765 during execution. If a migration fails during execution it still fails.
1767 If ``--ignore-ipolicy`` is given any instance policy violations occuring
1768 during this operation are ignored.
1770 The ``--no-runtime-changes`` option forbids migrate to alter an
1771 instance's runtime before migrating it (eg. ballooning an instance
1772 down because the target node doesn't have enough available memory).
1774 If an instance has the backend parameter ``always_failover`` set to
1775 true, then the migration is automatically converted into a failover.
1777 See **ganeti**\(7) for a description of ``--submit`` and other common
1780 Example (and expected output)::
1782 # gnt-instance migrate instance1
1783 Instance instance1 will be migrated. Note that migration
1784 might impact the instance if anything goes wrong (e.g. due to bugs in
1785 the hypervisor). Continue?
1787 Migrating instance instance1.example.com
1788 * checking disk consistency between source and target
1789 * switching node node2.example.com to secondary mode
1790 * changing into standalone mode
1791 * changing disks into dual-master mode
1792 * wait until resync is done
1793 * preparing node2.example.com to accept the instance
1794 * migrating instance to node2.example.com
1795 * switching node node1.example.com to secondary mode
1796 * wait until resync is done
1797 * changing into standalone mode
1798 * changing disks into single-master mode
1799 * wait until resync is done
1807 | **move** [-f] [\--ignore-consistency]
1808 | [-n *node*] [\--shutdown-timeout=*N*] [\--submit] [\--ignore-ipolicy]
1811 Move will move the instance to an arbitrary node in the cluster. This
1812 works only for instances having a plain or file disk template.
1814 Note that since this operation is done via data copy, it will take a
1815 long time for big disks (similar to replace-disks for a drbd
1818 The ``--shutdown-timeout`` is used to specify how much time to wait
1819 before forcing the shutdown (e.g. ``xm destroy`` in XEN, killing the
1820 kvm process for KVM, etc.). By default two minutes are given to each
1823 The ``--ignore-consistency`` option will make Ganeti ignore any errors
1824 in trying to shutdown the instance on its node; useful if the
1825 hypervisor is broken and you want to recover the data.
1827 If ``--ignore-ipolicy`` is given any instance policy violations occuring
1828 during this operation are ignored.
1830 See **ganeti**\(7) for a description of ``--submit`` and other common
1835 # gnt-instance move -n node3.example.com instance1.example.com
1841 | **change-group** [\--submit]
1842 | [\--iallocator *NAME*] [\--to *GROUP*...] {*instance*}
1844 This command moves an instance to another node group. The move is
1845 calculated by an iallocator, either given on the command line or as a
1848 If no specific destination groups are specified using ``--to``, all
1849 groups except the one containing the instance are considered.
1851 See **ganeti**\(7) for a description of ``--submit`` and other common
1856 # gnt-instance change-group -I hail --to rack2 inst1.example.com
1865 **add-tags** [\--from *file*] {*instancename*} {*tag*...}
1867 Add tags to the given instance. If any of the tags contains invalid
1868 characters, the entire operation will abort.
1870 If the ``--from`` option is given, the list of tags will be extended
1871 with the contents of that file (each line becomes a tag). In this
1872 case, there is not need to pass tags on the command line (if you do,
1873 both sources will be used). A file name of ``-`` will be interpreted
1879 **list-tags** {*instancename*}
1881 List the tags of the given instance.
1886 **remove-tags** [\--from *file*] {*instancename*} {*tag*...}
1888 Remove tags from the given instance. If any of the tags are not
1889 existing on the node, the entire operation will abort.
1891 If the ``--from`` option is given, the list of tags to be removed will
1892 be extended with the contents of that file (each line becomes a tag).
1893 In this case, there is not need to pass tags on the command line (if
1894 you do, tags from both sources will be removed). A file name of ``-``
1895 will be interpreted as stdin.
1897 .. vim: set textwidth=72 :