The content of this template is expected to be fill out for M1 Release Planning Milestone.
Project Name | Enter the name of the project |
---|---|
Target Release Name | Kohn |
Project Lifecycle State | Mature |
Participating Companies | AT&T, Bell Canada, CapGemini, Fujitsu, Ericsson, IBM, Huawei, Nokia, Orange, Samsung, Tech Mahindra, Wipro |
The Jakarta release contains a number of enhancements primarily centered around 5G use cases and ORAN integration.
We are completing work begun in the Guilin release to create a springboot-based microservice which will offer the SLI-API (used by healthcheck) and GENERIC-RESOURCE-APIs. We will regression test our GR-API flows against both the current, OpenDaylight based implementation and the springboot-based version to validate that backward compatibility has been maintained.
The following table lists the new functional requirements SDNC is committing to support for the Kohn Release:
Requirements | Companies Supporting Requirement |
---|---|
CapGemini | |
Wipro | |
Huawei |
The following epics represent the minimum viable product of the SDNC Kohn Release:
The following epics are also in scope for Jakarta, 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 Kohn
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.
The following epics are committed for the SDNC Kohn Release:
The following epics are also in scope for Kohn, 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 Istanbul.
Stories
Bugs
Indicate at a high level the longer term roadmap. This is to put things into the big perspective.
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 |
Please see the INFO.yaml files associated with each repo as the authoritative sources of information. https://gerrit.onap.org/r/admin/repos/q/filter:sdnc
ONAP Dependencies
SDN-C depends on the following projects:
The following diagram shows the high level architecture of SDNC:
The major architectural components of the SDN-C controller are:
Please fill out the centralized wiki page: Kohn Release Platform Maturity
API Name | API Description | API Definition Date | API Delivery date | API Definition link (i.e.swagger) |
---|---|---|---|---|
A&AI : VNF | API used to read/write information about VNFs | Defined in seed code | Included in seed code | TBD |
SDC : distribution | API used to distribute artifacts from SDC to subscribers | Defined in seed code | Included in seed code | TBD |
DMaaP | API used to receive DHCP event notification | 8/23/17 | 8/23/17 | DMaaP API |
API Name | API Description | API Definition Date | API Delivery date | API Definition link (i.e.swagger) |
---|---|---|---|---|
Healthcheck | API used to verify that platform is available and healthy | Included in seed code | Delivered in seed code | TBD (requested Confluence OPEN API to be installed so this can be published on ONAP Wiki) |
Generic Resource API | API used to request resources for VNFs. This API is a superset of the generic VNF API, which it replaces | Included in Amsterdam release | Delivered in Amsterdam | TBD (requested Confluence OPEN API to be installed so this can be published on ONAP Wiki) |
Third Party Products Dependencies
Name | Description | Version |
---|---|---|
OpenDaylight | OpenDaylight SDN Controller Platform | Sulfur SR1 |
Provide a description of the testing activities (unit test, functional test, automation,...) that will be performed by the team within the scope of this release.
Describe the plan to integrate and test the release deliverables within the overall ONAP system.
Confirm that resources have been allocated to perform such activities.
By M3,
This section is used to document a limitation on a functionality or platform support. We are currently aware of this limitation and it will be delivered in a future Release.
List identified release gaps (if any), and its impact.
Gaps identified | Impact |
---|---|
To fill out | To fill out |
Please refer to the "Bugs" section above
List the risks identified for this release along with the plan to prevent the risk to occur (mitigation) and the plan of action in the case the risk would materialized (contingency).
Please update any risk on the centralized wiki page - Kohn Risks
Please see the INFO.yaml files associated with each repo as the authoritative sources of information. https://gerrit.onap.org/r/admin/repos/q/filter:sdnc
The milestones are defined at the Release Planning: Kohn and all the supporting project agreed to comply with these dates.
Milestone | Description | Date | Comments |
---|---|---|---|
M2 | Spec Freeze |
| |
M3 | Final Code Submission |
| Last date for code reviews to be submitted for Kohn user stories |
M4 | Feature Freeze | ||
|
|
| |
|
| ||
|
| Released dockers must be built and code reviews submitted to OOM to bump to Jakarta M4 versions | |
RC | Release Candidate | ||
|
| Last date to submit code fixes for Kohn RC | |
|
| ||
| | ||
Release Sign-Off | Final TSC Sign-Off | | Kohn Release Sign-Off |
Please update the following centralized wiki: Kohn Documentation
That includes
The Documentation project will provide the Documentation Tool Chain to edit, configure, store and publish all Documentation asset. |
If this project is coming from an existing proprietary codebase, ensure that all proprietary trademarks, logos, product names, etc. have been removed. All ONAP deliverables must comply with this rule and be agnostic of any proprietary symbols.
FOSS activities are critical to the delivery of the whole ONAP initiative. The information may not be fully available at Release Planning, however to avoid late refactoring, it is critical to accomplish this task as early as possible.
List all third party Free and Open Source Software used within the release and provide License type (BSD, MIT, Apache, GNU GPL,... ).
In the case non Apache License are found inform immediately the TSC and the Release Manager and document your reasoning on why you believe we can use a non Apache version 2 license.
Each project must edit its project table available at Project FOSS.
Charter Compliance
The project team comply with the ONAP Charter.