[openstack-dev] 答复: Regarding ONOS L3 integration with OpenStack Neutron
Yes, as you can see from http://onosproject.org/ , ONOS is also a SDN controller just like ODL, there is necessity of implementing OpenStack Neutron virtual network features like L2, L3 in ONOS to enable ONOS as an option of OpenStack Networking backend. -邮件原件- 发件人: Neil Jerram [mailto:neil.jer...@metaswitch.com] 发送时间: 2015年4月16日 17:34 收件人: OpenStack Development Mailing List (not for usage questions); mest...@mestery.com 抄送: Yanchangjiang Yan(Changjiang); Jixiaofeng (Steven); Zhaokexue; Nihui (nihui, VRPDesign) 主题: Re: [openstack-dev] Regarding ONOS L3 integration with OpenStack Neutron On 16/04/15 07:40, Dongfeng (C) wrote: Hi Kyle, I am currently contributing to integrating ONOS with OpenStack Neutron. By ONOS do you mean http://onosproject.org/? http://onosproject.org/ looks very nice, but it's not obvious to me what the integration with OpenStack would be. Perhaps you could write a little more about that. Regards, Neil __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
[openstack-dev] 答复: Regarding ONOS L3 integration with OpenStack Neutron
Hi Kyle， Np, you can create your own L3 service plugin and just register a bug. Thanks for the quick response. I have gone through the link you gave and now I understand the main process. But I am still not very sure about registering a bug. Is it a lauchpad bug? What is the purpose for registering this bug? Regards, Feng 发件人: Kyle Mestery [mailto:mest...@mestery.com] 发送时间: 2015年4月16日 21:12 收件人: Dongfeng (C) 抄送: Jixiaofeng (Steven); Yanchangjiang Yan(Changjiang); Zhaokexue; Nihui (nihui, VRPDesign); openstack-dev@lists.openstack.org 主题: Re: Regarding ONOS L3 integration with OpenStack Neutron On Thu, Apr 16, 2015 at 1:40 AM, Dongfeng (C) albert.dongf...@huawei.commailto:albert.dongf...@huawei.com wrote: Hi Kyle, I am currently contributing to integrating ONOS with OpenStack Neutron. I just have a doubt. Could you please kindly clarify? Sure! For L2 integration, it is clear that we can directly develop a ML2 driver for ONOS without having to register a BP. Yes. But for L3 integration, since currently there is no provider and driver support for L3 router service plugin, do we still need to register a L3 plugin BP for ONOS? Np, you can create your own L3 service plugin and just register a bug. You can in fact keep it out of the tree in your stackforge repository, OpenDaylight does this already [1] Moreover, if the above BP is needed, will the corresponding code be part of Neutron or reside outside neutron as vendor code? It will be outside. The plugin decomposition spec [2] mandated that all new drivers which are proposed are thin-shims following the logic in that spec. Thanks, Kyle [1] https://github.com/stackforge/networking-odl/tree/master/networking_odl/l3 [2] http://specs.openstack.org/openstack/neutron-specs/specs/kilo/core-vendor-decomposition.html Regards, Feng __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] 答复: Regarding ONOS L3 integration with OpenStack Neutron
On Thu, Apr 16, 2015 at 8:36 PM, Dongfeng (C) albert.dongf...@huawei.com wrote: Hi Kyle， Np, you can create your own L3 service plugin and just register a bug. Thanks for the quick response. I have gone through the link you gave and now I understand the main process. But I am still not very sure about* registering a bug.* Is it a lauchpad bug? What is the purpose for registering this bug? Yes, it's a Launchpad bug in Neutron [1]. The purpose is simply to track your commit. We'll tag the bug as a Wishlist bug once you open it, and you can propose your shim plugin in-tree referencing your plugin. [1] https://bugs.launchpad.net/neutron *Regards,* *Feng* *发件人:* Kyle Mestery [mailto:mest...@mestery.com] *发送时间:* 2015年4月16日 21:12 *收件人:* Dongfeng (C) *抄送:* Jixiaofeng (Steven); Yanchangjiang Yan(Changjiang); Zhaokexue; Nihui (nihui, VRPDesign); openstack-dev@lists.openstack.org *主题:* Re: Regarding ONOS L3 integration with OpenStack Neutron On Thu, Apr 16, 2015 at 1:40 AM, Dongfeng (C) albert.dongf...@huawei.com wrote: Hi Kyle, I am currently contributing to integrating ONOS with OpenStack Neutron. I just have a doubt. Could you please kindly clarify? Sure! For L2 integration, it is clear that we can directly develop a ML2 driver for ONOS without having to register a BP. Yes. But for L3 integration, since currently there is no provider and driver support for L3 router service plugin, do we still need to register a L3 plugin BP for ONOS? Np, you can create your own L3 service plugin and just register a bug. You can in fact keep it out of the tree in your stackforge repository, OpenDaylight does this already [1] Moreover, if the above BP is needed, will the corresponding code be part of Neutron or reside outside neutron as vendor code? It will be outside. The plugin decomposition spec [2] mandated that all new drivers which are proposed are thin-shims following the logic in that spec. Thanks, Kyle [1] https://github.com/stackforge/networking-odl/tree/master/networking_odl/l3 [2] http://specs.openstack.org/openstack/neutron-specs/specs/kilo/core-vendor-decomposition.html Regards, Feng __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
