• <var id="lvoaz"></var>
      1. <output id="lvoaz"></output>

          OpenFlow 1.1+ support in Open vSwitch

          Open vSwitch support for OpenFlow 1.1 and beyond is a work in progress. This file describes the work still to be done.

          The Plan

          OpenFlow version support is not a build-time option. A single build of Open vSwitch must be able to handle all supported versions of OpenFlow. Ideally, even at runtime it should be able to support all protocol versions at the same time on different OpenFlow bridges (and perhaps even on the same bridge).

          At the same time, it would be a shame to litter the core of the OVS code with lots of ugly code concerned with the details of various OpenFlow protocol versions.

          The primary approach to compatibility is to abstract most of the details of the differences from the core code, by adding a protocol layer that translates between OF1.x and a slightly higher-level abstract representation. The core of this approach is the many struct ofputil_* structures in lib/ofp-util.h.

          As a consequence of this approach, OVS cannot use OpenFlow protocol definitions that closely resemble those in the OpenFlow specification, because openflow.h in different versions of the OpenFlow specification defines the same identifier with different values. Instead, openflow-common.h contains definitions that are common to all the specifications and separate protocol version-specific headers contain protocol-specific definitions renamed so as not to conflict, e.g. OFPAT10ENQUEUE and OFPAT11ENQUEUE for the OpenFlow 1.0 and 1.1 values for OFPATENQUEUE. Generally, in cases of conflict, the protocol layer will define a more abstract OFPUTIL* or struct ofputil_*.

          Here are the current approaches in a few tricky areas:

          OpenFlow 1.1

          The list of remaining work items for OpenFlow 1.1 is below. It is probably incomplete.

          OpenFlow 1.2

          OpenFlow 1.2 support requires OpenFlow 1.1 as a prerequisite. All the additional work specific to Openflow 1.2 are complete. (This is based on the change log at the end of the OF1.2 spec. I didn't compare the specs carefully yet.)

          OpenFlow 1.3

          OpenFlow 1.3 support requires OpenFlow 1.2 as a prerequisite, plus the following additional work. (This is based on the change log at the end of the OF1.3 spec, reusing most of the section titles directly. I didn't compare the specs carefully yet.)

          OpenFlow 1.4 & ONF Extensions for 1.3.X Pack1

          The following features are both defined as a set of ONF Extensions for 1.3 and integrated in 1.4. When defined as an ONF Extension for 1.3, the feature is using the Experimenter mechanism with the ONF Experimenter ID. When defined integrated in 1.4, the feature use the standard OpenFlow structures (for example defined in openflow-1.4.h). The two definitions for each feature are independant and can exist in parallel in OVS.

          OpenFlow 1.4 only

          Those features are those only available in OpenFlow 1.4, other OpenFlow 1.4 features are listed in the previous section.

          OpenFlow 1.5 & ONF Extensions for 1.3.X Pack2

          The following features are both defined as a set of ONF Extensions for 1.3 and integrated in 1.5. Note that this list is not definitive as those are not yet published. When defined as an ONF Extension for 1.3, the feature is using the Experimenter mechanism with the ONF Experimenter ID. When defined integrated in 1.5, the feature use the standard OpenFlow structures (for example defined in openflow-1.5.h). The two definitions for each feature are independant and can exist in parallel in OVS.

          OpenFlow 1.5 only

          Those features are those only available in OpenFlow 1.5, other OpenFlow 1.5 features are listed in the previous section. Note that this list is not definitive as OpenFlow 1.5 is not yet published.

          General

          How to contribute

          If you plan to contribute code for a feature, please let everyone know on ovs-dev before you start work. This will help avoid duplicating work.

          Please consider the following:

          Bug Reporting

          Please report problems to bugs@openvswitch.org.

          现金李逵劈鱼