|
|
| Line 70: |
Line 70: |
| | * Nova-Network to Neutron Migration | | * Nova-Network to Neutron Migration |
| | ** anteaya to give an update (http://lists.openstack.org/pipermail/openstack-dev/2014-December/053355.html) | | ** anteaya to give an update (http://lists.openstack.org/pipermail/openstack-dev/2014-December/053355.html) |
| − | * 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 (added by roaet)
| |
| − | **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 == |
