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 \| blktap2}]
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 enable
470 PAE support for this instance. The default is false, disabling PAE
474 Valid for the Xen HVM hypervisor.
476 A boolean option that specifies if the hypervisor should enable
477 viridian (Hyper-V) for this instance. The default is false,
478 disabling viridian support.
481 Valid for the Xen HVM and KVM hypervisors.
483 A boolean option that specifies if the instance should be started
484 with its clock set to the localtime of the machine (when true) or
485 to the UTC (When false). The default is false, which is useful for
486 Linux/Unix machines; for Windows OSes, it is recommended to enable
490 Valid for the Xen PVM and KVM hypervisors.
492 This option specifies the path (on the node) to the kernel to boot
493 the instance with. Xen PVM instances always require this, while for
494 KVM if this option is empty, it will cause the machine to load the
495 kernel from its disks (and the boot will be done accordingly to
499 Valid for the Xen PVM and KVM hypervisors.
501 This options specifies extra arguments to the kernel that will be
502 loaded. device. This is always used for Xen PVM, while for KVM it
503 is only used if the ``kernel_path`` option is also specified.
505 The default setting for this value is simply ``"ro"``, which
506 mounts the root disk (initially) in read-only one. For example,
507 setting this to single will cause the instance to start in
511 Valid for the Xen PVM and KVM hypervisors.
513 This option specifies the path (on the node) to the initrd to boot
514 the instance with. Xen PVM instances can use this always, while
515 for KVM if this option is only used if the ``kernel_path`` option
516 is also specified. You can pass here either an absolute filename
517 (the path to the initrd) if you want to use an initrd, or use the
518 format no\_initrd\_path for no initrd.
521 Valid for the Xen PVM and KVM hypervisors.
523 This options specifies the name of the root device. This is always
524 needed for Xen PVM, while for KVM it is only used if the
525 ``kernel_path`` option is also specified.
527 Please note, that if this setting is an empty string and the
528 hypervisor is Xen it will not be written to the Xen configuration
532 Valid for the KVM hypervisor.
534 This boolean option specifies whether to emulate a serial console
535 for the instance. Note that some versions of KVM have a bug that
536 will make an instance hang when configured to use the serial console
537 unless a connection is made to it within about 2 seconds of the
538 instance's startup. For such case it's recommended to disable this
539 option, which is enabled by default.
542 Valid for the KVM hypervisor.
544 This integer option specifies the speed of the serial console.
545 Common values are 9600, 19200, 38400, 57600 and 115200: choose the
546 one which works on your system. (The default is 38400 for historical
547 reasons, but newer versions of kvm/qemu work with 115200)
550 Valid for the KVM hypervisor.
552 The disk cache mode. It can be either default to not pass any
553 cache option to KVM, or one of the KVM cache modes: none (for
554 direct I/O), writethrough (to use the host cache but report
555 completion to the guest only when the host has committed the
556 changes to disk) or writeback (to use the host cache and report
557 completion as soon as the data is in the host cache). Note that
558 there are special considerations for the cache mode depending on
559 version of KVM used and disk type (always raw file under Ganeti),
560 please refer to the KVM documentation for more details.
563 Valid for the KVM hypervisor.
565 The security model for kvm. Currently one of *none*, *user* or
566 *pool*. Under *none*, the default, nothing is done and instances
567 are run as the Ganeti daemon user (normally root).
569 Under *user* kvm will drop privileges and become the user
570 specified by the security\_domain parameter.
572 Under *pool* a global cluster pool of users will be used, making
573 sure no two instances share the same user on the same node. (this
574 mode is not implemented yet)
577 Valid for the KVM hypervisor.
579 Under security model *user* the username to run the instance
580 under. It must be a valid username existing on the host.
582 Cannot be set under security model *none* or *pool*.
585 Valid for the KVM hypervisor.
587 If *enabled* the -enable-kvm flag is passed to kvm. If *disabled*
588 -disable-kvm is passed. If unset no flag is passed, and the
589 default running mode for your kvm binary will be used.
592 Valid for the KVM hypervisor.
594 This option passes the -mem-path argument to kvm with the path (on
595 the node) to the mount point of the hugetlbfs file system, along
596 with the -mem-prealloc argument too.
599 Valid for the KVM hypervisor.
601 This boolean option determines whether to run the KVM instance in a
604 If it is set to ``true``, an empty directory is created before
605 starting the instance and its path is passed via the -chroot flag
606 to kvm. The directory is removed when the instance is stopped.
608 It is set to ``false`` by default.
611 Valid for the KVM hypervisor.
613 The maximum amount of time (in ms) a KVM instance is allowed to be
614 frozen during a live migration, in order to copy dirty memory
615 pages. Default value is 30ms, but you may need to increase this
616 value for busy instances.
618 This option is only effective with kvm versions >= 87 and qemu-kvm
622 Valid for the Xen, KVM and LXC hypervisors.
624 The processes belonging to the given instance are only scheduled
625 on the specified CPUs.
627 The format of the mask can be given in three forms. First, the word
628 "all", which signifies the common case where all VCPUs can live on
629 any CPU, based on the hypervisor's decisions.
631 Second, a comma-separated list of CPU IDs or CPU ID ranges. The
632 ranges are defined by a lower and higher boundary, separated by a
633 dash, and the boundaries are inclusive. In this form, all VCPUs of
634 the instance will be mapped on the selected list of CPUs. Example:
635 ``0-2,5``, mapping all VCPUs (no matter how many) onto physical CPUs
638 The last form is used for explicit control of VCPU-CPU pinnings. In
639 this form, the list of VCPU mappings is given as a colon (:)
640 separated list, whose elements are the possible values for the
641 second or first form above. In this form, the number of elements in
642 the colon-separated list _must_ equal the number of VCPUs of the
649 # Map the entire instance to CPUs 0-2
650 gnt-instance modify -H cpu_mask=0-2 my-inst
652 # Map vCPU 0 to physical CPU 1 and vCPU 1 to CPU 3 (assuming 2 vCPUs)
653 gnt-instance modify -H cpu_mask=1:3 my-inst
655 # Pin vCPU 0 to CPUs 1 or 2, and vCPU 1 to any CPU
656 gnt-instance modify -H cpu_mask=1-2:all my-inst
658 # Pin vCPU 0 to any CPU, vCPU 1 to CPUs 1, 3, 4 or 5, and CPU 2 to
659 # CPU 0 (backslashes for escaping the comma)
660 gnt-instance modify -H cpu_mask=all:1\\,3-5:0 my-inst
662 # Pin entire VM to CPU 0
663 gnt-instance modify -H cpu_mask=0 my-inst
665 # Turn off CPU pinning (default setting)
666 gnt-instance modify -H cpu_mask=all my-inst
669 Valid for the Xen hypervisor.
671 Set the maximum amount of cpu usage by the VM. The value is a percentage
672 between 0 and (100 * number of VCPUs). Default cap is 0: unlimited.
675 Valid for the Xen hypervisor.
677 Set the cpu time ratio to be allocated to the VM. Valid values are
678 between 1 and 65535. Default weight is 256.
681 Valid for the KVM hypervisor.
683 This option specifies the usb mouse type to be used. It can be
684 "mouse" or "tablet". When using VNC it's recommended to set it to
688 Valid for the KVM hypervisor.
690 This option specifies the keyboard mapping to be used. It is only
691 needed when using the VNC console. For example: "fr" or "en-gb".
694 Valid for Xen PVM, Xen HVM and KVM hypervisors.
696 Normally if an instance reboots, the hypervisor will restart it. If
697 this option is set to ``exit``, the hypervisor will treat a reboot
698 as a shutdown instead.
700 It is set to ``reboot`` by default.
703 Valid for the KVM hypervisor.
705 Number of emulated CPU cores.
708 Valid for the KVM hypervisor.
710 Number of emulated CPU threads.
713 Valid for the KVM hypervisor.
715 Number of emulated CPU sockets.
718 Valid for the KVM hypervisor.
720 Comma separated list of emulated sounds cards, or "all" to enable
721 all the available ones.
724 Valid for the KVM hypervisor.
726 Comma separated list of usb devices. These can be emulated devices
727 or passthrough ones, and each one gets passed to kvm with its own
728 ``-usbdevice`` option. See the **qemu**\(1) manpage for the syntax
729 of the possible components.
732 Valid for the KVM hypervisor.
734 Emulated vga mode, passed the the kvm -vga option.
737 Valid for the KVM hypervisor.
739 Any other option to the KVM hypervisor, useful tweaking anything
740 that Ganeti doesn't support. Note that values set with this
741 parameter are split on a space character and currently don't support
745 Valid for the KVM hypervisor.
747 Use in case an instance must be booted with an exact type of
748 machine version (due to e.g. outdated drivers). In case it's not set
749 the default version supported by your version of kvm is used.
752 Valid for the KVM hypervisor.
754 Path to the userspace KVM (or qemu) program.
757 Valid for the KVM hypervisor.
759 This boolean option determines whether the tap devices used by the
760 KVM paravirtual nics (virtio-net) will get created with VNET_HDR
761 (IFF_VNET_HDR) support.
763 If set to false, it effectively disables offloading on the virio-net
764 interfaces, which prevents host kernel tainting and log flooding,
765 when dealing with broken or malicious virtio-net drivers.
767 It is set to ``true`` by default.
769 The ``-O (--os-parameters)`` option allows customisation of the OS
770 parameters. The actual parameter names and values depends on the OS
771 being used, but the syntax is the same key=value. For example, setting
772 a hypothetical ``dhcp`` parameter to yes can be achieved by::
774 gnt-instance add -O dhcp=yes ...
776 The ``-I (--iallocator)`` option specifies the instance allocator plugin
777 to use (``.`` means the default allocator). If you pass in this option
778 the allocator will select nodes for this instance automatically, so you
779 don't need to pass them with the ``-n`` option. For more information
780 please refer to the instance allocator documentation.
782 The ``-t (--disk-template)`` options specifies the disk layout type
783 for the instance. The available choices are:
786 This creates an instance with no disks. Its useful for testing only
787 (or other special cases).
790 Disk devices will be regular files.
793 Disk devices will be regulare files on a shared directory.
796 Disk devices will be logical volumes.
799 Disk devices will be drbd (version 8.x) on top of lvm volumes.
802 Disk devices will be rbd volumes residing inside a RADOS cluster.
805 Disk devices will be adopted pre-existent block devices.
808 Disk devices will be provided by external shared storage,
809 through the ExtStorage Interface using ExtStorage providers.
811 The optional second value of the ``-n (--node)`` is used for the drbd
812 template type and specifies the remote node.
814 If you do not want gnt-instance to wait for the disk mirror to be
815 synced, use the ``--no-wait-for-sync`` option.
817 The ``--file-storage-dir`` specifies the relative path under the
818 cluster-wide file storage directory to store file-based disks. It is
819 useful for having different subdirectories for different
820 instances. The full path of the directory where the disk files are
821 stored will consist of cluster-wide file storage directory + optional
822 subdirectory + instance name. Example:
823 ``@RPL_FILE_STORAGE_DIR@/mysubdir/instance1.example.com``. This
824 option is only relevant for instances using the file storage backend.
826 The ``--file-driver`` specifies the driver to use for file-based
827 disks. Note that currently these drivers work with the xen hypervisor
828 only. This option is only relevant for instances using the file
829 storage backend. The available choices are:
832 Kernel loopback driver. This driver uses loopback devices to
833 access the filesystem within the file. However, running I/O
834 intensive applications in your instance using the loop driver
835 might result in slowdowns. Furthermore, if you use the loopback
836 driver consider increasing the maximum amount of loopback devices
837 (on most systems it's 8) using the max\_loop param.
840 The blktap driver (for Xen hypervisors). In order to be able to
841 use the blktap driver you should check if the 'blktapctrl' user
842 space disk agent is running (usually automatically started via
843 xend). This user-level disk I/O interface has the advantage of
844 better performance. Especially if you use a network file system
845 (e.g. NFS) to store your instances this is the recommended choice.
848 Analogous to the blktap driver, but used by newer versions of Xen.
850 If ``--ignore-ipolicy`` is given any instance policy violations occuring
851 during this operation are ignored.
853 See **ganeti**\(7) for a description of ``--submit`` and other common
858 # gnt-instance add -t file --disk 0:size=30g -B maxmem=512 -o debian-etch \
859 -n node1.example.com --file-storage-dir=mysubdir instance1.example.com
860 # gnt-instance add -t plain --disk 0:size=30g -B maxmem=1024,minmem=512 \
861 -o debian-etch -n node1.example.com instance1.example.com
862 # gnt-instance add -t plain --disk 0:size=30g --disk 1:size=100g,vg=san \
863 -B maxmem=512 -o debian-etch -n node1.example.com instance1.example.com
864 # gnt-instance add -t drbd --disk 0:size=30g -B maxmem=512 -o debian-etch \
865 -n node1.example.com:node2.example.com instance2.example.com
866 # gnt-instance add -t rbd --disk 0:size=30g -B maxmem=512 -o debian-etch \
867 -n node1.example.com instance1.example.com
868 # gnt-instance add -t ext --disk 0:size=30g,provider=pvdr1 -B maxmem=512 \
869 -o debian-etch -n node1.example.com instance1.example.com
870 # gnt-instance add -t ext --disk 0:size=30g,provider=pvdr1,param1=val1 \
871 --disk 1:size=40g,provider=pvdr2,param2=val2,param3=val3 -B maxmem=512 \
872 -o debian-etch -n node1.example.com instance1.example.com
879 | [{-I|\--iallocator} *instance allocator*]
880 | {instances\_file.json}
882 This command (similar to the Ganeti 1.2 **batcher** tool) submits
883 multiple instance creation jobs based on a definition file. This
884 file can contain all options which are valid when adding an instance
885 with the exception of the ``iallocator`` field. The IAllocator is,
886 for optimization purposes, only allowed to be set for the whole batch
887 operation using the ``--iallocator`` parameter.
889 The instance file must be a valid-formed JSON file, containing an
890 array of dictionaries with instance creation parameters. All parameters
891 (except ``iallocator``) which are valid for the instance creation
892 OP code are allowed. The most important ones are:
895 The FQDN of the new instance.
898 The disk template to use for the instance, the same as in the
902 Array of disk specifications. Each entry describes one disk as a
903 dictionary of disk parameters.
906 A dictionary of backend parameters.
909 The hypervisor for the instance.
912 A dictionary with the hypervisor options. If not passed, the default
913 hypervisor options will be inherited.
916 List of NICs that will be created for the instance. Each entry
917 should be a dict, with mac, ip, mode and link as possible keys.
918 Please don't provide the "mac, ip, mode, link" parent keys if you
919 use this method for specifying NICs.
922 The primary and optionally the secondary node to use for the
923 instance (in case an iallocator script is not used). If those
924 parameters are given, they have to be given consistently for all
925 instances in the batch operation.
928 whether to start the instance
931 Skip the check for already-in-use instance; see the description in
932 the **add** command for details.
935 Skip the name check for instances; see the description in the
936 **add** command for details.
938 file\_storage\_dir, file\_driver
939 Configuration for the file disk type, see the **add** command for
943 A simple definition for one instance can be (with most of the
944 parameters taken from the cluster defaults)::
949 "instance_name": "instance1.example.com",
950 "disk_template": "drbd",
951 "os_type": "debootstrap",
952 "disks": [{"size":"1024"}],
954 "hypervisor": "xen-pvm"
958 "instance_name": "instance2.example.com",
959 "disk_template": "drbd",
960 "os_type": "debootstrap",
961 "disks": [{"size":"4096", "mode": "rw", "vg": "xenvg"}],
963 "hypervisor": "xen-hvm",
964 "hvparams": {"acpi": true},
965 "beparams": {"maxmem": 512, "minmem": 256}
969 The command will display the job id for each submitted instance, as
972 # gnt-instance batch-create instances.json
973 Submitted jobs 37, 38
978 **remove** [\--ignore-failures] [\--shutdown-timeout=*N*] [\--submit]
979 [\--force] {*instance*}
981 Remove an instance. This will remove all data from the instance and
982 there is *no way back*. If you are not sure if you use an instance
983 again, use **shutdown** first and leave it in the shutdown state for a
986 The ``--ignore-failures`` option will cause the removal to proceed
987 even in the presence of errors during the removal of the instance
988 (e.g. during the shutdown or the disk removal). If this option is not
989 given, the command will stop at the first error.
991 The ``--shutdown-timeout`` is used to specify how much time to wait
992 before forcing the shutdown (e.g. ``xm destroy`` in Xen, killing the
993 kvm process for KVM, etc.). By default two minutes are given to each
996 The ``--force`` option is used to skip the interactive confirmation.
998 See **ganeti**\(7) for a description of ``--submit`` and other common
1003 # gnt-instance remove instance1.example.com
1010 | [\--no-headers] [\--separator=*SEPARATOR*] [\--units=*UNITS*] [-v]
1011 | [{-o|\--output} *[+]FIELD,...*] [\--filter] [instance...]
1013 Shows the currently configured instances with memory usage, disk
1014 usage, the node they are running on, and their run status.
1016 The ``--no-headers`` option will skip the initial header line. The
1017 ``--separator`` option takes an argument which denotes what will be
1018 used between the output fields. Both these options are to help
1021 The units used to display the numeric values in the output varies,
1022 depending on the options given. By default, the values will be
1023 formatted in the most appropriate unit. If the ``--separator`` option
1024 is given, then the values are shown in mebibytes to allow parsing by
1025 scripts. In both cases, the ``--units`` option can be used to enforce
1026 a given output unit.
1028 The ``-v`` option activates verbose mode, which changes the display of
1029 special field states (see **ganeti**\(7)).
1031 The ``-o (--output)`` option takes a comma-separated list of output
1032 fields. The available fields and their meaning are:
1034 @QUERY_FIELDS_INSTANCE@
1036 If the value of the option starts with the character ``+``, the new
1037 field(s) will be added to the default list. This allows one to quickly
1038 see the default list plus a few other fields, instead of retyping the
1039 entire list of fields.
1041 There is a subtle grouping about the available output fields: all
1042 fields except for ``oper_state``, ``oper_ram``, ``oper_vcpus`` and
1043 ``status`` are configuration value and not run-time values. So if you
1044 don't select any of the these fields, the query will be satisfied
1045 instantly from the cluster configuration, without having to ask the
1046 remote nodes for the data. This can be helpful for big clusters when
1047 you only want some data and it makes sense to specify a reduced set of
1050 If exactly one argument is given and it appears to be a query filter
1051 (see **ganeti**\(7)), the query result is filtered accordingly. For
1052 ambiguous cases (e.g. a single field name as a filter) the ``--filter``
1053 (``-F``) option forces the argument to be treated as a filter (e.g.
1054 ``gnt-instance list -F admin_state``).
1056 The default output field list is: ``name``, ``os``, ``pnode``,
1057 ``admin_state``, ``oper_state``, ``oper_ram``.
1063 **list-fields** [field...]
1065 Lists available fields for instances.
1071 **info** [-s \| \--static] [\--roman] {\--all \| *instance*}
1073 Show detailed information about the given instance(s). This is
1074 different from **list** as it shows detailed data about the instance's
1075 disks (especially useful for the drbd disk template).
1077 If the option ``-s`` is used, only information available in the
1078 configuration file is returned, without querying nodes, making the
1081 Use the ``--all`` to get info about all instances, rather than
1082 explicitly passing the ones you're interested in.
1084 The ``--roman`` option can be used to cause envy among people who like
1085 ancient cultures, but are stuck with non-latin-friendly cluster
1086 virtualization technologies.
1092 | [{-H|\--hypervisor-parameters} *HYPERVISOR\_PARAMETERS*]
1093 | [{-B|\--backend-parameters} *BACKEND\_PARAMETERS*]
1094 | [{-m|\--runtime-memory} *SIZE*]
1095 | [\--net add[:options...] \|
1096 | \--net [*N*:]add[,options...] \|
1097 | \--net [*ID*:]remove \|
1098 | \--net *ID*:modify[,options...]]
1099 | [\--disk add:size=*SIZE*[,options...] \|
1100 | \--disk *N*:add,size=*SIZE*[,options...] \|
1101 | \--disk *N*:add,size=*SIZE*,provider=*PROVIDER*[,options...][,param=*value*... ] \|
1102 | \--disk *ID*:modify[,options...]
1103 | \--disk [*ID*:]remove]
1104 | [{-t|\--disk-template} plain | {-t|\--disk-template} drbd -n *new_secondary*] [\--no-wait-for-sync]
1105 | [\--new-primary=*node*]
1106 | [\--os-type=*OS* [\--force-variant]]
1107 | [{-O|\--os-parameters} *param*=*value*... ]
1108 | [\--offline \| \--online]
1110 | [\--ignore-ipolicy]
1113 Modifies the memory size, number of vcpus, ip address, MAC address
1114 and/or NIC parameters for an instance. It can also add and remove
1115 disks and NICs to/from the instance. Note that you need to give at
1116 least one of the arguments, otherwise the command complains.
1118 The ``-H (--hypervisor-parameters)``, ``-B (--backend-parameters)``
1119 and ``-O (--os-parameters)`` options specifies hypervisor, backend and
1120 OS parameter options in the form of name=value[,...]. For details
1121 which options can be specified, see the **add** command.
1123 The ``-t (--disk-template)`` option will change the disk template of
1124 the instance. Currently only conversions between the plain and drbd
1125 disk templates are supported, and the instance must be stopped before
1126 attempting the conversion. When changing from the plain to the drbd
1127 disk template, a new secondary node must be specified via the ``-n``
1128 option. The option ``--no-wait-for-sync`` can be used when converting
1129 to the ``drbd`` template in order to make the instance available for
1130 startup before DRBD has finished resyncing.
1132 The ``-m (--runtime-memory)`` option will change an instance's runtime
1133 memory to the given size (in MB if a different suffix is not specified),
1134 by ballooning it up or down to the new value.
1136 The ``--disk add:size=*SIZE*,[options..]`` option adds a disk to the
1137 instance, and ``--disk *N*:add:size=*SIZE*,[options..]`` will add a disk
1138 to the the instance at a specific index. The available options are the
1139 same as in the **add** command(``mode``, ``name``, ``vg``, ``metavg``).
1140 When adding an ExtStorage disk the ``provider=*PROVIDER*`` option is
1141 also mandatory and specifies the ExtStorage provider. Also, for
1142 ExtStorage disks arbitrary parameters can be passed as additional comma
1143 separated options, same as in the **add** command. -The ``--disk remove``
1144 option will remove the last disk of the instance. Use
1145 ``--disk `` *ID*``:remove`` to remove a disk by its identifier. *ID*
1146 can be the index of the disk, the disks's name or the disks's UUID. The
1147 ``--disk *ID*:modify[,options...]`` wil change the options of the disk.
1148 Available options are:
1151 The access mode. Either ``ro`` (read-only) or the default ``rw`` (read-write).
1154 this option specifies a name for the disk, which can be used as a disk
1155 identifier. An instance can not have two disks with the same name.
1157 The ``--net *N*:add[,options..]`` will add a new network interface to
1158 the instance. The available options are the same as in the **add**
1159 command (``mac``, ``ip``, ``link``, ``mode``, ``network``). The
1160 ``--net *ID*,remove`` will remove the intances' NIC with *ID* identifier,
1161 which can be the index of the NIC, the NIC's name or the NIC's UUID.
1162 The ``--net *ID*:modify[,options..]`` option will change the parameters of
1163 the instance network interface with the *ID* identifier.
1165 The option ``-o (--os-type)`` will change the OS name for the instance
1166 (without reinstallation). In case an OS variant is specified that is
1167 not found, then by default the modification is refused, unless
1168 ``--force-variant`` is passed. An invalid OS will also be refused,
1169 unless the ``--force`` option is given.
1171 The option ``--new-primary`` will set the new primary node of an instance
1172 assuming the disks have already been moved manually. Unless the ``--force``
1173 option is given, it is verified that the instance is no longer running
1174 on its current primary node.
1176 The ``--online`` and ``--offline`` options are used to transition an
1177 instance into and out of the ``offline`` state. An instance can be
1178 turned offline only if it was previously down. The ``--online`` option
1179 fails if the instance was not in the ``offline`` state, otherwise it
1180 changes instance's state to ``down``. These modifications take effect
1183 If ``--ignore-ipolicy`` is given any instance policy violations occuring
1184 during this operation are ignored.
1186 See **ganeti**\(7) for a description of ``--submit`` and other common
1189 Most of the changes take effect at the next restart. If the instance is
1190 running, there is no effect on the instance.
1195 | **reinstall** [{-o|\--os-type} *os-type*] [\--select-os] [-f *force*]
1196 | [\--force-multiple]
1197 | [\--instance \| \--node \| \--primary \| \--secondary \| \--all]
1198 | [{-O|\--os-parameters} *OS\_PARAMETERS*] [\--submit] {*instance*...}
1200 Reinstalls the operating system on the given instance(s). The
1201 instance(s) must be stopped when running this command. If the ``-o
1202 (--os-type)`` is specified, the operating system is changed.
1204 The ``--select-os`` option switches to an interactive OS reinstall.
1205 The user is prompted to select the OS template from the list of
1206 available OS templates. OS parameters can be overridden using ``-O
1207 (--os-parameters)`` (more documentation for this option under the
1210 Since this is a potentially dangerous command, the user will be
1211 required to confirm this action, unless the ``-f`` flag is passed.
1212 When multiple instances are selected (either by passing multiple
1213 arguments or by using the ``--node``, ``--primary``, ``--secondary``
1214 or ``--all`` options), the user must pass the ``--force-multiple``
1215 options to skip the interactive confirmation.
1217 See **ganeti**\(7) for a description of ``--submit`` and other common
1223 | **rename** [\--no-ip-check] [\--no-name-check] [\--submit]
1224 | {*instance*} {*new\_name*}
1226 Renames the given instance. The instance must be stopped when running
1227 this command. The requirements for the new name are the same as for
1228 adding an instance: the new name must be resolvable and the IP it
1229 resolves to must not be reachable (in order to prevent duplicate IPs
1230 the next time the instance is started). The IP test can be skipped if
1231 the ``--no-ip-check`` option is passed.
1233 Note that you can rename an instance to its same name, to force
1234 re-executing the os-specific rename script for that instance, if
1237 The ``--no-name-check`` skips the check for the new instance name via
1238 the resolver (e.g. in DNS or /etc/hosts, depending on your setup) and
1239 that the resolved name matches the provided name. Since the name check
1240 is used to compute the IP address, if you pass this option you must also
1241 pass the ``--no-ip-check`` option.
1243 See **ganeti**\(7) for a description of ``--submit`` and other common
1246 Starting/stopping/connecting to console
1247 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1253 | [\--force] [\--ignore-offline]
1254 | [\--force-multiple] [\--no-remember]
1255 | [\--instance \| \--node \| \--primary \| \--secondary \| \--all \|
1256 | \--tags \| \--node-tags \| \--pri-node-tags \| \--sec-node-tags]
1257 | [{-H|\--hypervisor-parameters} ``key=value...``]
1258 | [{-B|\--backend-parameters} ``key=value...``]
1259 | [\--submit] [\--paused]
1262 Starts one or more instances, depending on the following options. The
1263 four available modes are:
1266 will start the instances given as arguments (at least one argument
1267 required); this is the default selection
1270 will start the instances who have the given node as either primary
1274 will start all instances whose primary node is in the list of nodes
1275 passed as arguments (at least one node required)
1278 will start all instances whose secondary node is in the list of
1279 nodes passed as arguments (at least one node required)
1282 will start all instances in the cluster (no arguments accepted)
1285 will start all instances in the cluster with the tags given as
1289 will start all instances in the cluster on nodes with the tags
1293 will start all instances in the cluster on primary nodes with the
1294 tags given as arguments
1297 will start all instances in the cluster on secondary nodes with the
1298 tags given as arguments
1300 Note that although you can pass more than one selection option, the
1301 last one wins, so in order to guarantee the desired result, don't pass
1302 more than one such option.
1304 Use ``--force`` to start even if secondary disks are failing.
1305 ``--ignore-offline`` can be used to ignore offline primary nodes and
1306 mark the instance as started even if the primary is not available.
1308 The ``--force-multiple`` will skip the interactive confirmation in the
1309 case the more than one instance will be affected.
1311 The ``--no-remember`` option will perform the startup but not change
1312 the state of the instance in the configuration file (if it was stopped
1313 before, Ganeti will still think it needs to be stopped). This can be
1314 used for testing, or for a one shot-start where you don't want the
1315 watcher to restart the instance if it crashes.
1317 The ``-H (--hypervisor-parameters)`` and ``-B (--backend-parameters)``
1318 options specify temporary hypervisor and backend parameters that can
1319 be used to start an instance with modified parameters. They can be
1320 useful for quick testing without having to modify an instance back and
1323 # gnt-instance start -H kernel_args="single" instance1
1324 # gnt-instance start -B maxmem=2048 instance2
1327 The first form will start the instance instance1 in single-user mode,
1328 and the instance instance2 with 2GB of RAM (this time only, unless
1329 that is the actual instance memory size already). Note that the values
1330 override the instance parameters (and not extend them): an instance
1331 with "kernel\_args=ro" when started with -H kernel\_args=single will
1332 result in "single", not "ro single".
1334 The ``--paused`` option is only valid for Xen and kvm hypervisors. This
1335 pauses the instance at the start of bootup, awaiting ``gnt-instance
1336 console`` to unpause it, allowing the entire boot process to be
1337 monitored for debugging.
1339 See **ganeti**\(7) for a description of ``--submit`` and other common
1344 # gnt-instance start instance1.example.com
1345 # gnt-instance start --node node1.example.com node2.example.com
1346 # gnt-instance start --all
1354 | [\--force] [\--force-multiple] [\--ignore-offline] [\--no-remember]
1355 | [\--instance \| \--node \| \--primary \| \--secondary \| \--all \|
1356 | \--tags \| \--node-tags \| \--pri-node-tags \| \--sec-node-tags]
1360 Stops one or more instances. If the instance cannot be cleanly stopped
1361 during a hardcoded interval (currently 2 minutes), it will forcibly
1362 stop the instance (equivalent to switching off the power on a physical
1365 The ``--timeout`` is used to specify how much time to wait before
1366 forcing the shutdown (e.g. ``xm destroy`` in Xen, killing the kvm
1367 process for KVM, etc.). By default two minutes are given to each
1370 The ``--instance``, ``--node``, ``--primary``, ``--secondary``,
1371 ``--all``, ``--tags``, ``--node-tags``, ``--pri-node-tags`` and
1372 ``--sec-node-tags`` options are similar as for the **startup** command
1373 and they influence the actual instances being shutdown.
1375 ``--ignore-offline`` can be used to ignore offline primary nodes and
1376 force the instance to be marked as stopped. This option should be used
1377 with care as it can lead to an inconsistent cluster state.
1379 Use ``--force`` to be able to shutdown an instance even when it's marked
1380 as offline. This is useful is an offline instance ends up in the
1381 ``ERROR_up`` state, for example.
1383 The ``--no-remember`` option will perform the shutdown but not change
1384 the state of the instance in the configuration file (if it was running
1385 before, Ganeti will still thinks it needs to be running). This can be
1386 useful for a cluster-wide shutdown, where some instances are marked as
1387 up and some as down, and you don't want to change the running state:
1388 you just need to disable the watcher, shutdown all instances with
1389 ``--no-remember``, and when the watcher is activated again it will
1390 restore the correct runtime state for all instances.
1392 See **ganeti**\(7) for a description of ``--submit`` and other common
1397 # gnt-instance shutdown instance1.example.com
1398 # gnt-instance shutdown --all
1405 | [{-t|\--type} *REBOOT-TYPE*]
1406 | [\--ignore-secondaries]
1407 | [\--shutdown-timeout=*N*]
1408 | [\--force-multiple]
1409 | [\--instance \| \--node \| \--primary \| \--secondary \| \--all \|
1410 | \--tags \| \--node-tags \| \--pri-node-tags \| \--sec-node-tags]
1414 Reboots one or more instances. The type of reboot depends on the value
1415 of ``-t (--type)``. A soft reboot does a hypervisor reboot, a hard reboot
1416 does a instance stop, recreates the hypervisor config for the instance
1417 and starts the instance. A full reboot does the equivalent of
1418 **gnt-instance shutdown && gnt-instance startup**. The default is
1421 For the hard reboot the option ``--ignore-secondaries`` ignores errors
1422 for the secondary node while re-assembling the instance disks.
1424 The ``--instance``, ``--node``, ``--primary``, ``--secondary``,
1425 ``--all``, ``--tags``, ``--node-tags``, ``--pri-node-tags`` and
1426 ``--sec-node-tags`` options are similar as for the **startup** command
1427 and they influence the actual instances being rebooted.
1429 The ``--shutdown-timeout`` is used to specify how much time to wait
1430 before forcing the shutdown (xm destroy in xen, killing the kvm
1431 process, for kvm). By default two minutes are given to each instance
1434 The ``--force-multiple`` will skip the interactive confirmation in the
1435 case the more than one instance will be affected.
1437 See **ganeti**\(7) for a description of ``--submit`` and other common
1442 # gnt-instance reboot instance1.example.com
1443 # gnt-instance reboot --type=full instance1.example.com
1449 **console** [\--show-cmd] {*instance*}
1451 Connects to the console of the given instance. If the instance is not
1452 up, an error is returned. Use the ``--show-cmd`` option to display the
1453 command instead of executing it.
1455 For HVM instances, this will attempt to connect to the serial console
1456 of the instance. To connect to the virtualized "physical" console of a
1457 HVM instance, use a VNC client with the connection info from the
1460 For Xen/kvm instances, if the instance is paused, this attempts to
1461 unpause the instance after waiting a few seconds for the connection to
1462 the console to be made.
1466 # gnt-instance console instance1.example.com
1475 **replace-disks** [\--submit] [\--early-release] [\--ignore-ipolicy] {-p}
1476 [\--disks *idx*] {*instance*}
1478 **replace-disks** [\--submit] [\--early-release] [\--ignore-ipolicy] {-s}
1479 [\--disks *idx*] {*instance*}
1481 **replace-disks** [\--submit] [\--early-release] [\--ignore-ipolicy]
1482 {{-I\|\--iallocator} *name* \| {{-n|\--new-secondary} *node* } {*instance*}
1484 **replace-disks** [\--submit] [\--early-release] [\--ignore-ipolicy]
1485 {-a\|\--auto} {*instance*}
1487 This command is a generalized form for replacing disks. It is
1488 currently only valid for the mirrored (DRBD) disk template.
1490 The first form (when passing the ``-p`` option) will replace the disks
1491 on the primary, while the second form (when passing the ``-s`` option
1492 will replace the disks on the secondary node. For these two cases (as
1493 the node doesn't change), it is possible to only run the replace for a
1494 subset of the disks, using the option ``--disks`` which takes a list
1495 of comma-delimited disk indices (zero-based), e.g. 0,2 to replace only
1496 the first and third disks.
1498 The third form (when passing either the ``--iallocator`` or the
1499 ``--new-secondary`` option) is designed to change secondary node of the
1500 instance. Specifying ``--iallocator`` makes the new secondary be
1501 selected automatically by the specified allocator plugin (use ``.`` to
1502 indicate the default allocator), otherwise the new secondary node will
1503 be the one chosen manually via the ``--new-secondary`` option.
1505 Note that it is not possible to select an offline or drained node as a
1508 The fourth form (when using ``--auto``) will automatically determine
1509 which disks of an instance are faulty and replace them within the same
1510 node. The ``--auto`` option works only when an instance has only
1511 faulty disks on either the primary or secondary node; it doesn't work
1512 when both sides have faulty disks.
1514 The ``--early-release`` changes the code so that the old storage on
1515 secondary node(s) is removed early (before the resync is completed)
1516 and the internal Ganeti locks for the current (and new, if any)
1517 secondary node are also released, thus allowing more parallelism in
1518 the cluster operation. This should be used only when recovering from a
1519 disk failure on the current secondary (thus the old storage is already
1520 broken) or when the storage on the primary node is known to be fine
1521 (thus we won't need the old storage for potential recovery).
1523 The ``--ignore-ipolicy`` let the command ignore instance policy
1524 violations if replace-disks changes groups and the instance would
1525 violate the new groups instance policy.
1527 See **ganeti**\(7) for a description of ``--submit`` and other common
1533 **activate-disks** [\--submit] [\--ignore-size] [\--wait-for-sync] {*instance*}
1535 Activates the block devices of the given instance. If successful, the
1536 command will show the location and name of the block devices::
1538 node1.example.com:disk/0:/dev/drbd0
1539 node1.example.com:disk/1:/dev/drbd1
1542 In this example, *node1.example.com* is the name of the node on which
1543 the devices have been activated. The *disk/0* and *disk/1* are the
1544 Ganeti-names of the instance disks; how they are visible inside the
1545 instance is hypervisor-specific. */dev/drbd0* and */dev/drbd1* are the
1546 actual block devices as visible on the node.
1548 The ``--ignore-size`` option can be used to activate disks ignoring
1549 the currently configured size in Ganeti. This can be used in cases
1550 where the configuration has gotten out of sync with the real-world
1551 (e.g. after a partially-failed grow-disk operation or due to rounding
1552 in LVM devices). This should not be used in normal cases, but only
1553 when activate-disks fails without it.
1555 The ``--wait-for-sync`` option will ensure that the command returns only
1556 after the instance's disks are synchronised (mostly for DRBD); this can
1557 be useful to ensure consistency, as otherwise there are no commands that
1558 can wait until synchronisation is done. However when passing this
1559 option, the command will have additional output, making it harder to
1560 parse the disk information.
1562 Note that it is safe to run this command while the instance is already
1565 See **ganeti**\(7) for a description of ``--submit`` and other common
1571 **deactivate-disks** [-f] [\--submit] {*instance*}
1573 De-activates the block devices of the given instance. Note that if you
1574 run this command for an instance with a drbd disk template, while it
1575 is running, it will not be able to shutdown the block devices on the
1576 primary node, but it will shutdown the block devices on the secondary
1577 nodes, thus breaking the replication.
1579 The ``-f``/``--force`` option will skip checks that the instance is
1580 down; in case the hypervisor is confused and we can't talk to it,
1581 normally Ganeti will refuse to deactivate the disks, but with this
1582 option passed it will skip this check and directly try to deactivate
1583 the disks. This can still fail due to the instance actually running or
1586 See **ganeti**\(7) for a description of ``--submit`` and other common
1592 | **grow-disk** [\--no-wait-for-sync] [\--submit] [\--absolute]
1593 | {*instance*} {*disk*} {*amount*}
1595 Grows an instance's disk. This is only possible for instances having a
1596 plain, drbd, file, sharedfile, rbd or ext disk template. For the ext
1597 template to work, the ExtStorage provider should also support growing.
1598 This means having a ``grow`` script that actually grows the volume of
1599 the external shared storage.
1601 Note that this command only change the block device size; it will not
1602 grow the actual filesystems, partitions, etc. that live on that
1603 disk. Usually, you will need to:
1605 #. use **gnt-instance grow-disk**
1607 #. reboot the instance (later, at a convenient time)
1609 #. use a filesystem resizer, such as **ext2online**\(8) or
1610 **xfs\_growfs**\(8) to resize the filesystem, or use **fdisk**\(8) to
1611 change the partition table on the disk
1613 The *disk* argument is the index of the instance disk to grow. The
1614 *amount* argument is given as a number which can have a suffix (like the
1615 disk size in instance create); if the suffix is missing, the value will
1616 be interpreted as mebibytes.
1618 By default, the *amount* value represents the desired increase in the
1619 disk size (e.g. an amount of 1G will take a disk of size 3G to 4G). If
1620 the optional ``--absolute`` parameter is passed, then the *amount*
1621 argument doesn't represent the delta, but instead the desired final disk
1622 size (e.g. an amount of 8G will take a disk of size 4G to 8G).
1624 For instances with a drbd template, note that the disk grow operation
1625 might complete on one node but fail on the other; this will leave the
1626 instance with different-sized LVs on the two nodes, but this will not
1627 create problems (except for unused space).
1629 If you do not want gnt-instance to wait for the new disk region to be
1630 synced, use the ``--no-wait-for-sync`` option.
1632 See **ganeti**\(7) for a description of ``--submit`` and other common
1635 Example (increase the first disk for instance1 by 16GiB)::
1637 # gnt-instance grow-disk instance1.example.com 0 16g
1639 Example for increasing the disk size to a certain size::
1641 # gnt-instance grow-disk --absolute instance1.example.com 0 32g
1643 Also note that disk shrinking is not supported; use **gnt-backup
1644 export** and then **gnt-backup import** to reduce the disk size of an
1650 | **recreate-disks** [\--submit]
1651 | [{-n node1:[node2] \| {-I\|\--iallocator *name*}}]
1652 | [\--disk=*N*[:[size=*VAL*][,mode=*ro\|rw*]]] {*instance*}
1654 Recreates all or a subset of disks of the given instance.
1656 Note that this functionality should only be used for missing disks; if
1657 any of the given disks already exists, the operation will fail. While
1658 this is suboptimal, recreate-disks should hopefully not be needed in
1659 normal operation and as such the impact of this is low.
1661 If only a subset should be recreated, any number of ``disk`` options can
1662 be specified. It expects a disk index and an optional list of disk
1663 parameters to change. Only ``size`` and ``mode`` can be changed while
1664 recreating disks. To recreate all disks while changing parameters on
1665 a subset only, a ``--disk`` option must be given for every disk of the
1668 Optionally the instance's disks can be recreated on different
1669 nodes. This can be useful if, for example, the original nodes of the
1670 instance have gone down (and are marked offline), so we can't recreate
1671 on the same nodes. To do this, pass the new node(s) via ``-n`` option,
1672 with a syntax similar to the **add** command. The number of nodes
1673 passed must equal the number of nodes that the instance currently
1674 has. Note that changing nodes is only allowed when all disks are
1675 replaced, e.g. when no ``--disk`` option is passed.
1677 Another method of choosing which nodes to place the instance on is by
1678 using the specified iallocator, passing the ``--iallocator`` option.
1679 The primary and secondary nodes will be chosen by the specified
1680 iallocator plugin, or by the default allocator if ``.`` is specified.
1682 See **ganeti**\(7) for a description of ``--submit`` and other common
1691 | **failover** [-f] [\--ignore-consistency] [\--ignore-ipolicy]
1692 | [\--shutdown-timeout=*N*]
1693 | [{-n|\--target-node} *node* \| {-I|\--iallocator} *name*]
1694 | [\--submit] [\--cleanup]
1697 Failover will stop the instance (if running), change its primary node,
1698 and if it was originally running it will start it again (on the new
1699 primary). This works for instances with drbd template (in which case you
1700 can only fail to the secondary node) and for externally mirrored
1701 templates (sharedfile, blockdev, rbd and ext) (in which case you can
1702 fail to any other node).
1704 If the instance's disk template is of type sharedfile, blockdev, rbd or
1705 ext, then you can explicitly specify the target node (which can be any
1706 node) using the ``-n`` or ``--target-node`` option, or specify an
1707 iallocator plugin using the ``-I`` or ``--iallocator`` option. If you
1708 omit both, the default iallocator will be used to specify the target
1711 If the instance's disk template is of type drbd, the target node is
1712 automatically selected as the drbd's secondary node. Changing the
1713 secondary node is possible with a replace-disks operation.
1715 Normally the failover will check the consistency of the disks before
1716 failing over the instance. If you are trying to migrate instances off
1717 a dead node, this will fail. Use the ``--ignore-consistency`` option
1718 for this purpose. Note that this option can be dangerous as errors in
1719 shutting down the instance will be ignored, resulting in possibly
1720 having the instance running on two machines in parallel (on
1721 disconnected DRBD drives).
1723 The ``--shutdown-timeout`` is used to specify how much time to wait
1724 before forcing the shutdown (xm destroy in xen, killing the kvm
1725 process, for kvm). By default two minutes are given to each instance
1728 If ``--ignore-ipolicy`` is given any instance policy violations occuring
1729 during this operation are ignored.
1731 If the ``--cleanup`` option is passed, the operation changes from
1732 performin a failover to attempting recovery from a failed previous failover.
1733 In this mode, Ganeti checks if the instance runs on the correct node (and
1734 updates its configuration if not) and ensures the instances' disks
1735 are configured correctly.
1737 See **ganeti**\(7) for a description of ``--submit`` and other common
1742 # gnt-instance failover instance1.example.com
1744 For externally mirrored templates also ``-n`` is available::
1746 # gnt-instance failover -n node3.example.com instance1.example.com
1752 | **migrate** [-f] [\--allow-failover] [\--non-live]
1753 | [\--migration-mode=live\|non-live] [\--ignore-ipolicy]
1754 | [\--no-runtime-changes] [\--submit]
1755 | [{-n|\--target-node} *node* \| {-I|\--iallocator} *name*] {*instance*}
1757 | **migrate** [-f] \--cleanup [\--submit] {*instance*}
1759 Migrate will move the instance to its secondary node without shutdown.
1760 As with failover, it works for instances having the drbd disk template
1761 or an externally mirrored disk template type such as sharedfile,
1762 blockdev, rbd or ext.
1764 If the instance's disk template is of type sharedfile, blockdev, rbd or
1765 ext, then you can explicitly specify the target node (which can be any
1766 node) using the ``-n`` or ``--target-node`` option, or specify an
1767 iallocator plugin using the ``-I`` or ``--iallocator`` option. If you
1768 omit both, the default iallocator will be used to specify the target
1769 node. Alternatively, the default iallocator can be requested by
1770 specifying ``.`` as the name of the plugin.
1772 If the instance's disk template is of type drbd, the target node is
1773 automatically selected as the drbd's secondary node. Changing the
1774 secondary node is possible with a replace-disks operation.
1776 The migration command needs a perfectly healthy instance for drbd
1777 instances, as we rely on the dual-master capability of drbd8 and the
1778 disks of the instance are not allowed to be degraded.
1780 The ``--non-live`` and ``--migration-mode=non-live`` options will
1781 switch (for the hypervisors that support it) between a "fully live"
1782 (i.e. the interruption is as minimal as possible) migration and one in
1783 which the instance is frozen, its state saved and transported to the
1784 remote node, and then resumed there. This all depends on the
1785 hypervisor support for two different methods. In any case, it is not
1786 an error to pass this parameter (it will just be ignored if the
1787 hypervisor doesn't support it). The option ``--migration-mode=live``
1788 option will request a fully-live migration. The default, when neither
1789 option is passed, depends on the hypervisor parameters (and can be
1790 viewed with the **gnt-cluster info** command).
1792 If the ``--cleanup`` option is passed, the operation changes from
1793 migration to attempting recovery from a failed previous migration. In
1794 this mode, Ganeti checks if the instance runs on the correct node (and
1795 updates its configuration if not) and ensures the instances' disks
1796 are configured correctly. In this mode, the ``--non-live`` option is
1799 The option ``-f`` will skip the prompting for confirmation.
1801 If ``--allow-failover`` is specified it tries to fallback to failover if
1802 it already can determine that a migration won't work (e.g. if the
1803 instance is shut down). Please note that the fallback will not happen
1804 during execution. If a migration fails during execution it still fails.
1806 If ``--ignore-ipolicy`` is given any instance policy violations occuring
1807 during this operation are ignored.
1809 The ``--no-runtime-changes`` option forbids migrate to alter an
1810 instance's runtime before migrating it (eg. ballooning an instance
1811 down because the target node doesn't have enough available memory).
1813 If an instance has the backend parameter ``always_failover`` set to
1814 true, then the migration is automatically converted into a failover.
1816 See **ganeti**\(7) for a description of ``--submit`` and other common
1819 Example (and expected output)::
1821 # gnt-instance migrate instance1
1822 Instance instance1 will be migrated. Note that migration
1823 might impact the instance if anything goes wrong (e.g. due to bugs in
1824 the hypervisor). Continue?
1826 Migrating instance instance1.example.com
1827 * checking disk consistency between source and target
1828 * switching node node2.example.com to secondary mode
1829 * changing into standalone mode
1830 * changing disks into dual-master mode
1831 * wait until resync is done
1832 * preparing node2.example.com to accept the instance
1833 * migrating instance to node2.example.com
1834 * switching node node1.example.com to secondary mode
1835 * wait until resync is done
1836 * changing into standalone mode
1837 * changing disks into single-master mode
1838 * wait until resync is done
1846 | **move** [-f] [\--ignore-consistency]
1847 | [-n *node*] [\--shutdown-timeout=*N*] [\--submit] [\--ignore-ipolicy]
1850 Move will move the instance to an arbitrary node in the cluster. This
1851 works only for instances having a plain or file disk template.
1853 Note that since this operation is done via data copy, it will take a
1854 long time for big disks (similar to replace-disks for a drbd
1857 The ``--shutdown-timeout`` is used to specify how much time to wait
1858 before forcing the shutdown (e.g. ``xm destroy`` in XEN, killing the
1859 kvm process for KVM, etc.). By default two minutes are given to each
1862 The ``--ignore-consistency`` option will make Ganeti ignore any errors
1863 in trying to shutdown the instance on its node; useful if the
1864 hypervisor is broken and you want to recover the data.
1866 If ``--ignore-ipolicy`` is given any instance policy violations occuring
1867 during this operation are ignored.
1869 See **ganeti**\(7) for a description of ``--submit`` and other common
1874 # gnt-instance move -n node3.example.com instance1.example.com
1880 | **change-group** [\--submit]
1881 | [\--iallocator *NAME*] [\--to *GROUP*...] {*instance*}
1883 This command moves an instance to another node group. The move is
1884 calculated by an iallocator, either given on the command line or as a
1887 If no specific destination groups are specified using ``--to``, all
1888 groups except the one containing the instance are considered.
1890 See **ganeti**\(7) for a description of ``--submit`` and other common
1895 # gnt-instance change-group -I hail --to rack2 inst1.example.com
1904 **add-tags** [\--from *file*] {*instancename*} {*tag*...}
1906 Add tags to the given instance. If any of the tags contains invalid
1907 characters, the entire operation will abort.
1909 If the ``--from`` option is given, the list of tags will be extended
1910 with the contents of that file (each line becomes a tag). In this
1911 case, there is not need to pass tags on the command line (if you do,
1912 both sources will be used). A file name of ``-`` will be interpreted
1918 **list-tags** {*instancename*}
1920 List the tags of the given instance.
1925 **remove-tags** [\--from *file*] {*instancename*} {*tag*...}
1927 Remove tags from the given instance. If any of the tags are not
1928 existing on the node, the entire operation will abort.
1930 If the ``--from`` option is given, the list of tags to be removed will
1931 be extended with the contents of that file (each line becomes a tag).
1932 In this case, there is not need to pass tags on the command line (if
1933 you do, tags from both sources will be removed). A file name of ``-``
1934 will be interpreted as stdin.
1936 .. vim: set textwidth=72 :