neutron

  1. Bug #1361545
  2. Comment #4

Comment 4 for bug 1361545

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to neutron (stable/icehouse)

Reviewed: https://review.openstack.org/123074
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=645f9849b6ccf2653ec68e54cf793453af34fe6a
Submitter: Jenkins
Branch: stable/icehouse

commit 645f9849b6ccf2653ec68e54cf793453af34fe6a
Author: John Schwarz <email address hidden>
Date: Tue Aug 26 11:43:11 2014 +0300

    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.

    Conflicts:
     neutron/tests/unit/test_dhcp_agent.py

    Change-Id: I9bdb8c3d37997b22435bca33ec47a67db08efa51
    Closes-bug: #1361545
    (cherry picked from commit 9569b2fe58d0e836071992f545886ca985d5ace8)