On Thu, 13 Jul 2017 09:44:30 +0900 Iwase Yusuke <iwase.yusu...@gmail.com> wrote:
> Hi, > > > On 2017年07月13日 09:13, FUJITA Tomonori wrote: >> CC'ed Iwase, >> On Thu, 13 Jul 2017 09:15:25 +0900 >> Takashi YAMAMOTO <yamam...@ovn.org> wrote: >> >>> On Thu, Jul 13, 2017 at 7:04 AM, fumihiko kakuma >>> <kak...@valinux.co.jp> >>> wrote: >>> >>>> Hi Yamamoto-San, >>>> >>>> On Wed, 12 Jul 2017 23:43:25 +0900 >>>> Takashi YAMAMOTO <yamam...@ovn.org> wrote: >>>> >>>>> this breaks openstack neutron_dynamic_routing, doesn't it? >>>> >>>> I thank for advice. I know that. >>>> So as soon as the ryu version with this commit is released, >>>> I am going to push a patch to fix a breake to neutron-dynamic-routing. >>>> >>> >>> is it difficult to avoid breaking it? >>> eg. make it try-import new and old locations. >> Can we just let the testing directory alone? Nobody complains the size >> so far. I don't like to create issues for non-existing issue. >> Opinions? > > Yes, I think we can. Not so many users complain it, I guess. > Some user suggested to separate Ryu before, but with no response... > [Ryu-devel] Splitting Ryu > https://www.mail-archive.com/ryu-devel@lists.sourceforge.net/msg13454.html As far as I know, He wants to avoid version updates due to non openflow changes (e.g., bgp). > BTW, which modules or APIs are defined as the "public" libraries or > APIs of Ryu? > Or which are the "internal" (can be changed or relocated)? > Does any one know its policy? > "All APIs" must be the public and must be taken care of the use of > other project? For me, no APIs are written in stone. But I want to avoid disrupting major users like OpenStack. ------------------------------------------------------------------------------ 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
