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 |