Jump to: navigation, search

Difference between revisions of "Meetings/ML2"

m (Meeting June 10, 2015)
Line 5: Line 5:
 
==Agenda==
 
==Agenda==
  
 +
=== Meeting June 17, 2015 ===
 +
 +
* Announcements
 +
** VLAN aware VMs meeting 6-15-2015
 +
*** https://etherpad.openstack.org/p/YVR-neutron-vlan-trunk
 +
 +
* Action Items
 +
** banix to discuss Modular L2 agents topic in Neutron core team and drive the priority
 +
** asomya and shivharis to add Physical Topology to the ML2 charter for Liberty
 +
** manishg to propose two or three time slots for mid-cycle sprint for task flow
 +
*** Proposing a few dates here (we will probably need 2 days but just proposing a range)
 +
**** Jul/8 - Jul/10
 +
**** Jul/13 - Jul/15
 +
**** Sep/9 - Sep/11
 +
**** Sep/16 - Sep/18
 +
**** Sep/23 - Sep/25
 +
 +
* Neutron Mid-Cycle Sprint Discussion
 +
** https://etherpad.openstack.org/p/neutron-liberty-mid-cycle
 +
*** July 13-17 seems like the earliest possible week
 +
** Following participants are available - please add your name, if you can participate
 +
*** Sukhdev K
 +
*** Bob K
 +
*** Manish G
 +
*** Josh
 +
 +
* Task Flow Document
 +
** https://docs.google.com/document/d/1aSgTVB7nW_v7lHH0Z0DUgfymEsx0O16k1Jgu7QFXkFA/edit?usp=sharing document
 +
 +
* Open Discussion
 
=== Meeting June 10, 2015 ===
 
=== Meeting June 10, 2015 ===
 
*Absence:  
 
*Absence:  

Revision as of 05:14, 17 June 2015

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

Contents

Tracking ML2 Subgroup Reviews: here

Agenda

Meeting June 17, 2015

  • Action Items
    • banix to discuss Modular L2 agents topic in Neutron core team and drive the priority
    • asomya and shivharis to add Physical Topology to the ML2 charter for Liberty
    • manishg to propose two or three time slots for mid-cycle sprint for task flow
      • Proposing a few dates here (we will probably need 2 days but just proposing a range)
        • Jul/8 - Jul/10
        • Jul/13 - Jul/15
        • Sep/9 - Sep/11
        • Sep/16 - Sep/18
        • Sep/23 - Sep/25
  • Open Discussion

Meeting June 10, 2015

  • Absence:
    • banix. I will be away. Will follow up on my AI by next week.
  • Action Items
    • rkukura to discuss with QoS implications with ajo on ML2
    • banix to discuss Modular L2 agents topic in Neutron core team and drive the priority
    • asomya and shivharis to add Physical Topology to the ML2 charter for Liberty
    • manishg to propose two or three time slots for mid-cycle sprint for task flow
      • Proposing a few dates here (we will probably need 2 days but just proposing a range)
        • Jul/8 - Jul/10
        • Jul/13 - Jul/15
        • Sep/9 - Sep/11
        • Sep/16 - Sep/18
        • Sep/23 - Sep/25
  • Neutron Mid-Cycle Sprint Discussion
    • I have removed Task Flow item from etherpad for Ft. Collins mid-cycle.
    • https://etherpad.openstack.org/p/neutron-liberty-mid-cycle
    • Discussion on the time frame that works for people to have an ML2 mid-cycle in the Bay Area
      • July 13-17 seems like the earliest possible week
    • Following participants are available - please add your name, if you can participate
      • Sukhdev K
      • Bob K
      • Manish G
      • Josh
  • Open Discussion

Meeting June 3, 2015

  • Charter of ML2 sub-team for Liberty Cycle
    • Task Flow
    • Decomposition phase -2
  • Open Discussion

Meeting May 27, 2015

  • No meeting - recovering from summit

Meeting May 20, 2015

  • No meeting - Liberty Summit

Meeting May 13, 2015

  • Announcements
    • No meeting next two weeks. Next week everybody is at summit, following week to recover from travels
  • Open Discussion
    • Discussion on Port to network relationship - N:M relationship - is it allowed in our current design?
      • Can one port attach to multiple networks?
      • Can a (v)NIC attach to multiple networks?
      • Can one network attach to multiple ports of same instance/node?

Meeting May 6, 2015

  • Announcements
    • Kilo was released last week - congratulations to everybody
  • Open Discussion

Meeting April 29, 2015

  • Announcements
    • Kilo RC3 is due any day
    • Starting with Liberty Spec process for new features is being abandoned in favor of light weight RFE is being implemented
    • Changes to Driver team - Doug and Maru replacing Salvatore and Mark
  • Action Items from Last week
    • manishg to document task flow discussions and look into the midonet plugin
      • document (manishg)
      • midonet plugin (not done - will take care of it this week) (manishg)
  • Open Discussion

Meeting April 22, 2015

  • Action Items from Last week
    • Sukhdev to discuss with mestery about task flow during mid-cycle sprint
    • Document the discussion point related to ML2 Sync (Manish)
    • shivharis to find the information about release notes for Kilo and share with the team
  • Open Discussion

Meeting April 15, 2015

  • Announcements
    • Absence: Manish (Jury Duty)
    • Absence next week: rkukura (PTO - college tour)
    • Kilo RC is out
  • Action Items from Last week
    • Add next steps for the Drivers decomposition to summit topic etherpad - shivharis
    • shivharis to find the information about release notes for Kilo and share with the team
    • rkukura and Sukhdev to discuss with mestery about task flow during mid-cycle sprint
    • Document the discussion point related to ML2 Sync (Manish)
  • Quick update on DVR UT/fix/cleanup work (rkukura)
  • portsecurity tests: unit, functional and scenario
  • Open Discussion

Meeting April 8, 2015

  • Action Items from Last week
  • Mechanism drivers and DVR discussion (rkukura)
    • Have made good (but slow) progress on DVR port binding schema and logic cleanup
    • Discovered no current unit tests cover critical DVR port binding logic, so adding them as separate patch against current code, then will ensure they don't break in dependent cleanup patch
      • Extending test_port_binding to exercise update_dvr_port_binding, get_device_details, etc. for DVR ports, utilizing existing PortContext state asserts in mechanism_test MD
      • Hoped to get at least the new UTs into kilo, but probably too late, but can back-port to kilo
    • Discovered several issues (inconsistencies in per-host vs. host-independent state in PortContext) that would seem to break ToR switch MDs that need to track binding state per host:
      • When committing DVR port binding, PortContext passed to update_port methods has new binding:vif_type and binding:vif_details for the bound host, but shows 'distributed' for previous binding:vif_type instead of 'unbound' like for normal ports, and empty strings for current or previous binding:host_id - propose to make these work like for non-DVR ports
      • When updating DVR port's status, PortContext currently shows 'distributed' for binding:vif_type and empty string for host, but has binding_levels, etc., for the specific host - could change this to reflect host-specific state, or to only be called when port's status changes and reflect non-host-specific state
    • Issues to discuss
      • Has anyone tested their MDs with DVR?
      • Has anyone run into these (or other) issues?
      • Is back-porting these sorts of behavioral fixes to kilo acceptable?
      • Do we have consensus on making update_port methods reflect per-host state when committing DVR port binding?
      • Do we prefer to make update_port methods reflect per-host state or only host-independent state when changing DVR port status, or do we need separate updates for each?

Meeting April 1, 2015

Meeting March 25, 2015

Meeting March 18, 2015


Meeting March 11, 2015


Meeting March 4, 2015

Meeting February 25, 2015

Meeting February 18, 2015

Meeting February 11, 2015

Meeting February 4, 2015

Meeting January 28, 2015

Meeting January 21, 2015

Meeting January 14, 2015

Meeting January 7, 2015

  • Open Discussion

Meeting December 31, 2014

  • No meeting - holiday break

Meeting December 24, 2014

  • No meeting - holiday break

Meeting December 17, 2014

  • Announcements
  • Discussion about the ML2 Drivers decomposition
  • Blueprint list consolidation (shivharis and manishg)
    • Needs further split of drivers
  • Open Discussion

Meeting December 10, 2014

  • No meeting today due to Neutron Mid-cycle sprint

Meeting December 3, 2014

  • Action Items from previous Week
    • None
  • ML2 driver repository discussion - We did not get to cover it last week
    • It seems ML2 vendor drivers will likely be moving out of the main neutron git repository
    • Any vendor can use their own private repository (stackforge?)
    • Do we want a common repository for ML2 vendor drivers?
      • Merges reviewed/approved by an ML2 core team?
      • Pros
        • Reviews maintain consistent quality, style, functionality, etc.
        • Help ensure drivers can coexist in heterogeneous deployments
        • Changes to driver API can update all drivers in common repo in single merge
        • Distributions can package entire set of vendor drivers rather than having to interact with each vendor separately
      • Cons
        • Reviews and approval needed to merge
        • Vendors don't control release cycle for their own drivers
        • Not a level playing field for vendors who chose to use their own repositories
      • Formal poll coming?
  • Modular L2 agent
    • Separate task force?
    • Relationship to ML2?

Meeting November 26, 2014

  • Action Items from previous Week
    • Discuss rate limiting (throughput limiting)
    • Discuss port security
  • ML2 driver repository discussion
    • It seems ML2 vendor drivers will likely be moving out of the main neutron git repository
    • Any vendor can use their own private repository (stackforge?)
    • Do we want a common repository for ML2 vendor drivers?
      • Merges reviewed/approved by an ML2 core team?
      • Pros
        • Reviews maintain consistent quality, style, functionality, etc.
        • Help ensure drivers can coexist in heterogeneous deployments
        • Changes to driver API can update all drivers in common repo in single merge
        • Distributions can package entire set of vendor drivers rather than having to interact with each vendor separately
      • Cons
        • Reviews and approval needed to merge
        • Vendors don't control release cycle for their own drivers
        • Not a level playing field for vendors who chose to use their own repositories
      • Formal poll coming?
  • Modular L2 agent
    • Separate task force?
    • Relationship to ML2?

Meeting November 19, 2014

  • ML2 driver repository discussion
    • It seems ML2 vendor drivers will likely be moving out of the main neutron git repository
    • Any vendor can use their own private repository (stackforge?)
    • Do we want a common repository for ML2 vendor drivers?
      • Merges reviewed/approved by an ML2 core team?
      • Pros
        • Reviews maintain consistent quality, style, functionality, etc.
        • Help ensure drivers can coexist in heterogeneous deployments
        • Changes to driver API can update all drivers in common repo in single merge
        • Distributions can package entire set of vendor drivers rather than having to interact with each vendor separately
      • Cons
        • Reviews and approval needed to merge
        • Vendors don't control release cycle for their own drivers
        • Not a level playing field for vendors who chose to use their own repositories
      • Formal poll coming?
  • Modular L2 agent
    • Separate task force?
    • Relationship to ML2?
  • Open Discussion

Meeting November 12, 2014

  • No meeting this week due to people still traveling and/or recovering.

Meeting November 5, 2014

  • No meeting this week due to Paris Summit.

Meeting October 29, 2014

  • Announcements
    • Absent excuse: banix
    • Summit is next week!
  • Action Items from previous Week
    • None
  • Open Discussion

Meeting October 22, 2014

  • Action Items from previous Week
    • None
  • Open Discussion

Meeting October 15, 2014

  • Action Items from previous Week
    • None
  • Open Discussion

Meeting October 8, 2014

  • Action Items from previous Week
    • None
  • Open Discussion

Meeting October 1, 2014

  • Announcements
  • Action Items from previous Week
    • banix to work with mlavalle and the team to figure out best testing strategy for bulk operations
    • shivharis to follow up with mestery regarding ML2 RC1 bugs
  • Open Discussion

Meeting September 24, 2014

  • Action Items from previous Week
    • banix to work with mlavalle and others to define scenario test for Bulk Ops testing
      • We agreed to propose to the team to implement a special mechanism driver that will fail in predictable ways (e.g. every other post commit op or every 4th one) to enable a tempest script to confirm that, when failure occurs, all the bulk operations are rolled back

Meeting September 17, 2014

  • Open Discussion

Meeting September 10, 2014

  • Action Items from previous Week
  • Open Discussion

Meeting September 3, 2014

  • Announcements
    • Juno feature freeze deadline is over
  • Action Items from previous Week
    • rkukura to enter bugs for DVR ML2 issues he’s identified
    • nlahouti and rkukura to keep after markmclain to remove his -2 on https://review.openstack.org/#/c/89211/, or explain why its not being removed - Completed
  • Open Discussion

Meeting August 27, 2014

  • Announcements
    • Juno feature freeze deadline is 9/4
  • Action Items from previous Week
    • Sukhdev or rkukura to follow up with DVR team regarding Neutron OVS based Distributed Virtual Router - rkukura took care of this
  • Open Discussion

Meeting August 20, 2014

  • Open Discussion

Meeting August 13, 2014

  • Announcements
    • Juno feature proposal deadline is August 21 - week from tomorrow
  • Support for network adaptors that do not allow promiscuous mode (relevant for flat & vlan networking)
    • Extend openvswitch neutron agent
    • Introduce macvtap (modifications to novas libvirt driver and linuxbridge plugin/agent)
  • Open Discussion

Meeting August 6, 2014

  • Spec Reviews
    • No more spec reviews. We have moved into code review phase
  • ML2 Hierarchical Port Binding and Dynamic Segments
  • Open Discussion

Meeting July 30, 2014

  • Announcements
  • ML2 Hierarchical Port Binding and Dynamic Segments
  • Open Discussion

Meeting July 23, 2014

  • Announcements
  • Open Discussion

Meeting July 16, 2014

https://wiki.openstack.org/wiki/Neutron/MigrationFromNovaNetwork/HowTo

  • Provide node specific information to ML2 plugin
  • Open Discussion

Meeting July 9, 2014

  • Meeting cancelled due to mid-cycle sprint

Meeting July 2, 2014

Meeting June 25, 2014

Meeting June 18, 2014

Meeting June 11, 2014

Meeting June 04, 2014

Meeting May 28, 2014

Meeting May 21, 2014

Meeting May 7, 2014

Meeting Cancelled April 30, 2014

  • OpenStack vacation week!

Meeting April 23, 2014

Meeting April 16, 2014

Meeting April 9, 2014

Meeting April 2, 2014

  • Action items from last week
    • banix to push patch to call remaining MDs after postcommit exception
  • Reviews being tracked
  • Design Summit Session Ideas
    • Juno planning for ML2 should start now
    • Ideas for summit sessions

Meeting March 26, 2014

Meeting March 19, 2014

Meeting March 12, 2014

Meeting March 5, 2014

Meeting February 26, 2014

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: