[ovs-dev] [PATCH] documentation: Windows support multiple VTEP/NICs
Multiple VTEP and multiple physical NICs are supported on Hyper-V now. Update the documentation Signed-off-by: Alin Gabriel Serdean --- 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 YESYESYES NO IPFIX 3.10 YESYES NO Set actionYESYESYES PARTIAL -NIC Bonding YESYESYES NO -Multiple VTEPsYESYESYES NO +NIC Bonding YESYESYES YES +Multiple VTEPsYESYESYES 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 d...@openvswitch.org https://mail.openvswitch.org/mailman/listinfo/ovs-dev
Re: [ovs-dev] [PATCH] documentation: Windows support multiple VTEP/NICs
Acked-by: Sairam Venugopal On 1/26/17, 6:30 PM, "ovs-dev-boun...@openvswitch.org on behalf of Alin Serdean" wrote: >Multiple VTEP and multiple physical NICs are supported on Hyper-V now. >Update the documentation > >Signed-off-by: Alin Gabriel Serdean >--- >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 YESYESYES NO > IPFIX 3.10 YESYES NO > Set actionYESYESYES PARTIAL >-NIC Bonding YESYESYES NO >-Multiple VTEPsYESYESYES NO >+NIC Bonding YESYESYES YES >+Multiple VTEPsYESYESYES 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 >d...@openvswitch.org >https://urldefense.proofpoint.com/v2/url?u=https-3A__mail.openvswitch.org_mailman_listinfo_ovs-2Ddev&d=DwICAg&c=uilaK90D4TOVoH58JNXRgQ&r=Z6vowHUOjP5ysP_g372c49Nqc1vEKqHKNBkR5Q5Z7uo&m=T_rrUyNsK92gO-mgKelX89Gl9X7BN9l6R492H7PrFUg&s=cSew8mJ8O124153-iYqpdbkMzTjPsaPrD1UJS9_Kx2k&e= > ___ dev mailing list d...@openvswitch.org https://mail.openvswitch.org/mailman/listinfo/ovs-dev
Re: [ovs-dev] [PATCH] documentation: Windows support multiple VTEP/NICs
Applied, thanks Sairam and Alin! On Fri, Jan 27, 2017 at 07:58:09AM +, Sairam Venugopal wrote: > Acked-by: Sairam Venugopal > > > > > > On 1/26/17, 6:30 PM, "ovs-dev-boun...@openvswitch.org on behalf of Alin > Serdean" aserd...@cloudbasesolutions.com> wrote: > > >Multiple VTEP and multiple physical NICs are supported on Hyper-V now. > >Update the documentation > > > >Signed-off-by: Alin Gabriel Serdean > >--- > >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 YESYESYES NO > > IPFIX 3.10 YESYES NO > > Set actionYESYESYES PARTIAL > >-NIC Bonding YESYESYES NO > >-Multiple VTEPsYESYESYES NO > >+NIC Bonding YESYESYES YES > >+Multiple VTEPsYESYESYES 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 > >d...@openvswitch.org > >https://urldefense.proofpoint.com/v2/url?u=https-3A__mail.openvswitch.org_mailman_listinfo_ovs-2Ddev&d=DwICAg&c=uilaK90D4TOVoH58JNXRgQ&r=Z6vowHUOjP5ysP_g372c49Nqc1vEKqHKNBkR5Q5Z7uo&m=T_rrUyNsK92gO-mgKelX89Gl9X7BN9l6R492H7PrFUg&s=cSew8mJ8O124153-iYqpdbkMzTjPsaPrD1UJS9_Kx2k&e= > > > ___ > dev mailing list > d...@openvswitch.org > https://mail.openvswitch.org/mailman/listinfo/ovs-dev ___ dev mailing list d...@openvswitch.org https://mail.openvswitch.org/mailman/listinfo/ovs-dev
