Hi Bob, Its simply that our new team policy is that each new plugin should be discussed at the team meeting before we decide to include it. Since we have done this for hyper-v, brocade and are going to be doing it for midonet + plumgrid, I didn't want to appear to be being uneven in applying this rule by not having a discussion on the ML2 stuff as well.
dan On Mon, Feb 11, 2013 at 7:33 AM, Robert Kukura <[email protected]> wrote: > On 02/08/2013 12:45 PM, Dan Wendlandt wrote: > > also, we should discuss additional plugins that have recently been > > proposed and posted for review: > > > > * ML2: https://blueprints.launchpad.net/quantum/+spec/modular-l2 > > (note: this BP has been filed for a while, my fault for not raising it > > in a previous meeting) > > Dan, what do you mean by "raising it"? This BP was presented at the > Grizzly summit, has been approved for Grizzly, and an initial WIP > patchset has been in review for a while. I've had a lot of interest from > various vendors regarding using it when its ready, but little actual > feedback on the details. > > Progress completing the implementation has been slowed down due to other > priorities over the past month, but I am making progress again. I expect > to post a more complete patch set in the next couple days, and see no > reason this cannot make G-3. > > The critical issue of ml2 being able to use the portbindings extension > to work with nova's improved vif plugging seems to be resolved through > nova implementing the binding:host_id attribute on port. With this, I > expect the G-3 version of ml2 to be able to concurrently support the > existing openvswitch, linuxbridge, and probably hyperv agents, so this > plugin will have immediate benefit. > > The ml2 plugin will also be capable of supporting controllers and > top-of-rack switches via mechanism drivers. The Arista patch to > openvswitch would be a perfect candidate to make use of ml2 rather than > adding complexity to the existing openvswitch plugin. > > Even if ml2 does not get enough mileage to be considered fully supported > in Grizzly in place of the monolithic openvswitch, linuxbridge, and > hyperv plugins, I think it is critical that we get it into Grizzly so > that we can start to reduce this proliferation of new monolithic plugins. > > I'd like to have a session at the Havana summit on whether/how we can > converge around using ml2 to drastically reduce the amount of code we > need to maintain, and having at least an initial version in the Grizzly > code base would make this session much more concrete and productive. > > -Bob > > > * Plumgrid: > > https://blueprints.launchpad.net/quantum/+spec/plumgrid-quantum-plugin > > * Midonet: > > https://blueprints.launchpad.net/quantum/+spec/midonet-quantum-plugin > > > > Dan > > > > -- > > ~~~~~~~~~~~~~~~~~~~~~~~~~~~ > > Dan Wendlandt > > Nicira, Inc: www.nicira.com <http://www.nicira.com> > > twitter: danwendlandt > > ~~~~~~~~~~~~~~~~~~~~~~~~~~~ > > > > > > > -- > Mailing list: https://launchpad.net/~quantum-core > Post to : [email protected] > Unsubscribe : https://launchpad.net/~quantum-core > More help : https://help.launchpad.net/ListHelp > -- ~~~~~~~~~~~~~~~~~~~~~~~~~~~ Dan Wendlandt Nicira, Inc: www.nicira.com twitter: danwendlandt ~~~~~~~~~~~~~~~~~~~~~~~~~~~
-- Mailing list: https://launchpad.net/~quantum-core Post to : [email protected] Unsubscribe : https://launchpad.net/~quantum-core More help : https://help.launchpad.net/ListHelp
