summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorRichard Maw <richard.maw@codethink.co.uk>2015-03-20 09:52:35 +0000
committerRichard Maw <richard.maw@codethink.co.uk>2015-03-20 16:06:23 +0000
commitf9852d6a50ab56ebce951675d4a162b033d6dd42 (patch)
treeeb7c719a4e915745aaa5e836b25643c32a43d299
parent02f0fbe6cf19ed0645df23e14cab16d61a400661 (diff)
downloaddefinitions-f9852d6a50ab56ebce951675d4a162b033d6dd42.tar.gz
openstack: Disable nova firewall management
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 8b3522b5..30f265aa 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