Difference between revisions of "Network/Meetings"

Revision as of 19:40, 26 February 2015

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.

Apologies for Absence

Agenda for Next Neutron Team Meeting

Tuesday (3/2/2015) at 2100 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
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

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/
Dims needs Project Ideas, Mentors for GSoC 2015 - https://wiki.openstack.org/wiki/GSoC2015 (dims or dims__)
Report on progress of "MTU selection and advertisement" blueprint implementation.

Previous meeting logs

Previous meetings, with their notes and logs, can be found here.
Older meeting notes are here: ../MeetingLogs.

@@ Line 62: / Line 62: @@
 ** We need to document and create a single interface configuration - https://review.openstack.org/#/c/153208/
 * Dims needs Project Ideas, Mentors for GSoC 2015 - https://wiki.openstack.org/wiki/GSoC2015 (dims or dims__)
-* OVS and LinuxBridge agent configuration files
-** Prior to ML2, OVS and LinuxBridge were plugins with their own configuration files, ovs_neutron_plugin.ini and linuxbridge_conf.ini, respectively. After ML2, these plugins became agents/mechanisms and the installation guide now configures them in the ml2_conf.ini file using [ovs], [agent], etc. [1]. However, some downstream packagers still use ovs_neutron_plugin.ini and linuxbridge_conf.ini, the former of which generates the most confusion because it contains the word "plugin" and doesn't relate to a plugin anymore. These differing opinions periodically generate documentation bugs [2][3] that lack clear resolution. Can we officially resolve this issue? If separate files make sense, I suggest renaming them to reduce confusion regarding where they fit into the big picture... such as ml2_conf_ovs.ini, ovs_agent_conf.ini, etc.
-** [1] http://docs.openstack.org/juno/install-guide/install/apt/content/neutron-network-node.html
-** [2] https://bugs.launchpad.net/openstack-manuals/+bug/1422038
-** [3] https://bugs.launchpad.net/openstack-manuals/+bug/1375746
 * Report on progress of "MTU selection and advertisement" blueprint implementation.