c1e12a0fd1
As discussed in an openstack-discuss thread [1] we could improve the extraroute API to better support Neutron API clients, especially Heat. The problem is that the current extraroute API does not allow atomic additions/deletions of particular routing table entries. In the current API the routes attribute of a router (containing all routing table entries) must be updated at once. Therefore additions and deletions must be performed on the client side. Therefore multiple clients race to update the routes attribute and updates may get lost. [1] http://lists.openstack.org/pipermail/openstack-discuss/2019-April/005121.html Change-Id: I10407a74102bfd16e3a0b8d2bd08c92acb4cc27f Partial-Bug: #1826396 |
||
|---|---|---|
| .. | ||
| improve-extraroute-api.rst | ||
| index.rst | ||
| placeholder.rst | ||