...
Table of Contents | ||
---|---|---|
|
Overview
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 |
Scope
What is this release trying to address?
The Dublin Casablanca Release will be focusing on the following areas:
- Platform Maturity (i.e., S3P items)
- Resiliency
- Level 2 - regression from Beijing, plug close gap on DB resiliency.
- DB Resiliency was a limitation in Beijing due to the Active/Standby nature of MySQL. MariaDB w/Galera provides an active-active clustered configuration, which will support local fail-over.
- Scalability
- Level 1 will be a regression run on Dublin Casablanca release - anticipate this to be test only
- Stability
- Level 1 will be a regression run on Dublin Casablanca release - anticipate this to be test only
- Level 2 requirement is expected to be covered by the Integration team.
- Security
- Level 1 definition has changed in DublinCasablanca. Not clear we are achieve Level 1
- Address outstanding items related to CII Passing Badge:
- Clearing Critical and Medium Nexus IQ Security alerts to the extent possible
- Addressing 2 other security related items from Passing Badge related to encryption
- Secure DMaaP topics (Dependency on DMaaP project) - Stretch Goal, not currently committed for Dublin Casablanca
- DMaaP indicated delivery would be Sept, plus
- DMaaP story is still not written to enable APPC to assess impact at this stage.
- Resiliency
- Support new LCM action Reboot and various other enhancements to existing LCM actions (Tracked under Epic: APPC-899)
- Documentation updates for DublinCasablanca, such as, but not limited to:
- LCM API Guide
- Release Notes
- Code Coverage for UI of the Monitoring PagesCDT (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-id
of 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 - Commitment based on support from ATT resources
- 5G/PNF
- ConfigScaleOut - Partially supported
Use Cases
Describe the use case this release is targeted for (better if reference to customer use case).
...
SO will contribute to the following use cases as part of the functional requirements.
- Scaling Use Case -
- SO will support retrieving the data to be configured from AAI. This however has a dependency on SO to pass the
vf-module-id
of 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.
- 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
- VNFM SOL003 adapter support : Resources commitment from Ericsson
- SOL005 adapter support : Resources from Verizon (under discussion).
- CCVPN extension : Resources commitment from CMCC, VDF, ZTE.
- Change Management Extension : Commitment based on support from ATT resources.
- PNF extension : Resource commitment from Nokia.
- BBS : Resources under discussion
- .
- HPA extension for the other existing usecases : Support from Intel
- PNF resources orchestration 5G Support
Minimum Viable Product
Same as was defined for Beijing with the adding of CDT.
...
Jira server ONAP JIRA columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution maximumIssues 20 jqlQuery project=so and issuetype in (epic) and fixVersion = "Dublin Casablanca Release" serverId 425b2b0a-557c-3c0c-b515-579789cceedb
...
Deliverable Name | Deliverable Description | Deliverable Location |
---|---|---|
SO Docker Images | Executable | Docker image available on nexus3 |
MariaDB Docker Image | Executable | Docker image available on nexus3 |
SO Libs | Jar files | Available on nexus |
Deployment Scripts | Chef recipes used to configure the Docker containers. | found on SO Git repositories |
Sub-Components
onap/so/api-handler-infra
onap/so/bpmn-infra
onap/so/catalog-db-adapter
onap/so/openstack-adapter
onap/so/request-db-adapter
onap/so/sdc-controller
onap/so/sdnc-adapter
onap/so/so-monitoring
onap/so/vfc-adapter
NA
ONAP 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.
...
API Name | API Description | API Definition Date | API Delivery date | API Definition link (i.e.swagger) | |||
---|---|---|---|---|---|---|---|
SDC | APIs for distribute service models | Defined in Amsterdam | Delivered in Amsterdam | Interfaces Link | |||
A&AI | APIs for inventory data | Defined in Amsterdam | Delivered in Amsterdam | Interfaces Link | |||
SDN-C | APIs for network controller | Defined in Amsterdam | Delivered in Amsterdam | Interfaces Link | |||
APP-C | APIs for application controller | Defined in Amsterdam | Delivered in Amsterdam | Interfaces Link | |||
VF-C | APIs for Network Service | Defined in Amsterdam | Delivered in Amsterdam | Interfaces Link | |||
Multi-VIM | APIs for Multi-VIM | Defined in Amsterdam | Delivered in Amsterdam | Interfaces Link | |||
OOF | APIs for placement and homing | Defined in Beijing | Delivered in Beijing | Interfaces Link | |||
DCAE | For PNF instantiation initialisation message from DCAE over DMaap | Defined in Casablanca | Delivered in Casablanca | Interfaces Link | TBD | TBD |
API Outgoing Dependencies
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 |
...
Jira | ||||||||||
---|---|---|---|---|---|---|---|---|---|---|
|
...
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 |
---|---|---|
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
...