Release note for API extension: extraroute-atomic
Change-Id: Idb1be0ed3ca65aecb0d59d0b8644213774959807 Partial-Bug: #1826396 (rfe) Related-Change: https://review.opendev.org/655680 (spec)
This commit is contained in:
parent
a63f344748
commit
b3eda71638
12
releasenotes/notes/extraroute-atomic-5ae09e3f37c5fbda.yaml
Normal file
12
releasenotes/notes/extraroute-atomic-5ae09e3f37c5fbda.yaml
Normal file
@ -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.
|
Loading…
Reference in New Issue
Block a user