yahoo-eng-team team mailing list archive

[OpenStack Hudson <1182704@xxxxxxxxxxxxxxxxxx>]

Reviewed:  https://review.openstack.org/30380
Committed: http://github.com/stackforge/tripleo-image-elements/commit/ad81e8107151bd59b3b0a51cd0c8d21fb86a073a
Submitter: Jenkins
Branch:    master

commit ad81e8107151bd59b3b0a51cd0c8d21fb86a073a
Author: Clint Byrum <clint@xxxxxxxxxx>
Date:   Tue May 21 21:26:31 2013 -0700

    Add quantum-network-node element for network-node.
    
    The network-node is separate from the quantum-server and is used
    to enable communication between vms and external networks.
    
    Fixes bug #1182283
    Fixes bug #1182704
    Fixes bug #1185977
    Fixes bug #1185980
    
    Change-Id: Ie5674e4004ba935e9e4b7060830dcbc69a122ac7


** Changed in: tripleo
       Status: In Progress => Fix Released

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to quantum.
https://bugs.launchpad.net/bugs/1182704

Title:
  quantum-ns-metadata-proxy path is not configurable

Status in OpenStack Quantum (virtual network service):
  New
Status in tripleo - openstack on openstack:
  Fix Released

Bug description:
  We are running quantum in a virtualenv, which means quantum-ns-
  metadata-proxy isn't on root's path; adjusting the filters etc is
  doable, but the netns command run has just 'quantum-ns-metadata-proxy'
  to execute, rather than allowing us to supply the full path.

To manage notifications about this bug go to:
https://bugs.launchpad.net/quantum/+bug/1182704/+subscriptions