Table of Contents
outline true

Overview

Scope

What is this release trying to address

• Support TSC must have ONAP requirements mandatory Global Requirements Honolulu Release Requirementsimplements as much TSC must feature as possible
  

  
  

  Scope	Priority	Committer Lead	Resources Committed	Epic	Dependencies
  TSC Must haveSupport Global Requirement and selected Best practices as per Honolulu Release Requirements and Honolulu Impact View per Component	high	Adrian OSullivan	Adrian O'Sullivan, Priyadharshini B Rakesh Girija Ramesan Nair	Jira Legacy server System Jira columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution serverId 4733707d-2057-3a0f-ae5e-4fd8aff50176 key EXTAPI-533

  
  

• Stretch Goal in association with E2E Network Slicing - 

  Jira Legacy
  server System Jira serverId 4733707d-2057-3a0f-ae5e-4fd8aff50176 key EXTAPI-450

  - EXT-API impacts for support of TMF 628 APIs for KPI monitoring and 

  Jira Legacy
  server System Jira serverId 4733707d-2057-3a0f-ae5e-4fd8aff50176 key REQ-440

  • Slides presented covering the NBI requirement for E2E External API Framework: 5GNetworkSlicing_ExtAPI_20200610_v1.0.pptx
    • Specification & modelling work on (modernized) TMF 628 for "On Demand" PM collection and future mapping to DES API's

Use Cases

The existing use cases should still be supported ( BBS, CCVPN ) in the Honolulu Release as the APIs are built to be non use case specific.

...

The stretch goal impact is for the catering Performance Management and the possible inclusion of a subset of a new updated TMF 628 APIspecification and design work to support Performance Management API, via an enhanced TMF 628 worked with MEF  - Dependant on release of appropriate swagger from the SDOs

• Slides presented covering the NBI requirement for E2E External API Framework: 5GNetworkSlicing_ExtAPI_20200610_v1.0.pptx
• Specification aspects only of the mapping to be covered during Honolulu Release within Honolulu Release   

  Jira Legacy
  server System Jira serverId 4733707d-2057-3a0f-ae5e-4fd8aff50176 key EXTAPI-450

   

Platform Maturity

 Platform Maturity (i.e., S3P items)  Honolulu Release Platform Maturity 

Minimum Viable Product

• Documentation of User Stories; Use Cases and Interactions (e.g., swagger ); Data Models (e.g., JSON); Interface Profiles and Functional Definition; 
• ONAP Component Mapping and Functional Analysis; 
• Code contribution for External API Framework functionality.

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.

18 Non functionals :

10 - TSC MUST HAVE (please indicate where you plan to contribute)

...

Requirement Epic

...

TSC Priority

...

EXTAPI Epic(s) and/or EXTAPI Story(ies)

...

Committed Contributors

1 - TSC PRIORITY 2 Continuity (please indicate where you plan to contribute)

7- TSC PRIORITY 3 PTL GO/NO GO (please indicate where you plan to contribute)

Epics

Epics

...

Longer term Roadmap

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

...

• Service Provider controls aspects of the Service within the Partner domain (on behalf of the Customer) by requesting changes to dynamic parameters as permitted by service policies.
• Service Provider queries state of the Service.
• Service Provider requests change to administrative state or permitted attributes of a Service.
• Service Provider request creation of connectivity between two Service Interfaces as permitted by established business arrangement.
• Service Provider request instantiation of functional service components as permitted by established business arrangement.
• Service Provider queries the Partner for detailed information related to Services provided by the Partner to the Service Provider.
• Service Provider receives Service specific event notifications (e.g., Service Problem Alerts) from the Partner.
• Service Provider receives Service specific performance information from the Partner.
• Service Provider request Service related test initiation and receive test results from the Partner.

Release Deliverables

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

Sub-Components

List all sub-components part of this release.
Activities related to sub-component must be in sync with the overall release.

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

1. External API Agent:
   1. Core Agent Functionality
   2. Service Catalog API
   3. Service Ordering API
   4. Service Inventory API
   5. Performance Mgmt API

ONAP Dependencies

List the other ONAP projects your depends on.

Dependent on APIs from SDC, SO, DMaaP , AAI and DESAAI 

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.

...

Anyone reading this section should have a good understanding of all the interacting modules.

Platform Maturity

Refering to CII Badging Security Program and Platform Maturity Requirements, fill out the table below by indicating the actual level , the targeted level for the current release and the evidences on how you plan to achieve the targeted level.

API Incoming 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.

Prior to the delivery date, it is a good practice to organize an API review with the API consumers.

API Outgoing Dependencies

API this release is delivering to other releases.

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

...

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.

...

• BSS/OSS retrieves Service Models
• BSS/OSS orders a new Service.
• BSS/OSS subscribes to Service order tracking status notifications.
• BSS/OSS retrieves Service Inventory

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.

Known Defects and Issues

Provide a link toward the list of all known project bugs.

...

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

Resources

Fill out the Resources Committed to the Release centralized page.Please see the INFO.yaml files associated with each repo as the authoritative sources of information. https://gerrit.onap.org/r/admin/repos/q/filter:externalapi

Release Milestone

The milestones are defined at the Release LevelPlanning: Honolulu 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.

...

Documentation, Training

• Highlight the team contributions to the specific document related to he project (Config guide, installation guide...).
• Highlight the 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
  • ...

...

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

https://docs.onap.readthedocs.ioorg/en/latest/submodules/externalapi/nbi.git/docsprojects/onap-externalapi-nbi/en/latest/index.htmlhtml#master-index

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.