...
| 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 | Amdocs, AT&T, China Mobile, Huawei, Intel, Nokia, Orange, Tech Mahindra, ZTE |
...
- Support new LCM action Reboot and various other enhancements to existing LCM actions (Tracked under Epic: APPC-899)
- Documentation updates for Casablanca, such as, but not limited to:
- LCM API Guide
- Release Notes
- Code Coverage for CDT (Javascript) - TBD, no commitment at this stage
- Use Cases
- ConfigScaleOut - Partially supported
- Support Retrieval of configuration data from AAI instead of having SO pass configuration data in payload - (investigate if we can we reuse the named query)
- Dependency on SO to pass the
vf-module-idof the vDNS instance that must be added.
- Dependency on SO to pass the
- No commitment on Controller Type since requirements are still unclear.
- Support Retrieval of configuration data from AAI instead of having SO pass configuration data in payload - (investigate if we can we reuse the named query)
- Change Management - No Commitment based on support from ATT resources
- 5G/PNF - No Commitment (although APPC is listed as an impacted component, there does not appear to be any immediate requirement for Casablanca. Items noted are longer road map items)
- ConfigScaleOut - Partially supported
Use Cases
Describe the use case this release is targeted for (better if reference to customer use case).
The use cases supported in Beijing release will continue to be supported as part of regression assuming all other components do likewise.CCVPN
APPC SO will contribute partially to the following use cases as part of the functional requirements.
- Scaling Use Case -
- APPC SO will support retrieving the data to be configured from AAI. This however has a dependency on SO to pass the
vf-module-idof the vDNS that was instantiated.. - Discussions around how Controller Type will be handled are still too vague and unclear, so no commitment can be made to support this. APPC will continue to support APPC and SDNC via the Client Library as was done in Beijing.
- APPC SO will support retrieving the data to be configured from AAI. This however has a dependency on SO to pass the
- CCVPN Use Case
- Support the Cross Domain Cross Llink Virtual Private Network between 2 ONAP instances.
- HPA extension for the other existing usecases
- PNF resources orchestration
Minimum Viable Product
Same as was defined for Beijing with the adding of CDT.
...
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 this release is delivering to other releases.
...
API Name
...
API Description
...
API Definition Date
...
API Delivery date
...
| API Name | API Description | API Definition Date | API Delivery date | API Definition link (i.e.swagger) |
|---|---|---|---|---|
| Create service instance | Create a service instance | Defined in Amsterdam | Delivered in Amsterdam | Interfaces Link |
| Delete service instance | Delete a service instance | Defined in Amsterdam | Delivered in Amsterdam | Interfaces Link |
| Create vnf instance | Create vnf instance | Defined in Amsterdam | Delivered in Amsterdam | Interfaces Link |
| Delete vnf instance | Delete vnf instance | Defined in Amsterdam | Delivered in Amsterdam | Interfaces Link |
| Create vf module instance | Create vf module instance | Defined in Amsterdam | Delivered in Amsterdam | Interfaces Link |
| Delete vf module instance | Delete vf module instance | Defined in Amsterdam | Delivered in Amsterdam | Interfaces Link |
| Create volume group instance | Create volume group instance | Defined in Amsterdam | Delivered in Amsterdam | Interfaces Link |
| Delete volume group instance | Delete volume group instance | Defined in Amsterdam | Delivered in Amsterdam | Interfaces Link |
| Create network instance | Create network instance | Defined in Amsterdam | Delivered in Amsterdam | Interfaces Link |
| Delete network instance | Delete network instance | Defined in Amsterdam | Delivered in Amsterdam | Interfaces Link |
| Get orchestration requests | Get orchestration requests | Defined in Amsterdam | Delivered in Amsterdam | Interfaces Link |
| Get a specific orchestration request | Get a specific orchestration request | Defined in Amsterdam | Delivered in Amsterdam | Interfaces Link |
| Create E2E service | Create E2E service | Defined in Amsterdam | Delivered in Amsterdam | Interfaces Link |
| Delete E2E service | Delete E2E service | Defined in Amsterdam | Delivered in Amsterdam | Interfaces Link |
| Query progress status | Query progress status | Defined in Amsterdam | Delivered in Amsterdam | Interfaces Link |
...
| Risk identified | Mitigation Plan | Contingency Plan |
|---|---|---|
| Code merge from ATT Ecomp 1806 | started to work in a separate branch and will be merged to the main branch on basic testing completed | Drop the related features and move ahead |
| SO dependency to delivery needed data to support the ScaleOut use case? | ||
| DMaaP support of Secure Topics? | ||
Resources
Fill out the Resources Committed to the Release centralized page.
Release Milestone
...