Review [1] showed how tricky it can be to let the client
side deal with auto-network-topology cleanups. Rather than
pushing this complexity to the client, we should implement
the DELETE method for this extension, as it's rather
trival to do on this server side.
Since the DELETE method is exposed, but it fails with 500,
it is reasonable to deal with this as a bug fix, rather than
having to go through yet another extension. The neutronclient
side support should be added, but since the first user of this
is Tempest, we can safely assume they can leverage this directly
without depending on a python-neutronclient version bump.
Reviewed: https:/ /review. openstack. org/357662 /git.openstack. org/cgit/ openstack/ neutron/ commit/ ?id=dfa702fac80 312b0c5b93c78e9 2f9d01ea11bbd6
Committed: https:/
Submitter: Jenkins
Branch: master
commit dfa702fac80312b 0c5b93c78e92f9d 01ea11bbd6
Author: Armando Migliaccio <email address hidden>
Date: Fri Aug 19 00:18:54 2016 -0700
Implement the DELETE method for get-me-a-network
Review [1] showed how tricky it can be to let the client topology cleanups. Rather than
side deal with auto-network-
pushing this complexity to the client, we should implement
the DELETE method for this extension, as it's rather
trival to do on this server side.
Since the DELETE method is exposed, but it fails with 500, neutronclient version bump.
it is reasonable to deal with this as a bug fix, rather than
having to go through yet another extension. The neutronclient
side support should be added, but since the first user of this
is Tempest, we can safely assume they can leverage this directly
without depending on a python-
[1] https:/ /review. openstack. org/#/c/ 327191/
Closes-bug: #1614872
Change-Id: I2fba51bdf8c781 fcc0449e1e9947d e976c96eec4