Jump to: navigation, search

Difference between revisions of "Meetings/ML2"

(Meeting February 12, 2014)
Line 2: Line 2:
  
 
== Agenda ==
 
== Agenda ==
 +
=== Meeting February 19, 2014 ===
 +
* Action items from last week:
 +
** rkukura to move port binding discussion into Google Doc
 +
** matrohon to file BP for multi-node testing and bring this up in the infra meeting
 +
* Migration tool
 +
** BP: https://blueprints.launchpad.net/neutron/+spec/ml2-deprecated-plugin-migration
 +
** marun volunteered to own this working with rkukura
 +
* SR-IOV BPs in review:
 +
** https://blueprints.launchpad.net/neutron/+spec/ml2-binding-profile
 +
** https://blueprints.launchpad.net/neutron/+spec/ml2-request-vnic-type
 +
** https://blueprints.launchpad.net/neutron/+spec/vif-details
 +
* Port binding bug fixes which may affect MDs:
 +
** https://bugs.launchpad.net/neutron/+bug/1276395
 +
** https://bugs.launchpad.net/neutron/+bug/1276391
 +
* Proposed patch to ML2 to move away from providernet extension into the multi-provider extension with arbitrary attributes
 +
** https://review.openstack.org/#/c/37893/
 +
 
=== Meeting February 12, 2014 ===
 
=== Meeting February 12, 2014 ===
 
* Action items from last week:
 
* Action items from last week:
Line 35: Line 52:
 
* Tests
 
* Tests
 
** Add the capabality to test core MD (l2-pop, ovs, lb) by the gate
 
** Add the capabality to test core MD (l2-pop, ovs, lb) by the gate
 
=== '''Meeting February 5, 2014''' ===
 
* Announcements
 
** Neutron patches getting merged again!
 
*** Reviews needed
 
** Feature proposal deadline in less than two weeks!
 
** BP implementations must be in review by February 18th
 
** Need need to prioritize and track ML2 BPs for icehouse
 
* Action items from last week:
 
** rkukura to post proposal for portbinding changes to call MDs outside of transactions and with all needed information
 
*** http://lists.openstack.org/pipermail/openstack-dev/2014-February/026344.html
 
*** This addresses two bugs, but is needed by BP implementations.
 
* Blueprints
 
** https://blueprints.launchpad.net/neutron?searchtext=ml2
 
** 3 high, 13 medium, 3 low, 13 undefined priorities
 
** 19 not yet approved for icehouse
 
** all MDs should probably be same priority
 
** Which should we approve for icehouse, drop from icehouse or adjust priority?
 
* Bugs
 
** https://bugs.launchpad.net/neutron/+bugs?field.tag=ml2
 
* ovs-firewall security group update: asadoughi
 
 
=== '''Meeting January 29, 2014''' ===
 
* Action items from last week:
 
** rkukura to send summary around ML2 binding to the list.
 
* Bugs
 
** https://bugs.launchpad.net/neutron/+bugs?field.tag=ml2
 
* ovs-firewall security group update: asadoughi
 
* New ML2 MechanismDrivers:
 
** Will be good to get someone from each team to start attending ML2 meetings.
 
** Brocade:
 
*** https://review.openstack.org/#/c/60129/
 
** Huawei:
 
*** https://review.openstack.org/#/c/68148/
 
** Big Switch:
 
*** https://blueprints.launchpad.net/neutron/+spec/bsn-ml2-mechanism-driver
 
** OpenDaylight:
 
*** https://blueprints.launchpad.net/neutron/+spec/ml2-opendaylight-mechanism-driver
 
** Cisco APIC:
 
*** https://blueprints.launchpad.net/neutron/+spec/ml2-cisco-apic-mechanism-driver
 
** Cisco UCS:
 
*** https://blueprints.launchpad.net/neutron/+spec/ml2-ucs-manager-mechanism-driver
 
** Mellanox:
 
*** https://blueprints.launchpad.net/neutron/+spec/mlnx-ml2-support
 
** fsl-sdn-os-mech-driver
 
*** https://review.openstack.org/#/c/69838/
 
** Ryu ML2 Driver
 
*** https://blueprints.launchpad.net/neutron/+spec/ryu-ml2-driver
 
 
=== '''Meeting January 22, 2014''' ===
 
* Action items from last week:
 
** asomya to work on new typedriver refactoring patch with zhang
 
** rkukura to flesh out details of bind/unbind and send email to openstack-dev ML
 
* Port-binding discussion: Conclusion
 
* ovs-firewall security group update: asadoughi
 
* New ML2 MechanismDrivers:
 
** Will be good to get someone from each team to start attending ML2 meetings.
 
** Brocade:
 
*** https://review.openstack.org/#/c/60129/
 
** Huawei:
 
*** https://review.openstack.org/#/c/68148/
 
** Big Switch:
 
*** https://blueprints.launchpad.net/neutron/+spec/bsn-ml2-mechanism-driver
 
** OpenDaylight:
 
*** https://blueprints.launchpad.net/neutron/+spec/ml2-opendaylight-mechanism-driver
 
** Cisco UCS:
 
*** https://blueprints.launchpad.net/neutron/+spec/ml2-ucs-manager-mechanism-driver
 
** Mellanox:
 
*** https://blueprints.launchpad.net/neutron/+spec/mlnx-ml2-support
 
 
=== '''Meeting January 15, 2014''' ===
 
* Action items from last week:
 
** rcurran to verify if a bug exists for Cisco ML2 UT coverage
 
** asadoughi: ml2 unit test coverage bugs filed, tagged: https://bugs.launchpad.net/neutron/+bugs?field.tag=ml2-unit-test-coverage
 
** rkukura Look at moving bind_port() out of the TX and send email or a WIP patch to discuss.
 
*** Concluded two separate transactions are required, with bind_port() between them, so that MD's bind_port can reference the port as a foreign key in its own table if needed
 
*** Was considering a state machine to prevent multiple threads/processes from trying to bind the same port concurrently, but now thinking its safe and much simpler to simply allow them to bind concurrently
 
** mestery to ping asomya around https://docs.google.com/document/d/1ZHb2zzPmkSOpM6PR8M9sx2SJOJPHblaP5eVXHr5zOFg/edit
 
 
=== '''Meeting January 8, 2014''' ===
 
* Action items from last week:
 
** asadoughi: ml2 unit test coverage with line numbers! http://lists.openstack.org/pipermail/openstack-dev/2013-December/022649.html
 
* ML2 Binding Management
 
** ML2 Original vs. Bound Segment Discussion
 
*** Should https://review.openstack.org/#/c/62380/ be completed?
 
*** Is that sufficient?
 
*** Do we need to call update_port_precommit and update_port_postcommit for all binding changes?
 
*** Do we explicitly unbind before deleting port?
 
* ML2 Bugs
 
** https://review.openstack.org/#/c/62696/
 
** https://review.openstack.org/#/c/21946/
 
** https://review.openstack.org/#/c/62380/
 
 
=== '''Meeting Dec 18, 2013''' ===
 
* Action items from last week:
 
** asadoughi: ml2 unit test coverage
 
*** general ml2 plugin unit tests: http://lists.openstack.org/pipermail/openstack-dev/2013-December/021967.html
 
*** agent tests: http://lists.openstack.org/pipermail/openstack-dev/2013-December/022146.html
 
** asadoughi: blueprint ovs-firewall-driver
 
*** asking for feedback on security groups api addition http://lists.openstack.org/pipermail/openstack-dev/2013-December/022518.html
 
* Development discussions
 
** MechanismDriver API delete method ordering and the relationship between DB state and external mechanism state managed by the driver
 
** TypeDriver refactor and the providernet and multiprovidernet extension APIs
 
 
=== '''Meeting Dec 11, 2013''' ===
 
 
* Action items from last week:
 
** mestery: Setup etherpad for multi-node Tempest testing
 
*** https://etherpad.openstack.org/p/multi-node-neutron-tempest
 
* Development discussions:
 
** blueprint ovs-firewall-driver: progress and technical discussion
 
*** purpose
 
*** openvswitch statelessness and security groups frontend API and DB: https://etherpad.openstack.org/p/ovs-firewall-driver-stateless-2
 
*** ovs_neutron_agent nuances:
 
**** (1) firewall invoked before agent does anything in C[R]UD operations
 
**** (2) agent removes all flows at initialization
 
**** (3) not sure about ovs having atomicity like iptables-restore has (all connections might be dropped/allowed)
 
*** if extra time, quickly mention:
 
**** working on adding IPv6 flows
 
**** working on adding multiple ports in range (try port bitmask or N flows per N ports?)
 
**** of course, need to add unit/integration tests; if someone wants to help on integration tests, that would be good if that's possible
 
**** neutron-rootwrap-xen-dom0 bugs: https://bugs.launchpad.net/neutron/+bug/1185872/comments/3, https://bugs.launchpad.net/neutron/+bug/1259748
 
**** other network types: should work as-is since the tunnel OVS flows just pass it to the integration bridge where firewall flows live, but test environment not setup to do so
 
**** table, priority coordination: ok for now to be hard-coded in Neutron, but will need an abstraction in the future possibly
 
 
=== '''Meeting Dec 4, 2013''' ===
 
 
* Action items from last week:
 
** mestery: follow up with the ci team to determine if multi-node testing can be performed in the gate.
 
** asomya: provide review comments for TypeDriver patch from ZangMingJie.
 
* Development issues
 
** VLAN availability issue during delete_port_postcommit()
 
* Testing
 
** Additional unit tests needed
 
** Multi-node devstack based gate testing
 
** Tempest tests
 
*** Scenario tests around ML2+LinuxBridge
 
*** Scenario tests around ML2+L2 Population
 
*** Scenario tests around ML2+OpenDaylight (coming soon)
 
** Vendor Tempest testing discussion for MechanismDrivers
 
* Revisit "Modular L2 TypeDriver extra port information"
 
** https://review.openstack.org/37893
 
** https://blueprints.launchpad.net/neutron/+spec/ml2-typedriver-extra-port-info
 
  
 
===Previous Agenda===
 
===Previous Agenda===

Revision as of 15:32, 19 February 2014

Weekly on Wednesdays at 1600 UTC on #openstack-meeting-alt

Agenda

Meeting February 19, 2014

Meeting February 12, 2014

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: