QuantumManager does not correctly handle multiple nova-network nodes

[Mandar Vaze]

Scenario :
========

Two hosts running nova-network process for two networks
HostA for networkA (say 10.0.8.0/24)
HostB for networkB (say 10.0.9.0/24)

Both these networks are associated with a tenant (say Demo)

Expected Result :
==============

When we launch an new VM instance, dnsmasq setup related requests from allocate_for_instance() request should go to each HostA and HostB (for networkA and networkB respectively)

Actual Result :
============
dnsmasq setup related request randomly goes to HostA or HostB

Additional Background :
===================

During init_host() - QuantumManager incorrectly associates self.host for all the networks, so any host associations done via "nova-manage network modify --host" are lost if one of the nova-network restarts. (In this case, both nova-networks are now "owned" by nova-network process that restarted)

So now, QuantumManager can not update dnsmasq settings correctly.

[OpenStack Infra (hudson-openstack)]

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

[dan wendlandt (danwent)]

You're welcome to work on this, but a word of caution that QuantumManager code will likely be removed in Folsom, as we're shifting to a model where Quantum runs without nova-network at all. This is why we haven't been focusing energy on fixing issues like this.

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/6829
Committed: http://github.com/openstack/nova/commit/d901b44fea897a038ce9a8afa32751ab79ffa210
Submitter: Jenkins
Branch: master

commit d901b44fea897a038ce9a8afa32751ab79ffa210
Author: Mandar Vaze <email address hidden>
Date: Thu Apr 26 04:24:26 2012 -0700

    Fixes bug 983024

    enable_dhcp, kill_dhcp and update_dhcp calls are sent to remote
    nova-network, when a network is not associated with current host.

    Change-Id: If7c7c6e58700cc171a8f56669e6455037df7f7e7