NeutronJunoProjectPlan

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.

Neutron Release Timelines
The following are the dates to be aware of for Neutron in the Juno release. Note that the numbers in parentheses are weeks before the Feature Proposal Freeze.


 * June 12 (-12): Juno-1
 * June 17-19 (-11): Neutron LBaaS Sprint
 * July 9-11 (-9): Neutron Mid-Cycle Sprint
 * July 10 (-9): Spec Proposal Deadline (SPD)
 * Jul 20 (-7): Spec Approval Deadline (SAD)
 * Jul 24 (-6): Juno-2
 * Aug 21 (-2): Feature proposal freeze
 * Sep 4 ( 0): Juno-3 Feature freeze
 * Merged J specs with no code proposed get deleted from neutron-specs repo
 * K opens for spec proposals, un-merged J spec proposals must rebase and be re-approved
 * Sep 25 (+3): RC 1 build expected
 * K spec review approvals start
 * Oct 16 (+6): Release! (https://wiki.openstack.org/wiki/Juno_Release_Schedule)
 * Oct 30: K summit spec proposal freeze
 * Nov 6: K design summit

Mid-Cycle Sprints
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.

nova-network parity
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.

Juno-1 (6-12-2014)

 * Distributed Virtual Router (DVR) implementation
 * Spec: https://review.openstack.org/#/c/89934/
 * Neutron full-job bugs:
 * https://bugs.launchpad.net/neutron/+bug/1291947
 * Some of these landed in Juno-1
 * IPv6
 * provider network SLAAC support
 * Option to disable DF for GRE and VXLAN tunnels in the OVS agent

Juno-2 (7-24-2014)

 * Neutron DB migrations
 * Spec: https://review.openstack.org/#/c/95738/
 * Plan for this is here: https://etherpad.openstack.org/p/neutron-db-migrations
 * https://bugs.launchpad.net/neutron/+bug/1307344
 * Distributed Virtual Router (DVR) implementation
 * Spec: https://review.openstack.org/#/c/89934/
 * nova-network API calls which are missing in neutron
 * https://bugs.launchpad.net/nova/+bug/1269060
 * https://bugs.launchpad.net/nova/+bug/1269061
 * https://bugs.launchpad.net/nova/+bug/1269062
 * https://bugs.launchpad.net/nova/+bug/1293539
 * IPv6
 * RA support
 * SLAAC support
 * Refactoring the core to use pecan
 * Flavor framework
 * https://review.openstack.org/90070
 * FWaaS integration with flavors
 * LBaaS integration with flavors
 * Make Neutron the default in devstack
 * https://bugs.launchpad.net/devstack/+bug/1321003
 * nova-network to neutron migration script
 * grenade testing for nova-network to neutron migrations
 * Remove OVS and Linuxbridge plugins from the source tree
 * LBaaS
 * New object model and new API
 * oslo.messaging port
 * Group-Based Policy abstractions in Neutron
 * https://blueprints.launchpad.net/neutron/+spec/group-based-policy-abstraction
 * HA for L3 routers
 * Current spec review: https://review.openstack.org/#/c/94175/
 * Firewall rule service objects
 * https://review.openstack.org/#/c/94133

Juno-2 BP Assignments
As Juno-2 approaches, I'd like to assign core reviewers to shepherd the following community features along. The idea is to have assigned cores responsible for reviewing and helping to merge these BPs. This is not meant to prevent other core reviews from reviewing, but rather to ensure core's have a specifically focused review target for Juno-2 to assist in merging these once the code is ready, and to work with submitters on these. The following are the assignments:


 * DVR (https://blueprints.launchpad.net/neutron/+spec/neutron-ovs-dvr)
 * Cores assigned: Akihiro and Maru
 * nova-network to neutron migration (Spec https://review.openstack.org/#/c/101921 and code https://review.openstack.org/#/c/100265)
 * Cores assigned: Salvatore and Maru
 * DB Refactor (https://blueprints.launchpad.net/neutron/+spec/db-migration-refactor)
 * Cores assigned: Mark and Salvatore
 * New LBaaS API (https://blueprints.launchpad.net/neutron/+spec/lbaas-api-and-objmodel-improvement)
 * Cores assigned: Kyle and Akihiro
 * Refactor haproxy driver to use new LBaaS API (https://blueprints.launchpad.net/neutron/+spec/lbaas-refactor-haproxy-namespace-driver-to-new-driver-interface)
 * Cores assigned: Mark and Armando
 * Group Based Policy API (https://blueprints.launchpad.net/neutron/+spec/group-based-policy-abstraction)
 * Cores assigned: Nachi and Oleg
 * HA for L3 Agent (https://blueprints.launchpad.net/neutron/+spec/l3-high-availability)
 * Cores assigned: Carl and Gary
 * SLaaC in IPV6 (https://blueprints.launchpad.net/neutron/+spec/dnsmasq-ipv6-slaac)
 * Cores assigned: Nachi and Edgar
 * RADVD support (https://blueprints.launchpad.net/neutron/+spec/neutron-ipv6-radvd-ra)
 * Cores assigned: Bob and Kyle
 * Flavor Framework (https://review.openstack.org/#/c/102723/)
 * Cores assigned: Sumit and Aaron

Juno-3 (8-21-2014, FPF)

 * Refactoring
 * Tasks library
 * Service insertion, chaining, and steering
 * NFV sub-project needs this. Need to break this up and prioritize it a bit.
 * FWaaS integration
 * LBaaS
 * Barbican integration
 * L7, SSL
 * VPN
 * Barbican integration
 * Flavor framework integration