From b3eda71638973836c68dca90da9e017b285a642c Mon Sep 17 00:00:00 2001
From: Bence Romsics <bence.romsics@gmail.com>
Date: Tue, 24 Sep 2019 16:35:48 +0200
Subject: [PATCH] Release note for API extension: extraroute-atomic

Change-Id: Idb1be0ed3ca65aecb0d59d0b8644213774959807
Partial-Bug: #1826396 (rfe)
Related-Change: https://review.opendev.org/655680 (spec)
---
 .../notes/extraroute-atomic-5ae09e3f37c5fbda.yaml    | 12 ++++++++++++
 1 file changed, 12 insertions(+)
 create mode 100644 releasenotes/notes/extraroute-atomic-5ae09e3f37c5fbda.yaml

diff --git a/releasenotes/notes/extraroute-atomic-5ae09e3f37c5fbda.yaml b/releasenotes/notes/extraroute-atomic-5ae09e3f37c5fbda.yaml
new file mode 100644
index 00000000000..cbd95eab577
--- /dev/null
+++ b/releasenotes/notes/extraroute-atomic-5ae09e3f37c5fbda.yaml
@@ -0,0 +1,12 @@
+---
+features:
+  - |
+    The new API extension ``extraroute-atomic`` introduces two new member
+    actions on routers to add/remove routes atomically on the server side.
+    The use of these new member actions
+    (``PUT /v2.0/routers/ROUTER-ID/add_extraroutes`` and
+    ``PUT /v2.0/routers/ROUTER-ID/remove_extraroutes``) is always preferred
+    to the old way (``PUT /v2.0/routers/ROUTER-ID``) when multiple clients
+    edit the extra routes of a router since the old way is prone to race
+    conditions between concurrent clients and therefore to possible lost
+    updates.