4452f3a83b
The following commit 7e26074b changed the previous behavior of quantum security groups by explicitly adding egress rules to the security profile. When these rules are removed the vm is no longer able to send traffic out. This patch adds these rules for NVP. One thing to note in the patch is that now a bunk rule of IPv4 127.0.0.1/32 is added to each security profile. The reason for this is by default NVP security profiles allow all egress traffic until a rule is added and then it just lets traffic matching those rules out. Adding this bunk rule achieves this behavior that quantum now uses. Fixes bug 1150378 Change-Id: I005880fcf39d539ae99be428d75c43cc0b39a7b6
# -- Welcome! You have come across a cloud computing network fabric controller. It has identified itself as "Quantum." It aims to tame your (cloud) networking! # -- External Resources: The homepage for Quantum is: http://launchpad.net/quantum . Use this site for asking for help, and filing bugs. Code is available on github at <http://github.com/openstack/quantum>. The latest and most in-depth documentation on how to use Quantum is available at: <http://docs.openstack.org>. This includes: Quantum Administrator Guide http://docs.openstack.org/trunk/openstack-network/admin/content/ Quantum API Reference: http://docs.openstack.org/api/openstack-network/2.0/content/ The start of some developer documentation is available at: http://wiki.openstack.org/QuantumDevelopment For help using or hacking on Quantum, you can send mail to <mailto:openstack-dev@lists.openstack.org>.