yahoo-eng-team team mailing list archive

[YAMAMOTO Takashi <yamamoto@xxxxxxxxxxxx>]

Public bug reported:

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".

** Affects: neutron
     Importance: Undecided
         Status: New


** Tags: qos

** Tags added: qos

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1627749

Title:
  qos driver api can have better error handling

Status in neutron:
  New

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".

To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1627749/+subscriptions