summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorLinus Nordberg <linus@nordu.net>2017-02-11 00:30:17 +0100
committerLinus Nordberg <linus@nordu.net>2017-02-11 00:30:17 +0100
commit5b5cf55ccc4b96040b5b526c76ddea2ee7ae187e (patch)
tree9db2bd839261d2b29ed2a6da5c6e7bdc390dc849
parentc7031b2d5cfa6a67253282a69bb3b7f6550f9d5d (diff)
Proposed NEWS.md.
-rw-r--r--NEWS.md52
1 files changed, 52 insertions, 0 deletions
diff --git a/NEWS.md b/NEWS.md
index 278f9ec..8e74ade 100644
--- a/NEWS.md
+++ b/NEWS.md
@@ -1,3 +1,55 @@
+# Changes in catlfish 0.10.0 - 2017-02-11
+
+## Incompatible changes
+
+- Local configuration files need two new settings: 'configurl' and
+ 'logadminkey'. The former is where the log administrator publishes
+ the (generated) global config file and the latter can be found in
+ that file.
+
+- The configuration setting 'publicaddresses', used by frontend nodes,
+ has changed to 'ctapiaddresses'.
+
+- The configuration setting 'known_roots' in merge configuration files
+ has changed to 'knownroots' to match what's being used by all other
+ nodes types.
+
+ It should be noted that regeneration of Erlang config files is
+ necessary when upgrading to 0.10.0 from a previous version.
+
+ This is indeed recommended for every release, and even recommended
+ to be done before restarting of nodes, in order to take advantage of
+ the new config management system.
+
+## Features
+
+- A new database backend, permdb, has been added. This is the
+ recommended backend.
+
+- Support for managing log configuration and log keys has been
+ added. Most notably, the log API keys have moved into the global
+ configuration file and a new logadmin key is used by the log owner
+ to sign that file. Node operators should regularly download the
+ global config, verify it and use it together with local config to
+ generate the Erlang config files used by the system (closes
+ CATLFISH-77).
+
+- Many configuration options can now be reloaded without restarting
+ a node (closes CATLFISH-32).
+
+## Improvements
+
+- Most of the merge process has been parallelised. It's now possible
+ to add both new frontend nodes and new secondary merge nodes to a
+ running log without risking long delays in publishing of new STH's
+ (closes CATLFISH-88).
+
+- Tooling both for initiating a log instance and for promoting a
+ secondary merge node to primary in an existing log instance has been
+ added.
+
+- The tests now do a better job at testing the merge failover case.
+
# Changes in catlfish 0.9.0 - 2016-12-04
## Features