Re: [openstack-dev] [neutron] - L3 flavors and issues with usecases for multiple L3 backends

+1 – Good discussion in this thread. We once had the plan to go with Gantt (https://wiki.openstack.org/wiki/Gantt) rather than re-invent that wheel but… in any case we have a simple framework to start experimenting ;-) German From: Doug Wiegley

Re: [openstack-dev] [neutron] - L3 flavors and issues with usecases for multiple L3 backends

So flavors are for routers with different behaviors that you want the user to be able to choose from (e.g. High performance, slow but free, packet logged, etc). Multiple drivers are for when you have multiple backends providing the same flavor (e.g. The high performance flavor has several drivers

Re: [openstack-dev] [neutron] - L3 flavors and issues with usecases for multiple L3 backends

What advantage can we get from putting multiple drivers into one flavor over strictly limit one flavor one driver (or whatever it is called). Thanks, Rui -- Original -- From: "Kevin Benton";; Send time: Wednesday, Feb 3, 2016 8:55 AM To:

Re: [openstack-dev] [neutron] - L3 flavors and issues with usecases for multiple L3 backends

The lbaas use case was something like having one flavor with hardware SSL offload and one that doesn’t, e.g. You can easily have multiple backends that can do both (in fact, you might even want to let the lower flavor provision onto the higher, if you have spare capacity on one and not the