[RFE] Extend l2-extensions-api for flow management
Bug #1563967 reported by
David Shaughnessy
This bug affects 4 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
neutron |
Won't Fix
|
Wishlist
|
Rui Zang |
Bug Description
The l2-extensions-api that merged in Mitaka allows extensions of the OvSNeutronAgent to use the OvS flow table.
This introduces a new challenge of interoperability between extensions creating flows.
As the OvS flow table matches traffic to flows based on packet characteristics in the order of priority assigned to the flow,
it will inevitably result in two extensions using flows that will block the extension that uses the lower priority flows.
Therefore a flow manager or flow pipeline is necessary that will prevent extensions from blocking other flows from matching traffic.
Changed in neutron: | |
assignee: | nobody → Miguel Angel Ajo (mangelajo) |
status: | Confirmed → In Progress |
Changed in neutron: | |
status: | In Progress → Confirmed |
tags: |
added: rfe-approved removed: rfe |
Changed in neutron: | |
milestone: | none → newton-1 |
Changed in neutron: | |
milestone: | newton-1 → newton-2 |
Changed in neutron: | |
milestone: | newton-2 → newton-3 |
Changed in neutron: | |
milestone: | newton-3 → newton-rc1 |
Changed in neutron: | |
milestone: | newton-rc1 → ocata-1 |
Changed in neutron: | |
milestone: | ocata-1 → ocata-2 |
Changed in neutron: | |
milestone: | ocata-2 → ocata-3 |
Changed in neutron: | |
milestone: | ocata-3 → ocata-rc1 |
Changed in neutron: | |
milestone: | ocata-rc1 → pike-1 |
Changed in neutron: | |
milestone: | pike-1 → pike-2 |
Changed in neutron: | |
assignee: | David Shaughnessy (david-shaughnessy) → Rui Zang (rui-zang) |
To post a comment you must log in.
We may want to consider assigning separate table(s) and separate meta-data fields to each feature. This would result in something like (removing cruft for clarity) what is seen in the top-most table0 flow, and the table10 flow :
cookie=abcd, table=0, priority= 65535,reg2= 0x0,in_ port=6 actions= resubmit( ,10) 10,arp, in_port= 6 actions= resubmit( ,24)
cookie=1234, table=0, priority=
cookie=1234, table=0, priority=0 actions=NORMAL
cookie=abcd, table=10, priority=0 actions= load:0x37- >NXM_NX_ REG2[0. .5],mod_ nw_tos: 104,resubmit( ,0)
cookie=1234, table=24, priority= 2,arp,in_ port=6, arp_spa= 10.251. 2.136 actions=NORMAL
All features can then use the highest priority in table0 without contention.