Direction support for Firewall Policy

Registered by Slawek Kaplonski on 2015-03-21

In the current specification it is not possible to define a firewall policy for a specific (ingress/egress) direction. By default, policy rules will be applied for both ingress and egress traffic. This is inefficient as the policy rules will be enforced to all incoming and outgoing traffics even if it is not desired.This BP propose a solution for associating firewall policy with a specific direction.

Blueprint information

Status:
Complete
Approver:
Kyle Mestery
Priority:
Undefined
Drafter:
Slawek Kaplonski
Direction:
Needs approval
Assignee:
vikram.choudhary
Definition:
Obsolete
Series goal:
None
Implementation:
Deferred
Milestone target:
None
Completed by
Armando Migliaccio on 2015-11-09

Related branches

Sprints

Whiteboard

Nov-09-2015(armax): If someone is interested in pursuing it, this must be re-submitted according to guidelines defined in [1]. That said, firewall is being overhauled, so I am not sure this can be simply resumed as is.

[1] http://docs.openstack.org/developer/neutron/policies/blueprints.html

-----------------

Gerrit topic: https://review.openstack.org/#q,topic:bp/fwaas-rules-directions,n,z

Addressed by: https://review.openstack.org/171340
    fwaas rules directions

(?)

Work Items

This blueprint contains Public information 
Everyone can see this information.