Re: [openstack-dev] [neutron] out-of-tree l3 service providers

2017-09-08 Thread Kevin Benton
Please add the requirements underneath the l3 flavors section of the etherpad so we can come up with a plan during the PTG. On Thu, Sep 7, 2017 at 11:04 PM, Isaku Yamahata wrote: > On Fri, Sep 08, 2017 at 12:26:56PM +0900, > Takashi Yamamoto

Re: [openstack-dev] [neutron] out-of-tree l3 service providers

2017-09-08 Thread Isaku Yamahata
On Fri, Sep 08, 2017 at 12:26:56PM +0900, Takashi Yamamoto wrote: > hi, > > On Fri, Sep 8, 2017 at 5:52 AM, Isaku Yamahata > wrote: > > Hi. > > > > Any update on this? Now L3 service provider got the time slot at the PTG. > > > > Yamamoto, do

Re: [openstack-dev] [neutron] out-of-tree l3 service providers

2017-09-07 Thread Takashi Yamamoto
hi, On Fri, Sep 8, 2017 at 5:52 AM, Isaku Yamahata wrote: > Hi. > > Any update on this? Now L3 service provider got the time slot at the PTG. > > Yamamoto, do you have any proposal for the interface? no > Although ODL surely is interested in L3 flavor, the

Re: [openstack-dev] [neutron] out-of-tree l3 service providers

2017-09-07 Thread Isaku Yamahata
Hi. Any update on this? Now L3 service provider got the time slot at the PTG. Yamamoto, do you have any proposal for the interface? Although ODL surely is interested in L3 flavor, the networking-odl team hasn't spec or experimental patch yet unfortunately. Dragon flow folks seems to have their

Re: [openstack-dev] [neutron] out-of-tree l3 service providers

2017-07-30 Thread Takashi Yamamoto
hi, On Mon, Jul 24, 2017 at 8:49 AM, Kevin Benton wrote: > If I understand the main issue with using regular callbacks, it's mainly > just that the flavor assignment itself is in a callback, right? yes. > > If so, couldn't we solve the problem by just moving flavor assignment

Re: [openstack-dev] [neutron] out-of-tree l3 service providers

2017-07-23 Thread Kevin Benton
If I understand the main issue with using regular callbacks, it's mainly just that the flavor assignment itself is in a callback, right? If so, couldn't we solve the problem by just moving flavor assignment to an explicit call before emitting the callbacks? Or would that still result in other

[openstack-dev] [neutron] out-of-tree l3 service providers

2017-07-13 Thread Takashi Yamamoto
hi, today i managed to play with l3 flavors. i wrote a crude patch to implement midonet flavor. [1] [1] https://review.openstack.org/#/c/483174/ a good news is it's somehow working. a bad news is it has a lot of issues, as you can see in TODO comments in the patch. given these issues, now i