Jump to: navigation, search

Difference between revisions of "Network/Meetings"

Line 9: Line 9:
 
== Agenda for Next Quantum Team Meeting ==
 
== Agenda for Next Quantum Team Meeting ==
 
* Announcements:  
 
* Announcements:  
** Quantum support in Horizon merged.
+
** Folsom-3 is out: https://launchpad.net/quantum/+milestone/folsom-3
** About to release python-quantumclient 2.0 (so nova + horizon can properly depend on it in pip-requires).
+
* Folsom RC1: https://launchpad.net/quantum/+milestone/folsom-rc1 
* Folsom-3:   https://launchpad.net/quantum/+milestone/folsom-3
+
** RC Goal: stabilize and release existing feature-set.
** Huge effort by Quantum team over the weekend... great work!
+
** Focus should be on testing, bug-fixing, and documentation.
** All F-3 features must be reviewed and in by end-of-day Tuesday (Pacific time).  
+
** DATE:  depends on bugs outstanding.  Target week of 9/3 (i.e., two weeks from now).
** If you are no longer working on a major branch for F-3, focus should shift to testing.  
+
** no new features without a 'feature freeze exception' (FFE)
** Folsom feature-freeze exception (ffes) will be VERY limitedFocus on "community-wide" benefit.   
+
** NOTE: filing something as a 'bug' rather than a 'bp' does not make it a bugCould should make existing functionality work properly (fixing bugs or filling in "gaps"), not introduce new capabilities.   
** Review Status:
+
** Point of freeze is not just to stabilize code.  Also to free up developer + reviewer cycles to focus on on testing + bugfixing. 
*** provider networks:
+
** FFE work should be available for non-WIP review by end of week, otherwise we need to revisit FFE grant.   
**** one review close to merge: https://review.openstack.org/#/c/10938/ (dan + salv are cores)
+
** python-quantumclient + devstack are NOT subject to FFE, as they do not have the same release schedule.   
**** another review for OVS support expected tomorrow.   
+
** Granted FFEs:  
** L3 fwd + nat:  
+
*** L3 + Floating IPs
*** Branches for server, agent, and CLI are fully functional.  unit tests for agent + CLI are not finished, hence WIP.  (aaron & maru are cores)
+
**** main branch merged.  
*** slicing off some smaller portions for separate review, including: https://review.openstack.org/#/c/11259/
+
**** a few additional changes coming as separate change-sets, including LB support.
*** non-polling wont' make F-3, possible ffe candidate.  
+
** provider networks (phase 2 - OVS)
** DBplugin impl for host-routes, dnsnameservers.
+
*** Bob is wrapping up this branch from F-3: https://bugs.launchpad.net/quantum/+bug/1037341
*** ready to be approved: https://review.openstack.org/#/c/10791/ (salvatore & aaron are cores)
+
** Quantum test-agent
** Non-polling for DHCP:
+
*** important for devstack gating.   
*** https://review.openstack.org/#/c/10997/ (garyk & sumit are cores)
+
** rootwrap in Quantum
** per-tenant API quotas:
+
*** https://review.openstack.org/#/c/11524/
*** https://review.openstack.org/#/c/10484/
+
* Under Consideration FFEs:
*** dan & yong need to iron out a design issue (talk on IRC after the meeting?)
+
** multi-host
** devstack gating + v2:
+
*** important gap between nova-network + quantummay result in forcing openstack docs to steer users to nova-network over quantum.  
*** still needs some attention. 
 
*** https://review.openstack.org/#/q/topic:bp/test-agent,n,z 
 
** multi-host DHCP
 
*** definitely at riskpossible candidate for ffe.  
 
 
*** https://blueprints.launchpad.net/quantum/+spec/quantum-multihost-dhcp
 
*** https://blueprints.launchpad.net/quantum/+spec/quantum-multihost-dhcp
* Discussion topics
+
* XML support
** XML support: https://review.openstack.org/#/c/10856/1
+
** existing review is not in good standing: https://review.openstack.org/#/c/10856/1
** rootwrap in Quantum (thread on ML)
+
** need a firm plan here fast.
** 'device_owner' attribute of a port, device_id as a UUID. https://review.openstack.org/#/c/10922/
+
* Key Bugs:  
** Documentation work: API spec (Salvatore) and Admin/User Guide (Dan)
+
**  
 +
* Folsom Documentation work:  
 +
** API spec (point person: Salvatore)
 +
** Admin/User Guide (point person: Dan)
 
* Open Discussion
 
* Open Discussion
  
 
Previous meetings, with their notes and logs, can be found in under ../MeetingLogs.
 
Previous meetings, with their notes and logs, can be found in under ../MeetingLogs.

Revision as of 20:44, 20 August 2012


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

Apologies for Absence

Agenda for Next Quantum Team Meeting

  • Announcements:
  • Folsom RC1: https://launchpad.net/quantum/+milestone/folsom-rc1
    • RC Goal: stabilize and release existing feature-set.
    • Focus should be on testing, bug-fixing, and documentation.
    • DATE: depends on bugs outstanding. Target week of 9/3 (i.e., two weeks from now).
    • no new features without a 'feature freeze exception' (FFE)
    • 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.
    • Point of freeze is not just to stabilize code. Also to free up developer + reviewer cycles to focus on on testing + bugfixing.
    • FFE work should be available for non-WIP review by end of week, otherwise we need to revisit FFE grant.
    • python-quantumclient + devstack are NOT subject to FFE, as they do not have the same release schedule.
    • Granted FFEs:
      • L3 + Floating IPs
        • main branch merged.
        • a few additional changes coming as separate change-sets, including LB support.
    • provider networks (phase 2 - OVS)
    • Quantum test-agent
      • important for devstack gating.
    • rootwrap in Quantum
  • Under Consideration FFEs:
  • XML support
  • Key Bugs:
  • Folsom Documentation work:
    • 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.