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}}
31 | {--disk=*N*: {size=*VAL* \| adopt=*LV*}[,vg=*VG*][,metavg=*VG*][,mode=*ro\|rw*]
32 | \| {-s|--os-size} *SIZE*}
33 | [--no-ip-check] [--no-name-check] [--no-start] [--no-install]
34 | [--net=*N* [:options...] \| --no-nics]
35 | [{-B|--backend-parameters} *BEPARAMS*]
36 | [{-H|--hypervisor-parameters} *HYPERVISOR* [: option=*value*... ]]
37 | [{-O|--os-parameters} *param*=*value*... ]
38 | [--file-storage-dir *dir\_path*] [--file-driver {loop \| blktap}]
39 | {{-n|--node} *node[:secondary-node]* \| {-I|--iallocator} *name*}
40 | {{-o|--os-type} *os-type*}
45 Creates a new instance on the specified host. The *instance* argument
46 must be in DNS, but depending on the bridge/routing setup, need not be
47 in the same network as the nodes in the cluster.
49 The ``disk`` option specifies the parameters for the disks of the
50 instance. The numbering of disks starts at zero, and at least one disk
51 needs to be passed. For each disk, either the size or the adoption
52 source needs to be given, and optionally the access mode (read-only or
53 the default of read-write) and the LVM volume group can also be
54 specified (via the ``vg`` key). For DRBD devices, a different VG can
55 be specified for the metadata device using the ``metavg`` key. The
56 size is interpreted (when no unit is given) in mebibytes. You can also
57 use one of the suffixes *m*, *g* or *t* to specify the exact the units
58 used; these suffixes map to mebibytes, gibibytes and tebibytes.
60 When using the ``adopt`` key in the disk definition, Ganeti will
61 reuse those volumes (instead of creating new ones) as the
62 instance's disks. Ganeti will rename these volumes to the standard
63 format, and (without installing the OS) will use them as-is for the
64 instance. This allows migrating instances from non-managed mode
65 (e.g. plain KVM with LVM) to being managed via Ganeti. Please note that
66 this works only for the \`plain' disk template (see below for
69 Alternatively, a single-disk instance can be created via the ``-s``
70 option which takes a single argument, the size of the disk. This is
71 similar to the Ganeti 1.2 version (but will only create one disk).
73 The minimum disk specification is therefore ``--disk 0:size=20G`` (or
74 ``-s 20G`` when using the ``-s`` option), and a three-disk instance
75 can be specified as ``--disk 0:size=20G --disk 1:size=4G --disk
78 The ``--no-ip-check`` skips the checks that are done to see if the
79 instance's IP is not already alive (i.e. reachable from the master
82 The ``--no-name-check`` skips the check for the instance name via
83 the resolver (e.g. in DNS or /etc/hosts, depending on your setup).
84 Since the name check is used to compute the IP address, if you pass
85 this option you must also pass the ``--no-ip-check`` option.
87 If you don't wat the instance to automatically start after
88 creation, this is possible via the ``--no-start`` option. This will
89 leave the instance down until a subsequent **gnt-instance start**
92 The NICs of the instances can be specified via the ``--net``
93 option. By default, one NIC is created for the instance, with a
94 random MAC, and set up according the the cluster level nic
95 parameters. Each NIC can take these parameters (all optional):
98 either a value or 'generate' to generate a new unique MAC
101 specifies the IP address assigned to the instance from the Ganeti
102 side (this is not necessarily what the instance will use, but what
103 the node expects the instance to use)
106 specifies the connection mode for this nic: routed or bridged.
109 in bridged mode specifies the bridge to attach this NIC to, in
110 routed mode it's intended to differentiate between different
111 routing tables/instance groups (but the meaning is dependent on
112 the network script, see gnt-cluster(8) for more details)
115 Of these "mode" and "link" are nic parameters, and inherit their
116 default at cluster level. Alternatively, if no network is desired for
117 the instance, you can prevent the default of one NIC with the
118 ``--no-nics`` option.
120 The ``-o (--os-type)`` option specifies the operating system to be
121 installed. The available operating systems can be listed with
122 **gnt-os list**. Passing ``--no-install`` will however skip the OS
123 installation, allowing a manual import if so desired. Note that the
124 no-installation mode will automatically disable the start-up of the
125 instance (without an OS, it most likely won't be able to start-up
128 The ``-B (--backend-parameters)`` option specifies the backend
129 parameters for the instance. If no such parameters are specified, the
130 values are inherited from the cluster. Possible parameters are:
133 the maximum memory size of the instance; as usual, suffixes can be
134 used to denote the unit, otherwise the value is taken in mebibytes
137 the minimum memory size of the instance; as usual, suffixes can be
138 used to denote the unit, otherwise the value is taken in mebibytes
141 the number of VCPUs to assign to the instance (if this value makes
142 sense for the hypervisor)
145 whether the instance is considered in the N+1 cluster checks
146 (enough redundancy in the cluster to survive a node failure)
149 ``True`` or ``False``, whether the instance must be failed over
150 (shut down and rebooted) always or it may be migrated (briefly
153 Note that before 2.6 Ganeti had a ``memory`` parameter, which was the
154 only value of memory an instance could have. With the
155 ``maxmem``/``minmem`` change Ganeti guarantees that at least the minimum
156 memory is always available for an instance, but allows more memory to be
157 used (up to the maximum memory) should it be free.
159 The ``-H (--hypervisor-parameters)`` option specified the hypervisor
160 to use for the instance (must be one of the enabled hypervisors on the
161 cluster) and optionally custom parameters for this instance. If not
162 other options are used (i.e. the invocation is just -H *NAME*) the
163 instance will inherit the cluster options. The defaults below show the
164 cluster defaults at cluster creation time.
166 The possible hypervisor options are as follows:
169 Valid for the Xen HVM and KVM hypervisors.
171 A string value denoting the boot order. This has different meaning
172 for the Xen HVM hypervisor and for the KVM one.
174 For Xen HVM, The boot order is a string of letters listing the boot
175 devices, with valid device letters being:
189 The default is not to set an HVM boot order, which is interpreted
192 For KVM the boot order is either "floppy", "cdrom", "disk" or
193 "network". Please note that older versions of KVM couldn't
194 netboot from virtio interfaces. This has been fixed in more recent
195 versions and is confirmed to work at least with qemu-kvm 0.11.1.
198 Valid for the Xen HVM and PVM hypervisors.
200 Relevant to non-pvops guest kernels, in which the disk device names
201 are given by the host. Allows one to specify 'xvd', which helps run
202 Red Hat based installers, driven by anaconda.
205 Valid for the KVM hypervisor.
207 The path to a floppy disk image to attach to the instance. This
208 is useful to install Windows operating systems on Virt/IO disks
209 because you can specify here the floppy for the drivers at
213 Valid for the Xen HVM and KVM hypervisors.
215 The path to a CDROM image to attach to the instance.
218 Valid for the KVM hypervisor.
220 The path to a second CDROM image to attach to the instance.
221 **NOTE**: This image can't be used to boot the system. To do that
222 you have to use the 'cdrom\_image\_path' option.
225 Valid for the Xen HVM and KVM hypervisors.
227 This parameter determines the way the network cards are presented
228 to the instance. The possible options are:
230 - rtl8139 (default for Xen HVM) (HVM & KVM)
231 - ne2k\_isa (HVM & KVM)
232 - ne2k\_pci (HVM & KVM)
238 - paravirtual (default for KVM) (HVM & KVM)
241 Valid for the Xen HVM and KVM hypervisors.
243 This parameter determines the way the disks are presented to the
244 instance. The possible options are:
246 - ioemu [default] (HVM & KVM)
255 Valid for the KVM hypervisor.
257 This parameter determines the way the cdroms disks are presented
258 to the instance. The default behavior is to get the same value of
259 the eariler parameter (disk_type). The possible options are:
270 Valid for the Xen HVM and KVM hypervisors.
272 Specifies the address that the VNC listener for this instance
273 should bind to. Valid values are IPv4 addresses. Use the address
274 0.0.0.0 to bind to all available interfaces (this is the default)
275 or specify the address of one of the interfaces on the node to
276 restrict listening to that interface.
279 Valid for the KVM hypervisor.
281 A boolean option that controls whether the VNC connection is
285 Valid for the KVM hypervisor.
287 If ``vnc_tls`` is enabled, this options specifies the path to the
288 x509 certificate to use.
291 Valid for the KVM hypervisor.
294 Valid for the KVM hypervisor.
296 Specifies the address or interface on which the SPICE server will
297 listen. Valid values are:
299 - IPv4 addresses, including 0.0.0.0 and 127.0.0.1
300 - IPv6 addresses, including :: and ::1
301 - names of network interfaces
303 If a network interface is specified, the SPICE server will be bound
304 to one of the addresses of that interface.
307 Valid for the KVM hypervisor.
309 Specifies which version of the IP protocol should be used by the
312 It is mainly intended to be used for specifying what kind of IP
313 addresses should be used if a network interface with both IPv4 and
314 IPv6 addresses is specified via the ``spice_bind`` parameter. In
315 this case, if the ``spice_ip_version`` parameter is not used, the
316 default IP version of the cluster will be used.
318 spice\_password\_file
319 Valid for the KVM hypervisor.
321 Specifies a file containing the password that must be used when
322 connecting via the SPICE protocol. If the option is not specified,
323 passwordless connections are allowed.
325 spice\_image\_compression
326 Valid for the KVM hypervisor.
328 Configures the SPICE lossless image compression. Valid values are:
337 spice\_jpeg\_wan\_compression
338 Valid for the KVM hypervisor.
340 Configures how SPICE should use the jpeg algorithm for lossy image
341 compression on slow links. Valid values are:
347 spice\_zlib\_glz\_wan\_compression
348 Valid for the KVM hypervisor.
350 Configures how SPICE should use the zlib-glz algorithm for lossy image
351 compression on slow links. Valid values are:
357 spice\_streaming\_video
358 Valid for the KVM hypervisor.
360 Configures how SPICE should detect video streams. Valid values are:
366 spice\_playback\_compression
367 Valid for the KVM hypervisor.
369 Configures whether SPICE should compress audio streams or not.
372 Valid for the KVM hypervisor.
374 Specifies that the SPICE server must use TLS to encrypt all the
375 traffic with the client.
378 Valid for the KVM hypervisor.
380 Specifies a list of comma-separated ciphers that SPICE should use
381 for TLS connections. For the format, see man cipher(1).
384 Valid for the KVM hypervisor.
386 Enables or disables passing mouse events via SPICE vdagent.
389 Valid for the Xen HVM and KVM hypervisors.
391 A boolean option that specifies if the hypervisor should enable
392 ACPI support for this instance. By default, ACPI is disabled.
395 Valid for the Xen HVM and KVM hypervisors.
397 A boolean option that specifies if the hypervisor should enabled
398 PAE support for this instance. The default is false, disabling PAE
402 Valid for the Xen HVM and KVM hypervisors.
404 A boolean option that specifies if the instance should be started
405 with its clock set to the localtime of the machine (when true) or
406 to the UTC (When false). The default is false, which is useful for
407 Linux/Unix machines; for Windows OSes, it is recommended to enable
411 Valid for the Xen PVM and KVM hypervisors.
413 This option specifies the path (on the node) to the kernel to boot
414 the instance with. Xen PVM instances always require this, while
415 for KVM if this option is empty, it will cause the machine to load
416 the kernel from its disks.
419 Valid for the Xen PVM and KVM hypervisors.
421 This options specifies extra arguments to the kernel that will be
422 loaded. device. This is always used for Xen PVM, while for KVM it
423 is only used if the ``kernel_path`` option is also specified.
425 The default setting for this value is simply ``"ro"``, which
426 mounts the root disk (initially) in read-only one. For example,
427 setting this to single will cause the instance to start in
431 Valid for the Xen PVM and KVM hypervisors.
433 This option specifies the path (on the node) to the initrd to boot
434 the instance with. Xen PVM instances can use this always, while
435 for KVM if this option is only used if the ``kernel_path`` option
436 is also specified. You can pass here either an absolute filename
437 (the path to the initrd) if you want to use an initrd, or use the
438 format no\_initrd\_path for no initrd.
441 Valid for the Xen PVM and KVM hypervisors.
443 This options specifies the name of the root device. This is always
444 needed for Xen PVM, while for KVM it is only used if the
445 ``kernel_path`` option is also specified.
447 Please note, that if this setting is an empty string and the
448 hypervisor is Xen it will not be written to the Xen configuration
452 Valid for the KVM hypervisor.
454 This boolean option specifies whether to emulate a serial console
458 Valid for the KVM hypervisor.
460 The disk cache mode. It can be either default to not pass any
461 cache option to KVM, or one of the KVM cache modes: none (for
462 direct I/O), writethrough (to use the host cache but report
463 completion to the guest only when the host has committed the
464 changes to disk) or writeback (to use the host cache and report
465 completion as soon as the data is in the host cache). Note that
466 there are special considerations for the cache mode depending on
467 version of KVM used and disk type (always raw file under Ganeti),
468 please refer to the KVM documentation for more details.
471 Valid for the KVM hypervisor.
473 The security model for kvm. Currently one of *none*, *user* or
474 *pool*. Under *none*, the default, nothing is done and instances
475 are run as the Ganeti daemon user (normally root).
477 Under *user* kvm will drop privileges and become the user
478 specified by the security\_domain parameter.
480 Under *pool* a global cluster pool of users will be used, making
481 sure no two instances share the same user on the same node. (this
482 mode is not implemented yet)
485 Valid for the KVM hypervisor.
487 Under security model *user* the username to run the instance
488 under. It must be a valid username existing on the host.
490 Cannot be set under security model *none* or *pool*.
493 Valid for the KVM hypervisor.
495 If *enabled* the -enable-kvm flag is passed to kvm. If *disabled*
496 -disable-kvm is passed. If unset no flag is passed, and the
497 default running mode for your kvm binary will be used.
500 Valid for the KVM hypervisor.
502 This option passes the -mem-path argument to kvm with the path (on
503 the node) to the mount point of the hugetlbfs file system, along
504 with the -mem-prealloc argument too.
507 Valid for the KVM hypervisor.
509 This boolean option determines wether to run the KVM instance in a
512 If it is set to ``true``, an empty directory is created before
513 starting the instance and its path is passed via the -chroot flag
514 to kvm. The directory is removed when the instance is stopped.
516 It is set to ``false`` by default.
519 Valid for the KVM hypervisor.
521 The maximum amount of time (in ms) a KVM instance is allowed to be
522 frozen during a live migration, in order to copy dirty memory
523 pages. Default value is 30ms, but you may need to increase this
524 value for busy instances.
526 This option is only effective with kvm versions >= 87 and qemu-kvm
530 Valid for the LXC hypervisor.
532 The processes belonging to the given instance are only scheduled
533 on the specified CPUs.
535 The parameter format is a comma-separated list of CPU IDs or CPU
536 ID ranges. The ranges are defined by a lower and higher boundary,
537 separated by a dash. The boundaries are inclusive.
540 Valid for the KVM hypervisor.
542 This option specifies the usb mouse type to be used. It can be
543 "mouse" or "tablet". When using VNC it's recommended to set it to
547 Valid for the KVM hypervisor.
549 This option specifies the keyboard mapping to be used. It is only
550 needed when using the VNC console. For example: "fr" or "en-gb".
553 Valid for Xen PVM, Xen HVM and KVM hypervisors.
555 Normally if an instance reboots, the hypervisor will restart it. If
556 this option is set to ``exit``, the hypervisor will treat a reboot
557 as a shutdown instead.
559 It is set to ``reboot`` by default.
562 The ``-O (--os-parameters)`` option allows customisation of the OS
563 parameters. The actual parameter names and values depends on the OS
564 being used, but the syntax is the same key=value. For example, setting
565 a hypothetical ``dhcp`` parameter to yes can be achieved by::
567 gnt-instance add -O dhcp=yes ...
569 The ``-I (--iallocator)`` option specifies the instance allocator
570 plugin to use. If you pass in this option the allocator will select
571 nodes for this instance automatically, so you don't need to pass them
572 with the ``-n`` option. For more information please refer to the
573 instance allocator documentation.
575 The ``-t (--disk-template)`` options specifies the disk layout type
576 for the instance. The available choices are:
579 This creates an instance with no disks. Its useful for testing only
580 (or other special cases).
583 Disk devices will be regular files.
586 Disk devices will be logical volumes.
589 Disk devices will be drbd (version 8.x) on top of lvm volumes.
592 The optional second value of the ``-n (--node)`` is used for the drbd
593 template type and specifies the remote node.
595 If you do not want gnt-instance to wait for the disk mirror to be
596 synced, use the ``--no-wait-for-sync`` option.
598 The ``--file-storage-dir`` specifies the relative path under the
599 cluster-wide file storage directory to store file-based disks. It is
600 useful for having different subdirectories for different
601 instances. The full path of the directory where the disk files are
602 stored will consist of cluster-wide file storage directory + optional
603 subdirectory + instance name. Example:
604 ``@RPL_FILE_STORAGE_DIR@``*/mysubdir/instance1.example.com*. This
605 option is only relevant for instances using the file storage backend.
607 The ``--file-driver`` specifies the driver to use for file-based
608 disks. Note that currently these drivers work with the xen hypervisor
609 only. This option is only relevant for instances using the file
610 storage backend. The available choices are:
613 Kernel loopback driver. This driver uses loopback devices to
614 access the filesystem within the file. However, running I/O
615 intensive applications in your instance using the loop driver
616 might result in slowdowns. Furthermore, if you use the loopback
617 driver consider increasing the maximum amount of loopback devices
618 (on most systems it's 8) using the max\_loop param.
621 The blktap driver (for Xen hypervisors). In order to be able to
622 use the blktap driver you should check if the 'blktapctrl' user
623 space disk agent is running (usually automatically started via
624 xend). This user-level disk I/O interface has the advantage of
625 better performance. Especially if you use a network file system
626 (e.g. NFS) to store your instances this is the recommended choice.
629 The ``--submit`` option is used to send the job to the master daemon
630 but not wait for its completion. The job ID will be shown so that it
631 can be examined via **gnt-job info**.
633 If ``--ignore-ipolicy`` is given any instance policy violations occuring
634 during this operation are ignored.
638 # gnt-instance add -t file --disk 0:size=30g -B maxmem=512 -o debian-etch \
639 -n node1.example.com --file-storage-dir=mysubdir instance1.example.com
640 # gnt-instance add -t plain --disk 0:size=30g -B maxmem=1024,minmem=512 \
641 -o debian-etch -n node1.example.com instance1.example.com
642 # gnt-instance add -t plain --disk 0:size=30g --disk 1:size=100g,vg=san \
643 -B maxmem=512 -o debian-etch -n node1.example.com instance1.example.com
644 # gnt-instance add -t drbd --disk 0:size=30g -B maxmem=512 -o debian-etch \
645 -n node1.example.com:node2.example.com instance2.example.com
651 **batch-create** {instances\_file.json}
653 This command (similar to the Ganeti 1.2 **batcher** tool) submits
654 multiple instance creation jobs based on a definition file. The
655 instance configurations do not encompass all the possible options for
656 the **add** command, but only a subset.
658 The instance file should be a valid-formed JSON file, containing a
659 dictionary with instance name and instance parameters. The accepted
663 The size of the disks of the instance.
666 The disk template to use for the instance, the same as in the
670 A dictionary of backend parameters.
673 A dictionary with a single key (the hypervisor name), and as value
674 the hypervisor options. If not passed, the default hypervisor and
675 hypervisor options will be inherited.
678 Specifications for the one NIC that will be created for the
679 instance. 'bridge' is also accepted as a backwards compatibile
683 List of nics that will be created for the instance. Each entry
684 should be a dict, with mac, ip, mode and link as possible keys.
685 Please don't provide the "mac, ip, mode, link" parent keys if you
686 use this method for specifying nics.
688 primary\_node, secondary\_node
689 The primary and optionally the secondary node to use for the
690 instance (in case an iallocator script is not used).
693 Instead of specifying the nodes, an iallocator script can be used
694 to automatically compute them.
697 whether to start the instance
700 Skip the check for already-in-use instance; see the description in
701 the **add** command for details.
704 Skip the name check for instances; see the description in the
705 **add** command for details.
707 file\_storage\_dir, file\_driver
708 Configuration for the file disk type, see the **add** command for
712 A simple definition for one instance can be (with most of the
713 parameters taken from the cluster defaults)::
719 "disk_size": ["25G"],
725 "disk_size": ["25G"],
726 "iallocator": "dumb",
727 "hypervisor": "xen-hvm",
728 "hvparams": {"acpi": true},
729 "backend": {"maxmem": 512, "minmem": 256}
733 The command will display the job id for each submitted instance, as
736 # gnt-instance batch-create instances.json
743 **remove** [--ignore-failures] [--shutdown-timeout=*N*] [--submit]
744 [--force] {*instance*}
746 Remove an instance. This will remove all data from the instance and
747 there is *no way back*. If you are not sure if you use an instance
748 again, use **shutdown** first and leave it in the shutdown state for a
751 The ``--ignore-failures`` option will cause the removal to proceed
752 even in the presence of errors during the removal of the instance
753 (e.g. during the shutdown or the disk removal). If this option is not
754 given, the command will stop at the first error.
756 The ``--shutdown-timeout`` is used to specify how much time to wait
757 before forcing the shutdown (e.g. ``xm destroy`` in Xen, killing the
758 kvm process for KVM, etc.). By default two minutes are given to each
761 The ``--submit`` option is used to send the job to the master daemon
762 but not wait for its completion. The job ID will be shown so that it
763 can be examined via **gnt-job info**.
765 The ``--force`` option is used to skip the interactive confirmation.
769 # gnt-instance remove instance1.example.com
776 | [--no-headers] [--separator=*SEPARATOR*] [--units=*UNITS*] [-v]
777 | [{-o|--output} *[+]FIELD,...*] [--filter] [instance...]
779 Shows the currently configured instances with memory usage, disk
780 usage, the node they are running on, and their run status.
782 The ``--no-headers`` option will skip the initial header line. The
783 ``--separator`` option takes an argument which denotes what will be
784 used between the output fields. Both these options are to help
787 The units used to display the numeric values in the output varies,
788 depending on the options given. By default, the values will be
789 formatted in the most appropriate unit. If the ``--separator`` option
790 is given, then the values are shown in mebibytes to allow parsing by
791 scripts. In both cases, the ``--units`` option can be used to enforce
794 The ``-v`` option activates verbose mode, which changes the display of
795 special field states (see **ganeti(7)**).
797 The ``-o (--output)`` option takes a comma-separated list of output
798 fields. The available fields and their meaning are:
800 @QUERY_FIELDS_INSTANCE@
802 If the value of the option starts with the character ``+``, the new
803 field(s) will be added to the default list. This allows one to quickly
804 see the default list plus a few other fields, instead of retyping the
805 entire list of fields.
807 There is a subtle grouping about the available output fields: all
808 fields except for ``oper_state``, ``oper_ram``, ``oper_vcpus`` and
809 ``status`` are configuration value and not run-time values. So if you
810 don't select any of the these fields, the query will be satisfied
811 instantly from the cluster configuration, without having to ask the
812 remote nodes for the data. This can be helpful for big clusters when
813 you only want some data and it makes sense to specify a reduced set of
816 If exactly one argument is given and it appears to be a query filter
817 (see **ganeti(7)**), the query result is filtered accordingly. For
818 ambiguous cases (e.g. a single field name as a filter) the ``--filter``
819 (``-F``) option forces the argument to be treated as a filter (e.g.
820 ``gnt-instance list -F admin_state``).
822 The default output field list is: ``name``, ``os``, ``pnode``,
823 ``admin_state``, ``oper_state``, ``oper_ram``.
829 **list-fields** [field...]
831 Lists available fields for instances.
837 **info** [-s \| --static] [--roman] {--all \| *instance*}
839 Show detailed information about the given instance(s). This is
840 different from **list** as it shows detailed data about the instance's
841 disks (especially useful for the drbd disk template).
843 If the option ``-s`` is used, only information available in the
844 configuration file is returned, without querying nodes, making the
847 Use the ``--all`` to get info about all instances, rather than
848 explicitly passing the ones you're interested in.
850 The ``--roman`` option can be used to cause envy among people who like
851 ancient cultures, but are stuck with non-latin-friendly cluster
852 virtualization technologies.
858 | [{-H|--hypervisor-parameters} *HYPERVISOR\_PARAMETERS*]
859 | [{-B|--backend-parameters} *BACKEND\_PARAMETERS*]
860 | [--net add*[:options]* \| --net remove \| --net *N:options*]
861 | [--disk add:size=*SIZE*[,vg=*VG*][,metavg=*VG*] \| --disk remove \|
862 | --disk *N*:mode=*MODE*]
863 | [{-t|--disk-template} plain | {-t|--disk-template} drbd -n *new_secondary*] [--no-wait-for-sync]
864 | [--os-type=*OS* [--force-variant]]
865 | [{-O|--os-parameters} *param*=*value*... ]
866 | [--offline \| --online]
871 Modifies the memory size, number of vcpus, ip address, MAC address
872 and/or nic parameters for an instance. It can also add and remove
873 disks and NICs to/from the instance. Note that you need to give at
874 least one of the arguments, otherwise the command complains.
876 The ``-H (--hypervisor-parameters)``, ``-B (--backend-parameters)``
877 and ``-O (--os-parameters)`` options specifies hypervisor, backend and
878 OS parameter options in the form of name=value[,...]. For details
879 which options can be specified, see the **add** command.
881 The ``-t (--disk-template)`` option will change the disk template of
882 the instance. Currently only conversions between the plain and drbd
883 disk templates are supported, and the instance must be stopped before
884 attempting the conversion. When changing from the plain to the drbd
885 disk template, a new secondary node must be specified via the ``-n``
886 option. The option ``--no-wait-for-sync`` can be used when converting
887 to the ``drbd`` template in order to make the instance available for
888 startup before DRBD has finished resyncing.
890 The ``--disk add:size=``*SIZE* option adds a disk to the instance. The
891 optional ``vg=``*VG* option specifies LVM volume group other than
892 default vg to create the disk on. For DRBD disks, the ``metavg=``*VG*
893 option specifies the volume group for the metadata device. The
894 ``--disk remove`` option will remove the last disk of the
895 instance. The ``--disk`` *N*``:mode=``*MODE* option will change the
896 mode of the Nth disk of the instance between read-only (``ro``) and
899 The ``--net add:``*options* option will add a new NIC to the
900 instance. The available options are the same as in the **add** command
901 (mac, ip, link, mode). The ``--net remove`` will remove the last NIC
902 of the instance, while the ``--net`` *N*:*options* option will change
903 the parameters of the Nth instance NIC.
905 The option ``-o (--os-type)`` will change the OS name for the instance
906 (without reinstallation). In case an OS variant is specified that is
907 not found, then by default the modification is refused, unless
908 ``--force-variant`` is passed. An invalid OS will also be refused,
909 unless the ``--force`` option is given.
911 The ``--online`` and ``--offline`` options are used to transition an
912 instance into and out of the ``offline`` state. An instance can be
913 turned offline only if it was previously down. The ``--online`` option
914 fails if the instance was not in the ``offline`` state, otherwise it
915 changes instance's state to ``down``. These modifications take effect
918 The ``--submit`` option is used to send the job to the master daemon
919 but not wait for its completion. The job ID will be shown so that it
920 can be examined via **gnt-job info**.
922 If ``--ignore-ipolicy`` is given any instance policy violations occuring
923 during this operation are ignored.
925 Most of the changes take effect at the next restart. If the instance is
926 running, there is no effect on the instance.
931 | **reinstall** [{-o|--os-type} *os-type*] [--select-os] [-f *force*]
933 | [--instance \| --node \| --primary \| --secondary \| --all]
934 | [{-O|--os-parameters} *OS\_PARAMETERS*] [--submit] {*instance*...}
936 Reinstalls the operating system on the given instance(s). The
937 instance(s) must be stopped when running this command. If the ``-o
938 (--os-type)`` is specified, the operating system is changed.
940 The ``--select-os`` option switches to an interactive OS reinstall.
941 The user is prompted to select the OS template from the list of
942 available OS templates. OS parameters can be overridden using ``-O
943 (--os-parameters)`` (more documentation for this option under the
946 Since this is a potentially dangerous command, the user will be
947 required to confirm this action, unless the ``-f`` flag is passed.
948 When multiple instances are selected (either by passing multiple
949 arguments or by using the ``--node``, ``--primary``, ``--secondary``
950 or ``--all`` options), the user must pass the ``--force-multiple``
951 options to skip the interactive confirmation.
953 The ``--submit`` option is used to send the job to the master daemon
954 but not wait for its completion. The job ID will be shown so that it
955 can be examined via **gnt-job info**.
960 | **rename** [--no-ip-check] [--no-name-check] [--submit]
961 | {*instance*} {*new\_name*}
963 Renames the given instance. The instance must be stopped when running
964 this command. The requirements for the new name are the same as for
965 adding an instance: the new name must be resolvable and the IP it
966 resolves to must not be reachable (in order to prevent duplicate IPs
967 the next time the instance is started). The IP test can be skipped if
968 the ``--no-ip-check`` option is passed.
970 The ``--no-name-check`` skips the check for the new instance name via
971 the resolver (e.g. in DNS or /etc/hosts, depending on your setup) and
972 that the resolved name matches the provided name. Since the name check
973 is used to compute the IP address, if you pass this option you must also
974 pass the ``--no-ip-check`` option.
976 The ``--submit`` option is used to send the job to the master daemon
977 but not wait for its completion. The job ID will be shown so that it
978 can be examined via **gnt-job info**.
980 Starting/stopping/connecting to console
981 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
987 | [--force] [--ignore-offline]
988 | [--force-multiple] [--no-remember]
989 | [--instance \| --node \| --primary \| --secondary \| --all \|
990 | --tags \| --node-tags \| --pri-node-tags \| --sec-node-tags]
991 | [{-H|--hypervisor-parameters} ``key=value...``]
992 | [{-B|--backend-parameters} ``key=value...``]
993 | [--submit] [--paused]
996 Starts one or more instances, depending on the following options. The
997 four available modes are:
1000 will start the instances given as arguments (at least one argument
1001 required); this is the default selection
1004 will start the instances who have the given node as either primary
1008 will start all instances whose primary node is in the list of nodes
1009 passed as arguments (at least one node required)
1012 will start all instances whose secondary node is in the list of
1013 nodes passed as arguments (at least one node required)
1016 will start all instances in the cluster (no arguments accepted)
1019 will start all instances in the cluster with the tags given as
1023 will start all instances in the cluster on nodes with the tags
1027 will start all instances in the cluster on primary nodes with the
1028 tags given as arguments
1031 will start all instances in the cluster on secondary nodes with the
1032 tags given as arguments
1034 Note that although you can pass more than one selection option, the
1035 last one wins, so in order to guarantee the desired result, don't pass
1036 more than one such option.
1038 Use ``--force`` to start even if secondary disks are failing.
1039 ``--ignore-offline`` can be used to ignore offline primary nodes and
1040 mark the instance as started even if the primary is not available.
1042 The ``--force-multiple`` will skip the interactive confirmation in the
1043 case the more than one instance will be affected.
1045 The ``--no-remember`` option will perform the startup but not change
1046 the state of the instance in the configuration file (if it was stopped
1047 before, Ganeti will still thinks it needs to be stopped). This can be
1048 used for testing, or for a one shot-start where you don't want the
1049 watcher to restart the instance if it crashes.
1051 The ``-H (--hypervisor-parameters)`` and ``-B (--backend-parameters)``
1052 options specify temporary hypervisor and backend parameters that can
1053 be used to start an instance with modified parameters. They can be
1054 useful for quick testing without having to modify an instance back and
1057 # gnt-instance start -H kernel_args="single" instance1
1058 # gnt-instance start -B maxmem=2048 instance2
1061 The first form will start the instance instance1 in single-user mode,
1062 and the instance instance2 with 2GB of RAM (this time only, unless
1063 that is the actual instance memory size already). Note that the values
1064 override the instance parameters (and not extend them): an instance
1065 with "kernel\_args=ro" when started with -H kernel\_args=single will
1066 result in "single", not "ro single". The ``--submit`` option is used
1067 to send the job to the master daemon but not wait for its
1068 completion. The job ID will be shown so that it can be examined via
1071 The ``--paused`` option is only valid for Xen and kvm hypervisors. This
1072 pauses the instance at the start of bootup, awaiting ``gnt-instance
1073 console`` to unpause it, allowing the entire boot process to be
1074 monitored for debugging.
1078 # gnt-instance start instance1.example.com
1079 # gnt-instance start --node node1.example.com node2.example.com
1080 # gnt-instance start --all
1088 | [--force-multiple] [--ignore-offline] [--no-remember]
1089 | [--instance \| --node \| --primary \| --secondary \| --all \|
1090 | --tags \| --node-tags \| --pri-node-tags \| --sec-node-tags]
1094 Stops one or more instances. If the instance cannot be cleanly stopped
1095 during a hardcoded interval (currently 2 minutes), it will forcibly
1096 stop the instance (equivalent to switching off the power on a physical
1099 The ``--timeout`` is used to specify how much time to wait before
1100 forcing the shutdown (e.g. ``xm destroy`` in Xen, killing the kvm
1101 process for KVM, etc.). By default two minutes are given to each
1104 The ``--instance``, ``--node``, ``--primary``, ``--secondary``,
1105 ``--all``, ``--tags``, ``--node-tags``, ``--pri-node-tags`` and
1106 ``--sec-node-tags`` options are similar as for the **startup** command
1107 and they influence the actual instances being shutdown.
1109 The ``--submit`` option is used to send the job to the master daemon
1110 but not wait for its completion. The job ID will be shown so that it
1111 can be examined via **gnt-job info**.
1113 ``--ignore-offline`` can be used to ignore offline primary nodes and
1114 force the instance to be marked as stopped. This option should be used
1115 with care as it can lead to an inconsistent cluster state.
1117 The ``--no-remember`` option will perform the shutdown but not change
1118 the state of the instance in the configuration file (if it was running
1119 before, Ganeti will still thinks it needs to be running). This can be
1120 useful for a cluster-wide shutdown, where some instances are marked as
1121 up and some as down, and you don't want to change the running state:
1122 you just need to disable the watcher, shutdown all instances with
1123 ``--no-remember``, and when the watcher is activated again it will
1124 restore the correct runtime state for all instances.
1128 # gnt-instance shutdown instance1.example.com
1129 # gnt-instance shutdown --all
1136 | [{-t|--type} *REBOOT-TYPE*]
1137 | [--ignore-secondaries]
1138 | [--shutdown-timeout=*N*]
1139 | [--force-multiple]
1140 | [--instance \| --node \| --primary \| --secondary \| --all \|
1141 | --tags \| --node-tags \| --pri-node-tags \| --sec-node-tags]
1145 Reboots one or more instances. The type of reboot depends on the value
1146 of ``-t (--type)``. A soft reboot does a hypervisor reboot, a hard reboot
1147 does a instance stop, recreates the hypervisor config for the instance
1148 and starts the instance. A full reboot does the equivalent of
1149 **gnt-instance shutdown && gnt-instance startup**. The default is
1152 For the hard reboot the option ``--ignore-secondaries`` ignores errors
1153 for the secondary node while re-assembling the instance disks.
1155 The ``--instance``, ``--node``, ``--primary``, ``--secondary``,
1156 ``--all``, ``--tags``, ``--node-tags``, ``--pri-node-tags`` and
1157 ``--sec-node-tags`` options are similar as for the **startup** command
1158 and they influence the actual instances being rebooted.
1160 The ``--shutdown-timeout`` is used to specify how much time to wait
1161 before forcing the shutdown (xm destroy in xen, killing the kvm
1162 process, for kvm). By default two minutes are given to each instance
1165 The ``--force-multiple`` will skip the interactive confirmation in the
1166 case the more than one instance will be affected.
1170 # gnt-instance reboot instance1.example.com
1171 # gnt-instance reboot --type=full instance1.example.com
1177 **console** [--show-cmd] {*instance*}
1179 Connects to the console of the given instance. If the instance is not
1180 up, an error is returned. Use the ``--show-cmd`` option to display the
1181 command instead of executing it.
1183 For HVM instances, this will attempt to connect to the serial console
1184 of the instance. To connect to the virtualized "physical" console of a
1185 HVM instance, use a VNC client with the connection info from the
1188 For Xen/kvm instances, if the instance is paused, this attempts to
1189 unpause the instance after waiting a few seconds for the connection to
1190 the console to be made.
1194 # gnt-instance console instance1.example.com
1203 **replace-disks** [--submit] [--early-release] {-p} [--disks *idx*]
1206 **replace-disks** [--submit] [--early-release] {-s} [--disks *idx*]
1209 **replace-disks** [--submit] [--early-release] {--iallocator *name*
1210 \| --new-secondary *NODE*} {*instance*}
1212 **replace-disks** [--submit] [--early-release] {--auto}
1215 This command is a generalized form for replacing disks. It is
1216 currently only valid for the mirrored (DRBD) disk template.
1218 The first form (when passing the ``-p`` option) will replace the disks
1219 on the primary, while the second form (when passing the ``-s`` option
1220 will replace the disks on the secondary node. For these two cases (as
1221 the node doesn't change), it is possible to only run the replace for a
1222 subset of the disks, using the option ``--disks`` which takes a list
1223 of comma-delimited disk indices (zero-based), e.g. 0,2 to replace only
1224 the first and third disks.
1226 The third form (when passing either the ``--iallocator`` or the
1227 ``--new-secondary`` option) is designed to change secondary node of
1228 the instance. Specifying ``--iallocator`` makes the new secondary be
1229 selected automatically by the specified allocator plugin, otherwise
1230 the new secondary node will be the one chosen manually via the
1231 ``--new-secondary`` option.
1233 The fourth form (when using ``--auto``) will automatically determine
1234 which disks of an instance are faulty and replace them within the same
1235 node. The ``--auto`` option works only when an instance has only
1236 faulty disks on either the primary or secondary node; it doesn't work
1237 when both sides have faulty disks.
1239 The ``--submit`` option is used to send the job to the master daemon
1240 but not wait for its completion. The job ID will be shown so that it
1241 can be examined via **gnt-job info**.
1243 The ``--early-release`` changes the code so that the old storage on
1244 secondary node(s) is removed early (before the resync is completed)
1245 and the internal Ganeti locks for the current (and new, if any)
1246 secondary node are also released, thus allowing more parallelism in
1247 the cluster operation. This should be used only when recovering from a
1248 disk failure on the current secondary (thus the old storage is already
1249 broken) or when the storage on the primary node is known to be fine
1250 (thus we won't need the old storage for potential recovery).
1252 Note that it is not possible to select an offline or drained node as a
1258 **activate-disks** [--submit] [--ignore-size] {*instance*}
1260 Activates the block devices of the given instance. If successful, the
1261 command will show the location and name of the block devices::
1263 node1.example.com:disk/0:/dev/drbd0
1264 node1.example.com:disk/1:/dev/drbd1
1267 In this example, *node1.example.com* is the name of the node on which
1268 the devices have been activated. The *disk/0* and *disk/1* are the
1269 Ganeti-names of the instance disks; how they are visible inside the
1270 instance is hypervisor-specific. */dev/drbd0* and */dev/drbd1* are the
1271 actual block devices as visible on the node. The ``--submit`` option
1272 is used to send the job to the master daemon but not wait for its
1273 completion. The job ID will be shown so that it can be examined via
1276 The ``--ignore-size`` option can be used to activate disks ignoring
1277 the currently configured size in Ganeti. This can be used in cases
1278 where the configuration has gotten out of sync with the real-world
1279 (e.g. after a partially-failed grow-disk operation or due to rounding
1280 in LVM devices). This should not be used in normal cases, but only
1281 when activate-disks fails without it.
1283 Note that it is safe to run this command while the instance is already
1289 **deactivate-disks** [-f] [--submit] {*instance*}
1291 De-activates the block devices of the given instance. Note that if you
1292 run this command for an instance with a drbd disk template, while it
1293 is running, it will not be able to shutdown the block devices on the
1294 primary node, but it will shutdown the block devices on the secondary
1295 nodes, thus breaking the replication.
1297 The ``-f``/``--force`` option will skip checks that the instance is
1298 down; in case the hypervisor is confused and we can't talk to it,
1299 normally Ganeti will refuse to deactivate the disks, but with this
1300 option passed it will skip this check and directly try to deactivate
1301 the disks. This can still fail due to the instance actually running or
1304 The ``--submit`` option is used to send the job to the master daemon
1305 but not wait for its completion. The job ID will be shown so that it
1306 can be examined via **gnt-job info**.
1311 **grow-disk** [--no-wait-for-sync] [--submit] {*instance*} {*disk*}
1314 Grows an instance's disk. This is only possible for instances having a
1315 plain or drbd disk template.
1317 Note that this command only change the block device size; it will not
1318 grow the actual filesystems, partitions, etc. that live on that
1319 disk. Usually, you will need to:
1321 #. use **gnt-instance grow-disk**
1323 #. reboot the instance (later, at a convenient time)
1325 #. use a filesystem resizer, such as ext2online(8) or
1326 xfs\_growfs(8) to resize the filesystem, or use fdisk(8) to change
1327 the partition table on the disk
1329 The *disk* argument is the index of the instance disk to grow. The
1330 *amount* argument is given either as a number (and it represents the
1331 amount to increase the disk with in mebibytes) or can be given similar
1332 to the arguments in the create instance operation, with a suffix
1335 Note that the disk grow operation might complete on one node but fail
1336 on the other; this will leave the instance with different-sized LVs on
1337 the two nodes, but this will not create problems (except for unused
1340 If you do not want gnt-instance to wait for the new disk region to be
1341 synced, use the ``--no-wait-for-sync`` option.
1343 The ``--submit`` option is used to send the job to the master daemon
1344 but not wait for its completion. The job ID will be shown so that it
1345 can be examined via **gnt-job info**.
1347 Example (increase the first disk for instance1 by 16GiB)::
1349 # gnt-instance grow-disk instance1.example.com 0 16g
1352 Also note that disk shrinking is not supported; use **gnt-backup
1353 export** and then **gnt-backup import** to reduce the disk size of an
1359 **recreate-disks** [--submit] [--disks=``indices``] [-n node1:[node2]]
1362 Recreates the disks of the given instance, or only a subset of the
1363 disks (if the option ``disks`` is passed, which must be a
1364 comma-separated list of disk indices, starting from zero).
1366 Note that this functionality should only be used for missing disks; if
1367 any of the given disks already exists, the operation will fail. While
1368 this is suboptimal, recreate-disks should hopefully not be needed in
1369 normal operation and as such the impact of this is low.
1371 Optionally the instance's disks can be recreated on different
1372 nodes. This can be useful if, for example, the original nodes of the
1373 instance have gone down (and are marked offline), so we can't recreate
1374 on the same nodes. To do this, pass the new node(s) via ``-n`` option,
1375 with a syntax similar to the **add** command. The number of nodes
1376 passed must equal the number of nodes that the instance currently
1377 has. Note that changing nodes is only allowed for 'all disk'
1378 replacement (when ``--disks`` is not passed).
1380 The ``--submit`` option is used to send the job to the master daemon
1381 but not wait for its completion. The job ID will be shown so that it
1382 can be examined via **gnt-job info**.
1390 **failover** [-f] [--ignore-consistency] [--shutdown-timeout=*N*]
1391 [--submit] [--ignore-ipolicy] {*instance*}
1393 Failover will stop the instance (if running), change its primary node,
1394 and if it was originally running it will start it again (on the new
1395 primary). This only works for instances with drbd template (in which
1396 case you can only fail to the secondary node) and for externally
1397 mirrored templates (shared storage) (which can change to any other
1400 Normally the failover will check the consistency of the disks before
1401 failing over the instance. If you are trying to migrate instances off
1402 a dead node, this will fail. Use the ``--ignore-consistency`` option
1403 for this purpose. Note that this option can be dangerous as errors in
1404 shutting down the instance will be ignored, resulting in possibly
1405 having the instance running on two machines in parallel (on
1406 disconnected DRBD drives).
1408 The ``--shutdown-timeout`` is used to specify how much time to wait
1409 before forcing the shutdown (xm destroy in xen, killing the kvm
1410 process, for kvm). By default two minutes are given to each instance
1413 The ``--submit`` option is used to send the job to the master daemon
1414 but not wait for its completion. The job ID will be shown so that it
1415 can be examined via **gnt-job info**.
1417 If ``--ignore-ipolicy`` is given any instance policy violations occuring
1418 during this operation are ignored.
1422 # gnt-instance failover instance1.example.com
1428 **migrate** [-f] {--cleanup} {*instance*}
1430 **migrate** [-f] [--allow-failover] [--non-live]
1431 [--migration-mode=live\|non-live] [--ignore-ipolicy] {*instance*}
1433 Migrate will move the instance to its secondary node without
1434 shutdown. It only works for instances having the drbd8 disk template
1437 The migration command needs a perfectly healthy instance, as we rely
1438 on the dual-master capability of drbd8 and the disks of the instance
1439 are not allowed to be degraded.
1441 The ``--non-live`` and ``--migration-mode=non-live`` options will
1442 switch (for the hypervisors that support it) between a "fully live"
1443 (i.e. the interruption is as minimal as possible) migration and one in
1444 which the instance is frozen, its state saved and transported to the
1445 remote node, and then resumed there. This all depends on the
1446 hypervisor support for two different methods. In any case, it is not
1447 an error to pass this parameter (it will just be ignored if the
1448 hypervisor doesn't support it). The option ``--migration-mode=live``
1449 option will request a fully-live migration. The default, when neither
1450 option is passed, depends on the hypervisor parameters (and can be
1451 viewed with the **gnt-cluster info** command).
1453 If the ``--cleanup`` option is passed, the operation changes from
1454 migration to attempting recovery from a failed previous migration. In
1455 this mode, Ganeti checks if the instance runs on the correct node (and
1456 updates its configuration if not) and ensures the instances's disks
1457 are configured correctly. In this mode, the ``--non-live`` option is
1460 The option ``-f`` will skip the prompting for confirmation.
1462 If ``--allow-failover`` is specified it tries to fallback to failover if
1463 it already can determine that a migration won't work (e.g. if the
1464 instance is shut down). Please note that the fallback will not happen
1465 during execution. If a migration fails during execution it still fails.
1467 If ``--ignore-ipolicy`` is given any instance policy violations occuring
1468 during this operation are ignored.
1470 Example (and expected output)::
1472 # gnt-instance migrate instance1
1473 Instance instance1 will be migrated. Note that migration
1474 might impact the instance if anything goes wrong (e.g. due to bugs in
1475 the hypervisor). Continue?
1477 Migrating instance instance1.example.com
1478 * checking disk consistency between source and target
1479 * switching node node2.example.com to secondary mode
1480 * changing into standalone mode
1481 * changing disks into dual-master mode
1482 * wait until resync is done
1483 * preparing node2.example.com to accept the instance
1484 * migrating instance to node2.example.com
1485 * switching node node1.example.com to secondary mode
1486 * wait until resync is done
1487 * changing into standalone mode
1488 * changing disks into single-master mode
1489 * wait until resync is done
1497 **move** [-f] [--ignore-consistency]
1498 [-n *node*] [--shutdown-timeout=*N*] [--submit] [--ignore-ipolicy]
1501 Move will move the instance to an arbitrary node in the cluster. This
1502 works only for instances having a plain or file disk template.
1504 Note that since this operation is done via data copy, it will take a
1505 long time for big disks (similar to replace-disks for a drbd
1508 The ``--shutdown-timeout`` is used to specify how much time to wait
1509 before forcing the shutdown (e.g. ``xm destroy`` in XEN, killing the
1510 kvm process for KVM, etc.). By default two minutes are given to each
1513 The ``--ignore-consistency`` option will make Ganeti ignore any errors
1514 in trying to shutdown the instance on its node; useful if the
1515 hypervisor is broken and you want to recuperate the data.
1517 The ``--submit`` option is used to send the job to the master daemon
1518 but not wait for its completion. The job ID will be shown so that it
1519 can be examined via **gnt-job info**.
1521 If ``--ignore-ipolicy`` is given any instance policy violations occuring
1522 during this operation are ignored.
1526 # gnt-instance move -n node3.example.com instance1.example.com
1532 **change-group** [--iallocator *NAME*] [--to *GROUP*...] {*instance*}
1534 This command moves an instance to another node group. The move is
1535 calculated by an iallocator, either given on the command line or as a
1538 If no specific destination groups are specified using ``--to``, all
1539 groups except the one containing the instance are considered.
1543 # gnt-instance change-group -I hail --to rack2 inst1.example.com
1552 **add-tags** [--from *file*] {*instancename*} {*tag*...}
1554 Add tags to the given instance. If any of the tags contains invalid
1555 characters, the entire operation will abort.
1557 If the ``--from`` option is given, the list of tags will be extended
1558 with the contents of that file (each line becomes a tag). In this
1559 case, there is not need to pass tags on the command line (if you do,
1560 both sources will be used). A file name of ``-`` will be interpreted
1566 **list-tags** {*instancename*}
1568 List the tags of the given instance.
1573 **remove-tags** [--from *file*] {*instancename*} {*tag*...}
1575 Remove tags from the given instance. If any of the tags are not
1576 existing on the node, the entire operation will abort.
1578 If the ``--from`` option is given, the list of tags to be removed will
1579 be extended with the contents of that file (each line becomes a tag).
1580 In this case, there is not need to pass tags on the command line (if
1581 you do, tags from both sources will be removed). A file name of ``-``
1582 will be interpreted as stdin.
1584 .. vim: set textwidth=72 :