metadata_proxy_socket not configurable for agent/metadata/namespace_proxy.py

[Christian Berendt]

I think the parameter metadata_proxy_socket cannot be set for the namespace proxy, because the namespace proxy is started inside the DHCP or L3 agent without a config file parameter.

[OpenStack Infra (hudson-openstack)]

Fix proposed to branch: master
Review: https://review.openstack.org/37662

[Mark McClain (markmcclain)]

Why would we not add the socket path to the cmd line of the subprocess? Adding another configuration file and option adds to the deployer burden.

[Christian Berendt (berendt)]

Sure. That's also working. I'll change it.

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/37662
Committed: http://github.com/openstack/neutron/commit/495fd24fb0a776c207c36d437cb31e0d8807774a
Submitter: Jenkins
Branch: master

commit 495fd24fb0a776c207c36d437cb31e0d8807774a
Author: Christian Berendt <email address hidden>
Date: Thu Jul 18 13:13:05 2013 +0200

    make neutron-ns-metadata-proxy configurable

    Introduced a new configuration parameter for DHCP and L3 agent
    to be able to set the path of the metadata socket to be used
    by neutron-ns-metadata-proxy when started inside the DHCP or L3
    agent. Also moved the configuration parameter of the
    neutron-ns-metadata-proxy to the CLI parameters.

    fixes bug #1202628

    Change-Id: I3b1aa72b4e06c00f7fed152f0ee03d52b6bbc279