Neuton client always returns 204 code for delete action

[Evgeny Fedoruk]

Neuton client always returns 204 code for delete action which is not always correct.
In case of deleting Vip (or pool), LBaaS back-end driver may want to return 202 code and monitor the deletion completion later.

neutron/api/v2/resource.py:Resource class has action return status codes hard coded (create=201, delete=204)

Probably each Resource should define its return codes for actions.

[Eugene Nikanorov (enikanorov)]

I'm not sure this is the right approach to follow.
Instead, the drivers should be fixed in order to provide exactly same API experience.
User would expect uniform behavior, regardless of the chosen provider.
At some point we'll get rid of providers in favor of flavors, in this case there will be no direct correspondence between the flavor and the driver, so user will not be able to expect any specific return code.

[Evgeny Fedoruk (evgenyf)]

If I understand you right, driver should control the return code and not the client or any other entity in between.
In this case I agree.

[Launchpad Janitor (janitor)]

[Expired for neutron because there has been no activity for 60 days.]