Difference between revisions of "Projects/vpp/Release Plans/Release Plan 17.07"
From fd.io
| Line 10: | Line 10: | ||
== Release Deliverables == | == Release Deliverables == | ||
| − | + | {|class="wikitable" | |
| − | + | ! Name | |
| − | Name Description | + | ! Description |
| − | + | |- | |
| − | + | |IP multicast | |
| − | IP multicast | + | | |
| − | Infra DPDK 17.03 | + | |- |
| + | |Infra | ||
| + | |DPDK 17.03 | ||
| + | |||
DPDK in a separate shared library | DPDK in a separate shared library | ||
| Line 24: | Line 27: | ||
Test infrastructure - multi-thread support | Test infrastructure - multi-thread support | ||
| + | |- | ||
| + | |Host stack | ||
| + | |VPP TCP stack | ||
| − | |||
DHCPv4 relay multi-destination | DHCPv4 relay multi-destination | ||
| Line 36: | Line 41: | ||
ND Proxy | ND Proxy | ||
| − | SNAT CGN: Configurable port allocation | + | |- |
| + | |SNAT | ||
| + | |CGN: Configurable port allocation | ||
| + | |||
CGN: Configurable Address pooling | CGN: Configurable Address pooling | ||
| Line 43: | Line 51: | ||
NAT64, LW46 | NAT64, LW46 | ||
| − | Security Groups Routed interface support | + | |- |
| + | |Security Groups | ||
| + | |Routed interface support | ||
| + | |||
L4 filters with IPv6 Extension Headers | L4 filters with IPv6 Extension Headers | ||
| − | API Move to CFFI for Python binding | + | |- |
| + | |API | ||
| + | | Move to CFFI for Python binding | ||
| + | |||
Python Packaging improvements | Python Packaging improvements | ||
| Line 53: | Line 67: | ||
C/C++ language binding | C/C++ language binding | ||
| − | SRv6 | + | |- |
| + | |SRv6 | ||
(Segment routing for IPv6) | (Segment routing for IPv6) | ||
| + | |SR policies with weighted SID lists | ||
| − | |||
Binding SID | Binding SID | ||
| Line 64: | Line 79: | ||
Framework to expand SR localSIDs with VPP plugins | Framework to expand SR localSIDs with VPP plugins | ||
| − | + | |- | |
| − | IOAM | + | |IOAM |
(Inband OAM) | (Inband OAM) | ||
| + | |UDP Pinger with iOAM for path fault isolation | ||
| − | |||
IOAM data as type 2 metadata in NSH over VXLAN-GPE | IOAM data as type 2 metadata in NSH over VXLAN-GPE | ||
IOAM raw IPFIX records collector and analyzer | IOAM raw IPFIX records collector and analyzer | ||
| − | Anycast active server selection | + | Anycast active server selection |
| + | |||
| + | |- | ||
| + | |Netflow / IPFIX | ||
| + | | Collect IPv6 information | ||
| − | |||
Per flow state | Per flow state | ||
| − | BFD | + | |- |
| − | LISP | + | |BFD |
| + | | | ||
| + | |||
| + | |- | ||
| + | |LISP | ||
| + | | | ||
Mappings statistics | Mappings statistics | ||
| Line 85: | Line 108: | ||
Improve data plane speed | Improve data plane speed | ||
| + | |} | ||
| − | Release Milestones | + | == Release Milestones == |
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | mid-month release | + | <!-- It is not uncommon for a project as part of its release process to have Milestones (M0, M1, M2, RC0, RC1) with corresponding events which occur at various milestones (API Freeze, Code Freeze, etc). This is the place to list Milestones, their expected dates, and their expected events (whether process events, API Freeze, or noting a deliverable is coming in at a particular event. --> |
| − | milestone + days | + | |
| − | day after VPP community meeting, for discussion, go/no-go | + | {| class="wikitable" |
| − | Once we've pulled the 17.04 release throttle | + | ! Milestone |
| + | ! Date | ||
| + | ! Deliverables | ||
| + | |- | ||
| + | | F0 | ||
| + | | 2017-03-08 | ||
| + | | APIs frozen. Only low-risk changes accepted on main branch. | ||
| + | |- | ||
| + | | RC1 | ||
| + | | 2017-03-22 (F0+14) | ||
| + | | Code complete, pull first release throttle branch, only bug fixes accepted on throttle train. After pull: main branch reopens for new feature / risky commits. First artifacts posted. | ||
| + | |- | ||
| + | | RC2 | ||
| + | | 2017-04-05 (RC1+14) | ||
| + | | Second artifacts posted. | ||
| + | |- | ||
| + | | Formal Release | ||
| + | | 2017-04-19 (RC2+14) | ||
| + | | 17.04 artifacts available | ||
| + | |} | ||
| + | |||
| + | <span style="color:#ff0000; font-size:75%">''NOTE: Dates chosen based on:''</span> | ||
| + | * <span style="color:#ff0000; font-size:75%">''mid-month release''</span> | ||
| + | * <span style="color:#ff0000; font-size:75%">''milestone + days''</span> | ||
| + | * <span style="color:#ff0000; font-size:75%">''day after VPP community meeting, for discussion, go/no-go''</span> | ||
| + | |||
| + | == Once we've pulled the 17.04 release throttle == | ||
We need to be disciplined with respect to bugfix commits. Here are a few common-sense suggestions: | We need to be disciplined with respect to bugfix commits. Here are a few common-sense suggestions: | ||
| − | All bug fixes must be double-committed to the release throttle as well as to the master branch | + | * All bug fixes must be double-committed to the release throttle as well as to the master branch |
| − | Commit first to the release throttle, then "git cherry-pick" into master | + | ** Commit first to the release throttle, then "git cherry-pick" into master |
| − | Manual merges may be required, depending on the degree of divergence between throttle and master | + | ** Manual merges may be required, depending on the degree of divergence between throttle and master |
| − | All bug fixes need to have a Jira ticket | + | * All bug fixes need to have a Jira ticket |
| − | Please put Jira IDs into the commit messages. | + | ** Please put Jira IDs into the commit messages. |
| − | Please use the same Jira ID | + | ** Please use the same Jira ID |
| + | |||
| + | |||
| + | === Features to be added in 17.07 === | ||
| + | This list considered from JIRA:[https://jira.fd.io/secure/Dashboard.jspa?selectPageId=10700 vpp dashboard] | ||
| − | + | <span style="color:#ff0000; font-size:100%"><div style="text-align:center">NEED JIRA/CONFLUENCE IMPORT HERE</div></span> | |
| − | + | ||
| − | + | == Expected Dependencies on Other Projects == | |
| − | Expected Dependencies on Other Projects | + | |
Revision as of 09:40, 2 May 2017
Contents
Introduction
This page tracks release information for 17.07.
Release Deliverables
| Name | Description |
|---|---|
| IP multicast | |
| Infra | DPDK 17.03
DPDK in a separate shared library Retirement of VPP_Lite Lazy Polling mode Test infrastructure - multi-thread support |
| Host stack | VPP TCP stack
DHCPv4 relay multi-destination DHCPv4 option 82 DHCPv6 relay multi-destination DHPCv6 relay remote-id ND Proxy |
| SNAT | CGN: Configurable port allocation
CGN: Configurable Address pooling CPE: External interface DHCP support NAT64, LW46 |
| Security Groups | Routed interface support
L4 filters with IPv6 Extension Headers |
| API | Move to CFFI for Python binding
Python Packaging improvements CLI over API C/C++ language binding |
| SRv6
(Segment routing for IPv6) |
SR policies with weighted SID lists
Binding SID SR steering policies SR LocalSIDs Framework to expand SR localSIDs with VPP plugins |
| IOAM
(Inband OAM) |
UDP Pinger with iOAM for path fault isolation
IOAM data as type 2 metadata in NSH over VXLAN-GPE IOAM raw IPFIX records collector and analyzer Anycast active server selection |
| Netflow / IPFIX | Collect IPv6 information
Per flow state |
| BFD | |
| LISP |
Mappings statistics Generalize encap for overlay transport Improve data plane speed |
Release Milestones
| Milestone | Date | Deliverables |
|---|---|---|
| F0 | 2017-03-08 | APIs frozen. Only low-risk changes accepted on main branch. |
| RC1 | 2017-03-22 (F0+14) | Code complete, pull first release throttle branch, only bug fixes accepted on throttle train. After pull: main branch reopens for new feature / risky commits. First artifacts posted. |
| RC2 | 2017-04-05 (RC1+14) | Second artifacts posted. |
| Formal Release | 2017-04-19 (RC2+14) | 17.04 artifacts available |
NOTE: Dates chosen based on:
- mid-month release
- milestone + days
- day after VPP community meeting, for discussion, go/no-go
Once we've pulled the 17.04 release throttle
We need to be disciplined with respect to bugfix commits. Here are a few common-sense suggestions:
- All bug fixes must be double-committed to the release throttle as well as to the master branch
- Commit first to the release throttle, then "git cherry-pick" into master
- Manual merges may be required, depending on the degree of divergence between throttle and master
- All bug fixes need to have a Jira ticket
- Please put Jira IDs into the commit messages.
- Please use the same Jira ID
Features to be added in 17.07
This list considered from JIRA:vpp dashboard
NEED JIRA/CONFLUENCE IMPORT HERE
