CCSDK Honolulu Release Planning
The content of this template is expected to be fill out for M1 Release Planning Milestone.
Info
Use the "Copy" and "Move" options (available under the ..., top right of this page) to duplicate this template into your project wiki.
Use the Wiki to document the release plan. Don't provide PowerPoint.
Use as much diagrams and flow charts as you need, directly in the wiki, to convey your message.
Overview
Project Name | Enter the name of the project |
|---|---|
Target Release Name | Honolulu |
Project Lifecycle State | Mature |
Participating Companies | AT&T, Bell Canada, Fujitsu, Ericsson, IBM, Huawei, Nokia, Orange, Samsung, Tech Mahindra, Wipro |
Scope
What is this release trying to address?
The Honolulu release contains a number of enhancements primarily centered around 5G use cases and ORAN integration.
We are continuing work on OpenDaylight Decoupling in Honolulu by refactoring our installation packages to allow us to deploy the same CCSDK artifacts unaltered on different OpenDaylight releases, with only a separate release-specific installation bundle for Karaf feature dependency declarations (karaf "feature.xml" files).
The Honolulu release also includes a major release upgrade in OpenDaylight to the OpenDaylight Aluminum release - which is 2 releases ahead of the release supported in Guilin (Sodium).
As a proof of concept of OpenDaylight Decoupling, we plan to install the same CCSDK maven artifacts in OpenDaylight Silicon (the release after Aluminum), only varying the Karaf feature declarations to match Silicon versions.
Requirements
The following table lists the new functional requirements CCSDK is committing to support for the Guilin Release:
Requirements | Companies Supporting Requirement |
|---|---|
Orange, Samsung | |
Ericcson-EST | |
AT&T | |
AT&T | |
AT&T | |
Nokia, Orange, Ericcson, Highstreet |
Minimum Viable Product
The following epics represent the minimum viable product of the CCSDK Honolulu Release:
The following epics are also in scope for Honolulu, but are not considered of the minimum viable product. In the event of unanticipated resource constraints, these could be reduced in scope or deferred without impacting any functionality deemed by the TSC as critical for Honolulu.
Functionalities
List the functionalities that this release is committing to deliver by providing a link to JIRA Epics and Stories. In the JIRA Priority field, specify the priority (either High, Medium, Low). The priority will be used in case de-scoping is required. Don't assign High priority to all functionalities.
Epics
The following epics are committed for the CCSDK Honolulu Release:
The following epics are also in scope for Honolulu, but are not considered of the minimum viable product. In the event of unanticipated resource constraints, these could be reduced in scope or deferred without impacting any functionality deemed by the TSC as critical for Honolulu.
Stories
Bugs
Longer term roadmap
Indicate at a high level the longer term roadmap. This is to put things into the big perspective.
Release Deliverables
Indicate the outcome (Executable, Source Code, Library, API description, Tool, Documentation, Release Note, etc) of this release.
Deliverable Name | Deliverable Description | Deliverable Location |
|---|---|---|
CCSDK Source Code | Source code for CCSDK project | ONAP gerrit |
CCSDK Maven Artifacts | Compiled code that can be referenced in other projects as maven dependencies | ONAP Nexus |
CCSDK Docker Containers | Docker containers associated with SDNC project:
| ONAP Nexus |
Documentation | User and developer guides | ONAP Wiki |
CCSDK CI/CD automation | Scripts to automate compilation and deployment of maven artifacts and docker containers | ONAP gerrit ONAP Jenkins |