Jump to: navigation, search

Difference between revisions of "Meetings/ML2"

Line 2: Line 2:
  
 
== Agenda ==
 
== Agenda ==
 
=== '''No Meeting Nov 27, 2013''' ===
 
  
 
=== '''Meeting Dec 4, 2013''' ===
 
=== '''Meeting Dec 4, 2013''' ===
Line 9: Line 7:
 
* Testing
 
* Testing
 
** Additional unit tests needed
 
** Additional unit tests needed
 +
** Multi-node devstack based gate testing
 
** Tempest tests
 
** Tempest tests
 
*** Scenario tests around ML2+LinuxBridge
 
*** Scenario tests around ML2+LinuxBridge
 
*** Scenario tests around ML2+L2 Population
 
*** Scenario tests around ML2+L2 Population
 
*** Scenario tests around ML2+OpenDaylight (coming soon)
 
*** Scenario tests around ML2+OpenDaylight (coming soon)
 +
** Vendor Tempest testing discussion for MechanismDrivers
 
* Revisit "Modular L2 TypeDriver extra port information"
 
* Revisit "Modular L2 TypeDriver extra port information"
 
** https://review.openstack.org/37893
 
** https://review.openstack.org/37893

Revision as of 15:19, 3 December 2013

This page tracks ML2 meeting information.

Agenda

Meeting Dec 4, 2013

Previous Agenda

  • Icehouse Design Summit Topic ideas
    • RPC handling in ML2 for Type and Mechanism Drivers
    • More extensible TypeDrivers for controller-based MechanismDrivers
    • Monolithic Plugin vs. ML2 MechanismDriver - current and future plugins
    • Future Directions for ML2 (orchestration, deployment, management, ...)
    • Migration from deprecated Plugins (openvswitch, linuxbridge) to ML2 - automation?
    • Add support for VXLAN multicast to the OVS agent with newer versions of OVS and Linux kernel.
    • Multi-segment provider network implementations in MechanismDrivers, specifically OVS.
    • Additional provider network attributes for controller-based plugins such as ODL for networks created outside of Neutron.

Icehouse ML2 work for reference

Questions?

Previous Meeting Logs

General ML2 Information

Here are the current ml2-specific blueprints for havana:


These tunnel-related blueprints effect the openvswitch and/or linuxbridge agents, and the features should also (or exclusively) be supported (using both agents simultaneously where applicable) by the ml2 plugin:


These blueprints involve the ml2 MechanismDriver API: