Difference between revisions of "Honeycomb/Release Plans/Release Plan 16.09"

From fd.io
Jump to: navigation, search
(release plan update)
 
(10 intermediate revisions by one other user not shown)
Line 1: Line 1:
 
[[Category:Release Plan]]
 
[[Category:Release Plan]]
 
== Introduction ==
 
== Introduction ==
−
 
+
16.09 Release of Honeycomb is it's first official release. Relying on VPP's 16.09 release: https://wiki.fd.io/view/Projects/vpp/Release_Plans/Release_Plan_16.09
−
!!!THIS PLAN IS STILL WIP!!!
+
−
 
+
−
 
+
−
16.06 Release of Honeycomb is it's first official release. Relying on [[Projects:vpp:Release_Plans:Release_Plan_16.06|VPP's 16.06 release]].
+
−
Included in this release is the migration of vbd application into ODL's dedicated project. Code freeze milestone for vbd in ODL is 7/21/2016.
+
  
 
== Release Deliverables ==
 
== Release Deliverables ==
Line 15: Line 10:
 
! Name
 
! Name
 
! Description
 
! Description
 +
! Notes
 
|-
 
|-
 
| Infra: Data processing pipeline
 
| Infra: Data processing pipeline
 
| [https://jira.fd.io/browse/HONEYCOMB-8 Special pipeline reusing ODL's infrastructure, suitable for agent like architecture of Honeycomb]
 
| [https://jira.fd.io/browse/HONEYCOMB-8 Special pipeline reusing ODL's infrastructure, suitable for agent like architecture of Honeycomb]
 +
|
 
|-
 
|-
 
| Infra: Extensible translation layer (SPI)
 
| Infra: Extensible translation layer (SPI)
 
| [https://jira.fd.io/browse/HONEYCOMB-9 Extensible translation layer for mapping plugins (performing translation between YANG <-> VPP]
 
| [https://jira.fd.io/browse/HONEYCOMB-9 Extensible translation layer for mapping plugins (performing translation between YANG <-> VPP]
 +
|
 
|-
 
|-
 
| Infra: Configuration and context persistence
 
| Infra: Configuration and context persistence
 
| [https://jira.fd.io/browse/HONEYCOMB-61 JSON file based persistence for configuration flowing through Honeycomb + mapping context information stored by translation layer. Also restoration of VPP's configuration based on persisted ]
 
| [https://jira.fd.io/browse/HONEYCOMB-61 JSON file based persistence for configuration flowing through Honeycomb + mapping context information stored by translation layer. Also restoration of VPP's configuration based on persisted ]
 +
|
 
|-
 
|-
 
| Vpp: Base interface management
 
| Vpp: Base interface management
−
| Base management for VPP's interfaces according to ietf-interfaces yang model (revision 2014-05-08)
+
| Base management for VPP's interfaces according to ietf-interfaces yang model + ietf-ip yang model
 +
|
 
|-
 
|-
 
| Vpp: Bridge domain management
 
| Vpp: Bridge domain management
 
| CRUD for bridge domain + adding interfaces to bridge domains
 
| CRUD for bridge domain + adding interfaces to bridge domains
 +
|
 
|-
 
|-
 
| Vpp: Vxlan tunnel management
 
| Vpp: Vxlan tunnel management
 
| [https://jira.fd.io/browse/HONEYCOMB-37 CRD for vxlan tunnels]
 
| [https://jira.fd.io/browse/HONEYCOMB-37 CRD for vxlan tunnels]
 +
|
 
|-
 
|-
 
| Vpp: Vhost user interface management
 
| Vpp: Vhost user interface management
 
| [https://jira.fd.io/browse/HONEYCOMB-36 CRUD for vhost user interface types]
 
| [https://jira.fd.io/browse/HONEYCOMB-36 CRUD for vhost user interface types]
 +
|
 
|-
 
|-
 
| Vpp: Tap interface management
 
| Vpp: Tap interface management
 
| [https://jira.fd.io/browse/HONEYCOMB-47 CRUD for tap interface types]
 
| [https://jira.fd.io/browse/HONEYCOMB-47 CRUD for tap interface types]
 +
|
 
|-
 
|-
 
| Vpp: VLAN management
 
| Vpp: VLAN management
 
| [https://jira.fd.io/browse/HONEYCOMB-48 CRUD for sub-interfaces + support for tag rewrite]
 
| [https://jira.fd.io/browse/HONEYCOMB-48 CRUD for sub-interfaces + support for tag rewrite]
 +
|
 +
|-
 +
| <span style="color:lightcoral;"><b>Vpp: Low level classifier management</b></span>
 +
| [https://jira.fd.io/browse/HONEYCOMB-49 CRD for low-level classifier API. Tables and session management].
 +
| <span style="color:lightcoral;">Read not available from VPP(affects reconciliation): https://jira.fd.io/browse/VPP-203</span> <br/> <span style="color:lightcoral;">Delete with unexpected behavior: https://jira.fd.io/browse/VPP-206</span>
 
|-
 
|-
 
| Vpp: L2 ACL management
 
| Vpp: L2 ACL management
 
| [https://jira.fd.io/browse/HONEYCOMB-49 L2 ACL management based on ietf-acl model draft revision 7]
 
| [https://jira.fd.io/browse/HONEYCOMB-49 L2 ACL management based on ietf-acl model draft revision 7]
 +
|
 +
|-
 +
| Vpp: L3 ACL management
 +
| [https://jira.fd.io/browse/HONEYCOMB-49 L3 ACL management based on ietf-acl model draft revision 7]
 +
|
 +
|-
 +
| Vpp: Vxlan-GPE management
 +
| [https://jira.fd.io/browse/HONEYCOMB-71 CRD for vxlan-gpe tunnels]
 +
|
 +
|-
 +
| Vpp: GRE management
 +
| [https://jira.fd.io/browse/HONEYCOMB-83 CRD for gre tunnels]
 +
|
 +
|-
 +
| Vpp: NSH plugin support
 +
| [https://jira.fd.io/browse/HONEYCOMB-46]
 +
|
 +
|-
 +
| Vpp: LISP
 +
| [https://jira.fd.io/browse/HONEYCOMB-75]
 +
|
 +
|-
 +
| <span style="color:lightcoral;"><b>Vpp: bridge-domain ARP termination table management</b></span>
 +
| [https://jira.fd.io/browse/HONEYCOMB-125 CRUD for bridge domain ARP termination table management]
 +
| <span style="color:lightcoral;">Read not available from VPP(affects reconciliation): https://jira.fd.io/browse/VPP-212</span>
 
|-
 
|-
 
| Packaging
 
| Packaging
−
| ODL like, karaf based packaging
+
| Minimal, custom, runnable, packaged distribution (zip, tar.gz), RPM and DEB packages
 +
|
 
|}
 
|}
 +
 +
 +
* <span style="color:lightcoral;"><b>LIMITED</b></span>
  
 
== Release Milestones ==
 
== Release Milestones ==
Line 56: Line 94:
 
{| class="wikitable"
 
{| class="wikitable"
 
! Milestone
 
! Milestone
−
! Date (UPDATED 5/19/2016)
+
! Date
 
! Deliverables
 
! Deliverables
 
|-
 
|-
 
| F0
 
| F0
−
| 6/20/2016
+
| 8/17/2016  
−
| Only low-risk changes accepted on main branch.  
+
| APIs frozen. low-risk changes accepted on main branch.
 
|-
 
|-
 
| RC1
 
| RC1
−
| 7/4/2016
+
| (F0+14) 8/31/2016
−
| Code complete, APIs frozen, 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. VBD in opendaylight published, using RC1 version of Honeycomb's artifacts.
+
| 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  
−
| 7/18/2016
+
| (RC1+14) 9/14/2016
 
| Second artifacts posted.  
 
| Second artifacts posted.  
 
|-
 
|-
 
| Formal Release  
 
| Formal Release  
−
| 7/29/2016
+
| (RC2+7) 9/21/2016
−
| 16.06 artifacts available  
+
| 16.09 artifacts available  
 
|}
 
|}
  
−
== Once we've pulled the 16.06 release throttle ==
+
== Once we've pulled the 16.09 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:
  
Line 90: Line 128:
 
<!-- If your project depends on other projects, and particularly specific deliverables from other projects, list them here -->
 
<!-- If your project depends on other projects, and particularly specific deliverables from other projects, list them here -->
 
* ODL Beryllium-SR2 release
 
* ODL Beryllium-SR2 release
−
* VPP 16.06 release
+
* VPP 16.09 release
 
* CSIT functional and performance tests available, with adequate coverage
 
* CSIT functional and performance tests available, with adequate coverage
  

Latest revision as of 08:29, 20 September 2016

Introduction

16.09 Release of Honeycomb is it's first official release. Relying on VPP's 16.09 release: https://wiki.fd.io/view/Projects/vpp/Release_Plans/Release_Plan_16.09

Release Deliverables

Name Description Notes
Infra: Data processing pipeline Special pipeline reusing ODL's infrastructure, suitable for agent like architecture of Honeycomb
Infra: Extensible translation layer (SPI) Extensible translation layer for mapping plugins (performing translation between YANG <-> VPP
Infra: Configuration and context persistence JSON file based persistence for configuration flowing through Honeycomb + mapping context information stored by translation layer. Also restoration of VPP's configuration based on persisted
Vpp: Base interface management Base management for VPP's interfaces according to ietf-interfaces yang model + ietf-ip yang model
Vpp: Bridge domain management CRUD for bridge domain + adding interfaces to bridge domains
Vpp: Vxlan tunnel management CRD for vxlan tunnels
Vpp: Vhost user interface management CRUD for vhost user interface types
Vpp: Tap interface management CRUD for tap interface types
Vpp: VLAN management CRUD for sub-interfaces + support for tag rewrite
Vpp: Low level classifier management CRD for low-level classifier API. Tables and session management. Read not available from VPP(affects reconciliation): https://jira.fd.io/browse/VPP-203
Delete with unexpected behavior: https://jira.fd.io/browse/VPP-206
Vpp: L2 ACL management L2 ACL management based on ietf-acl model draft revision 7
Vpp: L3 ACL management L3 ACL management based on ietf-acl model draft revision 7
Vpp: Vxlan-GPE management CRD for vxlan-gpe tunnels
Vpp: GRE management CRD for gre tunnels
Vpp: NSH plugin support [1]
Vpp: LISP [2]
Vpp: bridge-domain ARP termination table management CRUD for bridge domain ARP termination table management Read not available from VPP(affects reconciliation): https://jira.fd.io/browse/VPP-212
Packaging Minimal, custom, runnable, packaged distribution (zip, tar.gz), RPM and DEB packages


  • LIMITED

Release Milestones

Milestone Date Deliverables
F0 8/17/2016 APIs frozen. low-risk changes accepted on main branch.
RC1 (F0+14) 8/31/2016 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 (RC1+14) 9/14/2016 Second artifacts posted.
Formal Release (RC2+7) 9/21/2016 16.09 artifacts available

Once we've pulled the 16.09 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

Expected Dependencies on Other Projects

  • ODL Beryllium-SR2 release
  • VPP 16.09 release
  • CSIT functional and performance tests available, with adequate coverage

Compatibility with Previous Release

  • N/A - first release.

Themes and Priorities

Other

Retrieved from "https://wiki.fd.io/index.php?title=Honeycomb/Release_Plans/Release_Plan_16.09&oldid=3092"