[OVSDB-109] Vlan flows needs merging from traditional rules to a single L2Fwding Service. Similar to OVSDB-107 Created: 21/Sep/14 Updated: 24/Sep/14 Resolved: 24/Sep/14 |
|
| Status: | Resolved |
| Project: | ovsdb |
| Component/s: | openstack.net-virt-providers |
| Affects Version/s: | unspecified |
| Fix Version/s: | None |
| Type: | Bug | ||
| Reporter: | Madhu Venugopal | Assignee: | Sam Hague |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
Operating System: All |
||
| Issue Links: |
|
||||||||
| External issue ID: | 2013 | ||||||||
| Description |
|
Traditionally Vlan flows were installed in Table 10 and Table 20 after classified in Table 0. But with the service pipeline architecture, this has changed and Table 110 (L2Fwd Service table) needs to have this intelligence.
Vlan needs to be addressed as well. |
| Comments |
| Comment by Dave Tucker [ 24/Sep/14 ] |
| Comment by Sam Hague [ 24/Sep/14 ] |