OVS agent firewall is not configurable
Bug #1618507 reported by
Brent Eagles
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| tripleo |
Fix Released
|
Medium
|
Brent Eagles | ||
Bug Description
New firewall support was added to the neutron OVS agent that does not rely on interposing a linux bridge between VIFs and the integration, reducing the number of "hops" we introduce into the network path. While the puppet modules support configuring the agent's firewall driver, we are missing the option in the TripleO heat templates.
| Changed in tripleo: | |
| assignee: | nobody → Brent Eagles (beagles) |
| status: | New → In Progress |
| Changed in tripleo: | |
| status: | In Progress → Confirmed |
| status: | Confirmed → In Progress |
| importance: | Undecided → Medium |
| milestone: | none → newton-rc1 |
Revision history for this message
| Steven Hardy (shardy) wrote | #1 |
Revision history for this message
| Brent Eagles (beagles) wrote | #2 |
Revision history for this message
| OpenStack Infra (hudson-openstack) wrote Fix merged to tripleo-heat-templates (master) | #3 |
| Changed in tripleo: | |
| status: | In Progress → Fix Released |
To post a comment you must log in.
Any patch planned for RC1?
If not I'll probably defer this to ocata-1 as it sounds like folks can work around it via ExtraConfig overrides?