+Version 2.0.3
+ - Added “--ignore-size” to the “gnt-instance activate-disks” command
+ to allow using the pre-2.0.2 behaviour in activation, if any
+ existing instances have mismatched disk sizes in the configuration
+ - Added “gnt-cluster repair-disk-sizes” command to check and update
+ any configuration mismatches for disk sizes
+ - Added “gnt-master cluste-failover --no-voting” to allow master
+ failover to work on two-node clusters
+ - Fixed the ‘--net’ option of “gnt-backup import”, which was unusable
+ - Fixed detection of OS script errors in “gnt-backup export”
+ - Fixed exit code of “gnt-backup export”
+
+Version 2.0.2
+ - Added experimental support for stripped logical volumes; this should
+ enhance performance but comes with a higher complexity in the block
+ device handling; stripping is only enabled when passing
+ --with-lvm-stripecount=N to configure, but codepaths are affected
+ even in the non-stripped mode
+ - Improved resiliency against transient failures at the end of DRBD
+ resyncs, and in general of DRBD resync checks
+ - Fixed a couple of issues with exports and snapshot errors
+ - Fixed a couple of issues in instance listing
+ - Added display of the disk size in “gnt-instance info”
+ - Fixed checking for valid OSes in instance creation
+ - Fixed handling of the ‘vcpus’ parameter in instance listing and in
+ general of invalid parameters
+ - Fixed http server library, and thus RAPI, to handle invalid
+ username/password combinations correctly; this means that now they
+ report unauthorized for queries too, not only for modifications,
+ allowing earlier detect of configuration problems
+ - Added a new ‘role’ node list field, equivalent to the master/master
+ candidate/drained/offline flags combinations
+ - Fixed cluster modify and changes of candidate pool size
+ - Fixed cluster verify error messages for wrong files on regular nodes
+ - Fixed a couple of issues with node demotion from master candidate
+ role
+ - Fixed node readd issues
+ - Added non-interactive mode for “ganeti-masterd --no-voting” startup
+ - Added a new ‘--no-voting’ option for masterfailover to fix failover
+ on two-nodes clusters when the former master node is unreachable
+ - Added instance reinstall over RAPI
+
+Version 2.0.1
+ - added -H/-B startup parameters to gnt-instance, which will allow
+ re-adding the start in single-user option (regression from 1.2)
+ - the watcher writes the instance status to a file, to allow
+ monitoring to report the instance status (from the master) based on
+ cached results of the watcher's queries; while this can get stale if
+ the watcher is being locked due to other work on the cluster, this
+ is still an improvement
+ - the watcher now also restarts the node daemon and the rapi daemon if
+ they died
+ - fixed the watcher to handle full and drained queue cases
+ - hooks export more instance data in the environment, which helps if
+ hook scripts need to take action based on the instance's properties
+ (no longer need to query back into ganeti)
+ - instance failovers when the instance is stopped do not check for
+ free RAM, so that failing over a stopped instance is possible in low
+ memory situations
+ - rapi uses queries for tags instead of jobs (for less job traffic),
+ and for cluster tags it won't talk to masterd at all but read them
+ from ssconf
+ - a couple of error handling fixes in RAPI
+ - drbd handling: improved the error handling of inconsistent disks
+ after resync to reduce the frequency of "there are some degraded
+ disks for this instance" message
+ - fixed a bug in live migration when DRBD doesn't want to reconnect
+ (the error handling path called a wrong function name)
+
+Version 2.0.0 final
+ - no changes from rc5
+
+Version 2.0 release candidate 5
+ - fix a couple of bugs (validation, argument checks)
+ - fix gnt-cluster getmaster on non-master nodes (regression)
+ - some small improvements to RAPI and IAllocator
+ - make watcher automatically start the master daemon if down
+
+Version 2.0 release candidate 4
+ - change the OS list to not require locks; this helps with big
+ clusters
+ - fix gnt-cluster verify and gnt-cluster verify-disks when the volume
+ group is broken
+ - “gnt-instance info”, without any arguments, doesn't run for all
+ instances anymore; either pass ‘--all’ or pass the desired
+ instances; this helps against mistakes on big clusters where listing
+ the information for all instances takes a long time
+ - miscellaneous doc and man pages fixes
+
Version 2.0 release candidate 3
- Change the internal locking model of some gnt-node commands, in
order to reduce contention (and blocking of master daemon) when