On Tue, 26 Feb 2013 19:18:44 +0100 Piotr Niedzwiedz <[email protected]> wrote:
> I will change my OVS version, but right now want to stay with OF1.0 to > be able > to fix this issue. > > I started adding support of OF1.0 into tests cases, but I noticed, that > ofproto_v1_0_parser.OFPMatch and ofproto_v1_2_parser.OFPMatch don't have the > same interface, > moreover theirs constructors are different too :( That's how OF specs are defined. > It is not nice feature, because in most RYU applications which I've seen > people just > don't care about it, and just use ofproto_parser from datapath object. > > I propose to fix those tests in one of following ways: > a) change test_*.py files to be more OFversion aware (some if statements…). > b) change ofproto_v1_0_parser.OFPMatch to have similar constructor to its > equivalent from ofproto_v1_2 > c) change mininet tests that they classify mismatch in OF version as skipped > tests instead NG I think that we had better make the tests work only with OF1.2. > I don't know how important is OpenFlow 1.0 for us. If it is, I suggest to > consider and discuss option b) in separate thread, > if no I suggest option c). OF1.0 is not important for us at all. Everyone is moving to OF1.2/1.3. ------------------------------------------------------------------------------ Everyone hates slow websites. So do we. Make your web apps faster with AppDynamics Download AppDynamics Lite for free today: http://p.sf.net/sfu/appdyn_d2d_feb _______________________________________________ Ryu-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/ryu-devel
