Jump to: navigation, search

Difference between revisions of "Network/Meetings"

(Bugs)
(Nova Parity (beagles))
Line 35: Line 35:
 
=== Nova Parity (beagles) ===
 
=== Nova Parity (beagles) ===
 
* Parity related milestones on https://etherpad.openstack.org/p/icehouse-neutron-nova-parity-prelim-outline.
 
* Parity related milestones on https://etherpad.openstack.org/p/icehouse-neutron-nova-parity-prelim-outline.
** Any new feedback? There wasn't much (any?) last week.
+
** I updated the milestones. Basically, with the holiday season things are looking rough.
** 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 e-mail went out to enquire about mimicking nova-network manager behaviors. I've create a starting point Wiki [[NovaNetNeutronRecipies]] that has some grist from an earlier parity doc.  
*** I think this still holds. Should we select individuals to take the lead on each area.
+
* Etherpad is garbage for really tracking stuff. Moving to [[NovaNetNeutronParity]]
** 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.
 
*** Running smokestack last week garnered several failures... some of which were pretty weird. During investigation I resolved some by adding some sanity around state syncing and others were resolved by improving handling of missing records. What else is pending?
 
** 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.
 
* I need some volunteers to look at "cookbooks" for mimicing nova-network "NetworkManager" behaviors.
 
 
 
* 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, 5-12-2013 0900 UTC and I'll get it in there. (Pushed from last week due to Thanksgiving)
 
  
 
=== Neutron Tempest (mlavalle) ===
 
=== Neutron Tempest (mlavalle) ===

Revision as of 20:23, 9 December 2013


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

Apologies for Absence

Agenda for Next Neutron Team Meeting

Announcements / Reminders

Bugs

Critical Open Bugs

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

    • Salvatore expects https://bugs.launchpad.net/swift/+bug/1224001 to be resolved when the patches to enable parallel testing are merged, do we have a gerrit url for neutron parallel testing and a timeline for merging? - just 3 hits since the 6th

Docs (emagana)

Nova Parity (beagles)

Neutron Tempest (mlavalle)

API (salv-orlando)

No report

IPv6 (sc68cal)

ML2 (mestery/rkukura)

VPN (nachi)

WIP for SSL-VPN API patch https://review.openstack.org/#/c/58897/

FWaaS (snaiksat)

garyduan has posted WIP patch for integration of FWaaS with service provider framework - https://review.openstack.org/#/c/60699. 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