For the curiosity sake - After some trial and error. It appears we have solved one half of our conundrum. Using the driver below, there is no ip data inserted into libvirt.xml which allows any ip to be used. It works for our uses (HA vip services, secondary addresses).
libvirt_vif_driver=nova.virt.libvirt.vif.LibvirtOpenVswitchVirtualPortDriver This however does not prevent quantum from assigning a used IP to a new port, but working on that. Carl Bolterstein -----Original Message----- From: openstack-bounces+cbolterstein=blackmesh....@lists.launchpad.net [mailto:openstack-bounces+cbolterstein=blackmesh....@lists.launchpad.net] On Behalf Of Jason Kölker Sent: Tuesday, October 23, 2012 6:38 PM To: openstack@lists.launchpad.net Subject: Re: [Openstack] quantum: two ips one vif On Tue, 2012-10-23 at 15:14 -0700, Dan Wendlandt wrote: > can you post your libvirt xml for the VM? It maybe well be libvirt > filtering if you are using the OVS Hybrid vif driver: > > for example, a VM would have xml like: > > <filterref filter='nova-instance-instance-00000001-fa163e0569ba'> > <parameter name='DHCPSERVER' value='10.0.0.2'/> > <parameter name='IP' value='10.0.0.3'/> > <parameter name='PROJMASK' value='255.255.0.0'/> > <parameter name='PROJNET' value='10.0.0.0'/> > </filterref> > > I'm not sure what the nova code would generate for multiple IPs. Libvirt's driver only supports 1 ip per interface. It needs to be updated to use the newer network models and not depend on the code in nova.virt.netutils.get_injected_network_template. Happy Hacking! 7-11 _______________________________________________ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp _______________________________________________ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
