| 2016-05-16 13:34:57 |
Mohankumar |
bug |
|
|
added bug |
| 2016-05-16 13:37:15 |
Mohankumar |
description |
In current flow_classifiers API design , If multiple flow_classifiers are configured in port chain ,the classification rule applied on the basis of order of configuration . If admin need to change the flow classifier order , admin have to delete existing chain and re-config new service chain .
This proposal introduce new "priority” field in flow-classifier to correct/update ordering of flows.
Reference :
OVS already supporting this priority field in flow rules .
http://openvswitch.org/support/dist-docs/ovs-ofctl.8.txt
priority=value
The priority at which a wildcarded entry will match in compari‐
son to others. value is a number between 0 and 65535, inclu‐
sive. A higher value will match before a lower one. An exact-
match entry will always have priority over an entry containing
wildcards, so it has an implicit priority value of 65535. When
adding a flow, if the field is not specified, the flow's prior‐
ity will default to 32768.
OpenFlow leaves behavior undefined when two or more flows with
the same priority can match a single packet. Some users expect
``sensible'' behavior, such as more specific flows taking prece‐
dence over less specific flows, but OpenFlow does not specify
this and Open vSwitch does not implement it. Users should
therefore take care to use priorities to ensure the behavior
that they expect. |
In current flow_classifiers API design , If multiple flow_classifiers are configured in port chain ,the classification rule applied on the basis of order of configuration . If admin need to change the flow classifier order , admin have to delete existing chain and re-config new service chain .
This proposal introduce new "priority” field in flow-classifier to correct/update ordering of flows.
Reference :
============
OVS already supporting this priority field in flow rules .
http://openvswitch.org/support/dist-docs/ovs-ofctl.8.txt
priority=value
The priority at which a wildcarded entry will match in comparison to others. value is a number between 0 and 65535, inclusive. A higher value will match before a lower one. An exact match entry will always have priority over an entry containing wildcards, so it has an implicit priority value of 65535. When adding a flow, if the field is not specified, the flow's priority will default to 32768.
OpenFlow leaves behavior undefined when two or more flows with the same priority can match a single packet. Some users expect ``sensible'' behavior, such as more specific flows taking precedence over less specific flows, but OpenFlow does not specify this and Open vSwitch does not implement it. Users should therefore take care to use priorities to ensure the behavior that they expect. |
|
| 2016-05-16 14:03:42 |
Mohankumar |
networking-sfc: status |
New |
In Progress |
|
| 2016-05-19 17:09:22 |
Mohankumar |
description |
In current flow_classifiers API design , If multiple flow_classifiers are configured in port chain ,the classification rule applied on the basis of order of configuration . If admin need to change the flow classifier order , admin have to delete existing chain and re-config new service chain .
This proposal introduce new "priority” field in flow-classifier to correct/update ordering of flows.
Reference :
============
OVS already supporting this priority field in flow rules .
http://openvswitch.org/support/dist-docs/ovs-ofctl.8.txt
priority=value
The priority at which a wildcarded entry will match in comparison to others. value is a number between 0 and 65535, inclusive. A higher value will match before a lower one. An exact match entry will always have priority over an entry containing wildcards, so it has an implicit priority value of 65535. When adding a flow, if the field is not specified, the flow's priority will default to 32768.
OpenFlow leaves behavior undefined when two or more flows with the same priority can match a single packet. Some users expect ``sensible'' behavior, such as more specific flows taking precedence over less specific flows, but OpenFlow does not specify this and Open vSwitch does not implement it. Users should therefore take care to use priorities to ensure the behavior that they expect. |
In current flow_classifiers API design ,
[1] If multiple flow_classifiers are configured in port chain ,the classification rule applied on the basis of order of configuration . If admin need to change the flow classifier order , admin have to delete existing chain and re-config new service chain .
[2] if all the classifier fields matches still we can use this priority
field to choose which flow_classifier to be applied first (i.e) user first want to treat the tcp traffic from same source and destination VM and UDP next .
This proposal introduce new "priority” field in flow-classifier to correct/update ordering of flows.
Reference :
============
OVS already supporting this priority field in flow rules .
http://openvswitch.org/support/dist-docs/ovs-ofctl.8.txt
priority=value
The priority at which a wildcarded entry will match in comparison to others. value is a number between 0 and 65535, inclusive. A higher value will match before a lower one. An exact match entry will always have priority over an entry containing wildcards, so it has an implicit priority value of 65535. When adding a flow, if the field is not specified, the flow's priority will default to 32768.
OpenFlow leaves behavior undefined when two or more flows with the same priority can match a single packet. Some users expect ``sensible'' behavior, such as more specific flows taking precedence over less specific flows, but OpenFlow does not specify this and Open vSwitch does not implement it. Users should therefore take care to use priorities to ensure the behavior that they expect. |
|
| 2016-05-19 17:10:31 |
Mohankumar |
description |
In current flow_classifiers API design ,
[1] If multiple flow_classifiers are configured in port chain ,the classification rule applied on the basis of order of configuration . If admin need to change the flow classifier order , admin have to delete existing chain and re-config new service chain .
[2] if all the classifier fields matches still we can use this priority
field to choose which flow_classifier to be applied first (i.e) user first want to treat the tcp traffic from same source and destination VM and UDP next .
This proposal introduce new "priority” field in flow-classifier to correct/update ordering of flows.
Reference :
============
OVS already supporting this priority field in flow rules .
http://openvswitch.org/support/dist-docs/ovs-ofctl.8.txt
priority=value
The priority at which a wildcarded entry will match in comparison to others. value is a number between 0 and 65535, inclusive. A higher value will match before a lower one. An exact match entry will always have priority over an entry containing wildcards, so it has an implicit priority value of 65535. When adding a flow, if the field is not specified, the flow's priority will default to 32768.
OpenFlow leaves behavior undefined when two or more flows with the same priority can match a single packet. Some users expect ``sensible'' behavior, such as more specific flows taking precedence over less specific flows, but OpenFlow does not specify this and Open vSwitch does not implement it. Users should therefore take care to use priorities to ensure the behavior that they expect. |
This proposal introduce new "priority” field in flow-classifier to correct/update ordering of flows. By considering below two scenarios
[1] If multiple flow_classifiers are configured in port chain ,the classification rule applied on the basis of order of configuration . If admin need to change the flow classifier order , admin have to delete existing chain and re-config new service chain .
[2] if all the classifier fields matches still we can use this priority
field to choose which flow_classifier to be applied first (i.e) user first want to treat the tcp traffic from same source and destination VM and UDP next .
This proposal introduce new "priority” field in flow-classifier to correct/update ordering of flows.
Reference :
============
OVS already supporting this priority field in flow rules .
http://openvswitch.org/support/dist-docs/ovs-ofctl.8.txt
priority=value
The priority at which a wildcarded entry will match in comparison to others. value is a number between 0 and 65535, inclusive. A higher value will match before a lower one. An exact match entry will always have priority over an entry containing wildcards, so it has an implicit priority value of 65535. When adding a flow, if the field is not specified, the flow's priority will default to 32768.
OpenFlow leaves behavior undefined when two or more flows with the same priority can match a single packet. Some users expect ``sensible'' behavior, such as more specific flows taking precedence over less specific flows, but OpenFlow does not specify this and Open vSwitch does not implement it. Users should therefore take care to use priorities to ensure the behavior that they expect. |
|
| 2016-05-19 17:10:39 |
Mohankumar |
description |
This proposal introduce new "priority” field in flow-classifier to correct/update ordering of flows. By considering below two scenarios
[1] If multiple flow_classifiers are configured in port chain ,the classification rule applied on the basis of order of configuration . If admin need to change the flow classifier order , admin have to delete existing chain and re-config new service chain .
[2] if all the classifier fields matches still we can use this priority
field to choose which flow_classifier to be applied first (i.e) user first want to treat the tcp traffic from same source and destination VM and UDP next .
This proposal introduce new "priority” field in flow-classifier to correct/update ordering of flows.
Reference :
============
OVS already supporting this priority field in flow rules .
http://openvswitch.org/support/dist-docs/ovs-ofctl.8.txt
priority=value
The priority at which a wildcarded entry will match in comparison to others. value is a number between 0 and 65535, inclusive. A higher value will match before a lower one. An exact match entry will always have priority over an entry containing wildcards, so it has an implicit priority value of 65535. When adding a flow, if the field is not specified, the flow's priority will default to 32768.
OpenFlow leaves behavior undefined when two or more flows with the same priority can match a single packet. Some users expect ``sensible'' behavior, such as more specific flows taking precedence over less specific flows, but OpenFlow does not specify this and Open vSwitch does not implement it. Users should therefore take care to use priorities to ensure the behavior that they expect. |
This proposal introduce new "priority” field in flow-classifier to correct/update ordering of flows. By considering below two scenarios
[1] If multiple flow_classifiers are configured in port chain ,the classification rule applied on the basis of order of configuration . If admin need to change the flow classifier order , admin have to delete existing chain and re-config new service chain .
[2] if all the classifier fields matches still we can use this priority
field to choose which flow_classifier to be applied first (i.e) user first want to treat the tcp traffic from same source and destination VM and UDP next .
Reference :
============
OVS already supporting this priority field in flow rules .
http://openvswitch.org/support/dist-docs/ovs-ofctl.8.txt
priority=value
The priority at which a wildcarded entry will match in comparison to others. value is a number between 0 and 65535, inclusive. A higher value will match before a lower one. An exact match entry will always have priority over an entry containing wildcards, so it has an implicit priority value of 65535. When adding a flow, if the field is not specified, the flow's priority will default to 32768.
OpenFlow leaves behavior undefined when two or more flows with the same priority can match a single packet. Some users expect ``sensible'' behavior, such as more specific flows taking precedence over less specific flows, but OpenFlow does not specify this and Open vSwitch does not implement it. Users should therefore take care to use priorities to ensure the behavior that they expect. |
|
| 2016-05-19 17:27:01 |
Mohankumar |
description |
This proposal introduce new "priority” field in flow-classifier to correct/update ordering of flows. By considering below two scenarios
[1] If multiple flow_classifiers are configured in port chain ,the classification rule applied on the basis of order of configuration . If admin need to change the flow classifier order , admin have to delete existing chain and re-config new service chain .
[2] if all the classifier fields matches still we can use this priority
field to choose which flow_classifier to be applied first (i.e) user first want to treat the tcp traffic from same source and destination VM and UDP next .
Reference :
============
OVS already supporting this priority field in flow rules .
http://openvswitch.org/support/dist-docs/ovs-ofctl.8.txt
priority=value
The priority at which a wildcarded entry will match in comparison to others. value is a number between 0 and 65535, inclusive. A higher value will match before a lower one. An exact match entry will always have priority over an entry containing wildcards, so it has an implicit priority value of 65535. When adding a flow, if the field is not specified, the flow's priority will default to 32768.
OpenFlow leaves behavior undefined when two or more flows with the same priority can match a single packet. Some users expect ``sensible'' behavior, such as more specific flows taking precedence over less specific flows, but OpenFlow does not specify this and Open vSwitch does not implement it. Users should therefore take care to use priorities to ensure the behavior that they expect. |
This proposal is to introduce new "priority” field in flow-classifier to correct/update ordering of flows. By considering below two scenarios
[1] If multiple flow_classifiers are configured in port chain ,the classification rule applied on the basis of order of configuration . If admin need to change the flow classifier order , admin have to delete existing chain and re-config new service chain .
[2] if all the classifier fields matches still we can use this priority
field to choose which flow_classifier to be applied first (i.e) user first want to treat the tcp traffic from same source and destination VM and UDP next .
Reference :
============
OVS already supporting this priority field in flow rules .
http://openvswitch.org/support/dist-docs/ovs-ofctl.8.txt
priority=value
The priority at which a wildcarded entry will match in comparison to others. value is a number between 0 and 65535, inclusive. A higher value will match before a lower one. An exact match entry will always have priority over an entry containing wildcards, so it has an implicit priority value of 65535. When adding a flow, if the field is not specified, the flow's priority will default to 32768.
OpenFlow leaves behavior undefined when two or more flows with the same priority can match a single packet. Some users expect ``sensible'' behavior, such as more specific flows taking precedence over less specific flows, but OpenFlow does not specify this and Open vSwitch does not implement it. Users should therefore take care to use priorities to ensure the behavior that they expect. |
|
| 2017-09-25 16:00:40 |
Igor D.C. |
bug |
|
|
added subscriber Igor Duarte Cardoso |
| 2017-10-09 18:04:30 |
Louis Fourie |
networking-sfc: importance |
Undecided |
Low |
|
