...
| Project Name | Enter the name of the project |
|---|---|
| Target Release Name | Casablanca Release |
| Project Lifecycle State | Incubation. Refer to ONAP Charter, section 3.3 Project Lifecycle for further information |
| Participating Company | AT&T, Amdocs, Nokia |
...
- S3P improvements
- VNF Scaling enhancements
- PNF support
- Scheduling capabilites PNF support(stretch goal)
Use Cases
VID will continue supporting the following use case:
Use Case: Residential Broadband vCPE (Approved)
Use Case Proposal - VNF Scale Out
And will add support to the following:
...
Change Management Extensions (partially)
Deployment of the hybrid 5G Network (PNF/VNF)
Change Management Extensions (best effort)
Centralized Representation and Consistent Identification of Cloud Regions In ONAP (best effort)
Minimum Viable Product
- Instantiation of service, vnfs and vf modules
- change management support
...
Sub-components are repositories and are consolidated in a single centralized place. Edit the Release Components name for your project in the centralized page.
...
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) |
|---|---|---|---|---|
| Scale out (endpoint TBD) | SO API for VNF scale out | TBD | TBD | TBD |
| Service instantiation - /ecomp/mso/infra/serviceInstances/v6 | SO API for service instantiation with PNF support | TBD | TBD | TBD |
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
...