63fe3a418c
Make function _bind_port_if_needed to bind at least one time when the port's binding status passed in is already in binding_failed. This is the second attempt to introduce the patch (the first one was reverted due to regression that broke Ironic), now with proper notification sent even when binding attempt failed. The patch also fixes several cases when we attempted to notify with a binding context that was not committed into database. The patch changes _attempt_binding to call _commit_port_binding only with the binding final state: 1. Successful binding: will just call _commit_port_binding. 2. Unsuccessful binding: will call _commit_port_binding at the final attempt to bind the port. This is in order to refrain from reverts, with will really complicate things even more. Co-Authored-By: Yalei Wang <yalei.wang@intel.com> Co-Authored-By: Nir Magnezi <nmagnezi@redhat.com> Co-Authored-By: John Schwarz <jschwarz@redhat.com> Change-Id: I437290affd8eb87177d0626bf7935a165859cbdd Closes-Bug: #1399249
Welcome!
You have come across a cloud computing network fabric controller. It has identified itself as "Neutron." It aims to tame your (cloud) networking!
External Resources:
The homepage for Neutron is: http://launchpad.net/neutron. Use this site for asking for help, and filing bugs. Code is available on git.openstack.org at <http://git.openstack.org/cgit/openstack/neutron>.
The latest and most in-depth documentation on how to use Neutron is available at: <http://docs.openstack.org>. This includes:
- Neutron Administrator Guide
- Networking Guide
- Neutron API Reference:
-
http://docs.openstack.org/api/openstack-network/2.0/content/
- Current Neutron developer documentation is available at:
For help on usage and hacking of Neutron, please send mail to <mailto:openstack-dev@lists.openstack.org>.
For information on how to contribute to Neutron, please see the contents of the CONTRIBUTING.rst file.