[compute] configuration should be changed to make the live migration feature working

[andrew yongjoon kong]

The openstack_cookbook_compute's setting for the VNC and config_disk is blocking vm migration.

if the VNClistening port is bind to specified IP and VM is migrated, it try to bind listening IP to source servers.
that's blocking live migration.

and using config_disk has also issue.
It's based on Openstack's bug.
config_disk is always turned on though specified as false. and the problem from this is that it's also blocking live-migration.(it cannot find config_disk at destinattion host)

[OpenStack Infra (hudson-openstack)]

Fix proposed to branch: master
Review: https://review.openstack.org/52263

[Mark Vanderwiel (vanderwl)]

Note: patch for live migration options is now in: https://review.openstack.org/#/c/102569/
I think this bug needs to be re-confirmed and more up to date details added.

[kraig (kamador)]

I can't comment on the config_disk setting but we were able to use live migration with NFS storage by changing the vncserver_listen address to 0.0.0.0. We still need vncserver_proxyclient_address to be set to the IP of the VM host machine to for consoles. vncserver_listen needs to be 0.0.0.0 since the target host will try to bind this IP.

These are the lines that need to be different: https://github.com/stackforge/cookbook-openstack-compute/blob/master/templates/default/nova.conf.erb#L194-195

The issue we are now experiencing is that the nova-common recipe forces these two to be the same. I can submit a patch to fix this, would adding a vnc_proxyclient_bind over here be acceptable? https://github.com/stackforge/cookbook-openstack-compute/blob/master/recipes/nova-common.rb#L98