[openstack-dev] [nova] vif type libvirt-network

Ian Wells ijw.ubuntu at cack.org.uk
Fri Jun 12 06:20:31 UTC 2015

On 11 June 2015 at 02:37, Andreas Scheuring <scheuran at linux.vnet.ibm.com>

> > Do you happen to know how data gets routed _to_ a VM, in the
> > type='network' case?
> Neil, sorry no. Haven't played around with that, yet. But from reading
> the libvirt man, it looks good. It's saying "Guest network traffic will
> be forwarded to the physical network via the host's IP routing stack" -
> so I would assume this is L3. Maybe you should give it a quick try to
> figure out...

You would at the least require a namespace to preserve network separation,
I think.  And in fact if you go this way the answer may be to set up a
namespace in the same way that LB sets a bridge up.  Nova or Neutron can
create the NS whichever happens to need it first, and ignore the failure if
it happens to get caught in the race.  Some slight risk that a true failure
is not spotted, though.  Or you could have the Neutron agent wait for the
appearance of the interface, which it could do with either polling or use
of rt_netlink, offhand.

And none of this appears to require a libvirt network, but I don't think a
simple TAP plug exists either (something along the lines that Neil (?)
proposed where Nova is simply told that if it creates a TAP with the right
name then all will be well).

(And I begin to remember why VIF plugging is horrible.)
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20150611/c730af20/attachment.html>

More information about the OpenStack-dev mailing list