yahoo-eng-team team mailing list archive
-
yahoo-eng-team team
-
Mailing list archive
-
Message #78194
[Bug 1826396] [NEW] Atomic Extraroute API
Public bug reported:
As discussed in an openstack-disciss 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.
A detailed spec is coming soon.
[1] http://lists.openstack.org/pipermail/openstack-
discuss/2019-April/005121.html1
** Affects: neutron
Importance: Undecided
Assignee: Bence Romsics (bence-romsics)
Status: New
** Tags: rfe
** Summary changed:
- Add atomic extraroute API
+ Atomic Extraroute API
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1826396
Title:
Atomic Extraroute API
Status in neutron:
New
Bug description:
As discussed in an openstack-disciss 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.
A detailed spec is coming soon.
[1] http://lists.openstack.org/pipermail/openstack-
discuss/2019-April/005121.html1
To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1826396/+subscriptions
Follow ups