Multiple VTEP and multiple physical NICs are supported on Hyper-V now. Update the documentation
Signed-off-by: Alin Gabriel Serdean <[email protected]> --- Intended for master and branch-2.7 --- Documentation/faq/releases.rst | 8 ++------ 1 file changed, 2 insertions(+), 6 deletions(-) diff --git a/Documentation/faq/releases.rst b/Documentation/faq/releases.rst index f9cb2e9..fcff5c3 100644 --- a/Documentation/faq/releases.rst +++ b/Documentation/faq/releases.rst @@ -118,18 +118,14 @@ Q: Are all features available with all datapaths? sFlow YES YES YES NO IPFIX 3.10 YES YES NO Set action YES YES YES PARTIAL - NIC Bonding YES YES YES NO - Multiple VTEPs YES YES YES NO + NIC Bonding YES YES YES YES + Multiple VTEPs YES YES YES YES ===================== ============== ============== ========= ======= Do note, however: * Only a limited set of flow fields is modifiable via the set action by the Hyper-V datapath. - * The Hyper-V datapath only supports one physical NIC per datapath. This is - why bonding is not supported. - * The Hyper-V datapath can have at most one IP address configured as a - tunnel endpoint. The following table lists features that do not *directly* impact an Open vSwitch user, e.g. because their absence can be hidden by the ofproto layer -- 2.10.2.windows.1 _______________________________________________ dev mailing list [email protected] https://mail.openvswitch.org/mailman/listinfo/ovs-dev
