Hi Lajos, Speaking from personal perspective, it's really great to see this development! I have been able to use my own fork of the FAUCET controller with os_ken, though not all the integration tests pass (I see the original REST API has been partially removed, so this would need to be refactored within FAUCET - the tests use it to check that expected flows are present, etc). I imagine, not too complex to change.
It would be great to hear more about future plans - for example, it would be nice to be able to perhaps refactor "Ryu" into smaller areas, protocol parsers versus applications etc. That would increase maintainability. Thanks, On Wed, Sep 15, 2021 at 9:54 PM Lajos Katona <katonal...@gmail.com> wrote: > Hi ryu developers > > I am a core reviewer on Neutron, and I work for Ericsson. I reach out to > you to highlight that ryu is used in Openstack Neutron. > > We forked ryu and made it an Opendev governed project when ryu announced > that they will not maintain the ryu codebase. The project was forked and > renamed to os-ken (see [1]). > Openstack has a well defined review culture, and the Neutron CI actively > tests os-ken/ryu (see [2]), and there are new features, and the code is > maintained (see [3]). > The question is if we can collaborate to share experience, have better > coverage and perhaps other benefits. > It Would be good to hear your opinion. > > [1]: https://opendev.org/openstack/os-ken > [2]: > https://zuul.openstack.org/builds?job_name=neutron-ovs-tempest-with-os-ken-master > [3]: https://review.opendev.org/q/project:openstack/os-ken > > Lajos Katona (irc: lajoskatona) > _______________________________________________ > Ryu-devel mailing list > Ryu-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/ryu-devel >
_______________________________________________ Ryu-devel mailing list Ryu-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/ryu-devel
