This page tracks the project plan for Neutron. Please note this only tracks blueprints of high and critical priority, and a handful of medium priority blueprints which are of importance to the community.
Juno Release Logistics
The Juno_Release_Schedule is available for viewing. This highlights the dates for Juno development.
Please note Neutron does observe the FeatureProposalFreeze, which is on August 21, 2014. This means any features which do not have a blueprint accepted in the neutron-specs repository and which do not have code proposed to gerrit will not make the Juno release.
For Juno, the Neutron team is conducting two mid-cycle sprints focused on key areas of Juno development. These sprints are targeted as coding sprints and will be 3 days each. The idea is to close on coding items by having team members collaborate in close proximity with core team members available for quick turnaround of patch reviews and merging.
The first sprint is the neutron LBaaS sprint. Please see the etherpad for dates and more details.
The second sprint is the neutron nova-network parity sprint. Please see the etherpad for dates and more details.
The key community feature for Neutron in Juno is around nova-network parity. Please see the page Neutron_Gap_Coverage for specific details on the plan agreed upon by the TC for achieving this in Juno. These tasks will be tracked in this project plan.
- Neutron DB migrations
- Distributed Virtual Router (DVR) implementation
- nova-network API calls which are missing in neutron
- OVS-based security groups
- Refactoring the core to use pecan
- Make Neutron the default in devstack
- nova-network to neutron migration script
- grenade testing for nova-network to neutron migrations
- Remove OVS and Linuxbridge plugins from the source tree
- Group-Based Policy abstractions in Neutron
- New object model and new API
- Service insertion, chaining, and steering
- NFV sub-project needs this. Need to break this up and prioritize it a bit.