LGTM, thanks
On Mon, Aug 18, 2014 at 02:58:50PM +0200, 'Klaus Aehlig' via ganeti-devel wrote: > > > commit f1ef879611594588b56d6581cc050e1a999e6d9e > Merge: 3077d76 7bcc5fc > Author: Klaus Aehlig <[email protected]> > Date: Mon Aug 18 14:53:27 2014 +0200 > > Merge branch 'stable-2.11' into stable-2.12 > > * stable-2.11 > Fix invalid use of RpcResult.Raise > Bump revision to 2.11.5 > Prepare NEWS file for 2.11.5 release > > * stable-2.10 > On upgrades, check for upgrades to resume first > Pause watcher during upgrade > Allow instance disks to be added with --no-wait-for-sync > Bump revision to 2.10.7 > Prepare NEWS file for 2.10.7 release > Fix lint error > Create the config backup archive in a safe way > > Conflicts: > NEWS: take ALL the entries > configure.ac: ignore revision bump > > diff --cc NEWS > index 56be58c,0e93785..918c9d9 > --- a/NEWS > +++ b/NEWS > @@@ -2,76 -2,49 +2,119 @@@ New > ==== > > > +Version 2.12.0 beta1 > +-------------------- > + > +*(Released Mon, 21 Jul 2014)* > + > +Incompatible/important changes > +~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ > + > +- Do not use debug mode in production. Certain daemons will issue warnings > + when launched in debug mode. Some debug logging violates some of the new > + invariants in the system (see "New features"). The logging has been kept > as > + it aids diagnostics and development. > + > +New features > +~~~~~~~~~~~~ > + > +- OS install script parameters now come in public, private and secret > + varieties: > + > + - Public parameters are like all other parameters in Ganeti. > + - Ganeti will not log private and secret parameters, *unless* it is > running > + in debug mode. > + - Ganeti will not save secret parameters to configuration. Secret > parameters > + must be supplied every time you install, or reinstall, an instance. > + - Attempting to override public parameters with private or secret > parameters > + results in an error. Similarly, you may not use secret parameters to > + override private parameters. > + > +- The move-instance tool can now attempt to allocate an instance by using > + opportunistic locking when an iallocator is used. > +- The build system creates sample systemd unit files, available under > + doc/examples/systemd. These unit files allow systemd to natively > + manage and supervise all Ganeti processes. > +- Different types of compression can be applied during instance moves, > including > + user-specified ones. > +- Ganeti jobs now run as separate processes. The jobs are coordinated by > + a new daemon "WConfd" that manages cluster's configuration and locks > + for individual jobs. A consequence is that more jobs can run in parallel; > + the number is run-time configurable, see "New features" entry > + of 2.11.0. To avoid luxid being overloaded with tracking running jobs, it > + backs of and only occasionally, in a sequential way, checks if jobs have > + finished and schedules new ones. In this way, luxid keeps responsive under > + high cluster load. The limit as when to start backing of is also run-time > + configurable. > +- The metadata daemon is now optionally available, as part of the > + partial implementation of the OS-installs design. It allows pass > + information to OS install scripts or to instances. > + It is also possible to run Ganeti without the daemon, if desired. > + > +New dependencies > +~~~~~~~~~~~~~~~~ > + > +- The KVM CPU pinning no longer uses the affinity python package, but psutil > + instead. The package is still optional and needed only if the feature is > to > + be used. > + > +Known issues > +~~~~~~~~~~~~ > + > +The following issues are known to be present in the beta and will be fixed > +before rc1: > + > +- Issue 881: Handle communication errors in mcpu > +- Issue 883: WConfd leaks memory for some long operations > +- Issue 884: Under heavy load the IAllocator fails with a "missing > + instance" error > +- Issue 885: Network hotplugging on KVM sometimes makes an instance > + inresponsive > + > + > + Version 2.11.5 > + -------------- > + > + *(Released Thu, 7 Aug 2014)* > + > + Inherited from the 2.10 branch: > + > + Important security release. In 2.10.0, the > + 'gnt-cluster upgrade' command was introduced. Before > + performing an upgrade, the configuration directory of > + the cluster is backed up. Unfortunately, the archive was > + written with permissions that make it possible for > + non-privileged users to read the archive and thus have > + access to cluster and RAPI keys. After this release, > + the archive will be created with privileged access only. > + > + We strongly advise you to restrict the permissions of > + previously created archives. The archives are found in > + /var/lib/ganeti*.tar (unless otherwise configured with > + --localstatedir or --with-backup-dir). > + > + If you suspect that non-privileged users have accessed > + your archives already, we advise you to renew the > + cluster's crypto keys using 'gnt-cluster renew-crypto' > + and to reset the RAPI credentials by editing > + /var/lib/ganeti/rapi_users (respectively under a > + different path if configured differently with > + --localstatedir). > + > + Other changes included in this release: > + > + - Fix handling of Xen instance states. > + - Fix NIC configuration with absent NIC VLAN > + - Adapt relative path expansion in PATH to new environment > + - Exclude archived jobs from configuration backups > + - Fix RAPI for split query setup > + - Allow disk hot-remove even with chroot or SM > + > + Inherited from the 2.9 branch: > + > + - Make htools tolerate missing 'spfree' on luxi > + > + > Version 2.11.4 > -------------- > > > -- > Klaus Aehlig > Google Germany GmbH, Dienerstr. 12, 80331 Muenchen > Registergericht und -nummer: Hamburg, HRB 86891 > Sitz der Gesellschaft: Hamburg > Geschaeftsfuehrer: Graham Law, Christine Elizabeth Flores
