SDNC Guilin 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 | Guilin |
Project Lifecycle State | Incubation |
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 Guilin release contains a number of enhancements primarily centered around 5G use cases.
We also plan enhancements to the Service Logic Interpreter (SLI) - which currently runs within the OpenDaylight Karaf container - to allow it to run in a separate container, independent of OpenDaylight. This work was begun in the Frankfurt release and continues in Guilin. In Guilin, 2 new microservices will be developed that run outside OpenDaylight:
sliboot - which runs the SLI-API interface
generic-resource-api which runs the GENERIC-RESOURCE-API interface
The Guilin release also includes a major release upgrade in OpenDaylight to the OpenDaylight Sodium release. This release is considered a "sea change" release - meaning it is a major, BREAKING release. Consequently, the CCSDK Giulin release numbering will roll to 1.0.x, reflecting that we cannot guarantee full backward compatibility with previous releases.
Requirements
The following table lists the new functional requirements CCSDK is committing to support for the Frankfurt Release:
Requirements | Companies Supporting Requirement |
|---|---|
Fujitsu | |
IBM | |
Huawei, IBM, Wipro | |
Huawei, CMCC, Wipro | |
IBM | |
T-Mobile, Orange | |
Ericsson IBM |
Minimum Viable Product
The following epics represent the minimum viable product of the CCSDK Guilin Release:
The following epics are also in scope for Guilin, 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 Guilin.
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 Guilin Release:
The following epics are also in scope for Guilin, 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 Guilin.
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 |
|---|---|---|
SDNC Source Code | Source code for SDNC project | ONAP gerrit |
SDNC Maven Artifacts | Compiled code that can be referenced in other projects as maven dependencies | ONAP Nexus |
SDNC Docker Containers | Docker containers associated with SDNC project:
| ONAP Nexus |
Documentation | User and developer guides | ONAP Wiki |
SDNC CI/CD automation | Scripts to automate compilation and deployment of maven artifacts and docker containers | ONAP gerrit ONAP Jenkins |