...
| 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 NameEnter the name of the project | Multi VIM/Cloud |
|---|---|
| Target Release Name | Enter the name of the release you are targeting to deliverAmsterdam |
| Project Lifecycle State | Either Incubation, Core, Mature. Refer to ONAP Charter, section 3.3 Project Lifecycle for further information |
| Participating Company List the company participating in this release. At least 3-4 organizations, including an operator are recommended | Amdocs, AT&T, ChinaMobile, IBM, Intel, Mirantis, VMware, WindRiver, ZTE. |
Scope
What is this release trying to address?
Describe the problem being solved by this release
Provide a Cloud Mediation Layer supporting multiple infrastructures.
Features and functionality for R1:
1. Implement backward compatibility with APP-C, DCAE, SDN-C, SO, and VF-C
2. Expose Life cycle management for VNF resources (VM/Tenant/image/heat...), Fcaps support, and other functionality reuqired for R1
3. Registry/unregistry of VIM providers
Use Cases
Describe the use case this release is targeted for (better if reference to customer use case).
Use Case: Residential Broadband vCPE (Approved)
Minimum Viable Product
...
Framework to provide restful services of lcm for VNF resources;
OpenStack API pass-through/proxy functions;
Support Multi VIM/Cloud Function and API list for R1
Integration with A&AI, APP-C, DCAE, SO, SDN-C, and VF-CDescribe the MVP for this release.
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.
In basic famework component, need to support below functions:
Functionality Name | In or Out | Priority | Stretch |
VIM management | IN | T | Registry/Unregistry |
Broker/Router | IN | T | Break VIM reqesut to proper backend |
Heat resources management | IN | T | Create/delete/Get/List stack and scaling |
VM LCM Management | IN | T | Manage lifecycle of VMs |
| Network Management | IN | T | Create/delete/List network/subnet/port |
Tenant Management | IN | T | Get all tenant list |
Image Management | IN | T | Create/Delete/Get/List image |
Flavor Management | IN | T | Create/Delete/Get/List flavor |
Volume management | IN | T | Create/Delete/Get/List volume |
Alert report | IN | T | Get/List Alert |
VM Health Management | IN | T | healing |
Integration with below projects:
Functionality Name | In or Out | Priority | Stretch |
| A&AI | In | T | Integration with A&AI/ESR |
APP-C Integration | In | T | Integration with APP-C |
| DCAE Integration | In | T | VES integration for pushing FCAPS data from cloud providers into DCAE. |
SO Integration | In | T | Integration with SO |
SDN-C Integration? | In | T | Integration with SDN-C? |
VF-C Integration | In | T | Integration with VF-C |
Epics
| Jira | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|
|
Stories
| Jira | ||||||||
|---|---|---|---|---|---|---|---|---|
|
|
Longer term roadmap
Indicate at a high level the longer term roadmap. This is to put things into the big perspective.
Ultimately, the team would like to have all these components, APP-C, VF-C, DCAE, SO, SDN-C, and VF-C to take advantage of a common API layer. The complete design of the common API layer is likely to be realized through the course of a few ONAP releases, and could involve code refactoring amongst some or all of these components. The plan is to work with all these teams to make sure the approach has been fully vetted and the transition does not break their functionality.
Release Deliverables
Indicate the outcome (Executable, Source Code, Library, API description, Tool, Documentation, Release Note...) of this release.
Deliverable Name | Deliverable Description | ||
framework/plugins | To provide restful services mentioned above | ||
| VIM VES agent | To emit VIM Fcaps data | ||
| Keystone proxy module | For compatibility with vanilla OpenStack | ||
| API document | To archive APIs in R1 | 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.
A&AI, APP-C, DCAE, SDN-C, SO, and VF-C for API design and integration
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) |
SBI | VIMs/Clouds: FOSS: OpenStack Ocata (vanila OpenStack) Commercial: OpenStack Mitaka (Wind River Titanium Cloud, VMware vIO, Miranties), Azure | |||
| A&AI | register/unregister | |||
| DCAE | VES data format |
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) |
Compatible API |
for compatibility with vanilla OpenStack and VF-C | API link (trivial VIM API) |
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.jira
| server | ONAP JIRA |
|---|---|
| columns | key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution |
| maximumIssues | 20 |
| jqlQuery | project=sanbox and issuetype in (bug) |
| serverId | 425b2b0a-557c-3c0c-b515-579789cceedb |
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 |
Integration with APP-C for shortage of functionality/API nail down | To fill out | To fill out To fill out |
Integration with A&AI for lock of synergy about AAI model change | ||
Integration with SO for unsettled arch about where to put instantiation part |
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.
...