On 16 January 2014 09:07, yongli he <yongli...@intel.com> wrote: > On 2014年01月16日 08:28, Ian Wells wrote: > > This is based on Robert's current code for macvtap based live migration. > The issue is that if you wish to migrate a VM and it's tied to a physical > interface, you can't guarantee that the same physical interface is going to > be used on the target machine, but at the same time you can't change the > libvirt.xml as it comes over with the migrating machine. The answer is to > define a network and refer out to it from libvirt.xml. In Robert's current > code he's using the group name of the PCI devices to create a network > containing the list of equivalent devices (those in the group) that can be > macvtapped. Thus when the host migrates it will find another, equivalent, > interface. This falls over in the use case under > > but, with flavor we defined, the group could be a tag for this purpose, > and all Robert's design still work, so it ok, right? >
Well, you could make a label up consisting of the values of the attributes in the group, but since a flavor can encompass multiple groups (for instance, I group by device and vendor and then I use two device types in my flavor) this still doesn't work. Irena's solution does, though.
_______________________________________________ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
