Versions Compared

Old Version 15

changes.mady.by.user cl664y@att.com

Saved on

compared with

New Version Current

changes.mady.by.user Adrian OSullivan

Saved on

Key

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


Table of Contents
outlinetrue

Overview

...

What is this release trying to address

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


    ScopePriorityCommitter LeadResources CommittedEpic Dependencies 
    TSC Must haveSupport Global Requirement and selected Best practices as per Honolulu Release Requirements and Honolulu Impact View per Componenthigh
    Adrian OSullivan

    Adrian O'Sullivan, Priyadharshini B Rakesh Girija Ramesan Nair

    Jira Legacy
    serverSystem Jira
    columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
    serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
    keyEXTAPI-533



  • Stretch Goal in association with E2E Network Slicing - 
    Jira Legacy
    serverSystem Jira
    serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
    keyEXTAPI-450
    - EXT-API impacts for support of TMF 628 APIs for KPI monitoring and 
    Jira Legacy
    serverSystem Jira
    serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
    keyREQ-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

...

  • 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
    serverSystem Jira
    serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
    keyEXTAPI-450
     

...

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

Jira LegacyserverSystem

Epics

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

...

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 APIPerformance 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

...

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.

Area

Actual Level

Targeted Level for current Release

How, Evidences

Comments

Performance0202
  • 0 -- none
  • 1 – baseline performance criteria identified and measured
  • 2 & 3 – performance improvement plans created & implemented
Stability0202
  • 0 – none
  • 1 – 72 hours component level soak w/random transactions
  • 2 – 72 hours platform level soak w/random transactions
  • 3 – 6 months track record of reduced defect rate
Resiliency0202
  • 0 – none
  • 1 – manual failure and recovery (< 30 minutes)
  • 2 – automated detection and recovery (single site)
  • 3 – automated detection and recovery (geo redundancy)
Security01+1+
  • 0 – none
  • 1 – CII Passing badge + 50% Test Coverage
  • 2 – CII Silver badge; internal communication encrypted; role-based access control and authorization for all calls
  • 3 – CII Gold
Scalability0101
  • 0 – no ability to scale
  • 1 – single site horizontal scaling
  • 2 – geographic scaling
  • 3 – scaling across multiple ONAP instances
Manageability0101
  • 1 – single logging system across components; instantiation in < 1 hour
  • 2 – ability to upgrade a single component; tracing across components; externalized configuration management
Usability0202
  • 1 – user guide; deployment documentation; API documentation
  • 2 – UI consistency; usability testing; tutorial documentation

...

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 Name

API Description

API Definition Date

API Delivery date

API Definition link (i.e.swagger)

SDC: Catalog APIExposes Service CatalogTBDTBDhttps://wikidocs.onap.org/display/DW/SDC+APIprojects/onap-externalapi-nbi/en/latest/consumedapis/consumedapis.html
SO: Service Instantiation APIRequests for Service InstantiationTBDTBDTBDhttps://docs.onap.org/projects/onap-externalapi-nbi/en/latest/consumedapis/consumedapis.html
AAI: Service Inventory APIQuery for Service InventoryTBDTBDhttps://docs.onap.org/projects/onap-externalapi-nbi/en/latest/consumedapis/consumedapis.html
DMaaP: Events APIQuery for AAI_EVENTS and SDC Distribution EventsTBDTBDDistribution EventsTBDTBDhttps://docs.onap.org/projects/onap-externalapi-nbi/en/latest/consumedapis/consumedapis.html

API Outgoing Dependencies

...

ExtAPI: Service

API Name

API Description

API Definition Date

API Delivery date

API Definition link (i.e.swagger)

ExtAPI: Service CatalogExternal Service Catalog APITBDTBDTBD

i.e.swagger)

ExtAPI: Service CatalogExternal Service Catalog APITBDTBDhttps://docs.onap.org/projects/onap-externalapi-nbi/en/latest/_downloads/ca979e4ad0e48c22d6e62f403b4b0c7c/swagger.json
ExtAPI: Service OrderingExternal Service Ordering APITBDTBDTBDhttps://docs.onap.org/projects/onap-externalapi-nbi/en/latest/_downloads/9450323ada78d8f7eeb360141ed68b63/swagger.json
ExtAPI: Service InventoryExternal Service Inventory APITBDTBDTBDhttps://docs.onap.org/projects/onap-externalapi-nbi/en/latest/_downloads/58f285f89bb1416ea0a0ceec1e325800/swagger.json

Third Party Products Dependencies

...

Risk identified

Mitigation Plan

Contingency Plan

TBDTBDTBD

Resources

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

...

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

...

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

...

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


Charter Compliance

The project team comply with the ONAP Charter.