Open Stack

On Thu, Apr 16, 2015 at 8:36 PM, Dongfeng (C) <albert.dongfeng at 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:mestery at mestery.com]
> *发送时间:* 2015年4月16日 21:12
> *收件人:* Dongfeng (C)
> *抄送:* Jixiaofeng (Steven); Yanchangjiang Yan(Changjiang); Zhaokexue;
> Nihui (nihui, VRPDesign); openstack-dev at lists.openstack.org
> *主题:* Re: Regarding ONOS L3 integration with OpenStack Neutron
>
>
>
> On Thu, Apr 16, 2015 at 1:40 AM, Dongfeng (C) <albert.dongfeng at 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
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20150416/6e793253/attachment.html>