]> review.fuel-infra Code Review - openstack-build/neutron-build.git/commit
Don't spawn metadata-proxy for non-isolated nets
authorJohn Schwarz <jschwarz@redhat.com>
Tue, 26 Aug 2014 08:43:11 +0000 (11:43 +0300)
committerAkihiro Motoki <motoki@da.jp.nec.com>
Mon, 1 Sep 2014 12:20:33 +0000 (21:20 +0900)
commit9569b2fe58d0e836071992f545886ca985d5ace8
tree10ae48fbba6586a62f8736256719a9bd22867ac4
parentbeae747ca8aa6b011cbd9648d7e770a4679f5071
Don't spawn metadata-proxy for non-isolated nets

If the configuation option "enable_isolated_metadata = True" for the
DHCP agent is set, the neutron-ns-metadata-proxy process is spawned
for all networks, regardless if they are isolated or not. In case
the network is not isolated (ie. connected to a neutron router), the
L3 agent also spawns a proxy process, and the DHCP's proxy is left
unused. This patch adds a check prior to the spawning of new proxies:
if a network is not isolated, no proxy is spawned.

Change-Id: I9bdb8c3d37997b22435bca33ec47a67db08efa51
Closes-bug: #1361545
neutron/agent/dhcp_agent.py
neutron/agent/linux/dhcp.py
neutron/tests/unit/test_dhcp_agent.py