The content of this template is expected to be fill out for M1 Release Planning Milestone.
...
Describe the problem being solved by this release
The Usecase-UI Istanbul release has following primary objectives:
- IBN module: Usecase UI will support kinds of service of intent management, such as creation, delete, deactivationvia adding a new intent management page
- IBN module: Usecase UI will support the monitoring of intent-instance via adding a new monirtoring page
- E2E Slicing: Usecase UI will support the binding of intent-instance and slicing business ID
2. UUI enhancement and new features:
- Remove GPLv3 from the dockers built by the ONAP community
USECASEUI-494 - usecase UI dockers contain GPLv3 开放
- Upgrade postgresql
- PACKAGES UPGRADES IN DIRECT DEPENDENCIES
USECASEUI-574 - PACKAGES UPGRADES IN DIRECT DEPENDENCIES FOR ISTANBUL 开放
- Add test code for UUI
Requirements
Describe the use case this release is targeted for (better if reference to customer requirements).
Smart Intent Guarantee based on IBN - R9 Intent Instance
Minimum Viable Product
...
Usecase-UI will include the necessary subcomponents supporting the primary objectives: supporting the use cases and meeting platform maturity goals.
- UUI BE Component for supporting Intent-instance Monitoring and Intent management enhancement, as well as supporting an api for binding the intend-instance and business id
- UUI FE Component for supporting Intent-instance Monitoring and Intent management enhancement
- UUI NLP Component for supporting the smart operator intent translation based on IBN
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.
...
Indicate the outcome (Executable, Source Code, Library, API description, Tool, Documentation, Release Note, etc) of this release.
Deliverable Name | Deliverable Description |
|---|
| Source Code | Source code for all UUI components |
| Maven Artifacts | Maven Artifacts for all UUI components |
| Docker Containers | Docker container associated with UUI components |
| Documentation | UUI detailed documentation |
Sub-Components
List all sub-components part of this release.
Activities related to sub-components must be in sync with the overall release.
...
Anyone reading this section should have a good understanding of all the interacting modules.
Block and sequence diagrams showing relation within the project as well as relation with external components are expected.
Anyone reading this section should have a good understanding of all the interacting modules.
Platform Maturity
Please fill out the centralized wiki page: Frankfurt Honolulu Release Platform Maturity
API Incoming Dependencies
...
Prior to the delivery date, it is a good practice to organize an API review with the API consumers.
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) |
API Outgoing Dependencies
API this project is delivering to other projects.
...
API Name
...
API Description
...
API Definition Date
...
API Delivery date
...
API Definition link (i.e.swagger)
...
Third Party Products Dependencies
Third Party Products mean products that are mandatory to provide services for your components. Development of new functionality in third party product may or not be expected.
List the Third Party Products (OpenStack, ODL, RabbitMQ, ElasticSearch,Crystal Reports, ...).
...
Name
...
Description
...
Version
...
In case there are specific dependencies (Centos 7 vs Ubuntu 16. Etc.) list them as well.
Testing and Integration Plans
Provide a description of the testing activities (unit test, functional test, automation,...) that will be performed by the team within the scope of this release.
...
| Portal Platform API | API for integration of portal applications | |||
Catalog API (SDC) | API to read the NS and VNF Catalog | |||
SO API(Modeling) | API for NS instantiation and termination | |||
MSB API | API for registration and use of micro-services bus | Microservice Bus API Documentation | ||
A&AI API | API for getting inventory and image management | AAI REST API Documentation | ||
| VF-C API | API for NS instantiation and termination | |||
| DataLake API | API for FCAPS (VNF/VM monitoring) | |||
| External API | API for external data |
API Outgoing Dependencies
None
Third Party Products Dependencies
None
Testing and Integration Plans
Usecase UI Honolulu- Functional Test Cases
Gaps
This section is used to document a limitation on a functionality or platform support. We are currently aware of this limitation and it will be delivered in a future Release.
List identified release gaps (if any), and its impact.
...