<div dir="ltr"><div class="gmail_extra"><div class="gmail_quote">On Thu, Apr 16, 2015 at 1:40 AM, Dongfeng (C) <span dir="ltr"><<a href="mailto:albert.dongfeng@huawei.com" target="_blank">albert.dongfeng@huawei.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">





<div link="blue" vlink="purple" lang="ZH-CN">
<div>
<p class="MsoNormal"><span lang="EN-US">Hi Kyle,<u></u><u></u></span></p>
<p class="MsoNormal"><span lang="EN-US"><u></u> <u></u></span></p>
<p class="MsoNormal"><span lang="EN-US">I am currently contributing to integrating ONOS with OpenStack Neutron. I just have a doubt. Could you please kindly clarify?<u></u><u></u></span></p>
<p class="MsoNormal"><span lang="EN-US"><u></u> </span></p></div></div></blockquote><div>Sure!<br> <br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div link="blue" vlink="purple" lang="ZH-CN"><div><p class="MsoNormal"><span lang="EN-US"><u></u></span></p>
<p class="MsoNormal"><span lang="EN-US">For L2 integration, it is clear that we can directly develop a ML2 driver for ONOS without having to register a BP.<u></u><u></u></span></p>
<p class="MsoNormal"><span lang="EN-US"><u></u> </span></p></div></div></blockquote><div>Yes.<br> <br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div link="blue" vlink="purple" lang="ZH-CN"><div><p class="MsoNormal"><span lang="EN-US"><u></u></span></p>
<p class="MsoNormal"><span lang="EN-US">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?<u></u><u></u></span></p>
<p class="MsoNormal"><span lang="EN-US"><u></u> </span></p></div></div></blockquote><div>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]<br> <br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div link="blue" vlink="purple" lang="ZH-CN"><div><p class="MsoNormal"><span lang="EN-US"><u></u></span></p>
<p class="MsoNormal"><span lang="EN-US">Moreover, if the above BP is needed, will the corresponding code be part of Neutron or reside outside neutron as vendor code?<u></u><u></u></span></p>
<p class="MsoNormal"><span lang="EN-US"><u></u> </span></p></div></div></blockquote><div>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.<br><br></div><div>Thanks,<br></div><div>Kyle <br></div><div><br>[1] <a href="https://github.com/stackforge/networking-odl/tree/master/networking_odl/l3">https://github.com/stackforge/networking-odl/tree/master/networking_odl/l3</a> <br>[2] <a href="http://specs.openstack.org/openstack/neutron-specs/specs/kilo/core-vendor-decomposition.html">http://specs.openstack.org/openstack/neutron-specs/specs/kilo/core-vendor-decomposition.html</a><br><br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div link="blue" vlink="purple" lang="ZH-CN"><div><p class="MsoNormal"><span lang="EN-US"><u></u></span></p>
<p class="MsoNormal"><span lang="EN-US"><u></u> <u></u></span></p>
<p class="MsoNormal"><span lang="EN-US">Regards,<u></u><u></u></span></p>
<p class="MsoNormal"><span lang="EN-US">Feng<u></u><u></u></span></p>
</div>
</div>

</blockquote></div><br></div></div>