openstack
/
neutron
Code Issues Proposed changes
OpenStack Networking (Neutron)
4,075 Commits 9 Branches 75 Tags 1,010 MiB
Python 99.5%
Shell 0.4%
Jinja 0.1%
Go to file
Salvatore Orlando 3c44da1a96 Do not mark device as processed if it wasn't 
Currently treat_devices_added_or_updated in the OVS agent skips
processing devices which disappeared from the integration bridge
during the agent loop.
This is fine, however the agent should not mark these devices as
processed. Otherwise they won't be processed, should they appear
again on the bridge.

This patch ensures these devices are not added to the current
device set.

The patch also changes treat_devices_added_or_updated. The
function now will return the list of skipped devices and not
anymore a flag signalling whether a resync is required.
With the current logic a resync would be required if retrieval
of device details fails. With this change, the function
treat_devices_added_or_updated will raise in this case and the
exception will be handled in process_network_ports.

For the sake of consistency, this patch also updates the
similar function treat_ancillary_devices_added in order to
use the same logic.

Finally, this patch amends an innaccurate related comment.

Closes-Bug: #1329546

Conflicts:
	neutron/plugins/openvswitch/agent/ovs_neutron_agent.py
	neutron/tests/unit/openvswitch/test_ovs_neutron_agent.py

Required changes:
- fetch all device details first before proceeding with handling ports
  to reflect Juno behaviour.
- unit test was modified to run with get_device_details since
  get_devices_details_list is not available in Icehouse.
- fixed E128 violation in the backported code.

Additional changes in Havana:
- modified patch not to pass ovs_restarted argument into
  treat_devices_added_or_updated() since it's not present in Havana.
- disabled test_schedule_pool_with_down_agent that fails in gate.

Change-Id: Icc744f32494c7a76004ff161536316924594fbdb
(cherry picked from commit 90fedbe44c)
(cherry picked from commit 231010bdf2)
 		2014-09-15 17:30:28 +02:00
bin Use built-in print() instead of print statement 2013-09-21 07:30:33 -07:00
contrib Update tox.ini to support RHEL 6.x. 2013-03-08 08:52:25 -05:00
doc Update references with new Mailing List location 2013-07-28 11:35:32 -07:00
etc L3 Agent can handle many external networks 2014-07-08 11:39:01 +00:00
neutron Do not mark device as processed if it wasn't 2014-09-15 17:30:28 +02:00
quantum Re-assign quantum.api module as last operation 2013-07-15 22:51:28 +02:00
tools Use built-in print() instead of print statement 2013-09-21 07:30:33 -07:00
.coveragerc fix some missing change from quantum to neutron 2013-07-08 12:11:04 +08:00
.gitignore Ignore pbr*.egg directory 2013-08-09 06:06:07 +08:00
.gitreview Open stable/havana 2013-10-17 17:31:36 +02:00
.mailmap fix conversion type missing 2013-09-06 02:16:13 +08:00
.pylintrc Rename Quantum to Neutron 2013-07-06 15:02:43 -04:00
.testr.conf Add support for managing async processes 2014-01-09 15:35:21 -06:00
HACKING.rst Fix wrong example in HACKING.rst 2013-08-18 14:26:36 +08:00
LICENSE Adding Apache Version 2.0 license file. This is the official license agreement under which Quantum code is available to 2011-08-08 12:31:04 -07:00
MANIFEST.in Rename Quantum to Neutron 2013-07-06 15:02:43 -04:00
README.rst Rename Quantum to Neutron 2013-07-06 15:02:43 -04:00
TESTING Add support for managing async processes 2014-01-09 15:35:21 -06:00
babel.cfg Use babel to generate translation file 2013-01-24 00:20:32 +08:00
openstack-common.conf Remove openstack.common.exception usage 2013-08-06 10:42:02 +02:00
requirements.txt Updated from global requirements 2014-07-23 19:49:13 +00:00
run_tests.sh Don't need to init testr in run_tests.sh 2013-09-12 01:04:09 +08:00
setup.cfg Added missing plugin .ini files to setup.cfg 2014-05-30 10:47:14 +02:00
setup.py Updated from global requirements 2013-10-01 16:13:29 +00:00
test-requirements.txt Updated from global requirements 2014-07-23 19:49:13 +00:00
tox.ini Set python hash seed to 0 in tox.ini 2014-07-25 13:36:53 -07:00

README.rst

# -- 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 github at <http://github.com/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 http://docs.openstack.org/trunk/openstack-network/admin/content/

Neutron 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/NeutronDevelopment

For help using or hacking on Neutron, you can send mail to <mailto:openstack-dev@lists.openstack.org>.