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 | Frankfurt Release |
| Project Lifecycle State | Either Incubation, Core, Mature. Refer to ONAP Charter, section 3.3 Project Lifecycle for further information |
| Participating Company (Alphabetical order) | AT&T, Amdocs, Bell Canada, CMCC, DT, Fujitsu, Huawei, Intel, Nokia, Orange, Samsung, Tech Mahindra |
Scope
What is this release trying to address?
- Integrate the AAF and upgrade the APIs to Https - ATT
- ETSI alignment improvements - Ericcson, Huawei, Verizon
- SOL005 adaptation
- SOL003 adaptation
- PNF orchestration Enhancements - Ericcson, Huawei, Nokia
- PNF sotware upgrade
- PNF PNP enhancement
- CCVPN Enhancement
- MDONS support - Fujitsu
- Eline support - Bell, Huawei, CMCC
- 5G Slicing - ATT, Amdocs, CMCC, Huawei, Wipro
- CDS integration enhancement - ATT, Bell, Tech Mahindra
- (SO Multi Cloud plugin improvements - Intel)
- HPA - Intel (Testing effort)
- Component Upgrades to new Policy Lifecycle API : Resource commitment is being checked (ATT??)
Release Requirements
Features Being considered for F release (As per the resource availability):
| SOL005 Adapter supports communication security |
| SOL005 Adapter supports NS/VNF Package Management and NS LCM |
| Multi-domain Optical Network Service Orchestration Support in SO |
| SOL002 Adapter - supports EM-triggered VNF/VNFC Management |
| SO Catalog Management Support |
| Frankfurt release planning milestone |
| Initiate/ Terminate slice service; Activate/deactivate Slice service |
| SO support of Network Slicing Demo in Frankfurt |
| ETSI Alignment Support - SOL003 Adapter Enhancement for Frankfurt |
| AAI update for VNF improvements |
| SO Multicloud plugin to Multicloud improvements |
| SO to CDS Enhancement for Generic Implementation |
| S3P improvement Requirements |
| Upgrade the APIs to Policy |
Minimum Viable Product
Same as was defined for E-alto, but is going to add AAF integration with external APIs updated to https.
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
Stories
Longer term roadmap
The long term road map is to achieve all the goals outlined in the approved project proposal; to be fully model and standards driven, be agnostics and make no assumptions about the network. Support configuration and lifecyle management of VNF/VNFC in a generic fashion so that on-boarding any new VNF/VNFC is just a matter of configuration and data. Longer term items include:
- Align to the controller architecture proposed by the architecture team.
- Work with CDS team to converge on a single controller design tool
- Support different types of clouds, currently only support Openstack;
Release Deliverables
Indicate the outcome (Executable, Source Code, Library, API description, Tool, Documentation, Release Note...) of this release.
| Deliverable Name | Deliverable Description | Deliverable Location |
| "App-c Image" Docker Container | Executable | Docker images available on nexus3 |
| Java Source Code | The Java code for the main App-c components. | appc Git repository |
| Deployment Scripts | Linux shell scripts and Maven pom files used to generate the Docker containers. | appc/deployment Git repository |
| Directed Graph Xml Files (DGs) | Xml files define the directed graphs which are installed to database during startup and are used to determine actions taken by app-c | appc/deployment Git repository |
| Yang Model Files | Yang files are used to define the LCM action | appc Git repository |
| Property Files | Property files are used to define values that may need to be changed depending on the environment app-c is run in. | appc Git repository |
| CDT tool | an APP-C Design Tool enabling VNF owners to create templates and other artifacts used by APP-C Configure actions (used to apply a post-instantiation configuration) as well as other life cycle commands | appc/cdt Git repository |
| Parent Repo | The repository for the parents pom files. | appc/parents Git repository |
Sub-Components
List all sub-components part of this release.
Activities related to sub-components must be in sync with the overall release.
Sub-components are repositories and are consolidated in a single centralized place. Edit the Release Components name for your project in the centralized page.
onap/so/api-handler-infra
onap/so/bpmn-infra
onap/so/catalog-db-adapter
onap/so/openstack-adapter
onap/so/request-db-adapter
onap/so/sdc-controller
onap/so/sdnc-adapter
onap/so/so-monitoring
onap/so/vfc-adapter
onap/so/vnfm-adapter
Architecture
High level architecture diagram
At that stage within the Release, the team is expected to provide more Architecture details describing how the functional modules are interacting.
Indicate where your project fit within the ONAP Architecture diagram.
Block and sequence diagrams showing relation within the project as well as relation with external components are expected.
Anyone reading this section should have a good understanding of all the interacting modules.
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 | 1 | 1 |
| |
| Stability | 1 | 1 |
| |
| Resiliency | 2 | 2 |
| |
| Security | 2 | 2 |
| |
| Scalability | 1 | 1 |
| |
| Manageability | 1 | 1 |
| |
| Usability | 1 | 1 |
|
API Incoming Dependencies
List the API this project is expecting from other projects.
Prior to Release Planning review, Team Leads must agreed on the date by which the API will be fully defined. The API Delivery date must not be later than the release API Freeze date.
Prior to the delivery date, it is a good practice to organize an API review with the API consumers.
Prior to the delivery date, it is a good practice to organize an API review with the API consumers.
API Name | API Description | API Definition Date | API Delivery date | API Definition link (i.e.swagger) | Interface Type |
|---|---|---|---|---|---|
| SDC | APIs for distribute service models | Defined in Amsterdam | Delivered in Amsterdam | Incoming and Out going | |
| A&AI | APIs for inventory data | Defined in Amsterdam | Delivered in Amsterdam | Out Going | |
| SDN-C | APIs for network controller | Defined in Amsterdam | Delivered in Amsterdam | Out going | |
| APP-C | APIs for application controller | Defined in Amsterdam | Delivered in Amsterdam | Out Going | |
| VF-C | APIs for Network Service | Defined in Amsterdam | Delivered in Amsterdam | Out Going | |
| Multi-VIM | APIs for Multi-VIM | Defined in Casablanca | Delivered in Casablanca and enhancements expected in F release. | Out Going | |
| OOF | APIs for placement and homing | Defined in Beijing | Delivered in Beijing | Out Going | |
| DCAE | For PNF instantiation message from DCAE over DMaap | Defined in Casablanca | Delivered in Casablanca | Incoming | |
| SOL003 | ETS SOL003 interafces between SO and VNFM | Defined in D release | Delivered in D release | Out Going | |
| CDS | gRPC APIs between SO and CDS | Defined in D release | Delivered in D release | Out Going | |
| SOl005 | ETSI SOL005 interface between SO and NFVO (VFC / external) | Defined in F release | Delivered in F release | SO-2504 - Getting issue details... STATUS | Out Going |
Third Party Products Dependencies
Third Party Products mean products that are mandatory to provide services for your components. Development of new functionality in third party product may or not be expected.
List the Third Party Products (OpenStack, ODL, RabbitMQ, ElasticSearch,Crystal Reports, ...).
Name
FOSS used for Service Orchestrator
In case there are specific dependencies (Centos 7 vs Ubuntu 16. Etc.) list them as well.
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.
- CSIT tests added as part of R1 will continue to be supported in Dublin.
- Pairwise testing will be done in the WindRiver Dev lab similar to what was done in Dublin.
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 |
|---|---|
| N/A | N/A |
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 materialised (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
This section is optional and may be used to document internal milestones within a project team or multiple project teams. For instance, in the case the team has made agreement with other team to deliver some artifacts on a certain date that are not in the release milestone, it is erecommended to provide these agreements and dates in this section.
It is not expected to have a detailed project plan.
| Date | Project | Deliverable |
|---|---|---|
| To fill out | To fill out | To fill out |
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.