[openstack-dev] [nova][neutron] ports management

Neil Jerram Neil.Jerram at metaswitch.com
Wed Oct 7 10:34:10 UTC 2015

Just some initial thoughts here, as I'm not yet clear on many of your

On 06/10/15 16:55, Peter V. Saveliev wrote:
> The problem.
> ------------
> There are use cases, when it us needed to attach vnic to some specific 
> network interface instead of br-int.
> For example, working with trunk ports, it is better to attach vnic to a 
> specific trunk bridge, and the bridge add to br-int. But it doesn't fit 
> in the current design.
I think this corresponds to a modified form of 'VIF plugging', which is
something that currently happens in Nova; see nova/virt/libvirt/vif.py

> There are several possible ways to solve the issue:
> 1. make the user responsible to pass the ready-to-use port to nova, so 
> nova will not care about adding port by libvirt to the bridge
> 2. make the neutron service synchronously call the agent to create the 
> required interface, e.g. the trunk bridge.
> 3. make the neutron somehow to delay vif plug
Why would a delay help?  (Also note, as above, that VIF plugging is in

> 4. make the nova to create the required port
A port is a Neutron object, so not sure what you could mean here.


More information about the OpenStack-dev mailing list