diff options
| author | Richard Maw <richard.maw@codethink.co.uk> | 2015-03-20 09:52:35 +0000 |
|---|---|---|
| committer | Richard Maw <richard.maw@codethink.co.uk> | 2015-03-20 15:22:29 +0000 |
| commit | d6f8e8b3bfebe053d04423d0f59c050f8ad7dbb3 (patch) | |
| tree | 7c941fc1c8189360eddb9c30c4d0ba230dd3f041 | |
| parent | 6eea03d6aa95e5a89d259c10cab23e419f07fc0a (diff) | |
| download | definitions-d6f8e8b3bfebe053d04423d0f59c050f8ad7dbb3.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.conf | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/openstack/etc/nova/nova.conf b/openstack/etc/nova/nova.conf index b703591f..8f2dee4a 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 |