summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorRichard Maw <richard.maw@codethink.co.uk>2015-03-20 09:52:35 (GMT)
committerRichard Maw <richard.maw@codethink.co.uk>2015-03-20 09:52:35 (GMT)
commite135c7bc5eeeb65814ddf541aa7dcc310b14d528 (patch)
treeb67c885d8ea855be70cea3cfd2778ddcbdd95afc
parentca722e669ab16b932f614dbf3b5ce5421b82dcfa (diff)
downloaddefinitions-baserock/richardmaw/openstack-v4/reliability.tar.gz
openstack: Disable nova firewall managementbaserock/richardmaw/openstack-v4/reliability
This should be handled by neutron, and except for the mis-configuration, it should have been. However, since both neutron and nova were configured to handle firewalling, they would both install their firewall rules into iptables, and it would be random which one would be used as either service is likely to start before the other and install their hook first. The result being that we'd randomly not be able to reach VMs after a reboot, unless we'd installed the same firewall rules in both nova and neutron.
-rw-r--r--openstack/etc/nova/nova.conf2
1 files changed, 1 insertions, 1 deletions
diff --git a/openstack/etc/nova/nova.conf b/openstack/etc/nova/nova.conf
index 0d6cdf9..c9ff85f 100644
--- a/openstack/etc/nova/nova.conf
+++ b/openstack/etc/nova/nova.conf
@@ -253,7 +253,7 @@ dhcpbridge_flagfile=/etc/nova/nova.conf
#dhcpbridge=$bindir/nova-dhcpbridge
#dhcp_lease_time=120
# Firewall driver (defaults to hypervisor specific iptables driver) (string value)
-firewall_driver=nova.virt.libvirt.firewall.IptablesFirewallDriver
+#firewall_driver=nova.virt.libvirt.firewall.IptablesFirewallDriver
# Interface for public IP addresses (default: eth0) (string value)
#public_interface=br-ext
public_interface=eth0