Jump to: navigation, search

Difference between revisions of "Network/Meetings"

(Announcements / Reminders)
(IPv6 (sc68cal))
Line 77: Line 77:
  
 
=== IPv6 (sc68cal) ===
 
=== IPv6 (sc68cal) ===
* Subteam meeting - discussed getting IPv6 working w/ SLAAC
+
* No meeting last week due to US holiday
** [https://review.openstack.org/#/c/58186/1|Adds IPv6 SLAAC Support to Neutron]
+
* Meeting this week scheduled for regular time (Thursday 2100 UTC, #openstack-meeting-alt)
** [https://blueprints.launchpad.net/openstack/?searchtext=dnsmasq-mode-keyword| Add support for IPv6 configuration in dnsmasq]
 
** Subteam will be doing code reviews, looking for places where IPv4 works but IPv6 doesn't
 
*** Horizon
 
  
 
=== ML2 (mestery/rkukura) ===
 
=== ML2 (mestery/rkukura) ===

Revision as of 19:33, 2 December 2013


The OpenStack Networking Team (Neutron) holds public meetings in #openstack-meeting. Everyone is encouraged to attend.

Apologies for Absence

  • amotoki

Agenda for Next Neutron Team Meeting

Announcements / Reminders

Bugs

Critical Open Bugs

(Note: replaces https://bugs.launchpad.net/neutron/+bug/1250168)

Docs (emagana)

Nova Parity (beagles)

  • There is a rough sketch for parity related milestones on https://etherpad.openstack.org/p/icehouse-neutron-nova-parity-prelim-outline.
    • These milestones will need to be refined and it may be more clear to separate them into functional groups (i.e. parity-feature-tracking, tempest-parity-test, etc)
    • An immediate objective would be to round-up what has already been down so far as part of the excellent efforts being made to clean up the tests in the past two weeks
    • As it is relevant for some of the gate failures, I propose that we do a functional tear-down of the integration module (nova/network/neutronv2) starting today and revisit areas where there are differences in behavior, describe them and:
      • examine if the differences are parity-blockers and get "sign-off" by the nova team and whomever else is appropriate,
      • agree that the implementations are still the most appropriate.
either might make some of the gate-bug-hunting moot (e.g. the mulitple network thing)
  • In addition to the above, there are some networking related operations available through nova that are not implemented "properly" (bulk floating ip operations) and may or may not be "mappable" to neutron. I intend to introduce them at the nova IRC meeting later this week and start the dialogue about how they want to handle them. If anybody is aware of specific issues of this sort that they would like me to include, please ping me via IRC or email before Thursday, 28-11-2013 0900 UTC and I'll get it in there.

Neutron Tempest (mlavalle)

API (salv-orlando)

No report

IPv6 (sc68cal)

  • No meeting last week due to US holiday
  • Meeting this week scheduled for regular time (Thursday 2100 UTC, #openstack-meeting-alt)

ML2 (mestery/rkukura)

  • Weekly ML2 meetings are held, please attend if interested!
  • Acion items from last meeting:
    • Discussion with QA team this week about multi-node testing in the gate
    • asomya to review TypeDriver patch providing extra port information
  • Continuing to focus on Summit blueprint work.

VPN (nachi)

tbd

FWaaS (snaiksat)

We will again start the weekly team meetings in the week of Dec 2nd. Waiting for PTL to get back on the proposed Icehouse plan (some blueprints have been pushed out to I3).

LBaaS (enikanorov)

tbd

Other team reports (e.g. Open Source Plugins)

Open Discussion

Previous meeting logs