There is yet approach on multi-host scheme with VlanManager for solve problem
with default gateway in VM. Look at the mechanism:
1. run live_migration from node-1 to node-2
2. reconfigure dnsmasq and drop lease on node-1
3. reconfigure dnsmasq on node-2
Realization by hands on test stand. At fir
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.
There was a thread about this in December:
http://www.mail-archive.com/openstack@lists.launchpad.net/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
Alternate approach:
Give all hosts the .1 gateway address:
diff --git a/nova/network/manager.py b/nova/network/manager.py
index 2d62581..e6a0ba8 100644
--- a/nova/network/manager.py
+++ b/nova/network/manager.py
@@ -477,8 +477,7 @@ class NetworkManager(manager.SchedulerDependentManager):
def
Dear all.
We want to use Kei's live migration feature while adopting Vish’s
multi_host network configuration, but there are problems as noted below by
Vish.
http://etherpad.openstack.org/live-migration-with-multi-host
Is there any way to change the gateway of a VM instance?
(i.e. is it possible t
5 matches
Mail list logo
