CCSDK : Dublin: Release Planning
- Yuriy Malakov
- Dan Timoney
- cl664y@att.com
DRAFT PROPOSAL FOR COMMENTS
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.
- 1.1 Info
- 2 Overview
- 3 Scope
- 4 Release Deliverables
- 5 Architecture
- 6 Testing and Integration Plans
- 7 Gaps
- 8 Known Defects and Issues
- 9 Risks
- 10 Resources
- 11 Release Milestone
- 12 Team Internal Milestone
- 12.1 Note
- 13 Other Information
Overview
Project Name | Enter the name of the project |
|---|---|
Target Release Name | Dublin |
Project Lifecycle State | Incubation |
Participating Company | AMDOCS, AT&T, Bell Canada, Ericsson,Huawei, IBM, Tech Mahendra |
Scope
What is this release trying to address?
The primary focus of the ONAP release 4 (Dublin) is to advance platform maturity, with a focus on S3P (Scalabllity, Stability, Security and Performance).
Use Cases
CCSDK will support the following use cases from previous releases:
vFW
vDNS
vCPE
VoLTE
CCVPN
CCSDK will also support the following additional use cases for Dublin:
5G
Minimum Viable Product
The following epics represent the minimum viable product for the Dublin CCSDK release:
The following epics represent stretch goals for the Dublin CCSDK release. These are currently planned for part of the release, but might be scaled back or deferred if necessary due to resource constraints.
Functionalities
Epics
The following epics are committed for the Dublin release
The following epics are considered stretch goals for the Dublin release. These are currently planned, but might scaled back or cut if necessary due to resource constraints.
Stories
The following stories are currently planned for the Dublin release.
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...) 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 |
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 will be 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:
Platform Maturity
Refering to CII Badging Security Program and Platform Maturity Requirements, fill out the table below by indicating the actual level , the targeted level for the current release and the evidences on how you plan to achieve the targeted level.
Area | Actual Level | Targeted Level for current Release | How, Evidences | Comments |
|---|---|---|---|---|
Performance | 0 | 0 | Awaiting guidance from Benchmark subcommittee |
|
Stability | 0 | N/A | As a project that provides a library framework, CCSDK has no standalone component that can be soaked |
|
Resiliency | 1 | 2 | While CCSDK itself has no standalone component, it does provide an OpenDaylight docker container used by SDNC and APPC. In Beijing, CCSDK will support a clustered OpenDaylight configuration in Kubernetes, as well as a clustered database, to allow for automated detection and recovery within a site. |
|
Security | 0 | 1 | CCSDK will achieve 50% code coverage |
|
Scalability | 0 | N/A | Scaling does not apply to CCSDK itself, as a set of libraries. |
|
Manageability | 1 | 1 | CCSDK will support ONAP standard logging. |
|
Usability | 1 | 1 | See readthedocs and wiki. |
|
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 | Fluorine |
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
Provide a link toward the list of all known project bugs.
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).
Risk identified | Mitigation Plan | Contingency Plan |
|---|---|---|
To fill out | To fill out | To fill out |
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
The following table shows the major project milestones and intermediate milestones for the Dublin release.
Milestone | Description | Date | Comments |
|---|---|---|---|
M1 | End of release planning | Formal commitment to release scope | |
| Jan 22, 2019 | Release manager reviews worksheets to assess readiness for M1 milestone | |
| Jan 24, 2019 | ||
M2 | Functionality Freeze | ||
| Feb 15, 2019 | ||
| Feb 19, 2019 | Release manager reviews worksheets to assess readiness for M2 milestone | |
| Feb 21, 2019 | ||
M3 | API Freeze | ||
| March 8, 2019 | Last day to submit Dublin swagger / Yang changes to Gerrit | |
| March 12, 2019 | Release manager reviews worksheets to assess readiness for M3 milestone | |
| March 14, 2019 | ||
M4 | Code Freeze | ||
| March 29, 2019 | Last day to submit Dublin code changes to Gerrit | |
| April 2, 2019 | Release manager reviews worksheets to assess readiness for M4 milestone, including the following checks:
| |
| April 4, 2019 | ||
RC0 | Release Candidate 0 | ||
| April 19, 2019 | Last date to submit code fixes for release candidate 0 | |
| April 23, 2019 | ||
| April 23, 2019 | ||
| April 25, 2019 | ||
RC1 | Release Candidate 1 | ||
| May 3, 2019 | Last date to submit code fixes for release candidate 1 | |
| May 7, 2019 | ||
| May 7, 2019 | ||
| May 9, 2019 | ||
RC2 | Release Candidate 2 | ||
| May 17, 2019 | Last date to submit code fixes for final Dublin release (RC2) | |
| May 21, 2019 | ||
| May 21, 2019 | ||
| May 23, 2019 | ||
Release Sign-Off | Final TSC Sign-Off | May 30, 2019 | Dublin Release Sign-Off |
Documentation, Training
Highlight the team contributions to the specific document related to he project (Config guide, installation guide...).
Highlight the team contributions to the overall Release Documentation and training asset
High level list of documentation, training and tutorials necessary to understand the release capabilities, configuration and operation.
Documentation includes items such as:
Installation instructions
Configuration instructions
Developer guide
End User guide
Admin guide
...
Note
The Documentation project will provide the Documentation Tool Chain to edit, configure, store and publish all Documentation asset.
Other Information
Vendor Neutral
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.
Each project must edit its project table available at Project FOSS.
Charter Compliance
The project team comply with the ONAP Charter.