Synnefo » snf-ganeti

News

====

Version 2.11.0 alpha1

---------------------

*(unreleased)*

Incompatible/important changes

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

- Over luxi, syntactially incorrect queries are now rejected as a whole;

  before, a 'SumbmitManyJobs' request was partially executed, if the outer

  structure of the request was syntactically correct. As the luxi protocol

  is internal (external applications are expected to use RAPI), the impact

  of this incompatible change should be limited.

- Queries for nodes, instances, groups, backups and networks are now

  exclusively done via the luxi daemon. Legacy python code was removed,

  as well as the --enable-split-queries configuration option.

New features

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

- Instance moves, backups and imports can now use compression to transfer the

  instance data.

- Node groups can be configured to use an SSH port different than the

  default 22.

New dependencies

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

The following new dependencies have been added:

For Haskell:

- ``zlib`` library (http://hackage.haskell.org/package/base64-bytestring)

- ``base64-bytestring`` library (http://hackage.haskell.org/package/zlib)

Version 2.10.0 alpha1

---------------------

*(unreleased)*

Incompatible/important changes

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

- Adding disks with 'gnt-instance modify' now waits for the disks to sync per

  default. Specify --no-wait-for-sync to override this behavior.

- The Ganeti python code now adheres to a private-module layout. In particular,

  the module 'ganeti' is no longer in the python search path.

- On instance allocation, the iallocator now considers non-LVM storage

  properly. In particular, actual file storage space information is used

  when allocating space for a file/sharedfile instance.

- When disabling disk templates cluster-wide, the cluster now first

  checks whether there are instances still using those templates.

- 'gnt-node list-storage' now also reports storage information about

  file-based storage types.

New features

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

- KVM hypervisors can now access RBD storage directly without having to

  go through a block device.

- A new command 'gnt-cluster upgrade' was added that automates the upgrade

  procedure between two Ganeti versions that are both 2.10 or higher.

- The move-instance command can now change disk templates when moving

  instances, and does not require any node placement options to be

  specified if the destination cluster has a default iallocator.

- Users can now change the soundhw and cpuid settings for XEN hypervisors.

- Hail and hbal now have the (optional) capability of accessing average CPU

  load information through the monitoring deamon, and to use it to dynamically

  adapt the allocation of instances.

- Hotplug support. Introduce new option '--hotplug' to ``gnt-instance modify``

  so that disk and NIC modifications take effect without the need of actual

  reboot. There are a couple of constrains currently for this feature:

   - only KVM hypervisor (versions >= 1.0) supports it,

   - one can not (yet) hotplug a disk using userspace access mode for RBD

   - in case of a downgrade instances should suffer a reboot in order to

     be migratable (due to core change of runtime files)

Misc changes

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

- A new test framework for logical units was introduced and the test

  coverage for logical units was improved significantly.

- Opcodes are entirely generated from Haskell using the tool 'hs2py' and

  the module 'src/Ganeti/OpCodes.hs'.

- Constants are also generated from Haskell using the tool

  'hs2py-constants' and the module 'src/Ganeti/Constants.hs', with the

  exception of socket related constants, which require changing the

  cluster configuration file, and HVS related constants, because they

  are part of a port of instance queries to Haskell.  As a result, these

  changes will be part of the next release of Ganeti.

New dependencies

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

The following new dependencies have been added/updated.

Python

- The version requirements for ``python-mock`` have increased to at least

  version 1.0.1. It is still used for testing only.

Version 2.9.1

-------------

*(Released Wed, 13 Nov 2013)*

- fix bug, that kept nodes offline when readding

- when verifying DRBD versions, ignore unavailable nodes

- fix bug that made the console unavailable on kvm in split-user

  setup (issue 608)

- DRBD: ensure peers are UpToDate for dual-primary (inherited 2.8.2)

Version 2.9.0

-------------

*(Released Tue, 5 Nov 2013)*

Incompatible/important changes

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

- hroller now also plans for capacity to move non-redundant instances off

  any node to be rebooted; the old behavior of completely ignoring any

  non-redundant instances can be restored by adding the --ignore-non-redundant

  option.

- The cluster option '--no-lvm-storage' was removed in favor of the new option

  '--enabled-disk-templates'.

- On instance creation, disk templates no longer need to be specified

  with '-t'. The default disk template will be taken from the list of

  enabled disk templates.

- The monitoring daemon is now running as root, in order to be able to collect

  information only available to root (such as the state of Xen instances).

- The ConfD client is now IPv6 compatible.

- File and shared file storage is no longer dis/enabled at configure time,

  but using the option '--enabled-disk-templates' at cluster initialization and

  modification.

- The default directories for file and shared file storage are not anymore

  specified at configure time, but taken from the cluster's configuration.

  They can be set at cluster initialization and modification with

  '--file-storage-dir' and '--shared-file-storage-dir'.

- Cluster verification now includes stricter checks regarding the

  default file and shared file storage directories. It now checks that

  the directories are explicitely allowed in the 'file-storage-paths' file and

  that the directories exist on all nodes.

- The list of allowed disk templates in the instance policy and the list

  of cluster-wide enabled disk templates is now checked for consistency

  on cluster or group modification. On cluster initialization, the ipolicy

  disk templates are ensured to be a subset of the cluster-wide enabled

  disk templates.

New features

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

- DRBD 8.4 support. Depending on the installed DRBD version, Ganeti now uses

  the correct command syntax. It is possible to use different DRBD versions

  on different nodes as long as they are compatible to each other. This

  enables rolling upgrades of DRBD with no downtime. As permanent operation

  of different DRBD versions within a node group is discouraged,

  ``gnt-cluster verify`` will emit a warning if it detects such a situation.

- New "inst-status-xen" data collector for the monitoring daemon, providing

  information about the state of the xen instances on the nodes.

- New "lv" data collector for the monitoring daemon, collecting data about the

  logical volumes on the nodes, and pairing them with the name of the instances

  they belong to.

- New "diskstats" data collector, collecting the data from /proc/diskstats and

  presenting them over the monitoring daemon interface.

- The ConfD client is now IPv6 compatible.

New dependencies

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

The following new dependencies have been added.

Python

- ``python-mock`` (http://www.voidspace.org.uk/python/mock/) is now a required

  for the unit tests (and only used for testing).

Haskell

- ``hslogger`` (http://software.complete.org/hslogger) is now always

  required, even if confd is not enabled.

Since 2.9.0 rc3

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

- Correctly start/stop luxid during gnt-cluster master-failover (inherited

  from stable-2.8)

- Improved error messsages (inherited from stable-2.8)

Version 2.9.0 rc3

-----------------

*(Released Tue, 15 Oct 2013)*

The third release candidate in the 2.9 series. Since 2.9.0 rc2:

- in implicit configuration upgrade, match ipolicy with enabled disk templates

- improved harep documentation (inherited from stable-2.8)

Version 2.9.0 rc2

-----------------

*(Released Wed, 9 Oct 2013)*

The second release candidate in the 2.9 series. Since 2.9.0 rc1:

- Fix bug in cfgupgrade that led to failure when upgrading from 2.8 with

  at least one DRBD instance.

- Fix bug in cfgupgrade that led to an invalid 2.8 configuration after

  downgrading.

Version 2.9.0 rc1

-----------------

*(Released Tue, 1 Oct 2013)*

The first release candidate in the 2.9 series. Since 2.9.0 beta1:

- various bug fixes

- update of the documentation, in particular installation instructions

- merging of LD_* constants into DT_* constants

- python style changes to be compatible with newer versions of pylint

Version 2.9.0 beta1

-------------------

*(Released Thu, 29 Aug 2013)*

This was the first beta release of the 2.9 series. All important changes

are listed in the latest 2.9 entry.

Version 2.8.2

-------------

*(Released Thu, 07 Nov 2013)*

- DRBD: ensure peers are UpToDate for dual-primary

- Improve error message for replace-disks

- More dependency checks at configure time

- Placate warnings on ganeti.outils_unittest.py

Version 2.8.1

-------------

*(Released Thu, 17 Oct 2013)*

- Correctly start/stop luxid during gnt-cluster master-failover

- Don't attempt IPv6 ssh in case of IPv4 cluster (Issue 595)

- Fix path for the job queue serial file

- Improved harep man page

- Minor documentation improvements

Version 2.8.0

-------------

*(Released Mon, 30 Sep 2013)*

Incompatible/important changes

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

- Instance policy can contain multiple instance specs, as described in

  the “Constrained instance sizes” section of :doc:`Partitioned Ganeti

  <design-partitioned>`. As a consequence, it's not possible to partially change

  or override instance specs. Bounding specs (min and max) can be specified as a

  whole using the new option ``--ipolicy-bounds-specs``, while standard

  specs use the new option ``--ipolicy-std-specs``.

- The output of the info command of gnt-cluster, gnt-group, gnt-node,

  gnt-instance is a valid YAML object.

- hail now honors network restrictions when allocating nodes. This led to an

  update of the IAllocator protocol. See the IAllocator documentation for

  details.

- confd now only answers static configuration request over the network. luxid

  was extracted, listens on the local LUXI socket and responds to live queries.

  This allows finer grained permissions if using separate users.

New features

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

- The :doc:`Remote API <rapi>` daemon now supports a command line flag

  to always require authentication, ``--require-authentication``. It can

  be specified in ``$sysconfdir/default/ganeti``.

- A new cluster attribute 'enabled_disk_templates' is introduced. It will

  be used to manage the disk templates to be used by instances in the cluster.

  Initially, it will be set to a list that includes plain, drbd, if they were

  enabled by specifying a volume group name, and file and sharedfile, if those

  were enabled at configure time. Additionally, it will include all disk

  templates that are currently used by instances. The order of disk templates

  will be based on Ganeti's history of supporting them. In the future, the

  first entry of the list will be used as a default disk template on instance

  creation.

- ``cfgupgrade`` now supports a ``--downgrade`` option to bring the

  configuration back to the previous stable version.

- Disk templates in group ipolicy can be restored to the default value.

- Initial support for diskless instances and virtual clusters in QA.

- More QA and unit tests for instance policies.

- Every opcode now contains a reason trail (visible through ``gnt-job info``)

  describing why the opcode itself was executed.

- The monitoring daemon is now available. It allows users to query the cluster

  for obtaining information about the status of the system. The daemon is only

  responsible for providing the information over the network: the actual data

  gathering is performed by data collectors (currently, only the DRBD status

  collector is available).

- In order to help developers work on Ganeti, a new script

  (``devel/build_chroot``) is provided, for building a chroot that contains all

  the required development libraries and tools for compiling Ganeti on a Debian

  Squeeze system.

- A new tool, ``harep``, for performing self-repair and recreation of instances

  in Ganeti has been added.

- Split queries are enabled for tags, network, exports, cluster info, groups,

  jobs, nodes.

- New command ``show-ispecs-cmd`` for ``gnt-cluster`` and ``gnt-group``.

  It prints the command line to set the current policies, to ease

  changing them.

- Add the ``vnet_hdr`` HV parameter for KVM, to control whether the tap

  devices for KVM virtio-net interfaces will get created with VNET_HDR

  (IFF_VNET_HDR) support. If set to false, it disables offloading on the

  virtio-net interfaces, which prevents host kernel tainting and log

  flooding, when dealing with broken or malicious virtio-net drivers.

  It's set to true by default.

- Instance failover now supports a ``--cleanup`` parameter for fixing previous

  failures.

- Support 'viridian' parameter in Xen HVM

- Support DSA SSH keys in bootstrap

- To simplify the work of packaging frameworks that want to add the needed users

  and groups in a split-user setup themselves, at build time three files in

  ``doc/users`` will be generated. The ``groups`` files contains, one per line,

  the groups to be generated, the ``users`` file contains, one per line, the

  users to be generated, optionally followed by their primary group, where

  important. The ``groupmemberships`` file contains, one per line, additional

  user-group membership relations that need to be established. The syntax of

  these files will remain stable in all future versions.

New dependencies

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

The following new dependencies have been added:

For Haskell:

- The ``curl`` library is not optional anymore for compiling the Haskell code.

- ``snap-server`` library (if monitoring is enabled).

For Python:

- The minimum Python version needed to run Ganeti is now 2.6.

- ``yaml`` library (only for running the QA).

Since 2.8.0 rc3

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

- Perform proper cleanup on termination of Haskell daemons

- Fix corner-case in handling of remaining retry time

Version 2.8.0 rc3

-----------------

*(Released Tue, 17 Sep 2013)*

- To simplify the work of packaging frameworks that want to add the needed users

  and groups in a split-user setup themselves, at build time three files in

  ``doc/users`` will be generated. The ``groups`` files contains, one per line,

  the groups to be generated, the ``users`` file contains, one per line, the

  users to be generated, optionally followed by their primary group, where

  important. The ``groupmemberships`` file contains, one per line, additional

  user-group membership relations that need to be established. The syntax of

  these files will remain stable in all future versions.

- Add a default to file-driver when unspecified over RAPI (Issue 571)

- Mark the DSA host pubkey as optional, and remove it during config downgrade

  (Issue 560)

- Some documentation fixes

Version 2.8.0 rc2

-----------------

*(Released Tue, 27 Aug 2013)*

The second release candidate of the 2.8 series. Since 2.8.0. rc1:

- Support 'viridian' parameter in Xen HVM (Issue 233)

- Include VCS version in ``gnt-cluster version``

- Support DSA SSH keys in bootstrap (Issue 338)

- Fix batch creation of instances

- Use FQDN to check master node status (Issue 551)

- Make the DRBD collector more failure-resilient

Version 2.8.0 rc1

-----------------

*(Released Fri, 2 Aug 2013)*

The first release candidate of the 2.8 series. Since 2.8.0 beta1:

- Fix upgrading/downgrading from 2.7

- Increase maximum RAPI message size

- Documentation updates

- Split ``confd`` between ``luxid`` and ``confd``

- Merge 2.7 series up to the 2.7.1 release

- Allow the ``modify_etc_hosts`` option to be changed

- Add better debugging for ``luxid`` queries

- Expose bulk parameter for GetJobs in RAPI client

- Expose missing ``network`` fields in RAPI

- Add some ``cluster verify`` tests

- Some unittest fixes

- Fix a malfunction in ``hspace``'s tiered allocation

- Fix query compatibility between haskell and python implementations

- Add the ``vnet_hdr`` HV parameter for KVM

- Add ``--cleanup`` to instance failover

- Change the connected groups format in ``gnt-network info`` output; it

  was previously displayed as a raw list by mistake. (Merged from 2.7)

Version 2.8.0 beta1

-------------------

*(Released Mon, 24 Jun 2013)*

This was the first beta release of the 2.8 series. All important changes

are listed in the latest 2.8 entry.

Version 2.7.2

-------------

*(Released Thu, 26 Sep 2013)*

- Change the connected groups format in ``gnt-network info`` output; it

  was previously displayed as a raw list by mistake

- Check disk template in right dict when copying

- Support multi-instance allocs without iallocator

- Fix some errors in the documentation

- Fix formatting of tuple in an error message

Version 2.7.1

-------------

*(Released Thu, 25 Jul 2013)*

- Add logrotate functionality in daemon-util

- Add logrotate example file

- Add missing fields to network queries over rapi

- Fix network object timestamps

- Add support for querying network timestamps

- Fix a typo in the example crontab

- Fix a documentation typo

Version 2.7.0

-------------

*(Released Thu, 04 Jul 2013)*

Incompatible/important changes

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

- Instance policies for disk size were documented to be on a per-disk

  basis, but hail applied them to the sum of all disks. This has been

  fixed.

- ``hbal`` will now exit with status 0 if, during job execution over

  LUXI, early exit has been requested and all jobs are successful;

  before, exit status 1 was used, which cannot be differentiated from

  "job error" case

- Compatibility with newer versions of rbd has been fixed

- ``gnt-instance batch-create`` has been changed to use the bulk create

  opcode from Ganeti. This lead to incompatible changes in the format of

  the JSON file. It's now not a custom dict anymore but a dict

  compatible with the ``OpInstanceCreate`` opcode.

- Parent directories for file storage need to be listed in

  ``$sysconfdir/ganeti/file-storage-paths`` now. ``cfgupgrade`` will

  write the file automatically based on old configuration values, but it

  can not distribute it across all nodes and the file contents should be

  verified. Use ``gnt-cluster copyfile

  $sysconfdir/ganeti/file-storage-paths`` once the cluster has been

  upgraded. The reason for requiring this list of paths now is that

  before it would have been possible to inject new paths via RPC,

  allowing files to be created in arbitrary locations. The RPC protocol

  is protected using SSL/X.509 certificates, but as a design principle

  Ganeti does not permit arbitrary paths to be passed.

- The parsing of the variants file for OSes (see

  :manpage:`ganeti-os-interface(7)`) has been slightly changed: now empty

  lines and comment lines (starting with ``#``) are ignored for better

  readability.

- The ``setup-ssh`` tool added in Ganeti 2.2 has been replaced and is no

  longer available. ``gnt-node add`` now invokes a new tool on the

  destination node, named ``prepare-node-join``, to configure the SSH

  daemon. Paramiko is no longer necessary to configure nodes' SSH

  daemons via ``gnt-node add``.

- Draining (``gnt-cluster queue drain``) and un-draining the job queue

  (``gnt-cluster queue undrain``) now affects all nodes in a cluster and

  the flag is not reset after a master failover.

- Python 2.4 has *not* been tested with this release. Using 2.6 or above

  is recommended. 2.6 will be mandatory from the 2.8 series.

New features

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

- New network management functionality to support automatic allocation

  of IP addresses and managing of network parameters. See

  :manpage:`gnt-network(8)` for more details.

- New external storage backend, to allow managing arbitrary storage

  systems external to the cluster. See

  :manpage:`ganeti-extstorage-interface(7)`.

- New ``exclusive-storage`` node parameter added, restricted to

  nodegroup level. When it's set to true, physical disks are assigned in

  an exclusive fashion to instances, as documented in :doc:`Partitioned

  Ganeti <design-partitioned>`.  Currently, only instances using the

  ``plain`` disk template are supported.

- The KVM hypervisor has been updated with many new hypervisor

  parameters, including a generic one for passing arbitrary command line

  values. See a complete list in :manpage:`gnt-instance(8)`. It is now

  compatible up to qemu 1.4.

- A new tool, called ``mon-collector``, is the stand-alone executor of

  the data collectors for a monitoring system. As of this version, it

  just includes the DRBD data collector, that can be executed by calling

  ``mon-collector`` using the ``drbd`` parameter. See

  :manpage:`mon-collector(7)`.

- A new user option, :pyeval:`rapi.RAPI_ACCESS_READ`, has been added

  for RAPI users. It allows granting permissions to query for

  information to a specific user without giving

  :pyeval:`rapi.RAPI_ACCESS_WRITE` permissions.

- A new tool named ``node-cleanup`` has been added. It cleans remains of

  a cluster from a machine by stopping all daemons, removing

  certificates and ssconf files. Unless the ``--no-backup`` option is

  given, copies of the certificates are made.

- Instance creations now support the use of opportunistic locking,

  potentially speeding up the (parallel) creation of multiple instances.

  This feature is currently only available via the :doc:`RAPI

  <rapi>` interface and when an instance allocator is used. If the

  ``opportunistic_locking`` parameter is set the opcode will try to

  acquire as many locks as possible, but will not wait for any locks

  held by other opcodes. If not enough resources can be found to

  allocate the instance, the temporary error code

  :pyeval:`errors.ECODE_TEMP_NORES` is returned. The operation can be

  retried thereafter, with or without opportunistic locking.

- New experimental linux-ha resource scripts.

- Restricted-commands support: ganeti can now be asked (via command line

  or rapi) to perform commands on a node. These are passed via ganeti

  RPC rather than ssh. This functionality is restricted to commands

  specified on the ``$sysconfdir/ganeti/restricted-commands`` for security

  reasons. The file is not copied automatically.

Misc changes

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

- Diskless instances are now externally mirrored (Issue 237). This for

  now has only been tested in conjunction with explicit target nodes for

  migration/failover.

- Queries not needing locks or RPC access to the node can now be

  performed by the confd daemon, making them independent from jobs, and

  thus faster to execute. This is selectable at configure time.

- The functionality for allocating multiple instances at once has been

  overhauled and is now also available through :doc:`RAPI <rapi>`.

There are no significant changes from version 2.7.0~rc3.

Version 2.7.0 rc3

-----------------

*(Released Tue, 25 Jun 2013)*

- Fix permissions on the confd query socket (Issue 477)

- Fix permissions on the job archive dir (Issue 498)

- Fix handling of an internal exception in replace-disks (Issue 472)

- Fix gnt-node info handling of shortened names (Issue 497)

- Fix gnt-instance grow-disk when wiping is enabled

- Documentation improvements, and support for newer pandoc

- Fix hspace honoring ipolicy for disks (Issue 484)

- Improve handling of the ``kvm_extra`` HV parameter

Version 2.7.0 rc2

-----------------

*(Released Fri, 24 May 2013)*

- ``devel/upload`` now works when ``/var/run`` on the target nodes is a

  symlink.

- Disks added through ``gnt-instance modify`` or created through

  ``gnt-instance recreate-disks`` are wiped, if the

  ``prealloc_wipe_disks`` flag is set.

- If wiping newly created disks fails, the disks are removed. Also,

  partial failures in creating disks through ``gnt-instance modify``

  triggers a cleanup of the partially-created disks.

- Removing the master IP address doesn't fail if the address has been

  already removed.

- Fix ownership of the OS log dir

- Workaround missing SO_PEERCRED constant (Issue 191)

Version 2.7.0 rc1

-----------------

*(Released Fri, 3 May 2013)*

This was the first release candidate of the 2.7 series. Since beta3:

- Fix kvm compatibility with qemu 1.4 (Issue 389)

- Documentation updates (admin guide, upgrade notes, install

  instructions) (Issue 372)

- Fix gnt-group list nodes and instances count (Issue 436)

- Fix compilation without non-mandatory libraries (Issue 441)

- Fix xen-hvm hypervisor forcing nics to type 'ioemu' (Issue 247)

- Make confd logging more verbose at INFO level (Issue 435)

- Improve "networks" documentation in :manpage:`gnt-instance(8)`

- Fix failure path for instance storage type conversion (Issue 229)

- Update htools text backend documentation

- Improve the renew-crypto section of :manpage:`gnt-cluster(8)`

- Disable inter-cluster instance move for file-based instances, because

  it is dependant on instance export, which is not supported for

  file-based instances. (Issue 414)

- Fix gnt-job crashes on non-ascii characters (Issue 427)

- Fix volume group checks on non-vm-capable nodes (Issue 432)

Version 2.7.0 beta3

-------------------

*(Released Mon, 22 Apr 2013)*

This was the third beta release of the 2.7 series. Since beta2:

- Fix hail to verify disk instance policies on a per-disk basis (Issue 418).

- Fix data loss on wrong usage of ``gnt-instance move``

- Properly export errors in confd-based job queries

- Add ``users-setup`` tool

- Fix iallocator protocol to report 0 as a disk size for diskless

  instances. This avoids hail breaking when a diskless instance is

  present.

- Fix job queue directory permission problem that made confd job queries

  fail. This requires running an ``ensure-dirs --full-run`` on upgrade

  for access to archived jobs (Issue 406).

- Limit the sizes of networks supported by ``gnt-network`` to something

  between a ``/16`` and a ``/30`` to prevent memory bloat and crashes.

- Fix bugs in instance disk template conversion

- Fix GHC 7 compatibility

- Fix ``burnin`` install path (Issue 426).

- Allow very small disk grows (Issue 347).

- Fix a ``ganeti-noded`` memory bloat introduced in 2.5, by making sure

  that noded doesn't import masterd code (Issue 419).

- Make sure the default metavg at cluster init is the same as the vg, if

  unspecified (Issue 358).

- Fix cleanup of partially created disks (part of Issue 416)

Version 2.7.0 beta2

-------------------

*(Released Tue, 2 Apr 2013)*

This was the second beta release of the 2.7 series. Since beta1:

- Networks no longer have a "type" slot, since this information was

  unused in Ganeti: instead of it tags should be used.

- The rapi client now has a ``target_node`` option to MigrateInstance.

- Fix early exit return code for hbal (Issue 386).

- Fix ``gnt-instance migrate/failover -n`` (Issue 396).

- Fix ``rbd showmapped`` output parsing (Issue 312).

- Networks are now referenced indexed by UUID, rather than name. This

  will require running cfgupgrade, from 2.7.0beta1, if networks are in

  use.

- The OS environment now includes network information.

- Deleting of a network is now disallowed if any instance nic is using

  it, to prevent dangling references.

- External storage is now documented in man pages.

- The exclusive_storage flag can now only be set at nodegroup level.

- Hbal can now submit an explicit priority with its jobs.

- Many network related locking fixes.

- Bump up the required pylint version to 0.25.1.

- Fix the ``no_remember`` option in RAPI client.

- Many ipolicy related tests, qa, and fixes.

- Many documentation improvements and fixes.

- Fix building with ``--disable-file-storage``.

- Fix ``-q`` option in htools, which was broken if passed more than

  once.

- Some haskell/python interaction improvements and fixes.

- Fix iallocator in case of missing LVM storage.

- Fix confd config load in case of ``--no-lvm-storage``.

- The confd/query functionality is now mentioned in the security

  documentation.

Version 2.7.0 beta1

-------------------

*(Released Wed, 6 Feb 2013)*

This was the first beta release of the 2.7 series. All important changes

are listed in the latest 2.7 entry.

Version 2.6.2

-------------

*(Released Fri, 21 Dec 2012)*

Important behaviour change: hbal won't rebalance anymore instances which

have the ``auto_balance`` attribute set to false. This was the intention

all along, but until now it only skipped those from the N+1 memory

reservation (DRBD-specific).

A significant number of bug fixes in this release:

- Fixed disk adoption interaction with ipolicy checks.

- Fixed networking issues when instances are started, stopped or

  migrated, by forcing the tap device's MAC prefix to "fe" (issue 217).

- Fixed the warning in cluster verify for shared storage instances not

  being redundant.

- Fixed removal of storage directory on shared file storage (issue 262).

- Fixed validation of LVM volume group name in OpClusterSetParams

  (``gnt-cluster modify``) (issue 285).

- Fixed runtime memory increases (``gnt-instance modify -m``).

- Fixed live migration under Xen's ``xl`` mode.

- Fixed ``gnt-instance console`` with ``xl``.

- Fixed building with newer Haskell compiler/libraries.

- Fixed PID file writing in Haskell daemons (confd); this prevents

  restart issues if confd was launched manually (outside of

  ``daemon-util``) while another copy of it was running

- Fixed a type error when doing live migrations with KVM (issue 297) and

  the error messages for failing migrations have been improved.

- Fixed opcode validation for the out-of-band commands (``gnt-node

  power``).

- Fixed a type error when unsetting OS hypervisor parameters (issue

  311); now it's possible to unset all OS-specific hypervisor

  parameters.

- Fixed the ``dry-run`` mode for many operations: verification of

  results was over-zealous but didn't take into account the ``dry-run``

  operation, resulting in "wrong" failures.

- Fixed bash completion in ``gnt-job list`` when the job queue has

  hundreds of entries; especially with older ``bash`` versions, this

  results in significant CPU usage.

And lastly, a few other improvements have been made:

- Added option to force master-failover without voting (issue 282).

- Clarified error message on lock conflict (issue 287).

- Logging of newly submitted jobs has been improved (issue 290).

- Hostname checks have been made uniform between instance rename and

  create (issue 291).

- The ``--submit`` option is now supported by ``gnt-debug delay``.

- Shutting down the master daemon by sending SIGTERM now stops it from

  processing jobs waiting for locks; instead, those jobs will be started

  once again after the master daemon is started the next time (issue

  296).

- Support for Xen's ``xl`` program has been improved (besides the fixes

  above).

- Reduced logging noise in the Haskell confd daemon (only show one log

  entry for each config reload, instead of two).

- Several man page updates and typo fixes.

Version 2.6.1

-------------

*(Released Fri, 12 Oct 2012)*

A small bugfix release. Among the bugs fixed:

- Fixed double use of ``PRIORITY_OPT`` in ``gnt-node migrate``, that

  made the command unusable.

- Commands that issue many jobs don't fail anymore just because some jobs

  take so long that other jobs are archived.

- Failures during ``gnt-instance reinstall`` are reflected by the exit

  status.

- Issue 190 fixed. Check for DRBD in cluster verify is enabled only when

  DRBD is enabled.

- When ``always_failover`` is set, ``--allow-failover`` is not required

  in migrate commands anymore.

- ``bash_completion`` works even if extglob is disabled.

- Fixed bug with locks that made failover for RDB-based instances fail.

- Fixed bug in non-mirrored instance allocation that made Ganeti choose

  a random node instead of one based on the allocator metric.

- Support for newer versions of pylint and pep8.

- Hail doesn't fail anymore when trying to add an instance of type

  ``file``, ``sharedfile`` or ``rbd``.

- Added new Makefile target to rebuild the whole distribution, so that

  all files are included.

Version 2.6.0

-------------

*(Released Fri, 27 Jul 2012)*

.. attention:: The ``LUXI`` protocol has been made more consistent

   regarding its handling of command arguments. This, however, leads to

   incompatibility issues with previous versions. Please ensure that you

   restart Ganeti daemons soon after the upgrade, otherwise most

   ``LUXI`` calls (job submission, setting/resetting the drain flag,

   pausing/resuming the watcher, cancelling and archiving jobs, querying

   the cluster configuration) will fail.

New features

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

Instance run status

+++++++++++++++++++

The current ``admin_up`` field, which used to denote whether an instance

should be running or not, has been removed. Instead, ``admin_state`` is

introduced, with 3 possible values -- ``up``, ``down`` and ``offline``.

The rational behind this is that an instance being “down” can have

different meanings:

- it could be down during a reboot

- it could be temporarily be down for a reinstall

- or it could be down because it is deprecated and kept just for its

  disk

The previous Boolean state was making it difficult to do capacity

calculations: should Ganeti reserve memory for a down instance? Now, the

tri-state field makes it clear:

- in ``up`` and ``down`` state, all resources are reserved for the

  instance, and it can be at any time brought up if it is down

- in ``offline`` state, only disk space is reserved for it, but not

  memory or CPUs

The field can have an extra use: since the transition between ``up`` and

``down`` and vice-versus is done via ``gnt-instance start/stop``, but

transition between ``offline`` and ``down`` is done via ``gnt-instance

modify``, it is possible to given different rights to users. For

example, owners of an instance could be allowed to start/stop it, but

not transition it out of the offline state.

Instance policies and specs

+++++++++++++++++++++++++++

In previous Ganeti versions, an instance creation request was not

limited on the minimum size and on the maximum size just by the cluster

resources. As such, any policy could be implemented only in third-party

clients (RAPI clients, or shell wrappers over ``gnt-*``

tools). Furthermore, calculating cluster capacity via ``hspace`` again

required external input with regards to instance sizes.

In order to improve these workflows and to allow for example better

per-node group differentiation, we introduced instance specs, which

allow declaring:

- minimum instance disk size, disk count, memory size, cpu count

- maximum values for the above metrics

- and “standard” values (used in ``hspace`` to calculate the standard

  sized instances)

The minimum/maximum values can be also customised at node-group level,

for example allowing more powerful hardware to support bigger instance

memory sizes.

Beside the instance specs, there are a few other settings belonging to

the instance policy framework. It is possible now to customise, per

cluster and node-group:

- the list of allowed disk templates

- the maximum ratio of VCPUs per PCPUs (to control CPU oversubscription)

- the maximum ratio of instance to spindles (see below for more

  information) for local storage

All these together should allow all tools that talk to Ganeti to know

what are the ranges of allowed values for instances and the

over-subscription that is allowed.

For the VCPU/PCPU ratio, we already have the VCPU configuration from the

instance configuration, and the physical CPU configuration from the

node. For the spindle ratios however, we didn't track before these

values, so new parameters have been added:

- a new node parameter ``spindle_count``, defaults to 1, customisable at

  node group or node level

- at new backend parameter (for instances), ``spindle_use`` defaults to 1

Note that spindles in this context doesn't need to mean actual

mechanical hard-drives; it's just a relative number for both the node

I/O capacity and instance I/O consumption.

Instance migration behaviour

++++++++++++++++++++++++++++

While live-migration is in general desirable over failover, it is

possible that for some workloads it is actually worse, due to the

variable time of the “suspend” phase during live migration.

To allow the tools to work consistently over such instances (without

having to hard-code instance names), a new backend parameter

``always_failover`` has been added to control the migration/failover

behaviour. When set to True, all migration requests for an instance will

instead fall-back to failover.

Instance memory ballooning

++++++++++++++++++++++++++

Initial support for memory ballooning has been added. The memory for an

instance is no longer fixed (backend parameter ``memory``), but instead

can vary between minimum and maximum values (backend parameters

``minmem`` and ``maxmem``). Currently we only change an instance's

memory when:

- live migrating or failing over and instance and the target node

  doesn't have enough memory

- user requests changing the memory via ``gnt-instance modify

  --runtime-memory``

Instance CPU pinning

++++++++++++++++++++

In order to control the use of specific CPUs by instance, support for

controlling CPU pinning has been added for the Xen, HVM and LXC

hypervisors. This is controlled by a new hypervisor parameter

``cpu_mask``; details about possible values for this are in the

:manpage:`gnt-instance(8)`. Note that use of the most specific (precise

VCPU-to-CPU mapping) form will work well only when all nodes in your

cluster have the same amount of CPUs.

Disk parameters

+++++++++++++++

Another area in which Ganeti was not customisable were the parameters

used for storage configuration, e.g. how many stripes to use for LVM,

DRBD resync configuration, etc.

To improve this area, we've added disks parameters, which are

customisable at cluster and node group level, and which allow to

specify various parameters for disks (DRBD has the most parameters

currently), for example:

- DRBD resync algorithm and parameters (e.g. speed)

- the default VG for meta-data volumes for DRBD

- number of stripes for LVM (plain disk template)

- the RBD pool

These parameters can be modified via ``gnt-cluster modify -D …`` and

``gnt-group modify -D …``, and are used at either instance creation (in

case of LVM stripes, for example) or at disk “activation” time

(e.g. resync speed).

Rados block device support

++++++++++++++++++++++++++

A Rados (http://ceph.com/wiki/Rbd) storage backend has been added,

denoted by the ``rbd`` disk template type. This is considered

experimental, feedback is welcome. For details on configuring it, see

the :doc:`install` document and the :manpage:`gnt-cluster(8)` man page.

Master IP setup

+++++++++++++++

The existing master IP functionality works well only in simple setups (a

single network shared by all nodes); however, if nodes belong to

different networks, then the ``/32`` setup and lack of routing

information is not enough.

To allow the master IP to function well in more complex cases, the

system was reworked as follows:

- a master IP netmask setting has been added

- the master IP activation/turn-down code was moved from the node daemon

  to a separate script

- whether to run the Ganeti-supplied master IP script or a user-supplied

  on is a ``gnt-cluster init`` setting

Details about the location of the standard and custom setup scripts are

in the man page :manpage:`gnt-cluster(8)`; for information about the

setup script protocol, look at the Ganeti-supplied script.

SPICE support

+++++++++++++

The `SPICE <http://www.linux-kvm.org/page/SPICE>`_ support has been

improved.

It is now possible to use TLS-protected connections, and when renewing

or changing the cluster certificates (via ``gnt-cluster renew-crypto``,

it is now possible to specify spice or spice CA certificates. Also, it

is possible to configure a password for SPICE sessions via the

hypervisor parameter ``spice_password_file``.

There are also new parameters to control the compression and streaming

options (e.g. ``spice_image_compression``, ``spice_streaming_video``,

etc.). For details, see the man page :manpage:`gnt-instance(8)` and look

for the spice parameters.

Lastly, it is now possible to see the SPICE connection information via

``gnt-instance console``.

OVF converter

+++++++++++++

A new tool (``tools/ovfconverter``) has been added that supports

conversion between Ganeti and the `Open Virtualization Format

<http://en.wikipedia.org/wiki/Open_Virtualization_Format>`_ (both to and

from).

This relies on the ``qemu-img`` tool to convert the disk formats, so the

actual compatibility with other virtualization solutions depends on it.

Confd daemon changes

++++++++++++++++++++

The configuration query daemon (``ganeti-confd``) is now optional, and

has been rewritten in Haskell; whether to use the daemon at all, use the

Python (default) or the Haskell version is selectable at configure time

via the ``--enable-confd`` parameter, which can take one of the

``haskell``, ``python`` or ``no`` values. If not used, disabling the

daemon will result in a smaller footprint; for larger systems, we

welcome feedback on the Haskell version which might become the default

in future versions.

If you want to use ``gnt-node list-drbd`` you need to have the Haskell

daemon running. The Python version doesn't implement the new call.

User interface changes

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

We have replaced the ``--disks`` option of ``gnt-instance

replace-disks`` with a more flexible ``--disk`` option, which allows

adding and removing disks at arbitrary indices (Issue 188). Furthermore,

disk size and mode can be changed upon recreation (via ``gnt-instance

recreate-disks``, which accepts the same ``--disk`` option).

As many people are used to a ``show`` command, we have added that as an

alias to ``info`` on all ``gnt-*`` commands.

The ``gnt-instance grow-disk`` command has a new mode in which it can

accept the target size of the disk, instead of the delta; this can be

more safe since two runs in absolute mode will be idempotent, and

sometimes it's also easier to specify the desired size directly.

Also the handling of instances with regard to offline secondaries has

been improved. Instance operations should not fail because one of it's

secondary nodes is offline, even though it's safe to proceed.

A new command ``list-drbd`` has been added to the ``gnt-node`` script to

support debugging of DRBD issues on nodes. It provides a mapping of DRBD

minors to instance name.

API changes

~~~~~~~~~~~

RAPI coverage has improved, with (for example) new resources for

recreate-disks, node power-cycle, etc.

Compatibility

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

There is partial support for ``xl`` in the Xen hypervisor; feedback is

welcome.

Python 2.7 is better supported, and after Ganeti 2.6 we will investigate

whether to still support Python 2.4 or move to Python 2.6 as minimum

required version.

Support for Fedora has been slightly improved; the provided example

init.d script should work better on it and the INSTALL file should

document the needed dependencies.

Internal changes

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

The deprecated ``QueryLocks`` LUXI request has been removed. Use

``Query(what=QR_LOCK, ...)`` instead.

The LUXI requests :pyeval:`luxi.REQ_QUERY_JOBS`,

:pyeval:`luxi.REQ_QUERY_INSTANCES`, :pyeval:`luxi.REQ_QUERY_NODES`,

:pyeval:`luxi.REQ_QUERY_GROUPS`, :pyeval:`luxi.REQ_QUERY_EXPORTS` and

:pyeval:`luxi.REQ_QUERY_TAGS` are deprecated and will be removed in a

future version. :pyeval:`luxi.REQ_QUERY` should be used instead.

RAPI client: ``CertificateError`` now derives from

``GanetiApiError``. This should make it more easy to handle Ganeti

errors.

Deprecation warnings due to PyCrypto/paramiko import in

``tools/setup-ssh`` have been silenced, as usually they are safe; please

make sure to run an up-to-date paramiko version, if you use this tool.

The QA scripts now depend on Python 2.5 or above (the main code base

still works with Python 2.4).

The configuration file (``config.data``) is now written without

indentation for performance reasons; if you want to edit it, it can be

re-formatted via ``tools/fmtjson``.

A number of bugs has been fixed in the cluster merge tool.

``x509`` certification verification (used in import-export) has been

changed to allow the same clock skew as permitted by the cluster

verification. This will remove some rare but hard to diagnose errors in

import-export.

Version 2.6.0 rc4

-----------------

*(Released Thu, 19 Jul 2012)*

Very few changes from rc4 to the final release, only bugfixes:

- integrated fixes from release 2.5.2 (fix general boot flag for KVM

  instance, fix CDROM booting for KVM instances)

- fixed node group modification of node parameters

- fixed issue in LUClusterVerifyGroup with multi-group clusters

- fixed generation of bash completion to ensure a stable ordering

- fixed a few typos

Version 2.6.0 rc3

-----------------

*(Released Fri, 13 Jul 2012)*

Third release candidate for 2.6. The following changes were done from

rc3 to rc4:

- Fixed ``UpgradeConfig`` w.r.t. to disk parameters on disk objects.

- Fixed an inconsistency in the LUXI protocol with the provided

  arguments (NOT backwards compatible)

- Fixed a bug with node groups ipolicy where ``min`` was greater than

  the cluster ``std`` value

- Implemented a new ``gnt-node list-drbd`` call to list DRBD minors for

  easier instance debugging on nodes (requires ``hconfd`` to work)

Version 2.6.0 rc2

-----------------

*(Released Tue, 03 Jul 2012)*

Second release candidate for 2.6. The following changes were done from

rc2 to rc3:

- Fixed ``gnt-cluster verify`` regarding ``master-ip-script`` on non

  master candidates

- Fixed a RAPI regression on missing beparams/memory

- Fixed redistribution of files on offline nodes

- Added possibility to run activate-disks even though secondaries are

  offline. With this change it relaxes also the strictness on some other

  commands which use activate disks internally:

  * ``gnt-instance start|reboot|rename|backup|export``

- Made it possible to remove safely an instance if its secondaries are

  offline

- Made it possible to reinstall even though secondaries are offline

Version 2.6.0 rc1

-----------------

*(Released Mon, 25 Jun 2012)*

First release candidate for 2.6. The following changes were done from

rc1 to rc2:

- Fixed bugs with disk parameters and ``rbd`` templates as well as

  ``instance_os_add``

- Made ``gnt-instance modify`` more consistent regarding new NIC/Disk

  behaviour. It supports now the modify operation

- ``hcheck`` implemented to analyze cluster health and possibility of

  improving health by rebalance

- ``hbal`` has been improved in dealing with split instances

Version 2.6.0 beta2

-------------------

*(Released Mon, 11 Jun 2012)*

Second beta release of 2.6. The following changes were done from beta2

to rc1:

- Fixed ``daemon-util`` with non-root user models

- Fixed creation of plain instances with ``--no-wait-for-sync``

- Fix wrong iv_names when running ``cfgupgrade``

- Export more information in RAPI group queries

- Fixed bug when changing instance network interfaces

- Extended burnin to do NIC changes

- query: Added ``<``, ``>``, ``<=``, ``>=`` comparison operators

- Changed default for DRBD barriers

- Fixed DRBD error reporting for syncer rate

- Verify the options on disk parameters

And of course various fixes to documentation and improved unittests and

QA.

Version 2.6.0 beta1

-------------------

*(Released Wed, 23 May 2012)*

First beta release of 2.6. The following changes were done from beta1 to

beta2:

- integrated patch for distributions without ``start-stop-daemon``

- adapted example init.d script to work on Fedora

- fixed log handling in Haskell daemons

- adapted checks in the watcher for pycurl linked against libnss

- add partial support for ``xl`` instead of ``xm`` for Xen

- fixed a type issue in cluster verification

- fixed ssconf handling in the Haskell code (was breaking confd in IPv6

  clusters)

Plus integrated fixes from the 2.5 branch:

- fixed ``kvm-ifup`` to use ``/bin/bash``

- fixed parallel build failures

- KVM live migration when using a custom keymap

Version 2.5.2

-------------

*(Released Tue, 24 Jul 2012)*

A small bugfix release, with no new features:

- fixed bash-isms in kvm-ifup, for compatibility with systems which use a

  different default shell (e.g. Debian, Ubuntu)

- fixed KVM startup and live migration with a custom keymap (fixes Issue

  243 and Debian bug #650664)

- fixed compatibility with KVM versions that don't support multiple boot

  devices (fixes Issue 230 and Debian bug #624256)

Additionally, a few fixes were done to the build system (fixed parallel

build failures) and to the unittests (fixed race condition in test for

FileID functions, and the default enable/disable mode for QA test is now

customisable).

Version 2.5.1

-------------

*(Released Fri, 11 May 2012)*

A small bugfix release.

The main issues solved are on the topic of compatibility with newer LVM

releases:

- fixed parsing of ``lv_attr`` field

- adapted to new ``vgreduce --removemissing`` behaviour where sometimes

  the ``--force`` flag is needed

Also on the topic of compatibility, ``tools/lvmstrap`` has been changed

to accept kernel 3.x too (was hardcoded to 2.6.*).

A regression present in 2.5.0 that broke handling (in the gnt-* scripts)

of hook results and that also made display of other errors suboptimal

was fixed; the code behaves now like 2.4 and earlier.

Another change in 2.5, the cleanup of the OS scripts environment, is too

aggressive: it removed even the ``PATH`` variable, which requires the OS

scripts to *always* need to export it. Since this is a bit too strict,

we now export a minimal PATH, the same that we export for hooks.

The fix for issue 201 (Preserve bridge MTU in KVM ifup script) was

integrated into this release.

Finally, a few other miscellaneous changes were done (no new features,

just small improvements):

- Fix ``gnt-group --help`` display

- Fix hardcoded Xen kernel path

- Fix grow-disk handling of invalid units

- Update synopsis for ``gnt-cluster repair-disk-sizes``

- Accept both PUT and POST in noded (makes future upgrade to 2.6 easier)

Version 2.5.0

-------------

*(Released Thu, 12 Apr 2012)*

Incompatible/important changes and bugfixes

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

- The default of the ``/2/instances/[instance_name]/rename`` RAPI

  resource's ``ip_check`` parameter changed from ``True`` to ``False``

  to match the underlying LUXI interface.

- The ``/2/nodes/[node_name]/evacuate`` RAPI resource was changed to use

  body parameters, see :doc:`RAPI documentation <rapi>`. The server does

  not maintain backwards-compatibility as the underlying operation

  changed in an incompatible way. The RAPI client can talk to old

  servers, but it needs to be told so as the return value changed.

- When creating file-based instances via RAPI, the ``file_driver``

  parameter no longer defaults to ``loop`` and must be specified.

- The deprecated ``bridge`` NIC parameter is no longer supported. Use

  ``link`` instead.

- Support for the undocumented and deprecated RAPI instance creation

  request format version 0 has been dropped. Use version 1, supported

  since Ganeti 2.1.3 and :doc:`documented <rapi>`, instead.

- Pyparsing 1.4.6 or above is required, see :doc:`installation

  documentation <install>`.

- The "cluster-verify" hooks are now executed per group by the

  ``OP_CLUSTER_VERIFY_GROUP`` opcode. This maintains the same behavior

  if you just run ``gnt-cluster verify``, which generates one opcode per

  group.

- The environment as passed to the OS scripts is cleared, and thus no

  environment variables defined in the node daemon's environment will be

  inherited by the scripts.

- The :doc:`iallocator <iallocator>` mode ``multi-evacuate`` has been

  deprecated.

- :doc:`New iallocator modes <design-multi-reloc>` have been added to

  support operations involving multiple node groups.

- Offline nodes are ignored when failing over an instance.

- Support for KVM version 1.0, which changed the version reporting format

  from 3 to 2 digits.

- TCP/IP ports used by DRBD disks are returned to a pool upon instance

  removal.

- ``Makefile`` is now compatible with Automake 1.11.2

- Includes all bugfixes made in the 2.4 series

New features

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

- The ganeti-htools project has been merged into the ganeti-core source

  tree and will be built as part of Ganeti (see :doc:`install-quick`).

- Implemented support for :doc:`shared storage <design-shared-storage>`.

- Add support for disks larger than 2 TB in ``lvmstrap`` by supporting

  GPT-style partition tables (requires `parted

  <http://www.gnu.org/s/parted/>`_).

- Added support for floppy drive and 2nd CD-ROM drive in KVM hypervisor.

- Allowed adding tags on instance creation.

- Export instance tags to hooks (``INSTANCE_TAGS``, see :doc:`hooks`)

- Allow instances to be started in a paused state, enabling the user to

  see the complete console output on boot using the console.

- Added new hypervisor flag to control default reboot behaviour

  (``reboot_behavior``).

- Added support for KVM keymaps (hypervisor parameter ``keymap``).

- Improved out-of-band management support:

  - Added ``gnt-node health`` command reporting the health status of

    nodes.

  - Added ``gnt-node power`` command to manage power status of nodes.

  - Added command for emergency power-off (EPO), ``gnt-cluster epo``.

- Instance migration can fall back to failover if instance is not

  running.

- Filters can be used when listing nodes, instances, groups and locks;

  see :manpage:`ganeti(7)` manpage.

- Added post-execution status as variables to :doc:`hooks <hooks>`

  environment.

- Instance tags are exported/imported together with the instance.

- When given an explicit job ID, ``gnt-job info`` will work for archived

  jobs.

- Jobs can define dependencies on other jobs (not yet supported via

  RAPI or command line, but used by internal commands and usable via

  LUXI).

  - Lock monitor (``gnt-debug locks``) shows jobs waiting for

    dependencies.

- Instance failover is now available as a RAPI resource

  (``/2/instances/[instance_name]/failover``).

- ``gnt-instance info`` defaults to static information if primary node

  is offline.

- Opcodes have a new ``comment`` attribute.

- Added basic SPICE support to KVM hypervisor.

- ``tools/ganeti-listrunner`` allows passing of arguments to executable.

Node group improvements

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

- ``gnt-cluster verify`` has been modified to check groups separately,

  thereby improving performance.

- Node group support has been added to ``gnt-cluster verify-disks``,

  which now operates per node group.

- Watcher has been changed to work better with node groups.

  - One process and state file per node group.

  - Slow watcher in one group doesn't block other group's watcher.

- Added new command, ``gnt-group evacuate``, to move all instances in a

  node group to other groups.

- Added ``gnt-instance change-group`` to move an instance to another

  node group.

- ``gnt-cluster command`` and ``gnt-cluster copyfile`` now support

  per-group operations.

- Node groups can be tagged.

- Some operations switch from an exclusive to a shared lock as soon as

  possible.

- Instance's primary and secondary nodes' groups are now available as

  query fields (``pnode.group``, ``pnode.group.uuid``, ``snodes.group``

  and ``snodes.group.uuid``).

Misc

~~~~

- Numerous updates to documentation and manpages.

  - :doc:`RAPI <rapi>` documentation now has detailed parameter

    descriptions.

  - Some opcode/job results are now also documented, see :doc:`RAPI

    <rapi>`.

- A lockset's internal lock is now also visible in lock monitor.

- Log messages from job queue workers now contain information about the

  opcode they're processing.

- ``gnt-instance console`` no longer requires the instance lock.

- A short delay when waiting for job changes reduces the number of LUXI

  requests significantly.

- DRBD metadata volumes are overwritten with zeros during disk creation.

- Out-of-band commands no longer acquire the cluster lock in exclusive

  mode.

- ``devel/upload`` now uses correct permissions for directories.

Version 2.5.0 rc6

-----------------

*(Released Fri, 23 Mar 2012)*

This was the sixth release candidate of the 2.5 series.

Version 2.5.0 rc5

-----------------

*(Released Mon, 9 Jan 2012)*

This was the fifth release candidate of the 2.5 series.

Version 2.5.0 rc4

-----------------

*(Released Thu, 27 Oct 2011)*

This was the fourth release candidate of the 2.5 series.

Version 2.5.0 rc3

-----------------

*(Released Wed, 26 Oct 2011)*

This was the third release candidate of the 2.5 series.

Version 2.5.0 rc2

-----------------

*(Released Tue, 18 Oct 2011)*

This was the second release candidate of the 2.5 series.

Version 2.5.0 rc1

-----------------

*(Released Tue, 4 Oct 2011)*

This was the first release candidate of the 2.5 series.

Version 2.5.0 beta3

-------------------

*(Released Wed, 31 Aug 2011)*

This was the third beta release of the 2.5 series.

Version 2.5.0 beta2

-------------------

*(Released Mon, 22 Aug 2011)*

This was the second beta release of the 2.5 series.

Version 2.5.0 beta1

-------------------

*(Released Fri, 12 Aug 2011)*

This was the first beta release of the 2.5 series.

Version 2.4.5

-------------

*(Released Thu, 27 Oct 2011)*

- Fixed bug when parsing command line parameter values ending in

  backslash

- Fixed assertion error after unclean master shutdown

- Disable HTTP client pool for RPC, significantly reducing memory usage

  of master daemon

- Fixed queue archive creation with wrong permissions

Version 2.4.4

-------------

*(Released Tue, 23 Aug 2011)*

Small bug-fixes:

- Fixed documentation for importing with ``--src-dir`` option

- Fixed a bug in ``ensure-dirs`` with queue/archive permissions

- Fixed a parsing issue with DRBD 8.3.11 in the Linux kernel

Version 2.4.3

-------------

*(Released Fri, 5 Aug 2011)*

Many bug-fixes and a few small features:

- Fixed argument order in ``ReserveLV`` and ``ReserveMAC`` which caused

  issues when you tried to add an instance with two MAC addresses in one

  request

- KVM: fixed per-instance stored UID value

- KVM: configure bridged NICs at migration start

- KVM: Fix a bug where instance will not start with never KVM versions

  (>= 0.14)

- Added OS search path to ``gnt-cluster info``

- Fixed an issue with ``file_storage_dir`` where you were forced to

  provide an absolute path, but the documentation states it is a

  relative path, the documentation was right

- Added a new parameter to instance stop/start called ``--no-remember``

  that will make the state change to not be remembered

- Implemented ``no_remember`` at RAPI level

- Improved the documentation

- Node evacuation: don't call IAllocator if node is already empty