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.
Reviewed: https:/ /review. opendev. org/655680 /git.openstack. org/cgit/ openstack/ neutron- specs/commit/ ?id=c1e12a0fd12 ffd6b2934fdff5a 0ee29de11a102d
Committed: https:/
Submitter: Zuul
Branch: master
commit c1e12a0fd12ffd6 b2934fdff5a0ee2 9de11a102d
Author: Bence Romsics <email address hidden>
Date: Thu Apr 25 14:32:31 2019 +0200
Improve Extraroute API
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 deletions of particular routing table entries. In the current
additions/
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: I10407a74102bfd 16e3a0b8d2bd08c 92acb4cc27f
Partial-Bug: #1826396