zuul
/
zuul
Code Issues Proposed changes

Add release note about the final 3.x release 

Change-Id: I8e83d8c40893a395dedb6afcbec3dc86f8be0ac9
This commit is contained in:
James E. Blair 2020-05-27 07:04:38 -07:00
parent ccfeb49fcc
commit a9543b3ba8
3 changed files with 30 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
doc/source/howtos/zookeeper.rst
View File

@ -18,6 +18,8 @@ The following general configuration setting in
This instructs ZooKeeper to purge old snapshots every 6 hours. This
will avoid filling the disk.
.. _zk-encrypted-connections:
Encrypted Connections
---------------------

2
doc/source/reference/drivers/sql.rst
View File

@ -1,5 +1,7 @@
:title: SQL Driver
.. _sql-driver:
SQL
===

26
releasenotes/notes/last3x-8682ada4910fa750.yaml Normal file
View File

@ -0,0 +1,26 @@
---
prelude: |
This is expected to be the last 3.x release of Zuul (barring any
unanticpated bugfix releases).
The next release of Zuul, 4.0.0, will require the following
deployment changes:
* TLS ZooKeeper connections
* Network connectivity from all components to ZooKeeper
* A SQL database
These features are supported now, so it is important that you take
this time to :ref:`switch your ZooKeeper connection to use
TLS<zk-encrypted-connections>`, and :ref:`configure a SQL
connection<sql-driver>`. Even though only some Zuul components
connect to ZooKeeper today, you should ensure that the
``[zookeeper]`` section is present in ``zuul.conf`` for all
components, and that they have network connectivity to the ZooKeeper
servers. Doing so will make the upgrade to 4.0.0 seamless.
These changes are in support of ongoing work to enable multiple
scheduler processes for scaling and availability. After the 4.0.0
release, it is anticipated that further upgrades to Zuul made in
support of this work will be done with minimal disruption in the
course of normal releases.