FWaaS changes to support Distributed Virtual Router(DVR)
The DVR model breaks basic FWaaS implementation as FWaaS relies on seeing both directions of traffic (stageful) at the router programmed with Firewall rules. DVR by design distributes routing across compute nodes to achieve scalability and this has unfavorable consequences for FWaaS. The first step is to at least ensure that we have an L3 Perimeter Firewall working for the North-South traffic use case.
Blueprint information
- Status:
- Complete
- Approver:
- Kyle Mestery
- Priority:
- High
- Drafter:
- Sridar Kandaswamy
- Direction:
- Approved
- Assignee:
- Sridar Kandaswamy
- Definition:
- Approved
- Series goal:
- Accepted for juno
- Implementation:
-
Implemented
- Milestone target:
-
2014.2
- Started by
- Sridar Kandaswamy
- Completed by
- Kyle Mestery
Related branches
Related bugs
Sprints
Whiteboard
20-July (mestery): Juno-3 as high priority.
You should not set a milestone target unless the blueprint has been properly prioritized by the project drivers.
(This is an automated message)
Gerrit topic: https:/
Addressed by: https:/
Specification for FWaaS changes for DVR
Addressed by: https:/
Changes to support FWaaS in a DVR based environment
Gerrit topic: https:/
Addressed by: https:/
Set firewall state to CREATED when dealing with DVR
