Jump to: navigation, search

Difference between revisions of "Network/Meetings"

(On Demand Agenda)
(Agenda for Next Neutron Team Meeting)
Line 6: Line 6:
  
 
== Agenda for Next Neutron Team Meeting ==
 
== Agenda for Next Neutron Team Meeting ==
'''Tuesday (8/11/2015) at 1400 UTC on #openstack-meeting'''
+
'''Monday (8/17/2015) at 2100 UTC on #openstack-meeting'''
  
 
=== Announcements / Reminders ===
 
=== Announcements / Reminders ===
 
* Liberty-3
 
* Liberty-3
** 3 weeks out
+
** 2 weeks out
 
** https://wiki.openstack.org/wiki/Liberty_Release_Schedule
 
** https://wiki.openstack.org/wiki/Liberty_Release_Schedule
 
** FF is also that week
 
** FF is also that week
Line 22: Line 22:
 
<br>
 
<br>
 
Important bugs:
 
Important bugs:
 +
** [https://bugs.launchpad.net/neutron/+bug/1404743] sporadic test failures due to VMs not getting a DHCP lease
 
** [https://bugs.launchpad.net/neutron/+bug/1477192] neutron test_multi_prefix_slaac failing in the gate with ping failures starting around 7/22
 
** [https://bugs.launchpad.net/neutron/+bug/1477192] neutron test_multi_prefix_slaac failing in the gate with ping failures starting around 7/22
 
** [https://bugs.launchpad.net/neutron/+bug/1461172] neutron.tests.functional.agent.test_l3_agent.MetadataL3AgentTestCase.test_access_to_metadata_proxy times out intermittently
 
** [https://bugs.launchpad.net/neutron/+bug/1461172] neutron.tests.functional.agent.test_l3_agent.MetadataL3AgentTestCase.test_access_to_metadata_proxy times out intermittently
 
** [https://bugs.launchpad.net/neutron/+bug/1439696] Referencing a lb-healthmonitor ID for the first time from Heat would fail
 
** [https://bugs.launchpad.net/neutron/+bug/1439696] Referencing a lb-healthmonitor ID for the first time from Heat would fail
** [https://bugs.launchpad.net/neutron/+bug/1404743] sporadic test failures due to VMs not getting a DHCP lease
 
 
** [https://bugs.launchpad.net/neutron/+bug/1378732] migrate_to_ml2 script doesn't work for Juno release
 
** [https://bugs.launchpad.net/neutron/+bug/1378732] migrate_to_ml2 script doesn't work for Juno release
 
** [https://bugs.launchpad.net/neutron/+bug/1163569] security groups don't work with vip and ovs plugin
 
** [https://bugs.launchpad.net/neutron/+bug/1163569] security groups don't work with vip and ovs plugin
Line 54: Line 54:
  
 
=== On Demand Agenda ===
 
=== On Demand Agenda ===
 +
* Stable branches for networking subproject
 +
** Discussion on this happened in July, decision which wasn't clear was here:
 +
*** http://lists.openstack.org/pipermail/openstack-dev/2015-July/068785.html
 +
** Currently, gerrit ACLs allow only neutron-stable-maint to merge stable patches here
 +
** Stable has meaning, and we have to follow rules of stable backports
 +
** Question: What does the team want here?
 
* 3rd party Ci systems: Can they vote -1?
 
* 3rd party Ci systems: Can they vote -1?
 
** https://review.openstack.org/207198
 
** https://review.openstack.org/207198

Revision as of 18:15, 12 August 2015


Meeting time: The OpenStack Networking Team (Neutron) holds public meetings alternating between Mondays at 2100 UTC (#openstack-meeting) and Tuesdays at 1400 UTC (#openstack-meeting). Everyone is encouraged to attend.

Apologies for Absence

Agenda for Next Neutron Team Meeting

Monday (8/17/2015) at 2100 UTC on #openstack-meeting

Announcements / Reminders

Bugs


Important bugs:

    • [1] sporadic test failures due to VMs not getting a DHCP lease
    • [2] neutron test_multi_prefix_slaac failing in the gate with ping failures starting around 7/22
    • [3] neutron.tests.functional.agent.test_l3_agent.MetadataL3AgentTestCase.test_access_to_metadata_proxy times out intermittently
    • [4] Referencing a lb-healthmonitor ID for the first time from Heat would fail
    • [5] migrate_to_ml2 script doesn't work for Juno release
    • [6] security groups don't work with vip and ovs plugin
  • Two bugs are hurting the functional job in the gate:
    • [7] agent.test_l3_agent.MetadataL3AgentTestCase.test_access_to_metadata_proxy times out intermittently
    • [8] radvd exits -1 intermittently in test_ha_router_process_ipv6_subnets_to_existing_port
  • Linuxbridge Gate Parity Bugs
    • [9] nova libvirtError: Unable to add bridge brqxxx-xx port tapxxx-xx: Device or resource busy


Docs (emagana)

Open Items for Liberty: (reviews needed)

Networking Guide

On Demand Agenda

  • Stable branches for networking subproject
  • 3rd party Ci systems: Can they vote -1?
  • Liberty-3 BPs and reviews
  • Concrete plan to merge back pecan and QoS work
    • Need to do this very early after Liberty-2 is cut this week
  • nova-network compatibility tasks
    • Summit session(s) in Vancouver were very productive
    • Tasks tracked here: https://etherpad.openstack.org/p/YVR-nova-network
    • Need to find owners for a few of these
      • Rolling upgrades (mostly a grenade patch)
      • Distributed SNAT with DVR
      • "Get me a network (https://review.openstack.org/#/c/184857/) (kevinbenton to own this)
      • ARP Spoof patch series is stalled, need to make a decision on how to proceed. (kevinbenton will do this after beating requirements out of markmcclain)
  • macvtap ml2 driver and agent - will land in neutron tree. Question is how to procede with agent code (scheuran)
    • 1) Copy (duplicate) required agent code like in the past.
    • 2) Extract a common base class for macvtap, linuxbridge and sriov-nic (impls are close to each other). Purpose: Sharing base agent code. Starting with macvtap only in liberty. Moving others to common base class in Mitaka. New agent base class cannot be used for OVS, as it already diverged too much from others.
      • Liberty: only methods that are obious common and only differ in details that can be abstracted (_setup_rpc, _report_state, _device_info_has_changes, _process_network_devices)
      • Mitaka: Methods that have a lot of common code, but require fruther thinking (treat_devices_added_updated, scan_devices, daemon_loop)
      • N: Having a common agent with interface drivers?
    • Modular l2 agent (spec not in a good shape) and agent extension (is just for extending existing agents) is is not an option

Previous meeting logs