Default behavior of Security groups egress handling has different semantics than ingress

[Tomoe Sugihara]

Currently, the default behavior of egress is invisible and has different semantics than egress one. Since the default behavior is hidden from the user, it is counter intuitive and hard to figure out what's happening under the hood.
It'd be better to add default explicit allow-all-egress rule to make it semantically symmetric to ingress.

For more details about the issue, there's a discussion thread in the email list here:
http://lists.openstack.org/pipermail/openstack-dev/2013-February/005982.html

[dan wendlandt (danwent)]

https://review.openstack.org/#/c/23264/

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/23264
Committed: http://github.com/openstack/quantum/commit/7e26074be5dbe1a9b629b035da46e7122c4c34c9
Submitter: Jenkins
Branch: master

commit 7e26074be5dbe1a9b629b035da46e7122c4c34c9
Author: Tomoe Sugihara <email address hidden>
Date: Fri Mar 1 20:19:13 2013 +0900

    Populate default explicit allow rules for egress

    This way, the default behavior becomes clear and
    symmetric to ingress processing.

    Fixes bug 1143283

    Change-Id: Id6496819aaceda50def597739f7872653d5b2e00