There is already an out-of-tree L3 plugin, and as part of the plugin
decomposition work, I'm planning to use this as the base for the new
ODL driver in Kilo. Before you file specs and BPs, we should talk a
bit more.

Thanks,
Kyle

[1] https://github.com/dave-tucker/odl-neutron-drivers

On Wed, Nov 26, 2014 at 12:53 PM, Kevin Benton <blak...@gmail.com> wrote:
> +1. In the ODL case you would just want a completely separate L3 plugin.
>
> On Wed, Nov 26, 2014 at 7:29 AM, Mathieu Rohon <mathieu.ro...@gmail.com>
> wrote:
>>
>> Hi,
>>
>> you can still add your own service plugin, as a mixin of
>> L3RouterPlugin (have a look at brocade's code).
>> AFAIU service framework would manage the coexistence several
>> implementation of a single service plugin.
>>
>> This is currently not prioritized by neutron. This kind of work might
>> restart in the advanced_services project.
>>
>> On Wed, Nov 26, 2014 at 2:28 PM, Priyanka Chopra
>> <priyanka.cho...@tcs.com> wrote:
>> > Hi Gary, All,
>> >
>> >
>> > This is with reference to blueprint - L3 router Service Type Framework
>> > and
>> > corresponding development at github repo.
>> >
>> > I noticed that the patch was abandoned due to inactivity. Wanted to know
>> > if
>> > there is a specific reason for which the development was put on hold?
>> >
>> > I am working on a Use-case to enable neutron calls (L2 and L3) from
>> > OpenStack to OpenDaylight neutron. However presently ML2 forwards the L2
>> > calls to ODL neutron, but not the L3 calls (router and FIP).
>> > With this blueprint submission the L3 Service framework (that includes
>> > L3
>> > driver, agent and plugin) will be completed and hence L3 calls from
>> > OpenStack can be redirected to any controller platform. Please suggest
>> > in
>> > case anyone else is working on the same or if we can do the enhancements
>> > required and submit the code to enable such a usecase.
>> >
>> >
>> > Best Regards
>> > Priyanka
>> >
>> > =====-----=====-----=====
>> > Notice: The information contained in this e-mail
>> > message and/or attachments to it may contain
>> > confidential or privileged information. If you are
>> > not the intended recipient, any dissemination, use,
>> > review, distribution, printing or copying of the
>> > information contained in this e-mail message
>> > and/or attachments to it are strictly prohibited. If
>> > you have received this communication in error,
>> > please notify us by reply e-mail or telephone and
>> > immediately and permanently delete the message
>> > and any attachments. Thank you
>> >
>> >
>> > _______________________________________________
>> > OpenStack-dev mailing list
>> > OpenStack-dev@lists.openstack.org
>> > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>> >
>>
>> _______________________________________________
>> OpenStack-dev mailing list
>> OpenStack-dev@lists.openstack.org
>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
>
>
>
> --
> Kevin Benton
>
> _______________________________________________
> OpenStack-dev mailing list
> OpenStack-dev@lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>

_______________________________________________
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Reply via email to