|
|
Line 79: |
Line 79: |
| **These back-ports are not allowed because they need to be in sync with master branch. | | **These back-ports are not allowed because they need to be in sync with master branch. |
| **The corresponding fixes are blocked in master pending decomposition of driver/plugin - hence it creates a chicken-and-egg issue. | | **The corresponding fixes are blocked in master pending decomposition of driver/plugin - hence it creates a chicken-and-egg issue. |
| + | *Client Extensibility |
| + | **Blueprint: https://blueprints.launchpad.net/python-neutronclient/+spec/extensible-neutronclient |
| + | **Current Change: https://review.openstack.org/#/c/148318/ |
| + | **Currently only implementing shell extensions (and not library extension as a whole) |
| | | |
| == Previous meeting logs == | | == Previous meeting logs == |
Revision as of 14:26, 27 January 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 (1/27/2015) at 1400 UTC on #openstack-meeting
Announcements / Reminders
- Kilo-2 is February 5:
- Bi-weekly meetings to discuss L2 Gateway API are scheduled every other Monday at 1800 UTC (added by Sukhdev)
- Neutron Policies are documented here:
Bugs
Important bugs:
- [1] DB failure during functional job run
- [2] Ensure a smooth upgrade path after adv svc split
- [3] Race to delete shared subnet in Tempest neutron full jobs
- [4] Failure to allocate tunnel id when creating networks concurrently
- [5] br-tun lost ports/flows if openvswitch restart
- [6] Security group rules errorneously applied to all ports having same ip addresses in different networks
- [7] 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 [8] Remove unneeded call to fetch network info on shutdown - arosen
- Merged [9] remove unneeded call to network_api on detach_interface - arosen
- Merged [10] remove unneeded call to network_api on rebuild_instance - arosen
- Merged [11] Optimize validate_networks to query neutron only when needed - arosen
- [12] deallocate_for_instance should delete all neutron ports on error - arosen
- [13] Fix port_security_enabled neutron extension - arosen
- [14] Fix pre-created ports in neutron from being deleted by nova - arosen
Docs (emagana)
Open Items for Kilo:
Networking Guide:
On Demand Agenda
- Plugin Decomposition Status and Updates
- Kilo-2 specs Critical and High Priority
- Nova-Network to Neutron Migration
- Compiling a list of Neutron upgrades implementation status and known problems
- upgrading running systems with no downtime - what are the major issues?
- upgrade compatibility: oslo.versionedobjects adoption status
- upgrade compatibility: other areas of focus and known problems
- Need clarity on direction/policy on allowing the fixes in Kilo while Driver/Plugin decomposition is going on (added by Sukhdev)
- Core team's mandate is to initiate driver/plugin decomposition in Kilo and complete by Lxx cycle. This creates a bit of confusion in terms of fixes to drivers.
- Certain customer visible/impacting fixes require back-ports.
- These back-ports are not allowed because they need to be in sync with master branch.
- The corresponding fixes are blocked in master pending decomposition of driver/plugin - hence it creates a chicken-and-egg issue.
- Client Extensibility
Previous meeting logs
- Previous meetings, with their notes and logs, can be found here.
- Older meeting notes are here: ../MeetingLogs.