Network/Meetings

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.

Agenda for Next Neutron Team Meeting

Monday (3/10/2015) at 1400 UTC on #openstack-meeting

Announcements / Reminders

• Kilo dates to be aware of:
  • Feature Proposal Freeze: March 5
  • Feature, String, and Dependency Freeze: March 19
  • RCs: April 9-23
  • Kilo release: April 30
  • https://wiki.openstack.org/wiki/Network/Meetings
• Kilo-3 LP page:
  • https://launchpad.net/neutron/+milestone/kilo-3
• OpenStack Client IRC meetings
  • Thursdays at 19:00 UTC in #openstack-meeting
  • https://wiki.openstack.org/wiki/Meetings/OpenStackClient#Next_Meeting_Agenda
  • Since we want to deprecate the client, would be great to get a representative to attend these
• Neutron Policies are documented here:
  • https://wiki.openstack.org/wiki/NeutronPolicies

Bugs

Important bugs:

• • [1] Ensure a smooth upgrade path after adv svc split
  • [2] Failure to allocate tunnel id when creating networks concurrently
  • [3] br-tun lost ports/flows if openvswitch restart
  • [4] Security group rules errorneously applied to all ports having same ip addresses in different networks
  • [5] ping still working after security group rule is created, updated, or deleted (related to previous one)

These bugs are in nova but are related to neutron. It would be great if we could get neutron reviews on:

• • Merged [6] Remove unneeded call to fetch network info on shutdown - arosen
  • Merged [7] remove unneeded call to network_api on detach_interface - arosen
  • Merged [8] remove unneeded call to network_api on rebuild_instance - arosen
  • Merged [9] Optimize validate_networks to query neutron only when needed - arosen
  • [10] deallocate_for_instance should delete all neutron ports on error - arosen
  • [11] Fix port_security_enabled neutron extension - arosen
  • [12] Fix pre-created ports in neutron from being deleted by nova - arosen

Docs (emagana)

Open Items for Kilo: (feedback needed)

• Legacy scenario OVS: https://github.com/ionosphere80/openstack-networking-guide/blob/master/scenario-legacy-ovs/scenario-legacy-ovs.md
• Legacy scenario LB: https://github.com/ionosphere80/openstack-networking-guide/blob/master/scenario-legacy-lb/scenario-legacy-lb.md
• New networking diagrams for DVR: https://github.com/ionosphere80/openstack-networking-guide/blob/master/scenario-dvr/scenario-dvr.md

Networking Guide:

• ToC: https://wiki.openstack.org/wiki/NetworkingGuide/TOC
• Gerrit: https://github.com/openstack/openstack-manuals/tree/master/doc/networking-guide
• Minutes from 1/30/15 meeting: http://lists.openstack.org/pipermail/openstack-docs/2015-January/005776.html

On Demand Agenda

• Should the *aas repos be depending on neutron HEAD?
  • Depending on a known-good git hash would separate development effort from ensuring compatibility with neutron
  • Periodic jobs could be used to detect when compatibility has been broken
• The future of Xen + OVS support
  • Does anyone care enough to devote resources to ensuring continued support, or should we deprecate?
• Plugin Decomposition Status and Updates
  • Update from Ihar on packagers dealing with decomposition
  • Spec is published here: http://specs.openstack.org/openstack/neutron-specs/specs/kilo/core-vendor-decomposition.html
  • Status updates and timelines
• Nova-Network to Neutron Migration
  • anteaya to give an update (http://lists.openstack.org/pipermail/openstack-dev/2014-December/053355.html)
• Neutron as the default in DevStack
  • We need to document and create a single interface configuration - https://review.openstack.org/#/c/153208/
• Report on progress of "MTU selection and advertisement" blueprint implementation.
• VPNaaS
  • Discussions will be held as on-demand topic, when needed, in Neutron meeting.
  • Need review of StrongSwan implementation to make K-3 Review 144391
  • Refactoring started for VPN agent to remove L3-agent dependency Review 160179
  • Setting up functional job for StrongSwan implementation Review 158389
• Proposal to remove py3* from the default tox envlist for now to address "fail blindness" Review 137516
  • Only default tox envlist. Environments are still there, `tox -e$venv` is unchanged.
  • Plan is to restore it when it is expected to pass (ie: blocked on eventlet).
  • Breathe, it's going to be ok :-)

Previous meeting logs

• Previous meetings, with their notes and logs, can be found here.
  • networking-2015
  • networking-2014
  • networking-2013
  • quantum-2013
  • quantum-2012
• Older meeting notes are here: ../MeetingLogs.