...
| 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 | Frankfurt |
| Project Lifecycle State | Incubation |
| Participating Companies | AT&T, Bell Canada, EricssonFujitsu, Ericsson, IBM, Huawei, Nokia, Orange, Samsung, Tech Mahindra, Wipro |
Scope
What is this release trying to address?
The Frankfurt 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. We believe this effort will span 2 releases - so we will begin in Frankfurt, and with the goal of being able to run the SLI as an independent container in Guilin.
Requirements
The following table lists the new functional requirements CCSDK is committing to support for the Frankfurt Release:
| Requirements | Companies Supporting Requirement |
|---|
| Jira Legacy |
|---|
| server | System Jira |
|---|
| serverId | 4733707d-2057-3a0f-ae5e-4fd8aff50176 |
|---|
| key | REQ-37 |
|---|
|
| Fujitsu |
| Jira Legacy |
|---|
| server | System Jira |
|---|
| columns | key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution |
|---|
| serverId | 4733707d-2057-3a0f-ae5e-4fd8aff50176 |
|---|
| key | REQ-33 |
|---|
|
| AT&T Bell Canada Ericsson Huawei Orange |
| Jira Legacy |
|---|
| server | System Jira |
|---|
| serverId | 4733707d-2057-3a0f-ae5e-4fd8aff50176 |
|---|
| key | REQ-267 |
|---|
|
| IBM |
| Jira Legacy |
|---|
| server | System Jira |
|---|
| serverId | 4733707d-2057-3a0f-ae5e-4fd8aff50176 |
|---|
| key | REQ-84 |
|---|
|
| Ericsson Huawei |
| Jira Legacy |
|---|
| server | System Jira |
|---|
| serverId | 4733707d-2057-3a0f-ae5e-4fd8aff50176 |
|---|
| key | REQ-53 |
|---|
|
| Huawei |
| Jira Legacy |
|---|
| server | System Jira |
|---|
| serverId | 4733707d-2057-3a0f-ae5e-4fd8aff50176 |
|---|
| key | REQ-96 |
|---|
|
| Huawei |
| Jira Legacy |
|---|
| server | System Jira |
|---|
| serverId | 4733707d-2057-3a0f-ae5e-4fd8aff50176 |
|---|
| key | REQ-38 |
|---|
|
| Ericsson IBM |
| Jira Legacy |
|---|
| server | System Jira |
|---|
| columns | key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution |
|---|
| serverId | 4733707d-2057-3a0f-ae5e-4fd8aff50176 |
|---|
| key | REQ-49 |
|---|
|
| Huawei |
| Jira Legacy |
|---|
| server | System Jira |
|---|
| serverId | 4733707d-2057-3a0f-ae5e-4fd8aff50176 |
|---|
| key | REQ-42 |
|---|
|
| Tech Mahindra |
| Jira Legacy |
|---|
| server | System Jira |
|---|
| serverId | 4733707d-2057-3a0f-ae5e-4fd8aff50176 |
|---|
| key | REQ-158 |
|---|
|
| Wipro |
| Jira Legacy |
|---|
| server | System Jira |
|---|
| serverId | 4733707d-2057-3a0f-ae5e-4fd8aff50176 |
|---|
| key | REQ-174 |
|---|
|
| AT&T |
| Jira Legacy |
|---|
| server | System Jira |
|---|
| serverId | 4733707d-2057-3a0f-ae5e-4fd8aff50176 |
|---|
| key | REQ-182 |
|---|
|
| Orange Samsung |
Minimum Viable Product
The following epics represent the minimum viable product of the CCSDK Frankfurt Release:
| Jira Legacy |
|---|
| server | System Jira |
|---|
| columns | key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution |
|---|
| maximumIssues | 20 |
|---|
| jqlQuery | project=CCSDK and issuetype in (epic) and fixversion="Frankfurt Release" and priority >= high |
|---|
| serverId | 4733707d-2057-3a0f-ae5e-4fd8aff50176 |
|---|
|
The following epics represent stretch goals, which may are also in scope for Frankfurt, but are not considered of the minimum viable product. In the event of unanticipated resource constraints, these could be reduced in scope or deferred if necessary due to resource constraints:without impacting any functionality deemed by the TSC as critical for Frankfurt.
| Jira Legacy |
|---|
| server | System Jira |
|---|
| columns | key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution |
|---|
| maximumIssues | 20 |
|---|
| jqlQuery | project=CCSDK and issuetype in (epic) and fixversion="Frankfurt Release" and priority >= priority< high |
|---|
| serverId | 4733707d-2057-3a0f-ae5e-4fd8aff50176 |
|---|
|
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 Frankfurt Release:
| Jira Legacy |
|---|
| server | System Jira |
|---|
| columns | key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution |
|---|
| maximumIssues | 20 |
|---|
| jqlQuery | project=CCSDK and issuetype in (epic) and fixversion="Frankfurt Release" and priority >= high |
|---|
| serverId | 4733707d-2057-3a0f-ae5e-4fd8aff50176 |
|---|
|
The following epics represent stretch goals, which may are also in scope for Frankfurt, but are not considered of the minimum viable product. In the event of unanticipated resource constraints, these could be reduced in scope or deferred if necessary due to resource constraints:without impacting any functionality deemed by the TSC as critical for Frankfurt.
| Jira Legacy |
|---|
| server | System Jira |
|---|
| columns | key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution |
|---|
| maximumIssues | 20 |
|---|
| jqlQuery | project=CCSDK and issuetype in (epic) and fixversion="Frankfurt Release" and priority >= < high |
|---|
| serverId | 4733707d-2057-3a0f-ae5e-4fd8aff50176 |
|---|
|
Stories
| Jira Legacy |
|---|
| server | System Jira |
|---|
| columns | key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution |
|---|
| maximumIssues | 20 |
|---|
| jqlQuery | project=CCSDK and issuetype in (story) and fixVersion = "Frankfurt Release" |
|---|
| serverId | 4733707d-2057-3a0f-ae5e-4fd8aff50176 |
|---|
|
Bugs
| Jira Legacy |
|---|
| server | System Jira |
|---|
| columns | key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution |
|---|
| maximumIssues | 20 |
|---|
| jqlQuery | project=CCSDK and issuetype in (bug) and fixVersion = "Frankfurt Release" |
|---|
| serverId | 4733707d-2057-3a0f-ae5e-4fd8aff50176 |
|---|
|
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: - Controller (OpenDaylight) container
- Database container
- Directed Graph Builder container
| 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 |
Sub-Components
Subcomponents of each ONAP project may be found on the Resources and Repositories (Deprecated) page on this wiki. Please see the CCSDK section of that page for subcomponent list of CCSDK.
Architecture
High level architecture diagram
CCSDK is delivered as a set of libraries accessible as Maven dependencies, as well as a set of base Docker containers. The docker containers themselves are intended to be used by other projects as a basis for their own controller-specific docker containers.
The following diagram illustrates how CCSDK is used by the controller projects:
Please fill out the centralized wiki page: Frankfurt Release Platform Maturity v1
API Incoming Dependencies
| API Name | API Description | API Definition Date | API Delivery date | API Definition link (i.e.swagger) |
|---|
| A&AI : schemas | A&AI schemas used by CCSDK aaa-service module | Defined in seed code | Included in seed code | TBD |
| SDC : distribution client | API used by ueb-listener (in CCSDK sdnc-northbound repo) to receive artifacts from SDC | Defined in seed code | Included in seed code | TBD |
API Outgoing Dependencies
| API Name | API Description | API Definition Date | API Delivery date | API Definition link (i.e.swagger) |
|---|
| Maven libraries | Libraries used as dependencies by SDN-C, APP-C, DCAE and OOM | Included in seed code | Delivered in seed code | Javadoc will be provided |
| Docker containers | Base docker containers will be provided which can be used by SDN-C and APP-C as a basis for their docker containers | Included in seed code | Delivered in seed code |
|
Third Party Products Dependencies
| Name | Description | Version |
|---|
| OpenDaylight | OpenDaylight SDN Controller Platform | Neon SR1 |
Testing and Integration Plans
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.
Gaps
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 |
Known Defects and Issues
Please refer to Frankfurt Defect Status
Risks
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 - Frankfurt Risks
Resources
Fill out the Resources Committed to the Release centralized page.
Release Milestone
The milestones are defined at the Release Level and all the supporting project agreed to comply with these dates.
Team Internal Milestone
| Anchor |
|---|
| FranklinSchedule |
|---|
| FranklinSchedule |
|---|
|
| Milestone | Description | Date | Comments |
|---|
| M2/M3 | Functionality Freeze / API Freeze |
- Stable user stories baselined
| Feb 15, 2019M3 | API Freeze | - M2 worksheets ready for review
| Feb 19, 2019 | Release manager reviews worksheets to assess readiness for M2 milestone | | Feb 21, 2019 | - Final API definitions (swagger, Yang) due
|
March 8 2019 Dublin | Frankfurt swagger / Yang changes to Gerrit |
| |
worksheets March 12 2019| 2020 | Release manager reviews worksheets to assess readiness for M2/M3 milestone |
| March 14, 2019
| | Jan 21, 2020 |
|
| - Code due for initial release
| Jan 31, 2020 | Last day to submit code for initial release
|
| - Initial release builds available
| Feb 4, 2020 |
|
| M4 | Code Freeze |
|
|
| |
Dublin March 29 2019 Dublin | Frankfurt code changes to Gerrit |
| - M4 worksheets ready for review
|
April 2019| 2020 | Release manager reviews worksheets to assess readiness for M4 milestone, including the following checks: |
50% - 55% code (line) coverage in Sonar
- No failed Jenkins jobs
- All CSIT tests pass
- Healthchecks pass
|
| April 4, 2019 |
| - M4 release builds available
| March 2, 2020 |
|
| | March 5, 2020
|
|
| RC0 | Release Candidate 0 |
|
|
| |
April 19 2019| 2020 | Last date to submit code fixes for release candidate 0 |
| - RC0 release artifacts available
|
April 2019 worksheets April 2019April 25 20192020
|
|
| RC1 | Release Candidate 1 |
|
|
| |
May 3 2019| 2020 | Last date to submit code fixes for Frankfurt release candidate 1 |
| - RC1 release artifacts available
|
May 7, 2019 worksheets May 7 2019May 2019| 2020 |
|
| RC2 | Release Candidate 2 |
|
|
| |
Dublin May 2019| 2020 | Last date to submit code fixes for final |
Dublin | Frankfurt release (RC2) |
| - RC2 release artifacts available
|
May 21 2019 worksheets May 21 2019May 20192020
|
|
| Release Sign-Off | Final TSC Sign-Off | May |
30 2019Dublin | Frankfurt Release Sign-Off |
Documentation, Training
Please update the following centralized wiki: Frankfurt Documentation
...
| Note |
|---|
|
The Documentation project will provide the Documentation Tool Chain to edit, configure, store and publish all Documentation asset. |
Other Information
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.
Free and Open Source Software
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.
...