Operating System: All
Platform: All

Current implementation of the new design as per Martin:

=============
Martin Bobák: When device connects ofp asks for description (OFPMPDESC). When successfull response is received we ask for meter,group, table and port features. If any of those feature requests (except table features) fails we are not propagating this device furhter. So we don't register its RPC's.
=============

This means that the issue is not just OVS 2.0 switches - but other OpenFlow 1.3 switches which do not support groups or meters cannot be used with the new OpenFlow plugin design. Examples of these could be hardware switches which were implemented OpenFlow 1.0 feature set but are now supporting that feature set over the 1.3 wire protocol (because ONF had declared 1.3 as a long term support version if I remember right).

Hence we need to back out the change described by Martin.

Why do we need to support buggy virtual switch if there is already released fixed version?

(In reply to michal rehak from comment #2)
> Why do we need to support buggy virtual switch if there is already released
> fixed version?

Because the customer has decided for whatever reason to go with it. It is a reality in telco world - getting customers to upgrade something which they perceive as working is not the easiest task.

While not everyone is like one, well known European telco which till recently had 20+ year old equipment and networking in their network, this is still the norm.

In any case, in my opinion, the opposite use case (switch reports stuff as working while it is not) is more important. That is something which happens on a regular basis with all vendors. Getting this implemented automatically covers the opposite case (switch working, but does not report all features).

(In reply to michal rehak from comment #2)
> Why do we need to support buggy virtual switch if there is already released
> fixed version?

Michal - from Martin's description the issue is not just some buggy OVS 2.0 switches - but other OpenFlow 1.3 switches which do not support groups or meters cannot be used with the new OpenFlow plugin design.

Also an example Anil mentioned (https://lists.opendaylight.org/pipermail/openflowplugin-dev/2015-May/003149.html):

ovsdb project will not be able to support compute node running ovs 2.0.2 which is stock install for Ubuntu 14.04 server system. It will force user to explicitly install ovs 2.3.0, which i believe a bit hit to the usability of the plugin and ovsdb solution as such.

https://git.opendaylight.org/gerrit/#/c/21658/

Gerrit url in previous comment should be a solution for this issue.