Versions Compared

Old Version 1

changes.mady.by.user xu ran

Saved on

compared with

New Version Current

changes.mady.by.user xu ran

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

The content of this template is expected to be fill out for M1 Release Planning Milestone.

Info

Use the "Copy" and "Move" options (available under the ..., top right of this page) to duplicate this template into your project wiki.
Use the Wiki to document the release plan. Don't provide PowerPoint.
Use as much diagrams and flow charts as you need, directly in the wiki, to convey your message.



Overview

Project Name

Enter the name of the project

Usecase UIEnter the name of the release you are targeting to deliverMatureEither Incubation, Core, Mature. Refer to ONAP Charter, section 3.3 Project Lifecycle for further information
Target Release NameIstanbul
Project Lifecycle StateMature

Participating Company 

China Mobile, Huawei, China Telecom
List the company participating in this release. At least 3-4 organizations, including an operator are recommended.

Scope

What is this release trying to address?

Describe the problem being solved by this release

The Usecase-UI Istanbul release has following primary objectives:

  1. IBN module:  Usecase UI will support kinds of service of intent management, such as creation, delete, deactivationvia adding a new “Intent-based Services” page
  2. IBN module:  Usecase UI will support the monitoring of intent-instance via adding a new monitoring page
  3. E2E Slicing: Usecase UI will support the binding of intent-instance and slicing business ID


2. UUI enhancement and new  features:

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.

  1. 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
  2. UUI FE Component  for supporting Intent-instance Monitoring and Intent management enhancement
  3. 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.

Epics


Jira Legacy
serverSystem Jira
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
maximumIssues20
jqlQueryproject = USECASEUI AND issuetype = Epic AND fixVersion = "Istanbul Release"
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176


Stories


Jira Legacy
serverSystem Jira
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
maximumIssues20
jqlQueryproject = USECASEUI AND issuetype = Story AND fixVersion = "Istanbul Release"
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176



Longer term roadmap

Indicate at a high level the longer term roadmap. This is to put things into the big perspective.

Release Deliverables

Indicate the outcome (Executable, Source Code, Library, API description, Tool, Documentation, Release Note, etc) of this release.

Deliverable Name

Deliverable Description

To fill outTo fill out

Source CodeSource code for all UUI components
Maven ArtifactsMaven Artifacts for all UUI components
Docker ContainersDocker container  associated with UUI components
DocumentationUUI 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.

Sub-components are repositories and are consolidated in a single centralized place. Edit the Release Components name for your project in the centralized page.

Architecture

High level architecture diagram

At that stage within the Release, the team is expected to provide more Architecture details describing how the functional modules are interacting.

Indicate where your project fit within the ONAP Architecture diagram.

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.


Image Added

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.

Image Added

Platform Maturity

Please fill out the centralized wiki page: 

...

Honolulu Release Platform Maturity


  • API Incoming Dependencies

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.



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)

To fill outHigh level description of the APIDate for which the API is reviewed and agreedTo fill outLink toward the detailed API description

  • 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 APIAPI 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 APIAPI for NS instantiation and termination


DataLake APIAPI for FCAPS (VNF/VM monitoring)


External APIAPI 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.

Gaps identified

Impact

To fill outTo fill out

  • Known Defects and Issues

Please refer to Frankfurt Defect Status


  • Risks

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).

Please update any risk on the centralized wiki page - Frankfurt Risks

  • Resources

Fill out the Resources Committed to the Release centralized page.

  • Release Milestone

The milestones are defined at the Release Level and all the supporting project agreed to comply with these dates.

  • Team Internal Milestone

This section is optional and may be used to document internal milestones within a project team or multiple project teams. For instance, in the case the team has made agreement with other team to deliver some artifacts on a certain date that are not in the release milestone, it is erecommended to provide these agreements and dates in this section.

It is not expected to have a detailed project plan.

Date

Project

Deliverable

To fill outTo fill outTo fill out

  • Documentation, Training

Please update the following centralized wiki: Frankfurt Documentation

That includes

  • Team contributions to the specific document related to he project (Config guide, installation guide...).
  • Team contributions to the overall Release Documentation and training asset
  • High level list of documentation, training and tutorials necessary to understand the release capabilities, configuration and operation.
  • Documentation includes items such as:
    • Installation instructions
    • Configuration instructions
    • Developer guide
    • End User guide
    • Admin guide
    • ...

Note

The Documentation project will provide the Documentation Tool Chain to edit, configure, store and publish all Documentation asset.


Other Information

  • Vendor Neutral

If this project is coming from an existing proprietary codebase, ensure that all proprietary trademarks, logos, product names, etc. have been removed. All ONAP deliverables must comply with this rule and be agnostic of any proprietary symbols.

  • Free and Open Source Software

FOSS activities are critical to the delivery of the whole ONAP initiative. The information may not be fully available at Release Planning, however to avoid late refactoring, it is critical to accomplish this task as early as possible.
List all third party Free and Open Source Software used within the release and provide License type (BSD, MIT, Apache, GNU GPL,... ).
In the case non Apache License are found inform immediately the TSC and the Release Manager and document your reasoning on why you believe we can use a non Apache version 2 license.

Each project must edit its project table available at Project FOSS.


Charter Compliance

The project team comply with the ONAP Charter.