diff options
| author | Soren Hansen <soren.hansen@rackspace.com> | 2010-10-03 18:33:31 +0000 |
|---|---|---|
| committer | Tarmac <> | 2010-10-03 18:33:31 +0000 |
| commit | 44134b3fb48bedc38a49ac4b516796329fd7b08a (patch) | |
| tree | 8c78f2be51179b6c0be3b92a7d081d5b44f054e6 /bin/stack | |
| parent | 4d13a8554459638387d772a23fffe6aaaab3348d (diff) | |
| parent | 4e45f9472a95207153d32c88df8396c633c67a5d (diff) | |
| download | nova-44134b3fb48bedc38a49ac4b516796329fd7b08a.tar.gz nova-44134b3fb48bedc38a49ac4b516796329fd7b08a.tar.xz nova-44134b3fb48bedc38a49ac4b516796329fd7b08a.zip | |
Fixes to address the following issues:
* nova-network no longer refrains from configuring bridges if it finds them already created. This solves a race condition with nova-network and nova-compute running on the same box. If nova-compute happened to do its network config first, nova-network would find the bridge already created and assume it was correctly setup. If nova-network got there first, it would apply the correct IP configuration to the interface. The assumption is that no harm will be done by reapplying the correct IP configuration, so we no longer make this check before doing so.
* nova-network does not use persistent network configuration (like putting stuff in /etc/network/interfaces), so it needs to check at boot time whether it's already set as a network's designated network node and do the appropriate configuration.
* If installed, dnsmasq wouldn't find nova-dhcpbridge properly (it would look for it in /usr/lib/python2.6/blahblahblha). Add a flag to specify its location (and make use of it in the packaging).
* dnsmasq needs to be able to read the dhcp config written by nova. dnsmasq runs as user "nobody", so chmod 644 the config file so that it can be read.
* dnsmasq needs to be sent a SIGHUP to reread its config. Wrap this call in sudo, because we may be running as non-root.
Diffstat (limited to 'bin/stack')
0 files changed, 0 insertions, 0 deletions
