X-Git-Url: https://pintos-os.org/cgi-bin/gitweb.cgi?a=blobdiff_plain;f=NEWS;h=675e4c4fa94bbc968693a35af3bf9ec30141ad1a;hb=4dd1e3cabbd109e322553a7b3d4c875e697d2069;hp=fa78da870ca1e161ce8bf45a393a46040c57cbf0;hpb=a206a8c6254e4079560e8449787605a28e9059dd;p=openvswitch diff --git a/NEWS b/NEWS index fa78da87..675e4c4f 100644 --- a/NEWS +++ b/NEWS @@ -1,3 +1,10 @@ +port-v1.4.0 +------------------------ + - OpenFlow: + - Added support for querying, modifying, and deleting flows + based on flow cookie when using NXM. + + v1.4.0 - xx xxx xxxx ------------------------ - New "VLAN splinters" feature to work around buggy device drivers @@ -16,6 +23,8 @@ v1.4.0 - xx xxx xxxx now be properly mirrored for any flows, regardless of their actions. - Track packet and byte statistics sent on mirrors. + - The sFlow implementation can now usually infer the correct agent + device instead of having to be told explicitly. - ovs-appctl: - New "fdb/flush" command to flush bridge's MAC learning table. - ovs-test: @@ -23,9 +32,16 @@ v1.4.0 - xx xxx xxxx and connectivity issues. This tool currently is not included in RH or Xen packages. - RHEL packaging now supports integration with Red Hat network scripts. + - bonding: + - Post 1.4.*, OVS will be changing the default bond mode from balance-slb + to active-backup. SLB bonds carry significant risks with them + (documented vswitchd/INTERNALS) which we want to prevent unsuspecting + users from running into. Users are advised to update any scripts or + configuration which may be negatively impacted by explicitly setting + the bond mode which they want to use. -v1.3.0 - xx xxx xxxx +v1.3.0 - 09 Dec 2011 ------------------------ - OpenFlow: - Added an OpenFlow extension which allows the "output" action to accept @@ -55,8 +71,8 @@ v1.3.0 - xx xxx xxxx via "ip_frag" in ovs-ofctl). - New ovs-ofctl "get-frags" and "set-frags" commands to get and set fragment handling policy. - - CAPWAP tunneling now supports an extension to transport a 64-key. By - default it remains compatible with the old version and other + - CAPWAP tunneling now supports an extension to transport a 64-bit key. + By default it remains compatible with the old version and other standards-based implementations. - Flow setups are now processed in a round-robin manner across ports to prevent any single client from monopolizing the CPU and conducting