...
| 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, Mirantis, VMware, WindRiver, ZTE. |
Scope
...
Provide a Cloud Mediation Layer supporting multiple infrastructures.
Features and functionality for R1:
1. Registry/unregistry of VIM providers 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. Implement backward compatibility with SO, APP-C, DCAE and VF-CRegistry/unregistry of VIM providers
Use Cases
Describe the use case this release is targeted for (better if reference to customer use case).
...
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/ESR, APP-C, DCAE, SO, VFSDN-C, and SOVF-C.
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 |
Functionality Name | In or Out | Priority | Stretch |
VIM management | IN | T | Registry/Unregistry |
Broker/Router | IN | T | Break VIM reqesut to proper backend |
In each plugin of different cloud provider, we need to implement below functions:
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/ESR | 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 |
...
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, SO, 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.
...
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 |
...
List the other ONAP projects your depends on.
A&AI/ESR, APP-C, DCAE, VF-C, and SO for API design and integration
...
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-CSBI | Azure, OpenStack(Mitaka - Comercial and Ocata - Open), Miranties, Windriver, VMware | |||
| A&AI | register/unregister | ||||
| DCAE | VES data format |
API Outgoing Dependencies
...
API Name | API Description | API Definition Date | API Delivery date | API Definition link (i.e.swagger) | |
Common API | Approach to drive common APICompatible API | for compatibility with vanilla OpenStack and VF-C | API link (trivial VIM API) |
Third Party Products Dependencies
...