Honeycomb/Release Plans/Release Plan 16.09

Introduction

16.06 Release of Honeycomb is it's first official release. Relying on 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

Name	Description
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 (revision 2014-05-08)
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: L2 ACL management	L2 ACL management based on ietf-acl model draft revision 7
Packaging	ODL like, karaf based packaging

Release Milestones

Milestone	Date (UPDATED 5/19/2016)	Deliverables
F0	6/20/2016	Only low-risk changes accepted on main branch.
RC1	7/4/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.
RC2	7/18/2016	Second artifacts posted.
Formal Release	7/29/2016	16.06 artifacts available

Once we've pulled the 16.06 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.06 release
• CSIT functional and performance tests available, with adequate coverage

Compatibility with Previous Release

• N/A - first release.