Difference between revisions of "Projects/vpp/Release Plans/Release Plan 17.07"

From fd.io
Jump to: navigation, search
(Release Deliverables)
(Release Deliverables)
Line 16: Line 16:
 
|Infra
 
|Infra
 
|Test
 
|Test
 +
|Test
 +
BFD integration with FIB
 +
Multicast MPLS FIB
 +
BFD basic testing with other BFD implementations: NxOS, IOS-XE, IOS-XR
 +
Lazy Polling Mode
 +
native cuckoo hash implementation
 +
"make test" improvements - multi thread
 +
Muti threaded buffer manager for vpp lite
 +
IPSec rework - utilize new FIB
 +
IGMP + IGMP Proxy (TBD)
 +
ABI versioning / consolidation of client libraries
 +
RPM  Debian packaging
 +
Add elasticity to vpp data plane.  Add/remove cpu cores.  (vPC & cCMTS)
 +
DPDK Interrupt mode
 +
Common interface placement infra
 +
MEMIF – enhancements (multi-que, jump frame support, external libraries)
 +
DPDK 17.05 integration
 +
HW offload - SmartNIC offload
 +
Migrate vhost to use device infra for interface/queue to thread placement
 +
P2P Ethernet ?
 +
 
|-
 
|-
 
|Infra
 
|Infra

Revision as of 09:54, 3 May 2017


Introduction

This page tracks release information for 17.07.


Release Deliverables

Name Description
Infra Test Test

BFD integration with FIB Multicast MPLS FIB BFD basic testing with other BFD implementations: NxOS, IOS-XE, IOS-XR Lazy Polling Mode native cuckoo hash implementation "make test" improvements - multi thread Muti threaded buffer manager for vpp lite IPSec rework - utilize new FIB IGMP + IGMP Proxy (TBD) ABI versioning / consolidation of client libraries RPM Debian packaging Add elasticity to vpp data plane. Add/remove cpu cores. (vPC & cCMTS) DPDK Interrupt mode Common interface placement infra MEMIF – enhancements (multi-que, jump frame support, external libraries) DPDK 17.05 integration HW offload - SmartNIC offload Migrate vhost to use device infra for interface/queue to thread placement P2P Ethernet ?

Infra DPDK 17.XX
Host stack VPP TCP stack

Release Milestones

Milestone Date Deliverables
F0 2017-06-08 APIs frozen. Only low-risk changes accepted on main branch.
RC1 2017-06-22 (F0+17) 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-07-05 (RC1+17) Second artifacts posted.
Formal Release 2017-07-19 (RC2+17) 17.07 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.07 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.10

NEED JIRA/CONFLUENCE IMPORT HERE

Expected Dependencies on Other Projects