Jump to: navigation, search

Difference between revisions of "Network/Meetings"

Line 8: Line 8:
  
 
== Agenda for Next Quantum Team Meeting ==
 
== Agenda for Next Quantum Team Meeting ==
* Announcements:  
+
* Announcement:  
** Folsom-3 is out: https://launchpad.net/quantum/+milestone/folsom-3
+
** Quantum Folsom RC1 targeted for 9/10.  Two short weeks out.
 +
** python-quantumclient will be subject to feature-freeze. 
 
* Folsom RC1: https://launchpad.net/quantum/+milestone/folsom-rc1   
 
* Folsom RC1: https://launchpad.net/quantum/+milestone/folsom-rc1   
** RC Goal: stabilize and release existing feature-set.
+
** We need full attention from core devs... next two weeks is crunch time and we are behind.    
** Focus should be on testing, bug-fixing, and documentation. 
+
** RC-phase rules:
** DATE: depends on bugs outstanding.  Target week of 9/3 (i.e., two weeks from now). 
+
*** Core devs: do not spend cycles on anything that is not targeted for rc1
** no new features without a 'feature freeze exception' (FFE)
+
*** Everyone: please do not even propose patches that are not targeted for rc1
** NOTE: filing something as a 'bug' rather than a 'bp' does not make it a bug.  Could should make existing functionality work properly (fixing bugs or filling in "gaps"), not introduce new capabilities. 
+
*** Everyone: Only core-devs can target bugs to rc1
** Point of freeze is not just to stabilize code.  Also to free up developer + reviewer cycles to focus on on testing + bugfixing.
+
*** Everyone: If a non-core dev has a bug they think needs to be targeted to rc1, please let PTL or core dev know, or send email to ML.  
** FFE work should be available for non-WIP review by end of week, otherwise we need to revisit FFE grant.   
+
* Taking an Axe to current set of bps/bugs.   
** python-quantumclient + devstack are NOT subject to FFE, as they do not have the same release schedule.   
+
** Expect to see blueprints/bugs moved out todayPlanned to remove:
** Granted FFEs:
+
*** XML v2 support
*** L3 + Floating IPs
+
*** multi-host dhcp
**** main branch merged.   
+
*** per-port host routes
**** a few additional changes coming as separate change-sets, including LB support. 
+
*** carlp, nova metadata service + overlapping IPs
** provider networks (phase 2 - OVS)
+
*** nova proxy for floating ips:
*** Bob is wrapping up this branch from F-3: https://bugs.launchpad.net/quantum/+bug/1037341
+
* Existing FFEs:
 +
** Bob is wrapping up this branch from F-3: https://bugs.launchpad.net/quantum/+bug/1037341
 
** Quantum test-agent
 
** Quantum test-agent
 
*** https://review.openstack.org/#/c/11189/
 
*** https://review.openstack.org/#/c/11189/
 
*** critical for devstack gating.   
 
*** critical for devstack gating.   
** rootwrap in Quantum
+
* rootwrap in Quantum
*** https://review.openstack.org/#/c/11524/
+
** https://review.openstack.org/#/c/11524/
* Under Consideration FFEs:
 
** multi-host
 
*** important gap between nova-network + quantum.  may result in forcing openstack docs to steer users to nova-network over quantum. 
 
*** https://blueprints.launchpad.net/quantum/+spec/quantum-multihost-dhcp
 
* XML support
 
** existing review is not in good standing: https://review.openstack.org/#/c/10856/1
 
** need a firm plan here fast.
 
* Other "Large" Bugs:
 
** NOTE: moving forward, filing a bug as high or above means we consider it release critical.  We will begin tracking those in detail starting next meeting. 
 
** markmclain, unable to delete network with dhcp: https://bugs.launchpad.net/quantum/+bug/1028174
 
** (no one), nova calls for floating ips with quantum: https://bugs.launchpad.net/bugs/1023169 and https://bugs.launchpad.net/bugs/1031119
 
** carlp, nova metadata service + overlapping IPs: https://bugs.launchpad.net/bugs/1038098
 
** nachi, host route distribution via dhcp: https://bugs.launchpad.net/quantum/+bug/1022737
 
 
* Folsom Documentation work:  
 
* Folsom Documentation work:  
 +
** Needs to be focus on 30% of time moving forward.
 
** API spec (point person: Salvatore)
 
** API spec (point person: Salvatore)
 
** Admin/User Guide (point person: Dan)
 
** Admin/User Guide (point person: Dan)

Revision as of 20:59, 27 August 2012


The OpenStack Quantum Team holds public meetings in #openstack-meeting. Everyone is encouraged to attend.

Apologies for Absence

  • Edgar Magana

Agenda for Next Quantum Team Meeting

  • Announcement:
    • Quantum Folsom RC1 targeted for 9/10. Two short weeks out.
    • python-quantumclient will be subject to feature-freeze.
  • Folsom RC1: https://launchpad.net/quantum/+milestone/folsom-rc1
    • We need full attention from core devs... next two weeks is crunch time and we are behind.
    • RC-phase rules:
      • Core devs: do not spend cycles on anything that is not targeted for rc1
      • Everyone: please do not even propose patches that are not targeted for rc1
      • Everyone: Only core-devs can target bugs to rc1
      • Everyone: If a non-core dev has a bug they think needs to be targeted to rc1, please let PTL or core dev know, or send email to ML.
  • Taking an Axe to current set of bps/bugs.
    • Expect to see blueprints/bugs moved out today. Planned to remove:
      • XML v2 support
      • multi-host dhcp
      • per-port host routes
      • carlp, nova metadata service + overlapping IPs
      • nova proxy for floating ips:
  • Existing FFEs:
  • rootwrap in Quantum
  • Folsom Documentation work:
    • Needs to be focus on 30% of time moving forward.
    • API spec (point person: Salvatore)
    • Admin/User Guide (point person: Dan)
  • Open Discussion

Previous meetings, with their notes and logs, can be found in under ../MeetingLogs.