Difference between revisions of "Honeycomb/Release Plans/Release Plan 16.09"
From fd.io
(→Release Deliverables) |
(→Introduction) |
||
| Line 5: | Line 5: | ||
| − | 16.09 Release of Honeycomb is it's first official release. Relying on | + | 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 == | == Release Deliverables == | ||
Revision as of 11:13, 28 July 2016
Contents
[hide]Introduction
!!! THIS PLAN IS STILL WIP !!!
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 | Affected by low level classifier API | |
| Vpp: L3 ACL management | L3 ACL management based on ietf-acl model draft revision 7 | Affected by low level classifier API | |
| Vpp: Vxlan-GPE management | CRD for vxlan-gpe tunnels | ||
| Vpp: GRE management | CRD for gre tunnels | ||
| Vpp: NAT | Required by FDS | No info provided yet | |
| 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 | ODL like, karaf based zip packaging, RPM and DEB packages |
- PARTIALLY BLOCKED
- BLOCKED
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.
