...
| Info | ||
|---|---|---|
| ||
Use the "Copy" and "Move" options (available under the ..., top right of this page) to duplicate this template into your project wiki. |
| Table of Contents | ||
|---|---|---|
|
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 |
| Mahindra |
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
SDNC will support the following use cases from previous releases:
...
Minimum Viable Product
The MVP for Dublin consists of the set of features required to support the use cases listed above.
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
following epics represent the minimum viable product for the Dublin SDNC release:
| Jira Legacy | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|
|
The following epics are considered stretch goals for the Dublin SDNC release. These are planned for Dublin, but may be scaled back or removed if necessary due to resource constraints.
| Jira Legacy | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|
|
Functionalities
Epics
The following epics are committed for the Dublin release
| Jira Legacy | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|
|
The following epics are considered stretch goals for the Dublin release. They are currently planned, but may be scaled back or cut if necessary due to resource constraints.
| Jira Legacy | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|
|
Stories
| Jira Legacy | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|
|
Longer term roadmap
One critical long term objective for the SDN-C project is support for integration with other third party SDN Controllers (e.g. Open Contrail), well as integration with the SDN Agent project from Open-O. For the Dublin release, since our primary goal is to support the use cases identified above and to improve platform maturity, the degree to which we support such integration will be dictated by the needs of those use cases. However, we do want to bear in mind that such integration is critical and will be included in our release plans going forward.
Release Deliverables
Indicate the outcome (Executable, Source Code, Library, API description, Tool, Documentation, Release Note...) 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 |
Sub-Components
Subcomponents of each ONAP project may be found on the Resources and Repositories (Deprecated) page on this wiki. Please see the SDN-C section of that page for subcomponent list of SDN-C.
ONAP Dependencies
SDN-C depends on the following projects:
- Active and Available Inventory (A&AI)
- Common Controller SDK (CCSDK).
- Service Design and Creation (SDC)
- Data Movement as a Platform (DMaaP)
- Documentation
- Integration
- External API
- Modeling
- Multi VIM/Cloud
- Policy
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:
High level architecture diagram
The following diagram shows the high level architecture of SDNC:
...
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 | 1 | SDNC will perform 72 hour soak at component level. We assume that integration team will also do a 72 hour ONAP soak which includes SDNC. |
|
| Resiliency | 1 | 2 | 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. SDNC will use that configuration to meet this requirement. See SDN-C Clustering on Kubernetes for further details |
|
| Security | 0 | 1 | SDNC will improve test coverage to > 50% |
|
| Scalability | 0 | 1 | SDNC can be scaled either by adding additional OpenDaylight containers and/or database containers, or by deploying multiple instances of SDNC cluster. |
|
| Manageability | 1 | 1 | SDNC 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 : 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 Outgoing Dependencies
| 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 VNF API | API used to request resources for VNFs. Will be deprecated in Beijing in favor of Generic Resource API. | 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 | 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.
| Jira Legacy | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|
|
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. Rows in green are interim milestones the project team needs to meet in order to meet the overall release schedule.
| 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 |
API/data model freeze. Mark the end of API and Data Model change. API and Data Model are now Frozen.
Any changes to the API must be brought to the knowledge of the TSC for review and approval.
| 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 |
Code Freeze. Mark the end of the Features coding.
Jira issues are either fixed in the current release or assigned to next release.
100% of Functional Test Case are automated.
End 2 End Release Test Cases are implemented (Integration Team).
All new VNF Requirements planned for the release reviewed and implemented in VNF Requirements project.
Release Candidate 0
RCs are to ensure proper alignment and execution on End 2 End Release Test Cases and End 2 End functional Test Cases.
Project Team focused its effort on:
- supporting integration testing (complete Health Check and Pair Wise Testing)
- closing high priority defects
- supporting Documentation team
| April 4, 2019 | Last day to submit Dublin code changes to Gerrit | |
| April 9, 2019 | Release manager reviews worksheets to assess readiness for M4 milestone, including the following checks:
| |
| April 11, 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.
...