Jump to: navigation, search

Difference between revisions of "Network/Meetings"

(Apologies for Absence)
Line 5: Line 5:
 
== Apologies for Absence ==
 
== Apologies for Absence ==
 
We expect core members to attend on a regular basis, especially during the meeting that is friendly to your timezone. If you can't, please add a note here.
 
We expect core members to attend on a regular basis, especially during the meeting that is friendly to your timezone. If you can't, please add a note here.
 
* amotoki -- will join late and cannot join first 20 minutes or some.
 
  
 
=== Announcements / Reminders ===
 
=== Announcements / Reminders ===
* Please make sure you are adding release notes for changes going in
+
* Pep8 gate validation - https://review.openstack.org/#/c/253676
** This includes reviewing patches and ensuring they have release notes added for new features
 
** http://docs.openstack.org/developer/reno/usage.html#creating-new-release-notes
 
* process change for closing bugs when patches merge -  http://lists.openstack.org/pipermail/openstack-dev/2015-November/080288.html
 
* Backwards compatibility for clients and libraries - https://review.openstack.org/#/c/226157/
 
* Release week - M-1 will be cut for neutron, neutron-lbaas, neutron-fwaas, neutron-vpnaas sometime mid-week, either by armax of mestery.
 
* Evolving the stadium - http://lists.openstack.org/pipermail/openstack-dev/2015-December/080865.html
 
  
 
=== Blueprints ===
 
=== Blueprints ===
  
Current milestone: https://launchpad.net/neutron/+milestone/mitaka-1 (ends Dec 1st)
+
Current milestone: https://launchpad.net/neutron/+milestone/mitaka-2 (ends Jan 16 2016)
  
 
=== Bugs ===
 
=== Bugs ===
Line 87: Line 79:
  
 
We can only pick one or two topics we can talk in the time left of the meeting. People should add ideas to the topics section. We will select one or two topics we can chew during the next meeting. Please follow the template below:
 
We can only pick one or two topics we can talk in the time left of the meeting. People should add ideas to the topics section. We will select one or two topics we can chew during the next meeting. Please follow the template below:
 
* Gate hook enabled job: do we want another gate job?
 
** we need a job to enable QoS service and allow tempest scenarios for that.
 
*** we have other services that may require something similar (flavor?)
 
*** we have gate hook enabled job proposed for neutron gate: https://review.openstack.org/#/q/status:open+branch:master+topic:neutron-tempest-gate-hook,n,z
 
*** are we ok with another job in gate? or we better enable services in existing integrated jobs?
 
*** if we want it in integrated jobs, then we are forced to move qos devstack stuff back from devstack plugin into devstack (as per infra folks). While initially we were requested to do it vice versa.
 
  
 
* Topic for the meeting:
 
* Topic for the meeting:

Revision as of 20:28, 4 December 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

We expect core members to attend on a regular basis, especially during the meeting that is friendly to your timezone. If you can't, please add a note here.

Announcements / Reminders

Blueprints

Current milestone: https://launchpad.net/neutron/+milestone/mitaka-2 (ends Jan 16 2016)

Bugs

Approximate stats for the current cycle:

  • From Mitaka beginning (Sep-23-2015), to the end of the week of Nov-30-2015 (previous week in parenthesis):
    • Total reports: 373 (335)
      • Fix committed: 144 (125)
      • Unassigned: 73 (67)
        • New: 17 (15)
        • Incomplete: 20 (19)
        • Confirmed: 27 (26)
        • Triaged: 6 (6)
  • For the weeks from Nov-23-2015 to Nov-30-2015:
    • Total reports: 49 (30)
      • Fix committed: 7 (5)
      • Unassigned: 14 (8)
        • New: 9 (3)
        • Incomplete: 0 (2)
        • Confirmed: 4 (3)
        • Triaged: 1 (0)

Bug deputy

Use this section to keep track of who volunteers for the 'bug deputy' role. This is usually edited at the end of the IRC Meeting.

Date ihrachys regXboi markmcclain armax mestery mangelajo garyk rossella_s dougwig
Oct-05-2015 x
Oct-12-2015 x
Oct-19-2015 x
Oct-24-2015 x
Nov-02-2015 x
Nov-09-2015 x
Nov-16-2015 x
Nov-23-2015 x
Nov-30-2015 x

Docs (emagana)

Open Items for Liberty: (reviews needed)

Networking Guide

On Demand Agenda

We can only pick one or two topics we can talk in the time left of the meeting. People should add ideas to the topics section. We will select one or two topics we can chew during the next meeting. Please follow the template below:

  • Topic for the meeting:
    • <Topic title> <submitter> <date submitted>
      • <brief description>
  • Topic for the meeting:
    • Add here

Previous meeting logs