Jump to: navigation, search

Difference between revisions of "Meetings/Neutron-DVR"

Line 9: Line 9:
  
 
= Agenda =
 
= Agenda =
== Meeting March 23rd , 2016 ==
+
== Meeting March 30th , 2016 ==
  
 
=== Announcements (haleyb) ===
 
=== Announcements (haleyb) ===
Line 15: Line 15:
  
 
* We still have one high bug:
 
* We still have one high bug:
** FloatingIP ping comes through the SNAT namespace
 
 
* When adding items below I'd like to try to get feedback on whether they are a MUST FIX, SHOULD FIX, or GOOD TO HAVE
 
* When adding items below I'd like to try to get feedback on whether they are a MUST FIX, SHOULD FIX, or GOOD TO HAVE
  
Line 25: Line 24:
  
 
==== New Bugs this week ====
 
==== New Bugs this week ====
*https://bugs.launchpad.net/neutron/+bug/1560945
+
 
 +
* https://bugs.launchpad.net/neutron/+bug/1526855 - (SHOULD FIX)
 +
* https://bugs.launchpad.net/neutron/+bug/1563879 ( RFE)
 +
* https://bugs.launchpad.net/neutron/+bug/1557290 ( RFE)
 +
 
 
==== Categorized Bugs ====
 
==== Categorized Bugs ====
  
Line 47: Line 50:
 
*** and nova https://review.openstack.org/#/c/246910/ (Needs review) Notify vif plugged event (related)
 
*** and nova https://review.openstack.org/#/c/246910/ (Needs review) Notify vif plugged event (related)
  
* https://bugs.launchpad.net/neutron/+bug/1462154 (High) - DVR pings to floatingip replied with fixed ips (SHOULD FIX)
 
** https://review.openstack.org/246855
 
** Doesn't seem to be making progress?
 
  
 
* https://bugs.launchpad.net/neutron/+bug/1445255 (Low) - DVR Floatingip to unbound port does not work (Allowed address pair) (SHOULD FIX)
 
* https://bugs.launchpad.net/neutron/+bug/1445255 (Low) - DVR Floatingip to unbound port does not work (Allowed address pair) (SHOULD FIX)
Line 81: Line 81:
  
 
==== Bugs Closed Recently====
 
==== Bugs Closed Recently====
 +
* https://bugs.launchpad.net/neutron/+bug/1462154 (High) - DVR pings to floatingip replied with fixed ips (SHOULD FIX) - Patch Merged
 +
** https://review.openstack.org/246855
 +
** Doesn't seem to be making progress?
 +
 
* https://bugs.launchpad.net/neutron/+bug/1533216 (Low) - Item allocator should return same value for key (GOOD TO HAVE)
 
* https://bugs.launchpad.net/neutron/+bug/1533216 (Low) - Item allocator should return same value for key (GOOD TO HAVE)
 
** https://review.openstack.org/266379 (Related Patch) - Patch Merged.
 
** https://review.openstack.org/266379 (Related Patch) - Patch Merged.
 +
*https://bugs.launchpad.net/neutron/+bug/1560945 - Patch merged. ( SHOULD FIX)
  
 
=== Performance/Scalability (obondarev) ===
 
=== Performance/Scalability (obondarev) ===
Line 92: Line 97:
 
* Current failure rate: https://goo.gl/L1WODG
 
* Current failure rate: https://goo.gl/L1WODG
 
** Single node check job failure rates stabilized 3/14 and are below 6% (non-DVR and DVR)
 
** Single node check job failure rates stabilized 3/14 and are below 6% (non-DVR and DVR)
** Multi-node check job failure rates have spiked and stay high, 40-50% failure (need to check it out - also the neutron mutinode job has spiked)
+
** Multi-node check job failure rate spike have gone down from last week
 
*** Bugs in Nova:
 
*** Bugs in Nova:
 
**** https://bugs.launchpad.net/nova/+bug/1524898 (Volume based live migration aborted unexpectedly)
 
**** https://bugs.launchpad.net/nova/+bug/1524898 (Volume based live migration aborted unexpectedly)
Line 98: Line 103:
 
* Debug the gate in the current failure state (Identify owners who can own this)
 
* Debug the gate in the current failure state (Identify owners who can own this)
 
* https://bugs.launchpad.net/neutron/+bug/1515360 - Tempest "SSHTimeout" failures (GOOD TO HAVE) - This patch seem to have some timing issues and so we are seeing more failures for the pings.
 
* https://bugs.launchpad.net/neutron/+bug/1515360 - Tempest "SSHTimeout" failures (GOOD TO HAVE) - This patch seem to have some timing issues and so we are seeing more failures for the pings.
** https://review.openstack.org/#/c/247748/ (add debugging code to l3-agent) - Still pings are not consistent with the tempest.
 
 
*https://drive.google.com/file/d/0B4kh-7VVPWlPMkdrQWFFdjNsSnM/view?usp=sharing - Logstash failures captured. Any logstash errors can be captured here
 
*https://drive.google.com/file/d/0B4kh-7VVPWlPMkdrQWFFdjNsSnM/view?usp=sharing - Logstash failures captured. Any logstash errors can be captured here
  

Revision as of 14:20, 30 March 2016

The OpenStack Networking L3 DVR Sub-team holds public meetings as advertised on OpenStack IRC Meetings Calendar. If you are unable to attend, please check the most recent logs.

Meetings

Agenda

Meeting March 30th , 2016

Announcements (haleyb)

  • Mitaka milestone RC1 released, RC2 planned from what I've seen
  • We still have one high bug:
  • When adding items below I'd like to try to get feedback on whether they are a MUST FIX, SHOULD FIX, or GOOD TO HAVE

Topics for Discussion

Bugs (Swami)

All DVR bugs should be tagged and listed here: https://bugs.launchpad.net/neutron/+bugs?field.tag=l3-dvr-backlog

New Bugs this week

Categorized Bugs

Gate Test Failures

Existing Functionality Broken Bugs


Scale and Performance Impact Bugs

New Features Bugs

Refactor or Cleanup Bugs

WishList Bugs

WatchList Bugs

Bugs Closed Recently

Performance/Scalability (obondarev)

Discuss a plan to address the gate failures (haleyb)

Open Discussion

Meeting commands

/join #openstack-meeting-alt
#startmeeting neutron_dvr
#topic Announcements
#undo topic
#link https://wiki.openstack.org/wiki/Meetings/Neutron-DVR
#action haleyb will get something specific done this week
#chair Swami
...
#endmeeting