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.
Overview
| Project Name | Enter the name of the project |
|---|---|
| Target Release Name | Casablanca |
| Project Lifecycle State | Incubation |
| Participating Company | China Mobile ,ZTE, Huawei, Nokia ,VMware, Boco, Jio, raisecom, Intel |
What is this release trying to address?
The VF-C Casablanca release has following primary objectives:
1. Improving platform maturity:enhance scalability, manageability,security (i.e., S3P items)
2. Supporting use cases identified by ONAP and integration: VoLTE, vCPE,
3. Supporting Functional Requirements identified: HPA, Centralized Representation and Consistent Identification of Cloud Regions In ONAP
4. Enhancement to VF-C existing features:
Integration with OOF, AAF(Strech goal)
R3 tosca data model alignment
ETSI Interface alignment(Depend on resource contribution)
Use Cases
Describe the use case this release is targeted for (better if reference to customer use case).
Use Case: Residential Broadband vCPE (Approved)
Functional Requirements:
Hardware Platform Enablement In ONAP
Centralized Representation and Consistent Identification of Cloud Regions In ONAP
Auto Scaling - stretch goal
Minimum Viable Product
VF-C will include the necessary subcomponents supporting the primary objectives: meeting platform maturity goals and supporting the use cases.
LCM(instantiate/terminate/heal/scaling) for NS and Vendor VNFs
FCAPS for vendor VNFs
LCM(instantiate/terminate) for open source VNFs
Minimum VF-C components supporting above functionalities:
NSLCM/Catalog/GVNFM/Vimproxy/EMS driver/vendor VNFM driver
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
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 |
| Source Code | Source code for all VF-C components |
| Maven Artifacts | Maven Artifacts for all VF-C components |
| Docker Containers | Docker container associated with VF-C componets |
| Documentation | VF-C detailed documentation |
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.
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 Archiecture diagram.
TBD (add new R3 arch diagram with new components and interface)
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 | 0 | 1 |
| |
| Stability | 1 | 2 | Need to do a 72 hours soak test for VF-C VFC-938 - Getting issue details... STATUS |
|
| Resiliency | 2 | 2 | In Casablanca we will split all VF-C DBs into a single container, so plan to support Resiliency at the DB level VFC-951 - Getting issue details... STATUS |
|
| Security | 1 | 1+ | Partial Need to know more clarification about the security level definitiion. There are still false positives and third party issues reported in NexusIQ; We will continute to solve critical issues first and then address medium issues.
VFC-937
-
Getting issue details...
STATUS
|
|
| Scalability | 0 | 1 | Will split DBs from current VF-C components. So that VF-C components can scale in signle site VFC-952 - Getting issue details... STATUS |
|
| Manageability | 1 | 1+ | Patial Need to know more clarification about manageablitilly level2 But we will update log format to compile log specification VFC-933 - Getting issue details... STATUS |
|
| Usability | 1 | 1 | APIs documentation update VFC-935 - Getting issue details... STATUS |
|
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.
API Name | API Description | API Definition Date | API Delivery date | API Definition link (i.e.swagger) |
Catalog API (SDC) | API to read the NS and VNF Catalog | |||
Parser API(Modeling) | API for parsering TOSCA file | |||
Micro-services bus API | API for registration and use of micro-services bus | |||
Multi-vim API | API to allocate resource to VIM | |||
DCAE VES collector SB API | API to push vnf fcaps data to VES collector | |||
A&AI API | API to store inventory | |||
| OOF API | API to chose VIM which is used to deploy VNF |
API Outgoing Dependencies
API this project is delivering to other projects.
| API Name | API Description | API Definition Date | API Delivery date | API Definition link (i.e.swagger) |
|---|---|---|---|---|
NSLCM API Definition | Network services lifecycle management APIs, including scaling API | Link toward the detailed API description | ||
VNFM Driver API Definition | VNFM Driver component northbound APIs, including scaling API | |||
| VNF LCM API Definition | provide VNF lifecycle management APIs |
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 | Description | Version |
|---|---|---|
| activiti workflow engine |
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.
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
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.