This is a bus for all reno problems we see with the relnotes :
* Change Id25bd4870c6e2fda08dc0177b7ed61a8a6091838 was having
a formatting problem with not retaining the newlines, and also
was mentioning "Nove" :-)
* Change I43ddc5164f88fb049fe49ad4672fbf09b2b1987e was using a
prelude section that is not needed because we will provide a
general prelude section (and commenting that) in the next change.
* Change I2dba71e71b1ed7cf8476e8bfe9481e84be5df128 was incorrectly
using the upgrades section while it was a deprecation.
* Change Ia6f1d8f9c7d700498b6441a6ba37fa25b2611ef8 is no longer
valid because Id7936be290b6febd18deb4c2db8ea4d678d4d9b1 has been
merged during Mitaka too.
* Change I2465e1bee618a552132d659014ea96cdbda161d6 was reverting
a reno file but due to a reno bug (see
https://review.openstack.org/#/c/293078/), the release note is
still kept in the output. Consequently, the workaround I found
is to reintroduce the same reno file with an empty content to
drop the previous content.
Note that I used the prelude section for "dropping" notes, that
prevents us to provide empty bullets for upgrade or features sections.
Change-Id: I1535aff80850fa3666da739133fc43e8579aa19b
We have had a "untested and risky to use in production" log warning
message for this driver since Kilo, it is currently broken (see below),
there are no obviously active users or contributors, and we are planning
on enabling Zookeeper usage by adopting the tooz library.
bug #1443910 shows that the driver fails to load because eventlet 0.17
broke evzookeeper by moving _SocketDuckForFd from eventlet.greenio to
eventlet.greenio.py2 in commit 449c90a. The 0.17 release was in Feb,
2015. The evzookeeper library hasn't been updated since Sep 2012 and the
sole maintainer is the original author of the zookeeper servicegroup
driver.
The tooz driver spec - Ibf70c2dbe308fc8e4dd277d8c75c4445b3dfce90 -
proposes a formal deprecation period for the zk driver, during which
existing zk driver users are encouraged to move to tooz. However, given
the state of the zk driver, we must conclude that there are no existing
users who need a graceful migration path. Removing the driver will
avoid potential confusion for new users and simplify the path to
adopting tooz.
Closes-Bug: #1443910
Closes-Bug: #1414517
Closes-Bug: #1414536
Signed-off-by: Mark McLoughlin <markmc@redhat.com>
Change-Id: I2dba71e71b1ed7cf8476e8bfe9481e84be5df128