qos driver api can have better error handling
Bug #1627749 reported by
YAMAMOTO Takashi
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
networking-odl |
Invalid
|
Medium
|
Manjeet Singh Bhatia | ||
neutron |
Fix Released
|
Medium
|
Miguel Angel Ajo |
Bug Description
the current qos (notification) driver api assumes driver methods are async and always success.
however, it might not be the case for some of possible backends. eg. a controller based implementation, where a driver would make a rest api call to the backend.
- currently one of drivers raises an exception, the rest of drivers are simply skipped.
it might not be what an api user would expect.
- whan driver calls end up with an error, the db changes should be reverted, or
the resource should be marked "possibly not sync".
tags: | added: qos |
Changed in neutron: | |
status: | New → Confirmed |
importance: | Undecided → Medium |
Changed in neutron: | |
assignee: | nobody → Miguel Angel Ajo (mangelajo) |
Changed in networking-odl: | |
status: | New → Confirmed |
importance: | Undecided → Medium |
assignee: | nobody → Manjeet Singh Bhatia (manjeet-s-bhatia) |
Changed in neutron: | |
status: | Confirmed → Fix Released |
Changed in networking-odl: | |
status: | Confirmed → Triaged |
Changed in networking-odl: | |
status: | Triaged → Invalid |
To post a comment you must log in.
Agreed, this has been discussed in last QoS meeting eavesdrop. openstack. org/meetings/ neutron_ qos/2016/ neutron_ qos.2016- 10-05-14. 01.log. html
http://