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 | Multi VIM/Cloud |
|---|---|
| Target Release Name | Amsterdam |
| Project Lifecycle State | Either Incubation, Core, Mature. Refer to ONAP Charter, section 3.3 Project Lifecycle for further information |
| Participating Company | Amdocs, AT&T, ChinaMobile, IBM, Intel, VMware, WindRiver, ZTE. |
Scope
What is this release trying to address?
Describe the problem being solved by this release
Use Cases
Describe the use case this release is targeted for (better if reference to customer use case).
Provide a Cloud Mediation Layer supporting multiple infrastructures.
Features and functionality for R1:
1.Full life cycle management for VNF resources
2.Basic Fcaps support - fault mangement notification/alerts
3.Provide unified NBI for SO/VF-C/APP-C/DCAE
4.Adaptable SBI based plugins for Vanilla OpenStack based on Ocata and commercial OpenStack based on Mitaka
5.Registry/unregistry VIM
Minimum Viable Product
Describe the MVP for this release.
Basic LCM for VNF resources
Basic Facps support for VNF resources
Integration specification with other components
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.
Functionality Name | In or Out | Priority | Stretch |
NS LCM | IN | H | NS instance creation, NS instance termination |
VNF LCM(GVNFM) | IN | H | VNF deployment, termination according to the VNF information model |
VNF FCAPS | IN | M | Collection fcaps data from the EMS |
Resource Granting | IN | H | Grant the resources requested from VNFMs |
VNFM Integration | IN | H | Integration with specific VNFMs of vendors to deploy commercial VNFs |
VNF Integration(GVNFM) | IN | H | Integration with the VNF |
NS LCM | IN | M | VM healing |
NS LCM | OUT | M | VM scaling |
Resource Granting | OUT | M | Intelligent monitoring, allocation and reservation resources based on the requirement of VNFs |
Interface provided | IN | H | Provide restful interfaces to Policy/SO/VID/portal |
Integration with other projects(VF-C will consume the interfaces these projects provided ):
Functionality Name | In or Out | Priority | Stretch |
VF-C Integration | In | H | Integration with VF-C |
SO Integration | In | H | Integration with SO |
APP-C Integration | In | M | Integration with APP-C |
| DCAE Integration | In | H | Integration with DACE to push vnf fcaps alerts to DACE |
| A&AI | In | M | Integration with A&AI |
VIM Management
registry/unregistry
Heat resources management
Create/delete/Get/List stack
Scale-out/scale-in ResourceGroups
Tenant Management
List tenants
Get Limits of tenant
VM Lifecycle management
Create/Delete/Get/List VM
Image Management
Create/Delete/Get/List image
Network Management
Create/Delete/Get/List port
Create/Delete/Get/List network
Create/Delete/Get/List subnets
Create/Delete/Get/List router
Flavor Management
Create/Delete/Get/List flavor
Volume Lifecycle management
Create/Delete/Get/List volume
Alert report
Get/List Alert
VM Health management
Restart/Recover VM
Epics
Stories
Longer term roadmap
Indicate at a high level the longer term roadmap. This is to put things into the big perspective.
Define integration models with other components
Define model for Cloud resources/capabilities/EPA
Release Deliverables
Indicate the outcome (Executable, Source Code, Library, API description, Tool, Documentation, Release Note...) of this release.
Deliverable Name | Deliverable Description |
To fill out | To fill out |
Sub-Components
List all sub-components part of this release.
Activities related to sub-component must be in sync with the overall release.
Sub-components are repositories are consolidate in a single centralized place. Edit the Release Components name for your project in the centralized page.
ONAP Dependencies
List the other ONAP projects your depends on.
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.
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.
API Incoming Dependencies
List the API this release is expecting from other releases.
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) |
To fill out | High level description of the API | Date for which the API is reviewed and agreed | To fill out | Link toward the detailed API description |
API Outgoing Dependencies
API this release is delivering to other releases.
API Name | API Description | API Definition Date | API Delivery date | API Definition link (i.e.swagger) |
To fill out | High level description of the API | Date for which the API is reviewed and agreed | To fill out | Link toward the detailed API description |
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 |
To fill out | To fill out | To fill out |
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
- ...
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.