Synnefo » snf-ganeti » ganeti-local

    better performance. Especially if you use a network file system

    (e.g. NFS) to store your instances this is the recommended choice.

If ``--ignore-ipolicy`` is given any instance policy violations occuring

during this operation are ignored.

Example::

    # gnt-instance add -t file --disk 0:size=30g -B maxmem=512 -o debian-etch \

kvm process for KVM, etc.). By default two minutes are given to each

instance to stop.

The ``--force`` option is used to skip the interactive confirmation.

Example::

    # gnt-instance remove instance1.example.com

changes instance's state to ``down``. These modifications take effect

immediately.

If ``--ignore-ipolicy`` is given any instance policy violations occuring

during this operation are ignored.

Most of the changes take effect at the next restart. If the instance is

running, there is no effect on the instance.

or ``--all`` options), the user must pass the ``--force-multiple``

options to skip the interactive confirmation.

RENAME

^^^^^^

is used to compute the IP address, if you pass this option you must also

pass the ``--no-ip-check`` option.

Starting/stopping/connecting to console

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

that is the actual instance memory size already). Note that the values

override the instance parameters (and not extend them): an instance

with "kernel\_args=ro" when started with -H kernel\_args=single will

The ``--paused`` option is only valid for Xen and kvm hypervisors.  This

pauses the instance at the start of bootup, awaiting ``gnt-instance

console`` to unpause it, allowing the entire boot process to be

monitored for debugging.

Example::

    # gnt-instance start instance1.example.com

``--sec-node-tags`` options are similar as for the **startup** command

and they influence the actual instances being shutdown.

``--ignore-offline`` can be used to ignore offline primary nodes and

force the instance to be marked as stopped. This option should be used

with care as it can lead to an inconsistent cluster state.

``--no-remember``, and when the watcher is activated again it will

restore the correct runtime state for all instances.

Example::

    # gnt-instance shutdown instance1.example.com

The ``--force-multiple`` will skip the interactive confirmation in the

case the more than one instance will be affected.

Example::

    # gnt-instance reboot instance1.example.com

the new secondary node will be the one chosen manually via the

``--new-secondary`` option.

The fourth form (when using ``--auto``) will automatically determine

which disks of an instance are faulty and replace them within the same

node. The ``--auto`` option works only when an instance has only

faulty disks on either the primary or secondary node; it doesn't work

when both sides have faulty disks.

The ``--early-release`` changes the code so that the old storage on

secondary node(s) is removed early (before the resync is completed)

and the internal Ganeti locks for the current (and new, if any)

violations if replace-disks changes groups and the instance would

violate the new groups instance policy.

ACTIVATE-DISKS

^^^^^^^^^^^^^^

the devices have been activated. The *disk/0* and *disk/1* are the

Ganeti-names of the instance disks; how they are visible inside the

instance is hypervisor-specific. */dev/drbd0* and */dev/drbd1* are the

The ``--ignore-size`` option can be used to activate disks ignoring

the currently configured size in Ganeti. This can be used in cases

Note that it is safe to run this command while the instance is already

running.

DEACTIVATE-DISKS

^^^^^^^^^^^^^^^^

the disks. This can still fail due to the instance actually running or

other issues.

GROW-DISK

^^^^^^^^^

Grows an instance's disk. This is only possible for instances having a

plain, drbd or rbd disk template.

If you do not want gnt-instance to wait for the new disk region to be

synced, use the ``--no-wait-for-sync`` option.

Example (increase the first disk for instance1 by 16GiB)::

has. Note that changing nodes is only allowed when all disks are

replaced, e.g. when no ``--disk`` option is passed.

Recovery

~~~~~~~~

process, for kvm). By default two minutes are given to each instance

to stop.

If ``--ignore-ipolicy`` is given any instance policy violations occuring

during this operation are ignored.

Example::

    # gnt-instance failover instance1.example.com

MOVE

^^^^

Move will move the instance to an arbitrary node in the cluster.  This

works only for instances having a plain or file disk template.

in trying to shutdown the instance on its node; useful if the

hypervisor is broken and you want to recuperate the data.

If ``--ignore-ipolicy`` is given any instance policy violations occuring

during this operation are ignored.

Example::

    # gnt-instance move -n node3.example.com instance1.example.com