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*[,spindles=*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*}
43 | [\--submit] [\--print-job-id]
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 How many spindles (physical disks on the node) the disk should span.
64 The access mode. Either ``ro`` (read-only) or the default ``rw``
68 This option specifies a name for the disk, which can be used as a disk
69 identifier. An instance can not have two disks with the same name.
72 The LVM volume group. This works only for LVM and DRBD devices.
75 This options specifies a different VG for the metadata device. This
76 works only for DRBD devices
78 When creating ExtStorage disks, also arbitrary parameters can be passed,
79 to the ExtStorage provider. Those parameters are passed as additional
80 comma separated options. Therefore, an ExtStorage disk provided by
81 provider ``pvdr1`` with parameters ``param1``, ``param2`` would be
82 passed as ``--disk 0:size=10G,provider=pvdr1,param1=val1,param2=val2``.
84 When using the ``adopt`` key in the disk definition, Ganeti will
85 reuse those volumes (instead of creating new ones) as the
86 instance's disks. Ganeti will rename these volumes to the standard
87 format, and (without installing the OS) will use them as-is for the
88 instance. This allows migrating instances from non-managed mode
89 (e.g. plain KVM with LVM) to being managed via Ganeti. Please note that
90 this works only for the \`plain' disk template (see below for
93 Alternatively, a single-disk instance can be created via the ``-s``
94 option which takes a single argument, the size of the disk. This is
95 similar to the Ganeti 1.2 version (but will only create one disk).
97 The minimum disk specification is therefore ``--disk 0:size=20G`` (or
98 ``-s 20G`` when using the ``-s`` option), and a three-disk instance
99 can be specified as ``--disk 0:size=20G --disk 1:size=4G --disk
102 The minimum information needed to specify an ExtStorage disk are the
103 ``size`` and the ``provider``. For example:
104 ``--disk 0:size=20G,provider=pvdr1``.
106 The ``--no-ip-check`` skips the checks that are done to see if the
107 instance's IP is not already alive (i.e. reachable from the master
110 The ``--no-name-check`` skips the check for the instance name via
111 the resolver (e.g. in DNS or /etc/hosts, depending on your setup).
112 Since the name check is used to compute the IP address, if you pass
113 this option you must also pass the ``--no-ip-check`` option.
115 If you don't want the instance to automatically start after
116 creation, this is possible via the ``--no-start`` option. This will
117 leave the instance down until a subsequent **gnt-instance start**
120 The NICs of the instances can be specified via the ``--net``
121 option. By default, one NIC is created for the instance, with a
122 random MAC, and set up according the the cluster level NIC
123 parameters. Each NIC can take these parameters (all optional):
126 either a value or 'generate' to generate a new unique MAC
129 specifies the IP address assigned to the instance from the Ganeti
130 side (this is not necessarily what the instance will use, but what
131 the node expects the instance to use). Note that if an IP in the
132 range of a network configured with **gnt-network**\(8) is used,
133 and the NIC is not already connected to it, this network has to be
134 passed in the **network** parameter if this NIC is meant to be
135 connected to the said network. ``--no-conflicts-check`` can be used
136 to override this check. The special value **pool** causes Ganeti to
137 select an IP from the the network the NIC is or will be connected to.
140 specifies the connection mode for this NIC: routed, bridged or
144 in bridged or openvswitch mode specifies the interface to attach
145 this NIC to, in routed mode it's intended to differentiate between
146 different routing tables/instance groups (but the meaning is
147 dependent on the network script, see **gnt-cluster**\(8) for more
148 details). Note that openvswitch support is also hypervisor
152 derives the mode and the link from the settings of the network
153 which is identified by its name. If the network option is chosen,
154 link and mode must not be specified. Note that the mode and link
155 depend on the network-to-nodegroup connection, thus allowing
156 different nodegroups to be connected to the same network in
160 this option specifies a name for the NIC, which can be used as a NIC
161 identifier. An instance can not have two NICs with the same name.
164 in openvswitch mode specifies the VLANs that the NIC will be
165 connected to. To connect as an access port use ``n`` or ``.n`` with
166 **n** being the VLAN ID. To connect as an trunk port use ``:n[:n]``.
167 A hybrid port can be created with ``.n:n[:n]``
169 Of these "mode" and "link" are NIC parameters, and inherit their
170 default at cluster level. Alternatively, if no network is desired for
171 the instance, you can prevent the default of one NIC with the
172 ``--no-nics`` option.
174 The ``-o (--os-type)`` option specifies the operating system to be
175 installed. The available operating systems can be listed with
176 **gnt-os list**. Passing ``--no-install`` will however skip the OS
177 installation, allowing a manual import if so desired. Note that the
178 no-installation mode will automatically disable the start-up of the
179 instance (without an OS, it most likely won't be able to start-up
182 The ``-B (--backend-parameters)`` option specifies the backend
183 parameters for the instance. If no such parameters are specified, the
184 values are inherited from the cluster. Possible parameters are:
187 the maximum memory size of the instance; as usual, suffixes can be
188 used to denote the unit, otherwise the value is taken in mebibytes
191 the minimum memory size of the instance; as usual, suffixes can be
192 used to denote the unit, otherwise the value is taken in mebibytes
195 the number of VCPUs to assign to the instance (if this value makes
196 sense for the hypervisor)
199 whether the instance is considered in the N+1 cluster checks
200 (enough redundancy in the cluster to survive a node failure)
203 ``True`` or ``False``, whether the instance must be failed over
204 (shut down and rebooted) always or it may be migrated (briefly
207 Note that before 2.6 Ganeti had a ``memory`` parameter, which was the
208 only value of memory an instance could have. With the
209 ``maxmem``/``minmem`` change Ganeti guarantees that at least the minimum
210 memory is always available for an instance, but allows more memory to be
211 used (up to the maximum memory) should it be free.
213 The ``-H (--hypervisor-parameters)`` option specified the hypervisor
214 to use for the instance (must be one of the enabled hypervisors on the
215 cluster) and optionally custom parameters for this instance. If not
216 other options are used (i.e. the invocation is just -H *NAME*) the
217 instance will inherit the cluster options. The defaults below show the
218 cluster defaults at cluster creation time.
220 The possible hypervisor options are as follows:
223 Valid for the Xen HVM and KVM hypervisors.
225 A string value denoting the boot order. This has different meaning
226 for the Xen HVM hypervisor and for the KVM one.
228 For Xen HVM, The boot order is a string of letters listing the boot
229 devices, with valid device letters being:
243 The default is not to set an HVM boot order, which is interpreted
246 For KVM the boot order is either "floppy", "cdrom", "disk" or
247 "network". Please note that older versions of KVM couldn't netboot
248 from virtio interfaces. This has been fixed in more recent versions
249 and is confirmed to work at least with qemu-kvm 0.11.1. Also note
250 that if you have set the ``kernel_path`` option, that will be used
251 for booting, and this setting will be silently ignored.
254 Valid for the Xen HVM and PVM hypervisors.
256 Relevant to non-pvops guest kernels, in which the disk device names
257 are given by the host. Allows one to specify 'xvd', which helps run
258 Red Hat based installers, driven by anaconda.
261 Valid for the KVM hypervisor.
263 The path to a floppy disk image to attach to the instance. This
264 is useful to install Windows operating systems on Virt/IO disks
265 because you can specify here the floppy for the drivers at
269 Valid for the Xen HVM and KVM hypervisors.
271 The path to a CDROM image to attach to the instance.
274 Valid for the KVM hypervisor.
276 The path to a second CDROM image to attach to the instance.
277 **NOTE**: This image can't be used to boot the system. To do that
278 you have to use the 'cdrom\_image\_path' option.
281 Valid for the Xen HVM and KVM hypervisors.
283 This parameter determines the way the network cards are presented
284 to the instance. The possible options are:
286 - rtl8139 (default for Xen HVM) (HVM & KVM)
287 - ne2k\_isa (HVM & KVM)
288 - ne2k\_pci (HVM & KVM)
294 - paravirtual (default for KVM) (HVM & KVM)
297 Valid for the Xen HVM hypervisor.
299 This parameter specifies the vif type of the nic configuration
300 of the instance. Unsetting the value leads to no type being specified
301 in the configuration. Note that this parameter only takes effect when
302 the 'nic_type' is not set. The possible options are:
308 Valid for the Xen HVM and KVM hypervisors.
310 This parameter determines the way the disks are presented to the
311 instance. The possible options are:
313 - ioemu [default] (HVM & KVM)
322 Valid for the KVM hypervisor.
324 This parameter determines the way the cdroms disks are presented
325 to the instance. The default behavior is to get the same value of
326 the earlier parameter (disk_type). The possible options are:
337 Valid for the Xen HVM and KVM hypervisors.
339 Specifies the address that the VNC listener for this instance
340 should bind to. Valid values are IPv4 addresses. Use the address
341 0.0.0.0 to bind to all available interfaces (this is the default)
342 or specify the address of one of the interfaces on the node to
343 restrict listening to that interface.
346 Valid for the KVM hypervisor.
348 A boolean option that controls whether the VNC connection is
352 Valid for the KVM hypervisor.
354 If ``vnc_tls`` is enabled, this options specifies the path to the
355 x509 certificate to use.
358 Valid for the KVM hypervisor.
361 Valid for the KVM hypervisor.
363 Specifies the address or interface on which the SPICE server will
364 listen. Valid values are:
366 - IPv4 addresses, including 0.0.0.0 and 127.0.0.1
367 - IPv6 addresses, including :: and ::1
368 - names of network interfaces
370 If a network interface is specified, the SPICE server will be bound
371 to one of the addresses of that interface.
374 Valid for the KVM hypervisor.
376 Specifies which version of the IP protocol should be used by the
379 It is mainly intended to be used for specifying what kind of IP
380 addresses should be used if a network interface with both IPv4 and
381 IPv6 addresses is specified via the ``spice_bind`` parameter. In
382 this case, if the ``spice_ip_version`` parameter is not used, the
383 default IP version of the cluster will be used.
385 spice\_password\_file
386 Valid for the KVM hypervisor.
388 Specifies a file containing the password that must be used when
389 connecting via the SPICE protocol. If the option is not specified,
390 passwordless connections are allowed.
392 spice\_image\_compression
393 Valid for the KVM hypervisor.
395 Configures the SPICE lossless image compression. Valid values are:
404 spice\_jpeg\_wan\_compression
405 Valid for the KVM hypervisor.
407 Configures how SPICE should use the jpeg algorithm for lossy image
408 compression on slow links. Valid values are:
414 spice\_zlib\_glz\_wan\_compression
415 Valid for the KVM hypervisor.
417 Configures how SPICE should use the zlib-glz algorithm for lossy image
418 compression on slow links. Valid values are:
424 spice\_streaming\_video
425 Valid for the KVM hypervisor.
427 Configures how SPICE should detect video streams. Valid values are:
433 spice\_playback\_compression
434 Valid for the KVM hypervisor.
436 Configures whether SPICE should compress audio streams or not.
439 Valid for the KVM hypervisor.
441 Specifies that the SPICE server must use TLS to encrypt all the
442 traffic with the client.
445 Valid for the KVM hypervisor.
447 Specifies a list of comma-separated ciphers that SPICE should use
448 for TLS connections. For the format, see man **cipher**\(1).
451 Valid for the KVM hypervisor.
453 Enables or disables passing mouse events via SPICE vdagent.
456 Valid for the KVM hypervisor.
458 This parameter determines the emulated cpu for the instance. If this
459 parameter is empty (which is the default configuration), it will not
462 Be aware of setting this parameter to ``"host"`` if you have nodes
463 with different CPUs from each other. Live migration may stop working
466 For more information please refer to the KVM manual.
469 Valid for the Xen HVM and KVM hypervisors.
471 A boolean option that specifies if the hypervisor should enable
472 ACPI support for this instance. By default, ACPI is disabled.
475 Valid for the Xen HVM and KVM hypervisors.
477 A boolean option that specifies if the hypervisor should enable
478 PAE support for this instance. The default is false, disabling PAE
482 Valid for the Xen HVM hypervisor.
484 A boolean option that specifies if the hypervisor should enable
485 viridian (Hyper-V) for this instance. The default is false,
486 disabling viridian support.
489 Valid for the Xen HVM and KVM hypervisors.
491 A boolean option that specifies if the instance should be started
492 with its clock set to the localtime of the machine (when true) or
493 to the UTC (When false). The default is false, which is useful for
494 Linux/Unix machines; for Windows OSes, it is recommended to enable
498 Valid for the Xen PVM and KVM hypervisors.
500 This option specifies the path (on the node) to the kernel to boot
501 the instance with. Xen PVM instances always require this, while for
502 KVM if this option is empty, it will cause the machine to load the
503 kernel from its disks (and the boot will be done accordingly to
507 Valid for the Xen PVM and KVM hypervisors.
509 This options specifies extra arguments to the kernel that will be
510 loaded. device. This is always used for Xen PVM, while for KVM it
511 is only used if the ``kernel_path`` option is also specified.
513 The default setting for this value is simply ``"ro"``, which
514 mounts the root disk (initially) in read-only one. For example,
515 setting this to single will cause the instance to start in
519 Valid for the Xen PVM and KVM hypervisors.
521 This option specifies the path (on the node) to the initrd to boot
522 the instance with. Xen PVM instances can use this always, while
523 for KVM if this option is only used if the ``kernel_path`` option
524 is also specified. You can pass here either an absolute filename
525 (the path to the initrd) if you want to use an initrd, or use the
526 format no\_initrd\_path for no initrd.
529 Valid for the Xen PVM and KVM hypervisors.
531 This options specifies the name of the root device. This is always
532 needed for Xen PVM, while for KVM it is only used if the
533 ``kernel_path`` option is also specified.
535 Please note, that if this setting is an empty string and the
536 hypervisor is Xen it will not be written to the Xen configuration
540 Valid for the KVM hypervisor.
542 This boolean option specifies whether to emulate a serial console
543 for the instance. Note that some versions of KVM have a bug that
544 will make an instance hang when configured to use the serial console
545 unless a connection is made to it within about 2 seconds of the
546 instance's startup. For such case it's recommended to disable this
547 option, which is enabled by default.
550 Valid for the KVM hypervisor.
552 This integer option specifies the speed of the serial console.
553 Common values are 9600, 19200, 38400, 57600 and 115200: choose the
554 one which works on your system. (The default is 38400 for historical
555 reasons, but newer versions of kvm/qemu work with 115200)
558 Valid for the KVM hypervisor.
560 The disk cache mode. It can be either default to not pass any
561 cache option to KVM, or one of the KVM cache modes: none (for
562 direct I/O), writethrough (to use the host cache but report
563 completion to the guest only when the host has committed the
564 changes to disk) or writeback (to use the host cache and report
565 completion as soon as the data is in the host cache). Note that
566 there are special considerations for the cache mode depending on
567 version of KVM used and disk type (always raw file under Ganeti),
568 please refer to the KVM documentation for more details.
571 Valid for the KVM hypervisor.
573 The security model for kvm. Currently one of *none*, *user* or
574 *pool*. Under *none*, the default, nothing is done and instances
575 are run as the Ganeti daemon user (normally root).
577 Under *user* kvm will drop privileges and become the user
578 specified by the security\_domain parameter.
580 Under *pool* a global cluster pool of users will be used, making
581 sure no two instances share the same user on the same node. (this
582 mode is not implemented yet)
585 Valid for the KVM hypervisor.
587 Under security model *user* the username to run the instance
588 under. It must be a valid username existing on the host.
590 Cannot be set under security model *none* or *pool*.
593 Valid for the KVM hypervisor.
595 If *enabled* the -enable-kvm flag is passed to kvm. If *disabled*
596 -disable-kvm is passed. If unset no flag is passed, and the
597 default running mode for your kvm binary will be used.
600 Valid for the KVM hypervisor.
602 This option passes the -mem-path argument to kvm with the path (on
603 the node) to the mount point of the hugetlbfs file system, along
604 with the -mem-prealloc argument too.
607 Valid for the KVM hypervisor.
609 This boolean option determines whether to run the KVM instance in a
612 If it is set to ``true``, an empty directory is created before
613 starting the instance and its path is passed via the -chroot flag
614 to kvm. The directory is removed when the instance is stopped.
616 It is set to ``false`` by default.
619 Valid for the KVM hypervisor.
621 The maximum amount of time (in ms) a KVM instance is allowed to be
622 frozen during a live migration, in order to copy dirty memory
623 pages. Default value is 30ms, but you may need to increase this
624 value for busy instances.
626 This option is only effective with kvm versions >= 87 and qemu-kvm
630 Valid for the Xen, KVM and LXC hypervisors.
632 The processes belonging to the given instance are only scheduled
633 on the specified CPUs.
635 The format of the mask can be given in three forms. First, the word
636 "all", which signifies the common case where all VCPUs can live on
637 any CPU, based on the hypervisor's decisions.
639 Second, a comma-separated list of CPU IDs or CPU ID ranges. The
640 ranges are defined by a lower and higher boundary, separated by a
641 dash, and the boundaries are inclusive. In this form, all VCPUs of
642 the instance will be mapped on the selected list of CPUs. Example:
643 ``0-2,5``, mapping all VCPUs (no matter how many) onto physical CPUs
646 The last form is used for explicit control of VCPU-CPU pinnings. In
647 this form, the list of VCPU mappings is given as a colon (:)
648 separated list, whose elements are the possible values for the
649 second or first form above. In this form, the number of elements in
650 the colon-separated list _must_ equal the number of VCPUs of the
657 # Map the entire instance to CPUs 0-2
658 gnt-instance modify -H cpu_mask=0-2 my-inst
660 # Map vCPU 0 to physical CPU 1 and vCPU 1 to CPU 3 (assuming 2 vCPUs)
661 gnt-instance modify -H cpu_mask=1:3 my-inst
663 # Pin vCPU 0 to CPUs 1 or 2, and vCPU 1 to any CPU
664 gnt-instance modify -H cpu_mask=1-2:all my-inst
666 # Pin vCPU 0 to any CPU, vCPU 1 to CPUs 1, 3, 4 or 5, and CPU 2 to
667 # CPU 0 (backslashes for escaping the comma)
668 gnt-instance modify -H cpu_mask=all:1\\,3-5:0 my-inst
670 # Pin entire VM to CPU 0
671 gnt-instance modify -H cpu_mask=0 my-inst
673 # Turn off CPU pinning (default setting)
674 gnt-instance modify -H cpu_mask=all my-inst
677 Valid for the Xen hypervisor.
679 Set the maximum amount of cpu usage by the VM. The value is a percentage
680 between 0 and (100 * number of VCPUs). Default cap is 0: unlimited.
683 Valid for the Xen hypervisor.
685 Set the cpu time ratio to be allocated to the VM. Valid values are
686 between 1 and 65535. Default weight is 256.
689 Valid for the KVM hypervisor.
691 This option specifies the usb mouse type to be used. It can be
692 "mouse" or "tablet". When using VNC it's recommended to set it to
696 Valid for the KVM hypervisor.
698 This option specifies the keyboard mapping to be used. It is only
699 needed when using the VNC console. For example: "fr" or "en-gb".
702 Valid for Xen PVM, Xen HVM and KVM hypervisors.
704 Normally if an instance reboots, the hypervisor will restart it. If
705 this option is set to ``exit``, the hypervisor will treat a reboot
706 as a shutdown instead.
708 It is set to ``reboot`` by default.
711 Valid for the KVM hypervisor.
713 Number of emulated CPU cores.
716 Valid for the KVM hypervisor.
718 Number of emulated CPU threads.
721 Valid for the KVM hypervisor.
723 Number of emulated CPU sockets.
726 Valid for the KVM hypervisor.
728 Comma separated list of emulated sounds cards, or "all" to enable
729 all the available ones.
732 Valid for the KVM hypervisor.
734 Comma separated list of usb devices. These can be emulated devices
735 or passthrough ones, and each one gets passed to kvm with its own
736 ``-usbdevice`` option. See the **qemu**\(1) manpage for the syntax
737 of the possible components.
740 Valid for the KVM hypervisor.
742 Emulated vga mode, passed the the kvm -vga option.
745 Valid for the KVM hypervisor.
747 Any other option to the KVM hypervisor, useful tweaking anything
748 that Ganeti doesn't support. Note that values set with this
749 parameter are split on a space character and currently don't support
753 Valid for the KVM hypervisor.
755 Use in case an instance must be booted with an exact type of
756 machine version (due to e.g. outdated drivers). In case it's not set
757 the default version supported by your version of kvm is used.
760 Valid for the KVM hypervisor.
762 Path to the userspace KVM (or qemu) program.
765 Valid for the KVM hypervisor.
767 This boolean option determines whether the tap devices used by the
768 KVM paravirtual nics (virtio-net) will get created with VNET_HDR
769 (IFF_VNET_HDR) support.
771 If set to false, it effectively disables offloading on the virio-net
772 interfaces, which prevents host kernel tainting and log flooding,
773 when dealing with broken or malicious virtio-net drivers.
775 It is set to ``true`` by default.
777 The ``-O (--os-parameters)`` option allows customisation of the OS
778 parameters. The actual parameter names and values depends on the OS
779 being used, but the syntax is the same key=value. For example, setting
780 a hypothetical ``dhcp`` parameter to yes can be achieved by::
782 gnt-instance add -O dhcp=yes ...
784 The ``-I (--iallocator)`` option specifies the instance allocator plugin
785 to use (``.`` means the default allocator). If you pass in this option
786 the allocator will select nodes for this instance automatically, so you
787 don't need to pass them with the ``-n`` option. For more information
788 please refer to the instance allocator documentation.
790 The ``-t (--disk-template)`` options specifies the disk layout type
791 for the instance. If no disk template is specified, the default disk
792 template is used. The default disk template is the first in the list
793 of enabled disk templates, which can be adjusted cluster-wide with
794 ``gnt-cluster modify``. The available choices for disk templates are:
797 This creates an instance with no disks. Its useful for testing only
798 (or other special cases).
801 Disk devices will be regular files.
804 Disk devices will be regulare files on a shared directory.
807 Disk devices will be logical volumes.
810 Disk devices will be drbd (version 8.x) on top of lvm volumes.
813 Disk devices will be rbd volumes residing inside a RADOS cluster.
816 Disk devices will be adopted pre-existent block devices.
819 Disk devices will be provided by external shared storage,
820 through the ExtStorage Interface using ExtStorage providers.
822 The optional second value of the ``-n (--node)`` is used for the drbd
823 template type and specifies the remote node.
825 If you do not want gnt-instance to wait for the disk mirror to be
826 synced, use the ``--no-wait-for-sync`` option.
828 The ``--file-storage-dir`` specifies the relative path under the
829 cluster-wide file storage directory to store file-based disks. It is
830 useful for having different subdirectories for different
831 instances. The full path of the directory where the disk files are
832 stored will consist of cluster-wide file storage directory + optional
833 subdirectory + instance name. This option is only relevant for
834 instances using the file storage backend.
836 The ``--file-driver`` specifies the driver to use for file-based
837 disks. Note that currently these drivers work with the xen hypervisor
838 only. This option is only relevant for instances using the file
839 storage backend. The available choices are:
842 Kernel loopback driver. This driver uses loopback devices to
843 access the filesystem within the file. However, running I/O
844 intensive applications in your instance using the loop driver
845 might result in slowdowns. Furthermore, if you use the loopback
846 driver consider increasing the maximum amount of loopback devices
847 (on most systems it's 8) using the max\_loop param.
850 The blktap driver (for Xen hypervisors). In order to be able to
851 use the blktap driver you should check if the 'blktapctrl' user
852 space disk agent is running (usually automatically started via
853 xend). This user-level disk I/O interface has the advantage of
854 better performance. Especially if you use a network file system
855 (e.g. NFS) to store your instances this is the recommended choice.
857 If ``--ignore-ipolicy`` is given any instance policy violations occuring
858 during this operation are ignored.
860 See **ganeti**\(7) for a description of ``--submit`` and other common
865 # gnt-instance add -t file --disk 0:size=30g -B maxmem=512 -o debian-etch \
866 -n node1.example.com --file-storage-dir=mysubdir instance1.example.com
867 # gnt-instance add -t plain --disk 0:size=30g -B maxmem=1024,minmem=512 \
868 -o debian-etch -n node1.example.com instance1.example.com
869 # gnt-instance add -t plain --disk 0:size=30g --disk 1:size=100g,vg=san \
870 -B maxmem=512 -o debian-etch -n node1.example.com instance1.example.com
871 # gnt-instance add -t drbd --disk 0:size=30g -B maxmem=512 -o debian-etch \
872 -n node1.example.com:node2.example.com instance2.example.com
873 # gnt-instance add -t rbd --disk 0:size=30g -B maxmem=512 -o debian-etch \
874 -n node1.example.com instance1.example.com
875 # gnt-instance add -t ext --disk 0:size=30g,provider=pvdr1 -B maxmem=512 \
876 -o debian-etch -n node1.example.com instance1.example.com
877 # gnt-instance add -t ext --disk 0:size=30g,provider=pvdr1,param1=val1 \
878 --disk 1:size=40g,provider=pvdr2,param2=val2,param3=val3 -B maxmem=512 \
879 -o debian-etch -n node1.example.com instance1.example.com
886 | [{-I|\--iallocator} *instance allocator*]
887 | {instances\_file.json}
889 This command (similar to the Ganeti 1.2 **batcher** tool) submits
890 multiple instance creation jobs based on a definition file. This
891 file can contain all options which are valid when adding an instance
892 with the exception of the ``iallocator`` field. The IAllocator is,
893 for optimization purposes, only allowed to be set for the whole batch
894 operation using the ``--iallocator`` parameter.
896 The instance file must be a valid-formed JSON file, containing an
897 array of dictionaries with instance creation parameters. All parameters
898 (except ``iallocator``) which are valid for the instance creation
899 OP code are allowed. The most important ones are:
902 The FQDN of the new instance.
905 The disk template to use for the instance, the same as in the
909 Array of disk specifications. Each entry describes one disk as a
910 dictionary of disk parameters.
913 A dictionary of backend parameters.
916 The hypervisor for the instance.
919 A dictionary with the hypervisor options. If not passed, the default
920 hypervisor options will be inherited.
923 List of NICs that will be created for the instance. Each entry
924 should be a dict, with mac, ip, mode and link as possible keys.
925 Please don't provide the "mac, ip, mode, link" parent keys if you
926 use this method for specifying NICs.
929 The primary and optionally the secondary node to use for the
930 instance (in case an iallocator script is not used). If those
931 parameters are given, they have to be given consistently for all
932 instances in the batch operation.
935 whether to start the instance
938 Skip the check for already-in-use instance; see the description in
939 the **add** command for details.
942 Skip the name check for instances; see the description in the
943 **add** command for details.
945 file\_storage\_dir, file\_driver
946 Configuration for the file disk type, see the **add** command for
950 A simple definition for one instance can be (with most of the
951 parameters taken from the cluster defaults)::
956 "instance_name": "instance1.example.com",
957 "disk_template": "drbd",
958 "os_type": "debootstrap",
959 "disks": [{"size":"1024"}],
961 "hypervisor": "xen-pvm"
965 "instance_name": "instance2.example.com",
966 "disk_template": "drbd",
967 "os_type": "debootstrap",
968 "disks": [{"size":"4096", "mode": "rw", "vg": "xenvg"}],
970 "hypervisor": "xen-hvm",
971 "hvparams": {"acpi": true},
972 "beparams": {"maxmem": 512, "minmem": 256}
976 The command will display the job id for each submitted instance, as
979 # gnt-instance batch-create instances.json
980 Submitted jobs 37, 38
985 | **remove** [\--ignore-failures] [\--shutdown-timeout=*N*] [\--submit]
986 | [\--print-job-id] [\--force] {*instance*}
988 Remove an instance. This will remove all data from the instance and
989 there is *no way back*. If you are not sure if you use an instance
990 again, use **shutdown** first and leave it in the shutdown state for a
993 The ``--ignore-failures`` option will cause the removal to proceed
994 even in the presence of errors during the removal of the instance
995 (e.g. during the shutdown or the disk removal). If this option is not
996 given, the command will stop at the first error.
998 The ``--shutdown-timeout`` is used to specify how much time to wait
999 before forcing the shutdown (e.g. ``xm destroy`` in Xen, killing the
1000 kvm process for KVM, etc.). By default two minutes are given to each
1003 The ``--force`` option is used to skip the interactive confirmation.
1005 See **ganeti**\(7) for a description of ``--submit`` and other common
1010 # gnt-instance remove instance1.example.com
1017 | [\--no-headers] [\--separator=*SEPARATOR*] [\--units=*UNITS*] [-v]
1018 | [{-o|\--output} *[+]FIELD,...*] [\--filter] [instance...]
1020 Shows the currently configured instances with memory usage, disk
1021 usage, the node they are running on, and their run status.
1023 The ``--no-headers`` option will skip the initial header line. The
1024 ``--separator`` option takes an argument which denotes what will be
1025 used between the output fields. Both these options are to help
1028 The units used to display the numeric values in the output varies,
1029 depending on the options given. By default, the values will be
1030 formatted in the most appropriate unit. If the ``--separator`` option
1031 is given, then the values are shown in mebibytes to allow parsing by
1032 scripts. In both cases, the ``--units`` option can be used to enforce
1033 a given output unit.
1035 The ``-v`` option activates verbose mode, which changes the display of
1036 special field states (see **ganeti**\(7)).
1038 The ``-o (--output)`` option takes a comma-separated list of output
1039 fields. The available fields and their meaning are:
1041 @QUERY_FIELDS_INSTANCE@
1043 If the value of the option starts with the character ``+``, the new
1044 field(s) will be added to the default list. This allows one to quickly
1045 see the default list plus a few other fields, instead of retyping the
1046 entire list of fields.
1048 There is a subtle grouping about the available output fields: all
1049 fields except for ``oper_state``, ``oper_ram``, ``oper_vcpus`` and
1050 ``status`` are configuration value and not run-time values. So if you
1051 don't select any of the these fields, the query will be satisfied
1052 instantly from the cluster configuration, without having to ask the
1053 remote nodes for the data. This can be helpful for big clusters when
1054 you only want some data and it makes sense to specify a reduced set of
1057 If exactly one argument is given and it appears to be a query filter
1058 (see **ganeti**\(7)), the query result is filtered accordingly. For
1059 ambiguous cases (e.g. a single field name as a filter) the ``--filter``
1060 (``-F``) option forces the argument to be treated as a filter (e.g.
1061 ``gnt-instance list -F admin_state``).
1063 The default output field list is: ``name``, ``os``, ``pnode``,
1064 ``admin_state``, ``oper_state``, ``oper_ram``.
1070 **list-fields** [field...]
1072 Lists available fields for instances.
1078 **info** [-s \| \--static] [\--roman] {\--all \| *instance*}
1080 Show detailed information about the given instance(s). This is
1081 different from **list** as it shows detailed data about the instance's
1082 disks (especially useful for the drbd disk template).
1084 If the option ``-s`` is used, only information available in the
1085 configuration file is returned, without querying nodes, making the
1088 Use the ``--all`` to get info about all instances, rather than
1089 explicitly passing the ones you're interested in.
1091 The ``--roman`` option can be used to cause envy among people who like
1092 ancient cultures, but are stuck with non-latin-friendly cluster
1093 virtualization technologies.
1099 | [{-H|\--hypervisor-parameters} *HYPERVISOR\_PARAMETERS*]
1100 | [{-B|\--backend-parameters} *BACKEND\_PARAMETERS*]
1101 | [{-m|\--runtime-memory} *SIZE*]
1102 | [\--net add[:options...] \|
1103 | \--net [*N*:]add[,options...] \|
1104 | \--net [*ID*:]remove \|
1105 | \--net *ID*:modify[,options...]]
1106 | [\--disk add:size=*SIZE*[,options...] \|
1107 | \--disk *N*:add,size=*SIZE*[,options...] \|
1108 | \--disk *N*:add,size=*SIZE*,provider=*PROVIDER*[,options...][,param=*value*... ] \|
1109 | \--disk *ID*:modify[,options...]
1110 | \--disk [*ID*:]remove]
1111 | [{-t|\--disk-template} plain \| {-t|\--disk-template} drbd -n *new_secondary*] [\--no-wait-for-sync]
1112 | [\--new-primary=*node*]
1113 | [\--os-type=*OS* [\--force-variant]]
1114 | [{-O|\--os-parameters} *param*=*value*... ]
1115 | [\--offline \| \--online]
1116 | [\--submit] [\--print-job-id]
1117 | [\--ignore-ipolicy]
1120 Modifies the memory size, number of vcpus, ip address, MAC address
1121 and/or NIC parameters for an instance. It can also add and remove
1122 disks and NICs to/from the instance. Note that you need to give at
1123 least one of the arguments, otherwise the command complains.
1125 The ``-H (--hypervisor-parameters)``, ``-B (--backend-parameters)``
1126 and ``-O (--os-parameters)`` options specifies hypervisor, backend and
1127 OS parameter options in the form of name=value[,...]. For details
1128 which options can be specified, see the **add** command.
1130 The ``-t (--disk-template)`` option will change the disk template of
1131 the instance. Currently only conversions between the plain and drbd
1132 disk templates are supported, and the instance must be stopped before
1133 attempting the conversion. When changing from the plain to the drbd
1134 disk template, a new secondary node must be specified via the ``-n``
1135 option. The option ``--no-wait-for-sync`` can be used when converting
1136 to the ``drbd`` template in order to make the instance available for
1137 startup before DRBD has finished resyncing.
1139 The ``-m (--runtime-memory)`` option will change an instance's runtime
1140 memory to the given size (in MB if a different suffix is not specified),
1141 by ballooning it up or down to the new value.
1143 The ``--disk add:size=*SIZE*,[options..]`` option adds a disk to the
1144 instance, and ``--disk *N*:add:size=*SIZE*,[options..]`` will add a disk
1145 to the the instance at a specific index. The available options are the
1146 same as in the **add** command(``spindles``, ``mode``, ``name``, ``vg``,
1147 ``metavg``). When adding an ExtStorage disk the ``provider=*PROVIDER*``
1148 option is also mandatory and specifies the ExtStorage provider. Also,
1149 for ExtStorage disks arbitrary parameters can be passed as additional
1150 comma separated options, same as in the **add** command. -The ``--disk
1151 remove`` option will remove the last disk of the instance. Use ``--disk
1152 `` *ID*``:remove`` to remove a disk by its identifier. *ID* can be the
1153 index of the disk, the disks's name or the disks's UUID. The ``--disk
1154 *ID*:modify[,options...]`` will change the options of the disk.
1155 Available options are:
1158 The access mode. Either ``ro`` (read-only) or the default ``rw`` (read-write).
1161 This option specifies a name for the disk, which can be used as a disk
1162 identifier. An instance can not have two disks with the same name.
1164 The ``--net *N*:add[,options..]`` will add a new network interface to
1165 the instance. The available options are the same as in the **add**
1166 command (``mac``, ``ip``, ``link``, ``mode``, ``network``). The
1167 ``--net *ID*,remove`` will remove the intances' NIC with *ID* identifier,
1168 which can be the index of the NIC, the NIC's name or the NIC's UUID.
1169 The ``--net *ID*:modify[,options..]`` option will change the parameters of
1170 the instance network interface with the *ID* identifier.
1172 The option ``-o (--os-type)`` will change the OS name for the instance
1173 (without reinstallation). In case an OS variant is specified that is
1174 not found, then by default the modification is refused, unless
1175 ``--force-variant`` is passed. An invalid OS will also be refused,
1176 unless the ``--force`` option is given.
1178 The option ``--new-primary`` will set the new primary node of an instance
1179 assuming the disks have already been moved manually. Unless the ``--force``
1180 option is given, it is verified that the instance is no longer running
1181 on its current primary node.
1183 The ``--online`` and ``--offline`` options are used to transition an
1184 instance into and out of the ``offline`` state. An instance can be
1185 turned offline only if it was previously down. The ``--online`` option
1186 fails if the instance was not in the ``offline`` state, otherwise it
1187 changes instance's state to ``down``. These modifications take effect
1190 If ``--ignore-ipolicy`` is given any instance policy violations occuring
1191 during this operation are ignored.
1193 See **ganeti**\(7) for a description of ``--submit`` and other common
1196 Most of the changes take effect at the next restart. If the instance is
1197 running, there is no effect on the instance.
1202 | **reinstall** [{-o|\--os-type} *os-type*] [\--select-os] [-f *force*]
1203 | [\--force-multiple]
1204 | [\--instance \| \--node \| \--primary \| \--secondary \| \--all]
1205 | [{-O|\--os-parameters} *OS\_PARAMETERS*] [\--submit] [\--print-job-id]
1208 Reinstalls the operating system on the given instance(s). The
1209 instance(s) must be stopped when running this command. If the ``-o
1210 (--os-type)`` is specified, the operating system is changed.
1212 The ``--select-os`` option switches to an interactive OS reinstall.
1213 The user is prompted to select the OS template from the list of
1214 available OS templates. OS parameters can be overridden using ``-O
1215 (--os-parameters)`` (more documentation for this option under the
1218 Since this is a potentially dangerous command, the user will be
1219 required to confirm this action, unless the ``-f`` flag is passed.
1220 When multiple instances are selected (either by passing multiple
1221 arguments or by using the ``--node``, ``--primary``, ``--secondary``
1222 or ``--all`` options), the user must pass the ``--force-multiple``
1223 options to skip the interactive confirmation.
1225 See **ganeti**\(7) for a description of ``--submit`` and other common
1231 | **rename** [\--no-ip-check] [\--no-name-check] [\--submit] [\--print-job-id]
1232 | {*instance*} {*new\_name*}
1234 Renames the given instance. The instance must be stopped when running
1235 this command. The requirements for the new name are the same as for
1236 adding an instance: the new name must be resolvable and the IP it
1237 resolves to must not be reachable (in order to prevent duplicate IPs
1238 the next time the instance is started). The IP test can be skipped if
1239 the ``--no-ip-check`` option is passed.
1241 Note that you can rename an instance to its same name, to force
1242 re-executing the os-specific rename script for that instance, if
1245 The ``--no-name-check`` skips the check for the new instance name via
1246 the resolver (e.g. in DNS or /etc/hosts, depending on your setup) and
1247 that the resolved name matches the provided name. Since the name check
1248 is used to compute the IP address, if you pass this option you must also
1249 pass the ``--no-ip-check`` option.
1251 See **ganeti**\(7) for a description of ``--submit`` and other common
1254 Starting/stopping/connecting to console
1255 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1261 | [\--force] [\--ignore-offline]
1262 | [\--force-multiple] [\--no-remember]
1263 | [\--instance \| \--node \| \--primary \| \--secondary \| \--all \|
1264 | \--tags \| \--node-tags \| \--pri-node-tags \| \--sec-node-tags]
1265 | [{-H|\--hypervisor-parameters} ``key=value...``]
1266 | [{-B|\--backend-parameters} ``key=value...``]
1267 | [\--submit] [\--print-job-id] [\--paused]
1270 Starts one or more instances, depending on the following options. The
1271 four available modes are:
1274 will start the instances given as arguments (at least one argument
1275 required); this is the default selection
1278 will start the instances who have the given node as either primary
1282 will start all instances whose primary node is in the list of nodes
1283 passed as arguments (at least one node required)
1286 will start all instances whose secondary node is in the list of
1287 nodes passed as arguments (at least one node required)
1290 will start all instances in the cluster (no arguments accepted)
1293 will start all instances in the cluster with the tags given as
1297 will start all instances in the cluster on nodes with the tags
1301 will start all instances in the cluster on primary nodes with the
1302 tags given as arguments
1305 will start all instances in the cluster on secondary nodes with the
1306 tags given as arguments
1308 Note that although you can pass more than one selection option, the
1309 last one wins, so in order to guarantee the desired result, don't pass
1310 more than one such option.
1312 Use ``--force`` to start even if secondary disks are failing.
1313 ``--ignore-offline`` can be used to ignore offline primary nodes and
1314 mark the instance as started even if the primary is not available.
1316 The ``--force-multiple`` will skip the interactive confirmation in the
1317 case the more than one instance will be affected.
1319 The ``--no-remember`` option will perform the startup but not change
1320 the state of the instance in the configuration file (if it was stopped
1321 before, Ganeti will still think it needs to be stopped). This can be
1322 used for testing, or for a one shot-start where you don't want the
1323 watcher to restart the instance if it crashes.
1325 The ``-H (--hypervisor-parameters)`` and ``-B (--backend-parameters)``
1326 options specify temporary hypervisor and backend parameters that can
1327 be used to start an instance with modified parameters. They can be
1328 useful for quick testing without having to modify an instance back and
1331 # gnt-instance start -H kernel_args="single" instance1
1332 # gnt-instance start -B maxmem=2048 instance2
1335 The first form will start the instance instance1 in single-user mode,
1336 and the instance instance2 with 2GB of RAM (this time only, unless
1337 that is the actual instance memory size already). Note that the values
1338 override the instance parameters (and not extend them): an instance
1339 with "kernel\_args=ro" when started with -H kernel\_args=single will
1340 result in "single", not "ro single".
1342 The ``--paused`` option is only valid for Xen and kvm hypervisors. This
1343 pauses the instance at the start of bootup, awaiting ``gnt-instance
1344 console`` to unpause it, allowing the entire boot process to be
1345 monitored for debugging.
1347 See **ganeti**\(7) for a description of ``--submit`` and other common
1352 # gnt-instance start instance1.example.com
1353 # gnt-instance start --node node1.example.com node2.example.com
1354 # gnt-instance start --all
1362 | [\--force] [\--force-multiple] [\--ignore-offline] [\--no-remember]
1363 | [\--instance \| \--node \| \--primary \| \--secondary \| \--all \|
1364 | \--tags \| \--node-tags \| \--pri-node-tags \| \--sec-node-tags]
1365 | [\--submit] [\--print-job-id]
1368 Stops one or more instances. If the instance cannot be cleanly stopped
1369 during a hardcoded interval (currently 2 minutes), it will forcibly
1370 stop the instance (equivalent to switching off the power on a physical
1373 The ``--timeout`` is used to specify how much time to wait before
1374 forcing the shutdown (e.g. ``xm destroy`` in Xen, killing the kvm
1375 process for KVM, etc.). By default two minutes are given to each
1378 The ``--instance``, ``--node``, ``--primary``, ``--secondary``,
1379 ``--all``, ``--tags``, ``--node-tags``, ``--pri-node-tags`` and
1380 ``--sec-node-tags`` options are similar as for the **startup** command
1381 and they influence the actual instances being shutdown.
1383 ``--ignore-offline`` can be used to ignore offline primary nodes and
1384 force the instance to be marked as stopped. This option should be used
1385 with care as it can lead to an inconsistent cluster state.
1387 Use ``--force`` to be able to shutdown an instance even when it's marked
1388 as offline. This is useful is an offline instance ends up in the
1389 ``ERROR_up`` state, for example.
1391 The ``--no-remember`` option will perform the shutdown but not change
1392 the state of the instance in the configuration file (if it was running
1393 before, Ganeti will still thinks it needs to be running). This can be
1394 useful for a cluster-wide shutdown, where some instances are marked as
1395 up and some as down, and you don't want to change the running state:
1396 you just need to disable the watcher, shutdown all instances with
1397 ``--no-remember``, and when the watcher is activated again it will
1398 restore the correct runtime state for all instances.
1400 See **ganeti**\(7) for a description of ``--submit`` and other common
1405 # gnt-instance shutdown instance1.example.com
1406 # gnt-instance shutdown --all
1413 | [{-t|\--type} *REBOOT-TYPE*]
1414 | [\--ignore-secondaries]
1415 | [\--shutdown-timeout=*N*]
1416 | [\--force-multiple]
1417 | [\--instance \| \--node \| \--primary \| \--secondary \| \--all \|
1418 | \--tags \| \--node-tags \| \--pri-node-tags \| \--sec-node-tags]
1419 | [\--submit] [\--print-job-id]
1422 Reboots one or more instances. The type of reboot depends on the value
1423 of ``-t (--type)``. A soft reboot does a hypervisor reboot, a hard reboot
1424 does a instance stop, recreates the hypervisor config for the instance
1425 and starts the instance. A full reboot does the equivalent of
1426 **gnt-instance shutdown && gnt-instance startup**. The default is
1429 For the hard reboot the option ``--ignore-secondaries`` ignores errors
1430 for the secondary node while re-assembling the instance disks.
1432 The ``--instance``, ``--node``, ``--primary``, ``--secondary``,
1433 ``--all``, ``--tags``, ``--node-tags``, ``--pri-node-tags`` and
1434 ``--sec-node-tags`` options are similar as for the **startup** command
1435 and they influence the actual instances being rebooted.
1437 The ``--shutdown-timeout`` is used to specify how much time to wait
1438 before forcing the shutdown (xm destroy in xen, killing the kvm
1439 process, for kvm). By default two minutes are given to each instance
1442 The ``--force-multiple`` will skip the interactive confirmation in the
1443 case the more than one instance will be affected.
1445 See **ganeti**\(7) for a description of ``--submit`` and other common
1450 # gnt-instance reboot instance1.example.com
1451 # gnt-instance reboot --type=full instance1.example.com
1457 **console** [\--show-cmd] {*instance*}
1459 Connects to the console of the given instance. If the instance is not
1460 up, an error is returned. Use the ``--show-cmd`` option to display the
1461 command instead of executing it.
1463 For HVM instances, this will attempt to connect to the serial console
1464 of the instance. To connect to the virtualized "physical" console of a
1465 HVM instance, use a VNC client with the connection info from the
1468 For Xen/kvm instances, if the instance is paused, this attempts to
1469 unpause the instance after waiting a few seconds for the connection to
1470 the console to be made.
1474 # gnt-instance console instance1.example.com
1483 | **replace-disks** [\--submit] [\--print-job-id] [\--early-release]
1484 | [\--ignore-ipolicy] {-p} [\--disks *idx*] {*instance*}
1486 | **replace-disks** [\--submit] [\--print-job-id] [\--early-release]
1487 | [\--ignore-ipolicy] {-s} [\--disks *idx*] {*instance*}
1489 | **replace-disks** [\--submit] [\--print-job-id] [\--early-release]
1490 | [\--ignore-ipolicy]
1491 | {{-I\|\--iallocator} *name* \| {{-n|\--new-secondary} *node* } {*instance*}
1493 | **replace-disks** [\--submit] [\--print-job-id] [\--early-release]
1494 | [\--ignore-ipolicy] {-a\|\--auto} {*instance*}
1496 This command is a generalized form for replacing disks. It is
1497 currently only valid for the mirrored (DRBD) disk template.
1499 The first form (when passing the ``-p`` option) will replace the disks
1500 on the primary, while the second form (when passing the ``-s`` option
1501 will replace the disks on the secondary node. For these two cases (as
1502 the node doesn't change), it is possible to only run the replace for a
1503 subset of the disks, using the option ``--disks`` which takes a list
1504 of comma-delimited disk indices (zero-based), e.g. 0,2 to replace only
1505 the first and third disks.
1507 The third form (when passing either the ``--iallocator`` or the
1508 ``--new-secondary`` option) is designed to change secondary node of the
1509 instance. Specifying ``--iallocator`` makes the new secondary be
1510 selected automatically by the specified allocator plugin (use ``.`` to
1511 indicate the default allocator), otherwise the new secondary node will
1512 be the one chosen manually via the ``--new-secondary`` option.
1514 Note that it is not possible to select an offline or drained node as a
1517 The fourth form (when using ``--auto``) will automatically determine
1518 which disks of an instance are faulty and replace them within the same
1519 node. The ``--auto`` option works only when an instance has only
1520 faulty disks on either the primary or secondary node; it doesn't work
1521 when both sides have faulty disks.
1523 The ``--early-release`` changes the code so that the old storage on
1524 secondary node(s) is removed early (before the resync is completed)
1525 and the internal Ganeti locks for the current (and new, if any)
1526 secondary node are also released, thus allowing more parallelism in
1527 the cluster operation. This should be used only when recovering from a
1528 disk failure on the current secondary (thus the old storage is already
1529 broken) or when the storage on the primary node is known to be fine
1530 (thus we won't need the old storage for potential recovery).
1532 The ``--ignore-ipolicy`` let the command ignore instance policy
1533 violations if replace-disks changes groups and the instance would
1534 violate the new groups instance policy.
1536 See **ganeti**\(7) for a description of ``--submit`` and other common
1542 | **activate-disks** [\--submit] [\--print-job-id] [\--ignore-size]
1543 | [\--wait-for-sync] {*instance*}
1545 Activates the block devices of the given instance. If successful, the
1546 command will show the location and name of the block devices::
1548 node1.example.com:disk/0:/dev/drbd0
1549 node1.example.com:disk/1:/dev/drbd1
1552 In this example, *node1.example.com* is the name of the node on which
1553 the devices have been activated. The *disk/0* and *disk/1* are the
1554 Ganeti-names of the instance disks; how they are visible inside the
1555 instance is hypervisor-specific. */dev/drbd0* and */dev/drbd1* are the
1556 actual block devices as visible on the node.
1558 The ``--ignore-size`` option can be used to activate disks ignoring
1559 the currently configured size in Ganeti. This can be used in cases
1560 where the configuration has gotten out of sync with the real-world
1561 (e.g. after a partially-failed grow-disk operation or due to rounding
1562 in LVM devices). This should not be used in normal cases, but only
1563 when activate-disks fails without it.
1565 The ``--wait-for-sync`` option will ensure that the command returns only
1566 after the instance's disks are synchronised (mostly for DRBD); this can
1567 be useful to ensure consistency, as otherwise there are no commands that
1568 can wait until synchronisation is done. However when passing this
1569 option, the command will have additional output, making it harder to
1570 parse the disk information.
1572 Note that it is safe to run this command while the instance is already
1575 See **ganeti**\(7) for a description of ``--submit`` and other common
1581 **deactivate-disks** [-f] [\--submit] [\--print-job-id] {*instance*}
1583 De-activates the block devices of the given instance. Note that if you
1584 run this command for an instance with a drbd disk template, while it
1585 is running, it will not be able to shutdown the block devices on the
1586 primary node, but it will shutdown the block devices on the secondary
1587 nodes, thus breaking the replication.
1589 The ``-f``/``--force`` option will skip checks that the instance is
1590 down; in case the hypervisor is confused and we can't talk to it,
1591 normally Ganeti will refuse to deactivate the disks, but with this
1592 option passed it will skip this check and directly try to deactivate
1593 the disks. This can still fail due to the instance actually running or
1596 See **ganeti**\(7) for a description of ``--submit`` and other common
1602 | **grow-disk** [\--no-wait-for-sync] [\--submit] [\--print-job-id]
1604 | {*instance*} {*disk*} {*amount*}
1606 Grows an instance's disk. This is only possible for instances having a
1607 plain, drbd, file, sharedfile, rbd or ext disk template. For the ext
1608 template to work, the ExtStorage provider should also support growing.
1609 This means having a ``grow`` script that actually grows the volume of
1610 the external shared storage.
1612 Note that this command only change the block device size; it will not
1613 grow the actual filesystems, partitions, etc. that live on that
1614 disk. Usually, you will need to:
1616 #. use **gnt-instance grow-disk**
1618 #. reboot the instance (later, at a convenient time)
1620 #. use a filesystem resizer, such as **ext2online**\(8) or
1621 **xfs\_growfs**\(8) to resize the filesystem, or use **fdisk**\(8) to
1622 change the partition table on the disk
1624 The *disk* argument is the index of the instance disk to grow. The
1625 *amount* argument is given as a number which can have a suffix (like the
1626 disk size in instance create); if the suffix is missing, the value will
1627 be interpreted as mebibytes.
1629 By default, the *amount* value represents the desired increase in the
1630 disk size (e.g. an amount of 1G will take a disk of size 3G to 4G). If
1631 the optional ``--absolute`` parameter is passed, then the *amount*
1632 argument doesn't represent the delta, but instead the desired final disk
1633 size (e.g. an amount of 8G will take a disk of size 4G to 8G).
1635 For instances with a drbd template, note that the disk grow operation
1636 might complete on one node but fail on the other; this will leave the
1637 instance with different-sized LVs on the two nodes, but this will not
1638 create problems (except for unused space).
1640 If you do not want gnt-instance to wait for the new disk region to be
1641 synced, use the ``--no-wait-for-sync`` option.
1643 See **ganeti**\(7) for a description of ``--submit`` and other common
1646 Example (increase the first disk for instance1 by 16GiB)::
1648 # gnt-instance grow-disk instance1.example.com 0 16g
1650 Example for increasing the disk size to a certain size::
1652 # gnt-instance grow-disk --absolute instance1.example.com 0 32g
1654 Also note that disk shrinking is not supported; use **gnt-backup
1655 export** and then **gnt-backup import** to reduce the disk size of an
1661 | **recreate-disks** [\--submit] [\--print-job-id]
1662 | [{-n node1:[node2] \| {-I\|\--iallocator *name*}}]
1663 | [\--disk=*N*[:[size=*VAL*][,spindles=*VAL*][,mode=*ro\|rw*]]] {*instance*}
1665 Recreates all or a subset of disks of the given instance.
1667 Note that this functionality should only be used for missing disks; if
1668 any of the given disks already exists, the operation will fail. While
1669 this is suboptimal, recreate-disks should hopefully not be needed in
1670 normal operation and as such the impact of this is low.
1672 If only a subset should be recreated, any number of ``disk`` options can
1673 be specified. It expects a disk index and an optional list of disk
1674 parameters to change. Only ``size``, ``spindles``, and ``mode`` can be
1675 changed while recreating disks. To recreate all disks while changing
1676 parameters on a subset only, a ``--disk`` option must be given for every
1677 disk of the instance.
1679 Optionally the instance's disks can be recreated on different
1680 nodes. This can be useful if, for example, the original nodes of the
1681 instance have gone down (and are marked offline), so we can't recreate
1682 on the same nodes. To do this, pass the new node(s) via ``-n`` option,
1683 with a syntax similar to the **add** command. The number of nodes
1684 passed must equal the number of nodes that the instance currently
1685 has. Note that changing nodes is only allowed when all disks are
1686 replaced, e.g. when no ``--disk`` option is passed.
1688 Another method of choosing which nodes to place the instance on is by
1689 using the specified iallocator, passing the ``--iallocator`` option.
1690 The primary and secondary nodes will be chosen by the specified
1691 iallocator plugin, or by the default allocator if ``.`` is specified.
1693 See **ganeti**\(7) for a description of ``--submit`` and other common
1702 | **failover** [-f] [\--ignore-consistency] [\--ignore-ipolicy]
1703 | [\--shutdown-timeout=*N*]
1704 | [{-n|\--target-node} *node* \| {-I|\--iallocator} *name*]
1706 | [\--submit] [\--print-job-id]
1709 Failover will stop the instance (if running), change its primary node,
1710 and if it was originally running it will start it again (on the new
1711 primary). This works for instances with drbd template (in which case you
1712 can only fail to the secondary node) and for externally mirrored
1713 templates (sharedfile, blockdev, rbd and ext) (in which case you can
1714 fail to any other node).
1716 If the instance's disk template is of type sharedfile, blockdev, rbd or
1717 ext, then you can explicitly specify the target node (which can be any
1718 node) using the ``-n`` or ``--target-node`` option, or specify an
1719 iallocator plugin using the ``-I`` or ``--iallocator`` option. If you
1720 omit both, the default iallocator will be used to specify the target
1723 If the instance's disk template is of type drbd, the target node is
1724 automatically selected as the drbd's secondary node. Changing the
1725 secondary node is possible with a replace-disks operation.
1727 Normally the failover will check the consistency of the disks before
1728 failing over the instance. If you are trying to migrate instances off
1729 a dead node, this will fail. Use the ``--ignore-consistency`` option
1730 for this purpose. Note that this option can be dangerous as errors in
1731 shutting down the instance will be ignored, resulting in possibly
1732 having the instance running on two machines in parallel (on
1733 disconnected DRBD drives).
1735 The ``--shutdown-timeout`` is used to specify how much time to wait
1736 before forcing the shutdown (xm destroy in xen, killing the kvm
1737 process, for kvm). By default two minutes are given to each instance
1740 If ``--ignore-ipolicy`` is given any instance policy violations occuring
1741 during this operation are ignored.
1743 If the ``--cleanup`` option is passed, the operation changes from
1744 performin a failover to attempting recovery from a failed previous failover.
1745 In this mode, Ganeti checks if the instance runs on the correct node (and
1746 updates its configuration if not) and ensures the instances' disks
1747 are configured correctly.
1749 See **ganeti**\(7) for a description of ``--submit`` and other common
1754 # gnt-instance failover instance1.example.com
1756 For externally mirrored templates also ``-n`` is available::
1758 # gnt-instance failover -n node3.example.com instance1.example.com
1764 | **migrate** [-f] [\--allow-failover] [\--non-live]
1765 | [\--migration-mode=live\|non-live] [\--ignore-ipolicy]
1766 | [\--no-runtime-changes] [\--submit] [\--print-job-id]
1767 | [{-n|\--target-node} *node* \| {-I|\--iallocator} *name*] {*instance*}
1769 | **migrate** [-f] \--cleanup [\--submit] [\--print-job-id] {*instance*}
1771 Migrate will move the instance to its secondary node without shutdown.
1772 As with failover, it works for instances having the drbd disk template
1773 or an externally mirrored disk template type such as sharedfile,
1774 blockdev, rbd or ext.
1776 If the instance's disk template is of type sharedfile, blockdev, rbd or
1777 ext, then you can explicitly specify the target node (which can be any
1778 node) using the ``-n`` or ``--target-node`` option, or specify an
1779 iallocator plugin using the ``-I`` or ``--iallocator`` option. If you
1780 omit both, the default iallocator will be used to specify the target
1781 node. Alternatively, the default iallocator can be requested by
1782 specifying ``.`` as the name of the plugin.
1784 If the instance's disk template is of type drbd, the target node is
1785 automatically selected as the drbd's secondary node. Changing the
1786 secondary node is possible with a replace-disks operation.
1788 The migration command needs a perfectly healthy instance for drbd
1789 instances, as we rely on the dual-master capability of drbd8 and the
1790 disks of the instance are not allowed to be degraded.
1792 The ``--non-live`` and ``--migration-mode=non-live`` options will
1793 switch (for the hypervisors that support it) between a "fully live"
1794 (i.e. the interruption is as minimal as possible) migration and one in
1795 which the instance is frozen, its state saved and transported to the
1796 remote node, and then resumed there. This all depends on the
1797 hypervisor support for two different methods. In any case, it is not
1798 an error to pass this parameter (it will just be ignored if the
1799 hypervisor doesn't support it). The option ``--migration-mode=live``
1800 option will request a fully-live migration. The default, when neither
1801 option is passed, depends on the hypervisor parameters (and can be
1802 viewed with the **gnt-cluster info** command).
1804 If the ``--cleanup`` option is passed, the operation changes from
1805 migration to attempting recovery from a failed previous migration. In
1806 this mode, Ganeti checks if the instance runs on the correct node (and
1807 updates its configuration if not) and ensures the instances' disks
1808 are configured correctly. In this mode, the ``--non-live`` option is
1811 The option ``-f`` will skip the prompting for confirmation.
1813 If ``--allow-failover`` is specified it tries to fallback to failover if
1814 it already can determine that a migration won't work (e.g. if the
1815 instance is shut down). Please note that the fallback will not happen
1816 during execution. If a migration fails during execution it still fails.
1818 If ``--ignore-ipolicy`` is given any instance policy violations occuring
1819 during this operation are ignored.
1821 The ``--no-runtime-changes`` option forbids migrate to alter an
1822 instance's runtime before migrating it (eg. ballooning an instance
1823 down because the target node doesn't have enough available memory).
1825 If an instance has the backend parameter ``always_failover`` set to
1826 true, then the migration is automatically converted into a failover.
1828 See **ganeti**\(7) for a description of ``--submit`` and other common
1831 Example (and expected output)::
1833 # gnt-instance migrate instance1
1834 Instance instance1 will be migrated. Note that migration
1835 might impact the instance if anything goes wrong (e.g. due to bugs in
1836 the hypervisor). Continue?
1838 Migrating instance instance1.example.com
1839 * checking disk consistency between source and target
1840 * switching node node2.example.com to secondary mode
1841 * changing into standalone mode
1842 * changing disks into dual-master mode
1843 * wait until resync is done
1844 * preparing node2.example.com to accept the instance
1845 * migrating instance to node2.example.com
1846 * switching node node1.example.com to secondary mode
1847 * wait until resync is done
1848 * changing into standalone mode
1849 * changing disks into single-master mode
1850 * wait until resync is done
1858 | **move** [-f] [\--ignore-consistency]
1859 | [-n *node*] [\--shutdown-timeout=*N*] [\--submit] [\--print-job-id]
1860 | [\--ignore-ipolicy]
1863 Move will move the instance to an arbitrary node in the cluster. This
1864 works only for instances having a plain or file disk template.
1866 Note that since this operation is done via data copy, it will take a
1867 long time for big disks (similar to replace-disks for a drbd
1870 The ``--shutdown-timeout`` is used to specify how much time to wait
1871 before forcing the shutdown (e.g. ``xm destroy`` in XEN, killing the
1872 kvm process for KVM, etc.). By default two minutes are given to each
1875 The ``--ignore-consistency`` option will make Ganeti ignore any errors
1876 in trying to shutdown the instance on its node; useful if the
1877 hypervisor is broken and you want to recover the data.
1879 If ``--ignore-ipolicy`` is given any instance policy violations occuring
1880 during this operation are ignored.
1882 See **ganeti**\(7) for a description of ``--submit`` and other common
1887 # gnt-instance move -n node3.example.com instance1.example.com
1893 | **change-group** [\--submit] [\--print-job-id]
1894 | [\--iallocator *NAME*] [\--to *GROUP*...] {*instance*}
1896 This command moves an instance to another node group. The move is
1897 calculated by an iallocator, either given on the command line or as a
1900 If no specific destination groups are specified using ``--to``, all
1901 groups except the one containing the instance are considered.
1903 See **ganeti**\(7) for a description of ``--submit`` and other common
1908 # gnt-instance change-group -I hail --to rack2 inst1.example.com
1917 **add-tags** [\--from *file*] {*instancename*} {*tag*...}
1919 Add tags to the given instance. If any of the tags contains invalid
1920 characters, the entire operation will abort.
1922 If the ``--from`` option is given, the list of tags will be extended
1923 with the contents of that file (each line becomes a tag). In this
1924 case, there is not need to pass tags on the command line (if you do,
1925 both sources will be used). A file name of ``-`` will be interpreted
1931 **list-tags** {*instancename*}
1933 List the tags of the given instance.
1938 **remove-tags** [\--from *file*] {*instancename*} {*tag*...}
1940 Remove tags from the given instance. If any of the tags are not
1941 existing on the node, the entire operation will abort.
1943 If the ``--from`` option is given, the list of tags to be removed will
1944 be extended with the contents of that file (each line becomes a tag).
1945 In this case, there is not need to pass tags on the command line (if
1946 you do, tags from both sources will be removed). A file name of ``-``
1947 will be interpreted as stdin.
1949 .. vim: set textwidth=72 :