Live migration will still work, it just means that your old host will still be dhcp, gateway. and floating ip host for the vm. A fix for moving the floating ip should be simple. Moving the dhcp host is a little harder, due to having to update security group rules to allow dhcp traffic as well. Moving the gateway is even harder, because you will have to leave the old gateway up until you are sure the dhcp lease has been renewed.
Patches for the first seems like a bug fix that someone could do for essex. The second is questionable but possible. The last is probably to complex for Essex, but could be addressed in Folsom if quantum doesn't have a better solution. Vish On Feb 7, 2012, at 9:01 AM, David Kranz wrote: > There was a thread about this in December: > http://www.mail-archive.com/[email protected]/msg06296.html > > I think that thread is saying that if you follow the official documentation > for configuring live migration, but use --multi_host, then > migration will not actually work. If that is right, is there (or will there > be) an officially documented way to to this, either for diablo or essex? > > -David > > _______________________________________________ > Mailing list: https://launchpad.net/~openstack > Post to : [email protected] > Unsubscribe : https://launchpad.net/~openstack > More help : https://help.launchpad.net/ListHelp _______________________________________________ Mailing list: https://launchpad.net/~openstack Post to : [email protected] Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
