On Fri, 04 May 2018 13:22:28 +0900, Steve Jarvis wrote: > > Hey Ryu Devel,
> We have an established project where we're adding OpenFlow for > (local) bridge management, and I'd like to use Ryu. Ryu wants to be > the main entry point of the process though (with ryu-manager), and > since we have a bigger application that does more than only > SDN-related work, it'd better fit our architecture if we could use > Ryu's messaging and callbacks in just another thread of the existing > application. Is there a way to use the Ryu library like that, and if > so, are there any examples of such a model? Is your application eventlet friendly? OpenStack Neutron's ovs-agent was initially a non Ryu app and has it's own main() function. On adopting Ryu, the original main() was wrapped into a RyuApp. See the followings. http://git.openstack.org/cgit/openstack/neutron/tree/neutron/plugins/ml2/drivers/openvswitch/agent/openflow/native/main.py http://git.openstack.org/cgit/openstack/neutron/tree/neutron/plugins/ml2/drivers/openvswitch/agent/openflow/native/ovs_ryuapp.py If the above doesn't work for you, Ryu using code can be a subprocess and inter-process-communtication can be used. -- IWAMOTO Toshihiro ------------------------------------------------------------------------------ Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot _______________________________________________ Ryu-devel mailing list Ryu-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/ryu-devel
