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

From fd.io
Jump to: navigation, search
m (Release Deliverables)
 
(12 intermediate revisions by 4 users not shown)
Line 1: Line 1:
 
 
== Introduction ==
 
== Introduction ==
 
 
  
 
This page tracks release information for 18.01.
 
This page tracks release information for 18.01.
 
  
 
== Release Deliverables ==
 
== Release Deliverables ==
Line 33: Line 29:
 
Fragmentation / Reassembly   
 
Fragmentation / Reassembly   
  
Syslog
+
DS-Lite
 +
 
 +
Removed old SNAT API
 +
 
 +
Delete session API/CLI
 +
 
 +
NAT64 to use IPv4 address from interface
 +
 
 +
Performance improvement
 +
 
 +
Port restricted NAT44 for MAP-E CE
 +
 
 +
NAT44 identity mapping
  
 
|-
 
|-
 
|API  
 
|API  
 
|VPP stats (Broadcast & Multicast support)  
 
|VPP stats (Broadcast & Multicast support)  
 
 
|-
 
|-
 
|Host stack
 
|Host stack
 
|VPP TCP stack - scale / congestion  
 
|VPP TCP stack - scale / congestion  
  
VPP Comms Library (VLC)
+
VPP Comms Library (VCL)
  
 
|-
 
|-
|ONE-LISP
+
|ACL
|TBD
+
|ACL stats
  
 
|-
 
|-
|ACL
+
|Kube-proxy Data Plane
|hash-acl lookup enhancement
+
|Support ingress load balancing and DNAT
 +
 
 +
Support egress SNAT
  
ACL stats
+
Support three service types.
  
 
|}
 
|}
Line 67: Line 76:
 
|-
 
|-
 
| F0
 
| F0
| 2017-12-06
+
| 2017-12-20
 
| APIs frozen. Only low-risk changes accepted on main branch.
 
| APIs frozen. Only low-risk changes accepted on main branch.
 
|-
 
|-
 
| RC1
 
| RC1
| 2017-12-20 (F0+14)
+
| 2018-01-03  (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.  
 
| 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  
 
| RC2  
| 2018-01-03 (RC1+14)
+
| 2018-01-10  (RC1+7)
 
| Second artifacts posted.  
 
| Second artifacts posted.  
 
|-
 
|-
 
| Formal Release  
 
| Formal Release  
| 2018-01-17 (RC2+14)
+
| 2018-01-24  (RC2+14)
 
| 18.01 artifacts available  
 
| 18.01 artifacts available  
 
|}
 
|}
Line 96: Line 105:
 
* 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 for commits into the stable branch and master.
  
  

Latest revision as of 20:37, 25 January 2018

Introduction

This page tracks release information for 18.01.

Release Deliverables

Name Description
Infra DPDK 17.11 integration

IP Reassembly

TCP Checksum Offload

VNET TBD
SNAT / NAT One armed NAT

NAT64: multi thread

Twice NAT

Fragmentation / Reassembly

DS-Lite

Removed old SNAT API

Delete session API/CLI

NAT64 to use IPv4 address from interface

Performance improvement

Port restricted NAT44 for MAP-E CE

NAT44 identity mapping

API VPP stats (Broadcast & Multicast support)
Host stack VPP TCP stack - scale / congestion

VPP Comms Library (VCL)

ACL ACL stats
Kube-proxy Data Plane Support ingress load balancing and DNAT

Support egress SNAT

Support three service types.

Release Milestones

Milestone Date Deliverables
F0 2017-12-20 APIs frozen. Only low-risk changes accepted on main branch.
RC1 2018-01-03 (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 2018-01-10 (RC1+7) Second artifacts posted.
Formal Release 2018-01-24 (RC2+14) 18.01 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 18.01 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 for commits into the stable branch and master.


Features to be added in 18.01

NEED JIRA/CONFLUENCE IMPORT HERE

Expected Dependencies on Other Projects