...
2, Fulfill functional requirements: Distributed Analytics as a Service (Dublin Summary) - Edge Automation, K8S based Cloud Region Support, Continuation of HPA (Dublin)
3, Expanding the infrastructure's support: StarlingX, Lenovo ThinkCloud
...
5, Further integration with SO
Use Cases
vFW/vDNS
vCPE
Minimum Viable Product
...
- Minimize docker image footprint
- Security enhancement: secured communication
- Enable F-GPS support with capacity check on AZ level
- Add SDC client for MultiCloud services
- Add StaringX plugin
- Add ThinkCloud plugin
- Add MultiCloud Normalization service for EA functional requirement
- Enhance the Azure plugin : Generic API for infra_workload LCM, vFW use case, etc.
- Enhance the K8S plugin : Generic API for infra_workload LCM, vFW use case, etc.
- Enhance WindRiver plugin: Support cloud region updating/auditing/etc.
- Enhance VIO plugin: support CCPVN usecase with DR capability
Stretch Goal
- Add MultiCloud Normalization service for EA functional requirement
- Further integation with SO: Generic API for extVL LCM, Generic API for VolumeGroup LCM
- CDI support: Change the project scope as Updated Proposal of Multi VIM/Cloud (Jan-17-2019)
- Accelerator Management Support
- Enhance WindRiver plugin: support CCVPN usecase with SFC LCM API,
- Enhance WindRiver plugin and OpenStack plugin: FCAPS enhancement with FM/PM collection on Infrastructure resources
- Secure credential storage for AAI cloud region
- Real-time capability as a cloud agnostic feature
- Support multiple tenants of a cloud region
...
Sub-components are repositories and are consolidated in a single centralized place. Edit the Release Components name for your project in the centralized page.
...
Indicate where your project fit within the ONAP Archiecture diagram.
Block and sequence diagrams showing relation within the project as well as relation with external components are expected.
...
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) |
|---|---|---|---|---|
| eventListener/v5 | VES collector event publish APIs | N/A since It is ready now | N/A since It is ready now | https://wikilf-onap.onapatlassian.orgnet/wiki/download/attachments/1359970816242677/ves.html?version=1&modificationDate=1503378662000&api=v2 |
API Outgoing Dependencies
...
| 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
...