2516c13654
To avoid a 'null' response body, the delete operation returns a response that is consistent with its add counterpart, i.e. we return the router id with details about the interface being affected by the operation, as well as the tenant id. A unit test is added to ensure that the right body is returned and minor adjustments have been made to the plugins affected by the change. Long-term, a delete operation should really return 204 w/o a body, but this requires some major rework of the WSGI handling within Quantum. This is an interim solution that deals with an 'ugly' response body, whilst keeping backward compatibility. Fixes bug 1173284 Change-Id: Icaab87ad0c8561c0690c8f0a14db815d8886bc71
# -- Welcome! You have come across a cloud computing network fabric controller. It has identified itself as "Quantum." It aims to tame your (cloud) networking! # -- External Resources: The homepage for Quantum is: http://launchpad.net/quantum . Use this site for asking for help, and filing bugs. Code is available on github at <http://github.com/openstack/quantum>. The latest and most in-depth documentation on how to use Quantum is available at: <http://docs.openstack.org>. This includes: Quantum Administrator Guide http://docs.openstack.org/trunk/openstack-network/admin/content/ Quantum API Reference: http://docs.openstack.org/api/openstack-network/2.0/content/ The start of some developer documentation is available at: http://wiki.openstack.org/QuantumDevelopment For help using or hacking on Quantum, you can send mail to <mailto:openstack-dev@lists.openstack.org>.